Supplier requirements under every procurement policy, filed and reviewed.
Government procurement policies, from the NSW Procurement Policy Framework to the Queensland Procurement Policy and Commonwealth procurement rules, set requirements that flow down to every trade partner (subcontractor) and supplier. GovAssure asks each party for those records at the frequency you set, has them reviewed and keeps coverage visible for the life of the contract.
How it works.
Insurances as Documents
Ask each package for its insurance certificates and policies as documents, as often as the contract sets.
Licences by Register
A register asks one question of every worker assigned to a package, or of every package, so one filing covers the crew.
Checked Against Your List
A CSV lookup question checks an answer against a list you upload, and flags the values you name as a problem.
Policies as Frameworks
Adopt a procurement policy as a framework, and the documents and targets it asks for are added to the project.
Your Own Standards Too
Organisation administrators build their own frameworks in the Policies & Frameworks library, each change a new version.
Reviewed Up the Chain
Each package’s Documents & Forms section is accepted or sent back before anything above it is shown.
One question. Every worker on the package.
A register asks a single question of each employee assigned to the package, or of each package. Its rows build themselves from who is assigned, so nobody is left off.
- Complete when every eligible row has its answer
- Someone who leaves stays listed as not eligible
- Register For Employees or Packages, fixed once saved
Checked against your list. Flagged when it fails.
A CSV lookup question searches a list you upload, such as licence numbers and their status. The package picks its match, and any value you name as a problem is flagged wherever the answer shows.
- Exact matches first, up to 20 results
- No match is recorded as an answer, not refused
- Other organisations search your list only through your question
Filed by each package. Reviewed by the package above.
Each package files its registers and documents in its monthly report. The package above accepts the section or sends it back, and nothing is shown further up until it is accepted.
- Group submissions by work package or by month
- Open a package to see every period it owed
- Accepted periods are locked
Government procurement policies, set up in one step.
Adopt a framework and the documents and targets its policy asks for are added to the project. Build your own for an internal standard, and every project that adopts it gets the same requirements.
Adoption
- A Project Takes a Copy
- It Keeps the Version It Took
- Archiving Never Breaks a Project
Versions
- Changed Targets Make a New Version
- A Rename Reaches Every Project
- New Versions Reach New Adoptions
Authoring
- Built by Organisation Administrators
- Readable by Everyone in the Organisation
- Each Name Used Once
Every supplier requirement, accounted for.
Procurement policies flow requirements down to every trade partner. Catchment asks each package for its records as often as the requirement sets, has them reviewed, and keeps each one against its package and period.
Owed by Frequency
Each document and register is owed again every cycle, and shows Overdue when missed.
Reviewed Up the Chain
Nothing is shown above a package until every package between has accepted it.
Checked Against a List
Lookup answers are matched against the list you uploaded, with problem values flagged.
Locked Once Accepted
An accepted period refuses any change to its files or answers.
Why it matters.
A lapsed insurance certificate or an unsigned policy acknowledgement is usually found after something goes wrong. Catchment collects licences, insurances and policy acknowledgements at the frequency each requirement sets, has them reviewed, and shows coverage across every package in one view, with what is overdue on screen.
Compliance Teams
See coverage across the whole chain at a glance.
Trade Partners and Suppliers
Upload from any device, or pick a file already in your Document Register.
Clients
See acknowledgements and current licences.
Licences, insurances and policies, in practice.
When are licences and insurances checked?+
When the package files them in its monthly report, as often as the requirement sets. A reviewer then accepts the section or sends it back.
What is the difference between a document and a register?+
A document asks for a file. A register asks one question of every employee assigned to the package, or of every package, and is complete when every row is answered.
What happens when a worker leaves a package?+
Someone already answered for stays on the register as a not-eligible row. A worker assigned later reopens the register while its period is still being worked on.
Can we check licence numbers against a list?+
Yes, with a CSV lookup question. Upload the list, choose the column to search and the column to return, and name the values that count as a problem.
Which procurement policies are in the framework library?+
Commonwealth policies such as the Modern Slavery Act 2018, the Indigenous Procurement Policy and the Buy Australian Plan, policies from NSW, Queensland, Victoria, South Australia, Tasmania, the ACT and the Northern Territory, and Green Star rating tools.
Can we add our own standard?+
Yes. An organisation administrator builds a framework in Policies & Frameworks. Changing its targets makes a new version, and each project keeps the version it adopted.
Can a register be changed to a document later?+
No. A register’s type, level and Register For are fixed once saved. Add a new one instead.
See policy and licence tracking on a real project.
30 minutes with our team, on live project data.
Book a Demo →