Skip to main content
Create Free Account

Contractor Management Software: 10 Questions and 10 Bad Answers

Contractor management software should be judged on one thing above all: whether it can tell you that a named person, on a named site, today, is cleared for the work they are about to do. Most systems verify the company instead. The ten questions that decide a purchase cover worker-level clearance, site-specific requirements, expiry chasing, document verification, gate access, inductions, evidence, integration, subcontractor adoption, and the total cost your suppliers absorb.

enterprise
Three colleagues working at laptops around one desk in a bright office, with a bar chart on the wall screen behind them and pens and notes spread across the table

Create your own Contractor Management Portal in minutes.

Create a Free Account

I sit in these conversations most weeks, usually with a safety lead, a procurement manager, and somebody from IT who was told to be there. By the third demo the room can recite the same feature list back to me, because every vendor in this category has more or less the same one. The feature list is not where the decision lives.

What decides it is a much smaller set of questions, and what comes back when you ask them properly. Below are the ten I would ask if I were buying rather than selling, in the order I would ask them, each with the answer that should slow you down. Nothing here requires you to buy from us, and the second-last section is about when you should not buy anything at all.

The Category’s Real Divide Is Company Versus Worker.

Most contractor management systems verify the company. They collect the ABN, the public liability certificate, the workers compensation policy, and the safety management plan, then tell you the supplier is approved to work for you. That is real work, it matters, and prequalification is where it belongs. It is also not what an incident involves.

An incident involves a person. A named apprentice, on a named site, on a Tuesday morning, holding a ticket that lapsed in March. Section 19 of the Work Health and Safety Act 2011 (Qld), which carries the model law’s wording, requires a business to ensure, so far as is reasonably practicable, the health and safety of ‘workers engaged, or caused to be engaged by the person’ and ‘workers whose activities in carrying out work are influenced or directed by the person’.12 Section 7 defines a worker to include a contractor, a subcontractor, an employee of a contractor or subcontractor, and a labour hire employee assigned into your business.1 The duty reaches the individual, not the entity that sent the invoice.

Safe Work Australia’s Key Work Health and Safety Statistics Australia 2025, released 16 October 2025, records 188 workers killed by traumatic injury in 2024, and 146,700 serious workers compensation claims involving at least a week off work in 2023-24.3 Not one of those was a company. Nor can you contract the exposure away: Safe Work Australia’s guidance for duty holders says plainly that WHS duties cannot be transferred, and that it is not acceptable to assume another duty holder will take responsibility for a health and safety issue.4

So the first question is the one that splits the category. Can this system tell me that this person, on this site, today, is cleared for the work they are about to do.

The answer that should worry you: “The contractor confirms their workers meet your requirements.” That is your supplier marking their own homework. Instead, ask the vendor to open one worker’s record in the demo and show you what that person holds, when each item expires, which sites they are cleared for, and who approved each document. If that takes longer than a minute, you are looking at a company register with a worker tab bolted on. ComplyFlow’s workforce compliance module is built the other way round: each document lands with a named approver who opens it, checks the dates, and approves or rejects it with a comment that goes back to the uploader.5

Requirements Have to Differ by Site, Work Type, and Client.

A single global checklist is the commonest reason a rollout collapses. A traffic controller on a live corridor needs a different set of things from a cleaner in a back-of-house plant room. A hospital adds a police check. A construction site with twelve trades on it needs twelve different lists, not one list twelve people ignore.

Ask whether a single site can carry a requirement the rest of the account does not, whether your own administrators can add it without raising a ticket, and what happens to the people already assigned to that site when you do.

The answer that should worry you: “We can configure that for you.” Configuration you cannot perform yourself becomes a support request every time a site opens, a client changes their rules, or a new work type appears. In ComplyFlow, a site can be assigned its own document and training requirements from a dropdown, and assigning one immediately moves the profiles of everyone on that site to documents pending.6

Expiry Chasing Should Not Be Anyone’s Daily Job.

