The Missing Subcontractor Certificate That Holds Up Everyone Else
Updated: Sep 4
The job can be finished, the invoice can be ready, and everyone can still be waiting on one PDF that nobody can find.
G’day, it’s Dazza. On a busy building or maintenance job, paperwork rarely feels urgent while the tools are moving. A subcontractor has the certificate. Someone in the office has the insurance document. The licence copy was emailed months ago. The test sheet is apparently “coming this afternoon”. Then handover, payment, site access or the next stage depends on that document — and suddenly everybody is chasing it.
One missing document can stop people who had nothing to do with losing it
That is what makes subcontractor paperwork such a frustrating little problem. The electrician may have completed their work. The plumber may be finished. The supervisor may be ready to close the job. But if a required certificate, licence record, insurance document, test result or other agreed handover item is missing, the delay can spread well beyond the person who was supposed to provide it.
The exact documents needed depend on the work, the contract, the project, the trade and the relevant requirements. This is not legal advice about which certificates are mandatory on a particular Australian job. The practical problem is simpler: when a document has been identified as required, somebody needs to know who owes it, when it is due and whether it has actually arrived.
“I asked him for it” is not a tracking system
Most document chasing starts reasonably enough. A supervisor sends a text. The office emails the subcontractor. Someone mentions it on site. The subcontractor says they will send it tonight.
Three days later, nobody is quite sure whether it arrived. One person assumes the office has it. The office assumes the supervisor received it. The subcontractor thinks they already sent it to somebody else. So another round of calls begins.
The business often has plenty of communication. What it does not have is one clear answer to three questions: What are we waiting for? Who are we waiting on? What happens if it still has not arrived by the next check?
Start the chase before the document becomes urgent
The worst time to discover a missing certificate is five minutes before somebody needs the handover pack. If a document will be required at completion, record that requirement when the subcontractor is engaged or when the relevant work is assigned.
A useful record does not need to become a giant compliance database. It might simply identify the subcontractor, the job, the document expected, the due point, the person responsible for following it up and its current status.
That gives the chase somewhere to start. More importantly, it gives it somewhere to stop. Once the correct document has arrived and been accepted for the purpose it was requested for, the follow-up can be closed instead of continuing because nobody told the other person.
Chasing and verifying are different jobs
There is another distinction worth keeping clear. A system can help chase a document without pretending it can decide whether that document is valid, legally sufficient or technically correct.
Receiving a file called insurance.pdf does not prove the policy covers the required work. Receiving a licence image does not automatically prove the licence is current or appropriate. A certificate may still need review by the person or process responsible for checking it.
So the useful workflow is: request it, know whether it arrived, keep the evidence of the request and receipt, and then send it to the proper verification step where one is required. Do not turn “file received” into “compliance approved” by accident.
The reminder should get firmer without becoming ridiculous
Not every missing document needs a phone call every morning. A sensible chase can start with a clear request, follow with a reminder if the due point passes, and escalate to the right person if the document is genuinely holding up work, payment or handover.
The important part is visibility. If the subcontractor replies, “I’ll have it tomorrow,” record that next expectation. If they send the wrong document, the case is not finished just because an attachment arrived. If the requirement no longer applies, close it rather than leaving a permanent red warning on somebody’s screen.
Good chasing is persistent enough to prevent things disappearing, but not so noisy that everyone learns to ignore it.
This is exactly the sort of small admin job software should quietly handle
Subcontractor document chasing is one of the workflows I’m working through with Dazza. The aim is not to build another giant construction management platform. It is to make a very specific loose end visible: this document is required, this person owes it, this is when we last asked, and this is what needs to happen next.
That workflow is still in development. There is not a finished Dazza subcontractor-document-chasing product I’m asking anyone to use today, and any future workflow needs to keep the boundary between chasing a document and verifying it very clear.
It also connects to the broader follow-up problem I mentioned in the service-reminder article. Whether you are waiting on a customer reply, a quote decision or a subcontractor certificate, the useful idea is much the same: something should keep an eye on the loose end so a busy person does not have to hold it in their head all week.
The goal is not more paperwork — it is less chasing
A required document will always need somebody to provide it. What should not be necessary is three supervisors, two office staff and the business owner all independently remembering to ask for the same thing.
Record what is needed before it becomes urgent. Make the owner of the next action visible. Keep the chase factual. Separate receipt from verification. And once the right document is in the right place, close the loop.
That is a very small process. But when one missing certificate is holding up everyone else, small processes can save a surprising amount of time.
Comments