From a spreadsheet to verified contractors, in about a week.

Import or sync your contractors via an integration

You send whatever you already have — a spreadsheet, an export from your management software, or just a list of trade names. We import it and build the register from it, so nobody starts from an empty system and nobody re-types anything.

Where your platform connects, there is no file at all. Urbanise Strata syncs automatically: supplier records flow into TradeVerify, and licence and insurance status is written back against the supplier in Urbanise, without anyone exporting or uploading anything. Other supported platforms update by file transfer, which a person still starts — which is which is set out in the integrations table.

We set the requirements by trade

We maintain what each trade type is expected to hold — the licence class, and the cover that trade is normally asked for. Fire safety is not the same as cleaning, and the configuration reflects that. You don't build the matrix.

What TradeVerify does not do is advise on whether the cover is adequate for a given scheme or a given building. That judgement, and the decision to engage a contractor, stay with your firm.

We onboard and chase the contractors

TradeVerify contacts each contractor, guides them through submission, and follows up until it is done. Your team is not in that loop at any point. It is free for the contractor, which is the single biggest reason completion rates hold up rather than stalling at the halfway mark.

There is no account to create and nothing to install: the contractor gets a single-use, time-limited link to a page listing exactly what is outstanding, including the specific licence or policy reference that has expired. Every file they upload is virus-scanned on arrival.

Licences are checked against the issuing registry

A licence is confirmed against the government register that issued it, rather than read off a PDF the contractor supplied. We search on the ABN, the registered entity name and every trading name the register holds against it, then match what comes back to the business before it counts for anything — an exact match on the licence number, the ABN or the registered name.

A match we cannot stand behind does not pass. It is held short of verified and raised for a person to resolve, because a shared trading name is precisely how one business's licence ends up on another's file.

Insurance certificates are checked against the requirements set in step two. Each one is read automatically, then checked against the record: the named insured has to be the contractor's registered entity, the cover has to meet the requirement for their trade, and the policy has to be current. All three line up and it verifies; anything short of that stops and comes to our team. The document is classified first either way, so a tax invoice, a quote or a renewal notice is never mistaken for proof that cover is in force.

Licensing is State and Territory based, so the register we ask depends on where the licence was issued — the full table is below, naming the authority in each jurisdiction. The mechanism is set out in full on the platform page.

Status flows into your management software

Compliance status is written back into the system your team already works in, through a direct integration. There is no second system to check and no weekly export to reconcile. See the integrations.

Every check is recorded

Each verification is timestamped and shows where the answer came from — the register that issued the licence, or the document the contractor supplied — and the record is kept. Automated checks are marked as automated, so the record distinguishes what a system concluded from what a person confirmed.

When an insurer, an owner, a committee or a regulator asks for evidence of due diligence, it already exists — you are not reconstructing it from an inbox six months later. It comes out as a compliance summary across your contractors, a report of everyone with something expired, or an export in the format your management software expects.