Compliance rarely fails at onboarding. It fails eleven months later, when a licence quietly lapses and nobody notices because the person who used to run the spreadsheet has moved teams.

Ask what happens on the day a document expires if no human being does anything: who is told, how many times, and what happens to that worker’s status and their access to site at the moment it lapses.

The answer that should worry you: “You can run a report.” A report is something a person has to remember to run, and the whole failure mode here is a person not remembering. ComplyFlow sets an expiry period on a training course and moves the record when it lapses,7 and the document report can be filtered by what expires within a set number of days and exported to CSV.8 The filter is useful. The status changing by itself is the part that matters.

Somebody Has to Check the Certificate, and It Should Not Be the Contractor.

An uploaded PDF is a picture of a claim. Somebody has to decide whether the claim is true, and the system should make that cheap rather than pretend it is unnecessary.

The regulators are specific about what checking means. SafeWork NSW tells employers to check workers’ licences regularly, and to confirm that the licence has not expired, includes the relevant classes, and carries the correct photo and name; NSW also runs a public register of high risk work, asbestos, and demolition licence holders and general construction induction card holders, showing status, expiry, conditions, and penalty notices.9 For nationally recognised training, a worker’s USI VET transcript is a government-authenticated record of what they have completed, and the Unique Student Identifier office is clear that it does not replace the certificate: where you doubt a training document, you contact the registered training organisation that issued it.10

Ask who reviews an upload, what they are shown, what happens on rejection, and whether the reason is kept.

The answer that should worry you: “It is automatic.” Nothing currently reads a certificate and knows it is real. In ComplyFlow a reviewer downloads the document, checks the expiry date the contractor typed in and corrects it if it is wrong, and approves or rejects with a comment; rejected documents stay visible in the entity’s history rather than disappearing.5 That is a person, leaving a trail.

A Clearance That Does Not Reach the Gate Is Not a Clearance.

A cleared worker in a database and a turnstile that admits anyone are two systems having a private disagreement, and the gate wins every time.

Ask how the gate finds out. A phone scan, a turnstile, a kiosk, a supervisor’s printed list. Then ask the two questions vendors prefer you did not: what happens when the network drops, and who can override the check, with the override recorded against their name.

The answer that should worry you: “The supervisor checks the portal.” That is a login, on a phone, at a boom gate, at 6am, in the rain, with eleven people waiting behind. It will not survive the second week. ComplyFlow’s site access puts the answer on the worker’s own card: scan the QR code with any phone camera and their record opens with their categories, training, and documents, a green tick when every assigned requirement is current and a red cross when something is outstanding.11

Inductions Are Per Site and Per Company, and Most Systems Do One.

A worker inducted for your Sydney depot is not inducted for your Perth one, and a worker who did your corporate induction has not been walked through the confined spaces on level three. Both facts have to live in the same record, or somebody starts keeping a second one.

Ask whether a worker can be cleared for one site and not another, whether the system knows the difference at sign-in, and whether an expired induction pulls the clearance or merely turns something amber on a dashboard nobody opens.

The answer that should worry you: “Everyone does the same induction.” Then it is too long for the cleaner and too thin for the crew entering a vessel, which in practice means it is both at once. ComplyFlow’s training and induction module assigns courses by worker category, by site or project, individually, in bulk, or through rules that fire automatically when conditions are met, and it records training completed elsewhere, including in person, alongside the online courses.7

Run the Evidence Test Before You Sign.

Here is the single test I would insist on doing inside the demo rather than discovering afterwards. Ask the vendor to show you how you would produce, in a morning, the evidence that a named person was cleared to do a named task on a named site on a named date eighteen months ago.

That request is not hypothetical and it is not a dashboard. It arrives after an incident, from a regulator, an insurer, or a lawyer, and what it wants is a defensible record with dates, approvers, and versions attached.

The answer that should worry you: “We can build you a custom report.” Custom means a vendor ticket, a queue, and usually a fee, at the worst possible moment to be waiting on any of the three. ComplyFlow’s document report covers every record for the life of the account, including documents that were rejected, expired, or never uploaded, filtered by entity, approver, project, company, category, and review date, and exported to CSV.8

