Fixed quote after a free call

Subcontractor compliance and certificate of insurance tracking, kept current

Before a subcontractor starts on site you need current insurance, licences, safety documents and, in the UK, a CIS verification. We build a workflow that collects those documents through one secure link, records expiry dates, chases anything missing or expiring, flags subcontractors who are not ready before their start date and keeps a full audit trail. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why subcontractor compliance slips mid-project

Subcontractor compliance usually lives in a spreadsheet and an inbox full of PDFs. Certificates expire mid-project, nobody notices, and the first time anyone checks is when there is an incident or a client audit.

The documents also vary by job and country: certificates of insurance with the right limits and additional insured wording in the US, licences by state and trade, safety plans and method statements, and in the UK a CIS verification with HMRC before the first payment.

What we build

What our subcontractor compliance tracking includes

One onboarding link

Subcontractors upload insurance, licences, safety documents and company details through one secure form per project.

Expiry tracking

Expiry dates recorded from each document and checked by staff, with a tracker per subcontractor and project.

Automatic chasers

Reminders to subcontractors weeks before anything expires, and again if documents are missing.

Site readiness flags

A list before each start date showing who is approved, who is missing what, and who must not start.

CIS step for UK firms

A task for an authorised person to verify new subcontractors with HMRC, with the result recorded.

Audit trail

Every upload, check, approval and reminder logged for clients and insurers.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Subcontractor invited

    A new or returning subcontractor gets the onboarding link for the project.

  2. 02 Automated

    Documents collected

    Uploads are logged and expiry dates are read for staff to confirm.

  3. 03 Automated

    Gaps chased

    Missing and expiring items trigger reminders to the subcontractor.

  4. 04 PM or estimator review

    Staff check

    The compliance coordinator checks limits, wording and dates and records approval.

  5. 05 Site manager or director decides

    Start approval

    Whether a subcontractor may start is decided by the project manager.

How it behaves

How COI and compliance tracking behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What subcontractors see

  • One secure upload link per project
  • A clear list of what is still missing
  • Reminders weeks before anything expires

What the coordinator and PM see

  • A tracker per subcontractor and project
  • A site readiness list before each start date
  • An audit trail for clients and insurers

What the automation does

  • Logs uploads and reads expiry dates for checking
  • Chases missing and expiring documents
  • Never approves a document by itself

Edge cases and fallbacks

Certificate is a poor scan
Flagged for the coordinator to read; no date is guessed.
Insurance expires mid-project
Reminders start weeks before, and the PM is alerted if it lapses.
Subcontractor uses a new company name
Flagged so details are checked and, in the UK, re-verified.
Storage or n8n outage
Uploads retry and the coordinator is alerted; nothing is marked approved.

Architecture

Subcontractor compliance tracking at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Subcontractor Onboarding link n8n workflow Log and remind Date extraction From certificates Tracker Per sub, per job Coordinator Checks and approves Project manager Start decision
  • Input
  • Logic and services
  • AI step
  • Data
  • People

How it flows

  1. 1 Each subcontractor gets one onboarding link per project and uploads their documents.
  2. 2 The workflow logs every upload and reads expiry dates for staff to confirm.
  3. 3 The tracker shows what is current, missing or expiring, and chasers go out automatically.
  4. 4 The coordinator checks and approves documents, and the project manager decides who may start.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Subcontractor compliance & COI tracking project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Documents required per trade and region, current tracking, insurance requirements and who approves.

  2. 02

    Design

    2 to 3 days

    Onboarding form, tracker fields, reminder timing and site readiness rules.

  3. 03

    Build

    1 to 2 weeks

    Form, storage, date extraction, tracker, chasers and readiness list.

  4. 04

    Data migration

    About 1 week

    Existing subcontractor documents loaded and dates checked with your team.

  5. 05

    Launch

    1 to 2 days

    Send links to active subcontractors and train the coordinator.

  6. 06

    Support

    Ongoing

    New document types, rule changes and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n A secure form tool with file upload SharePoint, Google Drive or Procore documents Procore REST API (company directory) Claude or OpenAI for reading expiry dates Gmail or Microsoft 365

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Document rules, tracker design and readiness rules.

    $200 – $400

  • Build

    Upload form, date extraction, tracker and chasers.

    $500 – $1,300

  • Integrations

    Storage, project system directory and email.

    $150 – $400

  • Testing and data migration

    QA and loading existing subcontractor documents.

    $100 – $250

  • Launch and training

    Subcontractor roll-out and coordinator training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. If you already use a compliance platform, we connect around it. Storage, AI usage and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Form tool and storage: Your form provider's plan and existing document storage.
  • AI model usage: Billed by the provider per use; reading certificates is usually a small monthly amount.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: verify subcontractors under CIS

Contractors must verify a new subcontractor with HMRC before paying them, and re-verify anyone not on a CIS return in the current or last two tax years.

Source: www.gov.uk

UK: CDM 2015 principal contractor duties

The principal contractor plans, manages, monitors and coordinates health and safety in the construction phase, so safety documents are collected for competent review, never approved automatically.

Source: www.hse.gov.uk

EU and UK: personal data in documents

Licences and training cards contain personal data, so storage is restricted and kept only as long as the project and insurers require.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Subcontractor compliance questions questions, answered.

Typically insurance certificates with the limits and wording your contract requires, trade licences, safety plans or method statements, training records and company details, plus a CIS verification in the UK. Your contract and local rules set the list; we automate collecting and tracking it.

It can read dates and limits from a certificate and compare them with your requirements, then flag mismatches. A coordinator still checks and approves, because wording and endorsements matter.

For many small and mid-sized contractors, yes. If you already use a dedicated platform, we connect around it and automate the gaps such as site readiness flags.

No. They get a secure link per project to upload documents and see what is still missing.

It flags who is not approved before their start date and alerts the project manager. Deciding who starts is the project manager's call.

Subcontractors with expired or missing documents, days before start that compliance is complete and time spent chasing documents.

Free 20-minute call

Want this for your construction firm?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call