Why Use Software Instead of Manual Prequalification Templates

Prequalification is not a form. It is a claim, made in the present tense, that a business you are about to engage is insured today, holds the right licences today, and is sending people who are qualified today.

A template cannot make that claim. It can only record that somebody once said so. I have been asked about this more often than any other question since 2009, usually by someone with a serviceable spreadsheet who wants to know why it is not enough. Here is the honest answer, including the part where the spreadsheet is fine.

A Template Is a Photograph, and Prequalification Is a Claim About Today.

Fill in a prequalification template on 3 March and you have a photograph of 3 March. The public liability policy was current on 3 March. The certificates had not expired on 3 March. The four workers listed on it were the four workers who turned up.

Every one of those facts has its own clock, and the document holds none of them. The certificate of currency expires. The high risk work licence expires. The white card stops counting. The worker leaves and is replaced by somebody the form has never heard of. The template is not wrong, exactly. It is describing a day that has passed, and it goes on describing it with complete confidence.

That confidence is the risk, not the missing data. A folder of completed prequalification forms reads exactly like a live register. Nothing on the page tells you how old it is, so the older it gets the more reassuring it looks.

What the Law Asks For Does Not Stop at the Form.

The duty is continuing, and that is the whole argument in one sentence.

Section 19 of the model Work Health and Safety Act requires a business to ensure, so far as is reasonably practicable, the health and safety of workers it engages or causes to be engaged, and of workers whose activities it influences or directs, while those workers are at work in the business or undertaking.¹ Not at the point of engagement. While they are at work. Section 46 then requires every duty holder over the same matter to consult, co-operate and co-ordinate activities with the others, which is also not a once-a-year event.¹ Safe Work Australia puts the consequence plainly in its construction guidance: a person cannot eliminate their health and safety duties by sub-contracting all, or elements of, the work to another business.³

The specific obligations follow the same pattern. A safe work method statement must be reviewed and, as necessary, revised whenever the relevant control measures are revised; it must be kept until the high risk construction work it relates to is finished, and for at least 2 years after a notifiable incident; and a copy has to stay readily accessible to the workers doing the work.² A principal contractor on a construction project must take all reasonable steps to obtain that statement before the high risk work starts, which is per job, not per supplier.² And nobody may be directed or allowed to carry out construction work unless they have completed general construction induction training, which stops counting if the worker has not carried out construction work in the preceding 2 years.²

Read those together and the pattern is obvious. Not one of them is satisfied by a form completed at onboarding and filed.

Expiry Is the Thing a Template Cannot Enforce.

A template can hold an expiry date. It cannot do anything on that date, and the distance between recording an expiry and acting on one is where almost every failure in this field lives.

Acting on an expiry means six things: knowing the date is approaching, knowing who owns it, asking the right person, receiving the replacement, checking the replacement is the right document, and updating the record. A spreadsheet does exactly one of those, and only if somebody opens it.

This is what configured requirements are actually for. ComplyFlow bundles documents, training and forms once, and the invitations, reminders and renewals run from the bundle rather than from anybody’s memory.⁴ On the supplier’s side the same thing shows up as a dashboard they can filter by what has expired and what is expiring soon, across every one of their clients at once.⁵

The diagnostic question is short. If a subcontractor’s public liability policy lapsed tomorrow, how would you find out? If the honest answer is “when somebody next opens the folder”, that is not a control. It is a filing convention.

The Gap Between the Approved List and Who Is on Site Today.

This is the failure that is hardest to see and the most expensive when it lands.

An approved supplier list answers one question: may this company work for us. It does not answer the question that matters at seven in the morning, which is whether the individual standing at the gate is cleared for the job they have come to do. A template answers the first and is routinely treated as though it answered the second.

The gap opens on its own, without anybody doing anything wrong. Your subcontractor subcontracts a tier down. An apprentice joins the crew. Agency labour covers a sick fitter. The scope grows to include work that turns out to be high risk construction work, which was not in scope when the form was completed. The approved list has not changed. The site has.

Scale is worth stating, because this is the point at which people ask whether it is proportionate. Construction alone recorded 17,600 serious workers compensation claims in the preliminary 2023-24 figures, 12.0% of the national total, on top of 37 of Australia’s 188 work-related traumatic injury deaths in 2024.⁶ The gap between the list and the gate is not an administrative detail. It is where people get hurt, and it is why worker-level compliance has to be a live record rather than an attachment to a supplier file.

Version Drift, When Every Site Keeps Its Own Copy.

Here is the failure nobody writes about, and the one I would look for first in any business still running on templates.

The template lives on a shared drive. Someone at the second site copies it and adds two questions after an incident. A third site strips out a question a contractor complained about. Within a year there are five versions in circulation and no reliable way to say which is current.

The symptoms are recognisable. The same contractor is asked for different things at different sites. A requirement exists at one location because of something that happened at another. A document accepted at one gate is rejected at the next, and the contractor concludes the whole thing is arbitrary.

What makes drift worse than inconsistency is that a distributed template cannot be repaired. Changing the master does nothing at all to the copies, and nothing to the paperwork already collected under them. A configured requirement set changes once for everybody, and when it is saved ComplyFlow re-checks every supplier and worker the set touches, so people who were clear become outstanding until they provide the new item.⁴ That reach backwards into records you have already collected is the thing a template structurally cannot do.

Where a Template Still Works, and the Point It Stops.

A template is genuinely fine, and I would not sell anybody software they do not need. It holds up when you have one site, a handful of regular subcontractors you know by name, one person who owns compliance and carries the dates, and work that does not involve high risk construction work.

The point at which it stops is knowable, and it is not a contractor count. Two things break it.

The second site breaks it, because the moment two places each keep a copy, drift starts and nobody notices for a year. And the first requirement with a clock on it that somebody other than its owner has to act on breaks it, because the compliance owner is now a reminder service rather than a reviewer, and reminder services fail quietly in busy weeks.

Cross either line and the choice is no longer between a template and software. What changes is what happens after the questions are answered. In ComplyFlow the questionnaire is issued to the supplier, the answers are reviewed, the document requests then appear on the supplier’s dashboard, and what they upload is reviewed by your team, by the ComplyFlow safety team, or both, before the requirement is met.⁷ On selected questions the supplier can also run an AI review of their own document against your criteria before they submit it, which returns a score and named gaps; it does not replace the human review, does not block submission, and the reviewer still makes the decision.⁸

The template is not the enemy. It is a good way to write down what you want and a poor way to know whether you are still getting it. Keep the questions and hand the dates to something that will act on them. If you are building that for the first time, how to set up your own contractor portal covers the order to do it in; if you already have a system and it is not working, how to transform your contractor management system covers what to migrate and what to leave behind. Either way, the test is the same: whether the answer to “can they start” is a fact about this morning or a memory of March.