Decide Who Owns the Contractor Master Record.

Your finance system already holds a supplier list and will not surrender it. Your HR system holds your own people. The compliance platform holds the workers nobody else has ever held. Two systems that each believe they own the supplier list will disagree quietly, and you will find out on a Friday.

Ask which system is the source of truth for which field, which way each field flows, whether it is a live interface or a nightly file, and what happens to a record when the other system deletes it.

The answer that should worry you: “We integrate with everything.” Ask for the endpoint list, and for the name of a customer who has done it in your stack. ComplyFlow’s integrations read through scoped API tokens: every scope is read-only, a token can only reach the modules you tick, and it expires on a term you set, up to a maximum of a year.12

Subcontractor Adoption Is Where the Money Is Lost.

This is the question buyers underweight most, and the one I would press hardest. The people who decide whether this system works do not work for you. They are a two-person electrical outfit, a labour hire crew, and a bloke with a ute and a subcontract, and they have no reason to log into anything.

Safe Work Australia’s fact sheet on WHS duties in a contractual chain describes exactly this arrangement: multiple contractors and subcontractors engaged on the same project or work matter, where an individual contractor can be both a business in their own right and a worker.13 That individual is your end user, whether or not anybody at the demo said so.

Ask who onboards them and on what device, what the support hours are for somebody who is not the vendor’s paying customer, what share of onboarding the vendor does rather than your team, and whether a document can be lodged on a worker’s behalf when they will not do it themselves. ComplyFlow lets a staff member upload on behalf of a worker, entering the valid-from and expiry dates at the time of upload.14

The answer that should worry you: “We will send them an email with a link.” That is how a rollout stalls one tier below your direct suppliers, which is the tier most of the people on your sites sit in.

Price the Whole Cost, Including the Time You Do Not Pay For.

Ask for the licence fee, the implementation, the integration work, the training, the support tier, and what the price does when you add a site or double your contractor count. Then ask the question almost nobody asks: what does this cost my subcontractors.

A subcontractor working for eight head contractors can be asked to keep eight profiles, upload the same white card eight times, sit eight inductions covering much the same ground, and under some commercial models pay eight separate fees. None of that appears in your business case. All of it comes back as slower mobilisation, higher quoted rates, and the quiet decision by a good subcontractor to work for somebody easier instead.

Ask whether a document approved for one client can count towards the next, and whether a worker keeps one profile across every client they serve.

The answer that should worry you: silence, or “that is their cost, not ours”. It is your cost. It arrives later and wearing a different name.

When a Platform Is Not the Answer.

If you engage the same four contractors, all long-standing, all on one site, and nobody new starts for months, a shared folder and a calendar reminder will hold, and you should not let anybody tell you otherwise. The overhead of a platform is real: somebody has to own the configuration, somebody has to approve documents, and your suppliers have to be walked through it.

Software earns its place when at least one of these is true. You cannot name, right now, who is on site. Your requirements differ by site or by work type. Your contractor base turns over. Or you have already been asked for evidence and could not produce it quickly. If none of them is true, buy the smallest thing that fixes the one that will become true first, or buy nothing this year and revisit it.

A system nobody uses is worse than a spreadsheet, because a spreadsheet has never told anyone that everything is fine.

The Two Answers That Sort a Shortlist.

If you take nothing else from this, take two questions. Can it tell you that a named person, on a named site, is cleared today. And will your subcontractors actually use it.

A system that does the first and fails the second will be beautifully accurate about a workforce that never finished onboarding. A system that does the second and fails the first will be popular right up until the morning somebody asks you to prove something. If you want to see how the two are meant to fit together, book a demo and make us run the evidence test in front of you. If you are buying for a construction program specifically, choosing construction safety management software covers the principal contractor duties and the site-by-site questions that sit underneath this list.

Contact our sales team to see how ComplyFlow can simplify compliance and keep your business safe.

Contact SalesCalculate Pricing