Shutdowns, inductions, prestarts, permits, plant currency and cost against scope, held in one system instead of six spreadsheets and a tub of paperwork.
A shut gets agreed months out and almost everything real happens in the last three weeks. Scope moves, work packs get added, half the labour has never set foot on that site, and somebody has to confirm every one of them holds a current induction, a valid medical and the right tickets before the bus leaves Mackay. Most enquiries about custom software for mining contractors in Australia start in that fortnight — from the person who lost a Sunday rebuilding a resource plan in Excel because the scope changed again.
This page is for the businesses that service mines, not the ones that own them. Mechanical and E&I contractors, scaffolders and riggers, labour hire, NDT and inspection outfits, vac trucks, camp and transport providers. Your problem is not a mine plan. It is holding scope, people, compliance and cost together across sites you do not control, under access rules written by someone else.
Drawn AI's founders came out of mining operations, and Queensland is one of our two bases alongside Melbourne. We have no published client work in resources and will not imply otherwise. What we bring is people who know what happens when a verification of competency lapses mid-shut, and why the gate is the worst possible place to find a paperwork problem.
We build custom systems onto the software you already run — accounting, rostering, maintenance, and the client contractor portal you did not choose and cannot change. Replacing all of that is rarely the right call. Connecting it, and putting the coordination layer on top, usually is.
The scope list, work packs, T-minus schedule and labour histogram in one place, so a scope change updates the resource plan rather than requiring somebody to rebuild it. Day crew and night crew, planned against actual, with growth work logged as it is found.
One record per person: induction, medical, high risk work licence, VOCs and site-specific authorisations, each with an expiry the system watches. Tickets arrive as phone photos and PDFs, so document AI can read the details off them and flag anything that will not match the record.
Who is approved for which site, on what access, and what has to be true before they get on the plane or the bus. Flights, camp rooms and DIDO travel tied to the roster the shut is planned against, so cancelling a person cancels their bed and their seat too.
Even time, 14/7, 8/6 — whatever you run, visible against hours actually worked, so a supervisor sees the person who has quietly rolled into a fourth night shift. On any day of a shut, the count of who is on site, travelling or on days off should take a second, not a phone call.
Prestarts, take 5s, JHAs, permits and isolations captured on a phone at the point of work — offline, because these sites have no coverage. Plant, lifting gear and pressure equipment held per asset with certification and inspection dates. This is the same ground as our risk and compliance systems and field and mobile app work.
Labour, plant hire, consumables and subcontractors booked to cost codes on the work pack, not the job as a whole. Day works and variations raised on the deck the day they happen. A shut that will lose money usually shows it by day four. Most contractors find out at the invoice.
We spend time with the people who carry the shut — the planner, the HSE coordinator, whoever does mobilisation, and a supervisor who will be on the tools. Not a workshop with head office. The crew decides whether a system gets used or worked around.
We trace every place a person, an asset or an hour is entered today. This is where a business usually finds the same worker keyed into four systems, and one record the client asks for that nobody ever captured.
We agree what the system holds and what it escalates. Expiry rules get designed deliberately — 90, 60, 30 and 7 days to a named role, then upward — and T-minus milestones get owners rather than being a date on a Gantt chart.
We connect it to what you run: Xero or MYOB, your rostering or payroll, your maintenance system, SharePoint, and the client-side contractor platforms your site access already depends on. Client data we host sits in Australian regions.
After the first shut we go through what the data showed — where scope grew, which crews lost hours to access, which forms people skipped. A control everyone bypasses is a design problem, and it is cheaper to fix once you can see it in the operational dashboards.
Mostly for contractors and service providers. Owner-operator systems are a different market, served by platforms tied to the mine's own asset and planning stack. The contractor side — mobilising people onto sites you do not control, under someone else's rules, at short notice — is far less well served.
No. If a site requires Pegasus, Rapid Global, Avetta or a client-built portal for access, that stays. What we build is your own record: every worker's currency in one place, warning you what is about to lapse, and giving your admin team what they need to feed those portals without rekeying it each time.
That is the default assumption, not an add-on. Forms are offline-first — the app writes to the device, a full shift can be completed with no signal, and it syncs when coverage returns. Records keep the time and location of capture rather than the time of sync, so the trail reflects when the work actually happened.
No. Queensland resources work carries site access, competency and record-keeping expectations that sit well above general workplace requirements, enforced through audit and inspection. What applies to your operation, and whether you meet it, is a matter for your HSE people and your advisers. We build the system that holds the evidence they specify. We do not give legal or compliance advice.
We work on a subscription: monthly billing, a three-month minimum term, thirty days' notice to cancel. Not fixed-price project work and not hourly. What moves the figure is how many sites and crews you run, how many forms are captured in the field, and how many existing systems it connects to. Email outreach@drawnai.app and we will talk through scope.
Do not try to land a whole system inside a shut window. Build and roll out between shuts, starting with one thing — usually competency currency or prestart capture — run alongside the current process for a fortnight. The heaviest demand on your people is during discovery, because they hold the knowledge of how mobilisation works.
A first conversation costs nothing and usually ends with a clearer idea of what is worth building — sometimes that answer is “not yet”, and we will say so.
No lock-in templates. Built around you.