Fixed quote after a free call

Compliance-focused hiring workflows for recruitment agencies

We build a candidate onboarding workflow that creates the right compliance checklist for each role and country, sends terms and documents for e-signature, chases missing items and references, reminds staff before visas, licences and certificates expire and shows the status of every file at a glance. Trained staff still carry out every eligibility check. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why compliance files hold up start dates

A placement can stall on one missing item: unsigned terms, a reference that never came back, an expired forklift licence or an incomplete eligibility check. Compliance teams chase by email and spreadsheet, and the status of each file lives in someone's head.

The deadlines are real and they differ. US employers must complete Section 2 of Form I-9 within three business days of the hire date. UK employment businesses must agree terms with work-seekers under the Conduct Regulations 2003 and run right to work checks before employment starts. Agency workers in the UK gain equal treatment rights after 12 weeks in the same role with the same hirer.

What we build

What our recruitment compliance automation includes

Checklists by role and country

The checklist is built from the placement type, role and location, so a US nurse, a UK driver and a contract developer each get the right list.

Terms out for e-signature

Agreements and required documents sent through DocuSign or your e-signature tool, with completion written back to the record.

Document and reference chasing

Polite reminders to candidates and referees for missing items, then a flag to compliance.

Expiry reminders

Visas, work permits, licences and certificates tracked with reminders well before they lapse.

Assignment-length alerts

For UK agency workers, a heads-up as a placement approaches the 12-week qualifying period.

File status board

One view of every worker's file: complete, waiting on candidate, waiting on staff or blocked.

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

    Placement agreed

    A placement or offer in the CRM starts the onboarding workflow.

  2. 02 Automated

    Checklist created

    The right checklist for role and country is attached and documents go out for signature.

  3. 03 Automated

    Items chased

    Missing documents and references are chased, with expiries tracked.

  4. 04 Consultant review

    Compliance checks

    Trained staff carry out eligibility checks and verify documents.

  5. 05 Recruiter or director decides

    Clear to start

    Whether a worker may start is decided by the compliance lead or director.

How it behaves

How candidate onboarding behaves

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

What the candidate sees

  • A clear list of what is needed and why
  • Terms to sign on their phone
  • Reminders for missing items and before documents expire

What compliance sees

  • One status board for every worker file
  • Items waiting on staff, ready to check
  • Expiry and 12-week alerts in good time

What the automation does

  • Builds checklists from role and country rules
  • Sends documents for signature and chases gaps
  • Never marks an eligibility check as done by itself

Edge cases and fallbacks

Role not covered by a checklist rule
Flagged to compliance to define before anything is sent.
Referee does not reply
Two reminders, then a task for the consultant to call.
Document expires mid-assignment
Alerts go to compliance and the consultant ahead of the date.
Start date moved earlier
The file is re-checked and gaps escalated at once.
E-signature or CRM outage
Requests are queued and retried, and compliance is alerted.

Architecture

Recruitment compliance and onboarding at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Placement In the CRM n8n workflow Checklist rules E-signature DocuSign Chasers Docs, references File status Per worker Compliance team Checks and sign-off
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 A placement or offer in the CRM starts onboarding.
  2. 2 n8n builds the checklist for the role and country and sends terms for e-signature.
  3. 3 Missing documents and references are chased, and every item updates the file status.
  4. 4 The compliance team carries out eligibility checks and signs the worker off to 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.

Recruitment compliance & candidate onboarding project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Placement types, countries, current checklists, document storage and e-signature setup.

  2. 02

    Design

    2 to 3 days

    Checklist rules, reminder timing, expiry windows and the status board.

  3. 03

    Build

    About 2 weeks

    Checklist engine, e-signature, chasers, expiry tracking and the board.

  4. 04

    Shadow run

    About 1 week

    New placements run through the workflow while compliance keeps the old tracker.

  5. 05

    Launch

    1 to 2 days

    Switch over and train compliance and consultants.

  6. 06

    Support

    Ongoing

    New roles, countries and rule changes.

What it runs on

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

n8n DocuSign eSignature API and Connect webhooks Bullhorn, JobAdder, Loxo or Vincere API SharePoint, Google Drive or your document store Twilio SMS and email Slack or Microsoft Teams alerts

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

    Placement types, checklist rules and the status board.

    $200 – $400

  • Build

    Checklists, chasers, expiry tracking and alerts.

    $500 – $1,300

  • Integrations

    CRM, e-signature, document store and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with the current tracker.

    $100 – $250

  • Launch and training

    Switch-over and compliance team walkthrough.

    $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. E-signature, storage and n8n are billed to you directly. Background screening providers are contracted by you.

Monthly running costs you pay directly

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

  • E-signature: Your DocuSign or e-signature provider's own plan.
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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.

US: Form I-9 timing

Employers must complete Section 2 of Form I-9 within 3 business days of the employee's hire date (the first day of work if the job lasts under 3 days). Staff complete it; the workflow tracks the deadline.

Source: www.uscis.gov

UK: Conduct Regulations 2003

Employment businesses must obtain agreement to terms with work-seekers and confirm information from hirers and about work-seekers under the Conduct of Employment Agencies and Employment Businesses Regulations 2003.

Source: www.legislation.gov.uk

UK: right to work checks

Home Office guidance sets out the checks employers must do before employing someone, and trained staff carry them out.

Source: www.gov.uk

UK: 12-week qualifying period

Under the Agency Workers Regulations 2010, equal treatment rights follow 12 continuous calendar weeks in the same role with the same hirer.

Source: www.legislation.gov.uk

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

Recruitment compliance & candidate onboarding questions, answered.

It sends, chases and tracks the items each worker file needs: terms, documents, references, licences and expiry dates. Staff still carry out and record the checks themselves.

No. It can request documents, track the three-business-day I-9 deadline or the UK pre-employment requirement and remind people, but trained staff do and record the check.

A checklist built from the role and country, terms signed before the start date, documents and references chased on a schedule and one status view. That is what this workflow gives you.

Yes. Checklists can require licences, certifications or vaccination records where the role needs them, with expiry reminders. Which items are required is set by your compliance team.

In your CRM or document store, never in our systems. Access follows your existing permissions.

Days from offer to compliant file, share of starts delayed by missing items, expiries caught before lapse and references returned on time.

Free 20-minute call

Want this for your recruitment agency?

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