Certifyd Contract Activation

Turn the contract into the compliance plan.

We read the complete client contract stack and produce a source-linked register of what the client, your organisation and every affected worker must do.

Human-reviewed before you act. Redacted documents welcome. No anonymous contract upload.

Governing stackCompiled
MSAMSA-2026-041
SOWSOW-2026-007
AMDAMD-2026-001
POLPSP-4.2
SCHUK / US
32 source-linked requirements
ClientDependencies
SupplierControls
PersonRequirements

Illustrative output from a synthetic benchmark. Counts show the worked example, not a customer contract.

Source linkedOwner separatedPerson specificChange aware

A signed contract is not an operating process.

The obligations sit across the MSA, statement of work, schedules, policies and later amendments. Someone still has to decide which requirements belong to the client, the supplier or each person.

If that interpretation is wrong, teams chase unnecessary documents, miss real controls or discover the gap when a worker is due to start.

See how the same clause changes the work.

This guided demo uses a fictional financial-services contract stack built to test precedence, applicability and ownership.

Source documents2 in view
MSA-2026-041SOW-2026-007

MSA 3.1 to 3.3 and SOW 4.1 to 4.4

Supplier conducts its allocated checks and maintains status. Client assigns category and access, provides Client-delivered training and makes final access decisions. Client obligations must not be assigned to Supplier personnel.
Fictional benchmarkSource retained
Activation outputHuman review required

One workflow, three accountable parties

SupplierMSA 3.1

Run and evidence the allocated checks

Supplier owns lawful notices, checks, evidence collection and current compliance status.

ClientMSA 3.2; SOW 4

Assign access and make the clearance decision

The Client owns category, access profile, training availability and final access approval.

PersonMSA 7 and 8

Complete declarations and applicable training

Each person completes the required forms and courses, but does not own Client approval.

QuestionSOW 4.4

Track the dependency without creating a false task

The Client clearance can block readiness, but it must not appear as an overdue worker action.

A working register, not another contract summary.

The pack is designed for the people who must activate a new client, configure the compliance process and prove what was done later.

  • 01A source-linked responsibility register
  • 02Organisation and personnel compliance matrix
  • 03Missing-document and ambiguity list
  • 04Owners, dates, evidence and recurrence
  • 05Existing-process gaps
  • 06A first 30-day activation plan

Start with one real contract stack.

01

Share the governing stack

MSA, SOW, schedules, amendments and incorporated policies. Redacted documents are welcome.

02

We compile and review it

Requirements are separated by owner, linked to their source and checked by a person before release.

03

You activate the work

Use the matrix in your current ATS, VMS, portal or compliance process. No platform migration is required.

One stack. One reviewed activation pack.

£750plus VAT
  • Up to five governing documents
  • Up to 150 pages in total
  • Five working day target turnaround
  • One 45-minute review session

We are accepting ten reviewed pilot packs. This is an operational compliance analysis, not legal advice.

Request a reviewed pack

Tell us about the client or contract type. We will confirm fit, scope and a secure transfer method before you share any documents.

Clear limits build better evidence.

Is this legal advice?

No. The pack turns agreed documents into an operational compliance register. Legal interpretation stays with your legal advisers.

Do we need to replace our ATS or VMS?

No. The first pack is delivered as a register and matrix you can use in the systems and processes you already have.

How do we share confidential documents?

Do not attach them to this form. We agree scope, handling and a secure transfer method before any contract is shared.