Article Vendors & commercial discipline ~8 minutes
Insurance certificates and licences often arrive in a flurry before award — then sit untouched until someone asks at the gate or an auditor asks mid-claim. By then the certificate may have expired, and the only copy is in a zip named `docs_final_USE_THIS`.
That pattern is not bad luck. It is what happens when compliance packs are treated as memorabilia of award day rather than time-sensitive credentials that keep earning their place while plant remains on site.
Clients, insurers, and HSE expectations vary, but the operational test does not: can you show, today, that the companies doing high-risk work still hold what your policy said they must hold?
What good compliance practice looks like
Compliance packs are time-sensitive credentials, not souvenirs.
In practice:
- Required documents are named before award pressure peaks — so award week is verification, not invention.
- Expiry is monitored, not discovered by accident after mobilisation.
- Evidence attaches to the company (and flows to jobs) with clear ownership.
- Gaps block risky work as your policy requires — or at least become visible early enough for an honest decision.
- Bulk uploads do not erase review — drafts and states still matter.
- Entity names on certificates match the registry company — not a near-miss trading name from a quote header.
Procurement and HSE plans often list categories: insurance, licences, systems certifications, trade competencies at company level. Site translation: if expiry cannot surface before the gate or the claims email, you chose surprise.
Good practice still allows temporary waivers where policy permits. Waivers that are invisible, indefinite, and unowned are not waivers — they are silent exemptions.
Enterprise baselines help packages stop reinventing the wishlist. If every job invents its own certificate cocktail, vendors drown in duplicate uploads and your organisation still cannot answer a single assurance question. Define the core pack once; let packages add risk-specific extras with a reason.
Review still matters after bulk upload. A zip full of PDFs is not assurance until someone confirms entity match, dates, and coverage types against what the policy asked for.
Where projects slip
- “We have it somewhere” culture across drives and inboxes.
- Expiry ignored until a stop-work, a claim, or an auditor’s question.
- Different packs demanded by different projects with no enterprise baseline — duplicate effort and conflicting answers.
- Certificates accepted without checking the entity name matches the registry.
- Award-week collectors who never hand ownership to someone who watches renewals.
- Soft copies of expired documents still looking “official” because the PDF has a logo.
The cost is not only process embarrassment. Soft compliance invites mobilisation of risk under a false green light — and weakens your position when an insurer asks what you knew when.
How Cynilo supports the practice
Cynilo lets compliance live with the vendor company record and remain visible when that company is onboarded to projects — so certificates are part of the commercial system, not souvenir PDFs.
Registry-first identity (Registry first — then the job) makes entity matching possible. Living contracts (Contracts are living records) explain why certain packs were required. Help How-tos cover capture. Leaders use Learn to insist: expired compliance that nobody tracked is a choice, not bad luck.
What good looks like in a week
On a programme that expires honestly:
- Upcoming expiries are visible before plant needs them.
- High-risk trades cannot quietly mobilise on stale paper where policy forbids it.
- Package teams inherit company compliance rather than re-collecting the same certificate four times under four filenames.
- Entity mismatches are caught at intake, not at claim time.
- Temporary exceptions have owners and end dates.
The weekly test: pick three high-risk vendors on site. Can you show current required documents without opening personal email? If not, souvenir culture still owns the drawer.
Gate and mobilisation should inherit the same truth procurement trusts. When HSE blocks at the fence using different files than commercial filed at award, the vendor learns which theatre to play. One compliance story beats two competing green lights.
A short story from a high-risk plant hire
A principal mobilised a specialist plant supplier mid-programme on the strength of certificates collected at award three packages earlier. Nobody owned renewal. The public liability period lapsed during a busy concrete window. Work continued until a neighbour incident triggered insurer questions. The certificates folder still looked full — and fully expired.
Aftermath was predictable: scramble renewals, uncomfortable client updates, and a rule that compliance expiry sits beside mobilisation checks, not in an archive folder. The cost of watching renewals would have been trivial beside the week spent proving what should have been a boring green status.
Closing
Company identity and living contracts set who and under what instrument. Compliance asks whether the papers that justified access to risk still hold. Performance memory is the last article in this spine — so next season’s selection is not folklore.
Previous: Contracts are living records
Next in the series: Performance needs a memory — rehiring from evidence, not hallway talk.
In the product: Help → How-to → Vendors
Topics:
Modules in Cynilo:
In the product: open Help → How-to when you need specific actions in Cynilo. Learn stays on industry practice.
Previous: Contracts that stay alive