Every payment,
under control.

Reads your subcontract and turns it into a checked, cited register you run the whole job from.

Validated on a real NEC4 package Reads JCT & FIDIC — benchmark-proven Synthetic golden-set · 96.8% precision Processed locally Not used to train SOC 2 / ISO — on the roadmap
The problem

Margin doesn’t vanish. It’s disputed away.

The variation nobody wrote down. The notice that missed its time-bar. The proof that isn’t there.

130 hrs
a year chasing overdue payment
BACS
50%
of disputes trace to poor contract admin
KCL 2024
14 months
the average dispute drags on
Arcadis
1 in 3
£ of contract value ends up disputed
HKA CRUX

Senedra captures the proof — before it ever gets here.

How it works

It finds and cites. You decide.

It pulls the terms out of the contract, word for word. A person checks every line before you see it.

01
Subcontract
redacted PDF + amendments
02
Read & cite
every term → clause + page
03
Human review
your team confirms
04
Control register
source-linked, locked
05
Export
Word · Excel

Nothing enters the register unseen. Step 3 isn’t optional — it’s the product.

Solutions

One read. Eight ways to stay in control.

No quote, no row. Everything below is the contract’s own words — quoted and cited. Click any one to see it in the product.

The whole subcontract, itemised

Every term that decides your money — payment, retention, notices, risk — quoted and cited to the clause.

ItemWhat it saysClausePageRiskStatus
Payment mechanism “…due 7 days after assessment…” Y(UK)2 p.12 med Ready
Retention “3%, half released at completion…” X16 p.18 med Ready
Notice / time-bar “…notify within 8 weeks…” 61.3 p.22 high To check
Delay damages “£1,500 per day of delay…” X7 p.24 high To check
Illustrative — payment, retention, notices, obligations & risk, each tied to the contract. Exports to Word & Excel.

Ask in plain English

Ask the way you’d ask a colleague; get back what the contract actually says, quoted and cited.

When does payment become due, and what's the notice deadline?

Payment becomes due 7 days after the assessment date; the related notice must be given within 8 weeks of the event or it is time-barred.

“…payment becomes due 7 days after the assessment date…” · Cl. Y(UK)2 · p.12 “…if the Subcontractor does not notify within 8 weeks…” · Cl. 61.3 · p.22

Answered only from your contract — quoted and page-cited, or it says it isn't covered.

Ask in plain English. Source-grounded answers, never invented.

The onerous terms, worst first

Every clause that shifts risk onto you, grouped and ranked by severity.

high
Pay-when-paid style mechanism
“…payment conditional on receipt from the Employer…” Cl. Y(UK)2 · p.12
high
Short notice / time-bar
“…notify within 8 weeks or the event is not a compensation event…” Cl. 61.3 · p.22
med
Uncapped delay damages
“Delay damages of £1,500 per day…” Cl. X7 · p.24
The clauses that shift risk onto you — grouped, worst first, each quoted and page-cited. A description, not advice.

This contract vs the standard form

See point by point what was amended off the standard NEC4 / JCT / FIDIC position.

PointStandard NEC4 / JCTThis contractClauseVerdict
Payment period Due 7 days after assessment As standard Y(UK)2 · p.12 standard
Retention Half released at completion 3% — half at completion X16 · p.18 standard
Notice / time-bar Notify when the event is known Hard 8-week bar — claim lost if missed 61.3 · p.22 onerous
Delay damages Capped, genuine pre-estimate £1,500 / day, uncapped X7 · p.24 onerous
Fluctuations Price-adjustment option Not included missing
Point by point against the standard form — what's standard, amended, onerous or missing, each clause-cited. A description, not advice.

The deliverable, ready to finish

One click turns the reviewed register into a branded Word + Excel pack, stamped DRAFT.

Commercial Control Diagnostic.docx
Word report
Registers.xlsx
Excel · 10 tabs
diagnostic_pack.zip
Everything, zipped
DRAFT A branded report pack built from the register — review and finish it before sending. Not legal or QS advice.
In the tool now

Every variation, captured and cited

Log each one as it happens — its status and the notice window read from the clause that governs it. In the tool today. Your QS owns the date.

VO-014 · extra fire-stoppingnotify · cl. 61.3
VO-015 · revised riser layoutagreed · £12,400
VO-016 · out-of-hours worksevidence gap

Example rows — the register is in the tool today, cited to the clause, for visibility. Your QS owns the date.

In the tool now

The notice windows your contract sets

The deadlines coming at you and the ones the contractor owes you, surfaced for visibility. In the tool today. Your QS confirms every date.

Compensation event · cl. 61.38-week window
Payment application · Y(UK)2due date read
Pay-less notice · Y(UK)2watch window

Example rows — the calendar is in the tool today; windows are indicative from the cited clause. Not a reliance tool, and not advice on Construction Act deadlines — confirm every statutory date with your QS.

In the tool now

Retention, tracked to its release dates

What’s being held, at what rate, and when each release falls due — read from the retention clause itself. Surfaced for visibility; your QS owns every number.

Retention held · 3% · cl. X16£18,300 held
First release · at Completiondate read
Second release · end of defects periodwatch window

Example rows — the tracker is in the tool today; rates and dates are read from the cited clause, for visibility. Your QS owns every number.

Who it's for

Whoever’s on the subcontract.

It reads the subcontract, not the job title. Every party to one gets the same register.

Subcontractors

“The variation agreed on site that never got written down.”

Capture every variation and notice with the proof, and reach the final account with it already in hand.

Main contractors

“Thirty sub-packages, every one amended differently.”

Control the packages you let: variations, notices and retention across every subcontract, and faster final accounts.

Clients & employers

“The final account lands, and the proof is a filing cabinet.”

Oversight without the spreadsheet: validate the final account, release retention on time, prove compliance.

Why it holds up

Source-grounded. Human-reviewed. Defensible.

Every rule that slows it down is a rule that makes it stand up: in front of your QS, or theirs.

01 · Source

Every item is a quote

No conclusions, no “in our opinion”. Each row is verbatim from your contract, with its page.

02 · Review

A person signs off

AI is fast at finding; people decide. Someone who knows the job signs off every item.

03 · Dispute

It stands up when contested

“Clause 61.3, page 22 — verbatim” is defensible to a QS, adjudicator or arbitrator. A spreadsheet or a memory isn’t.

Is A source-grounded, human-reviewed record where every item traces back to a verbatim clause — a clean foundation for control and dispute preparation.

Isn’t Legal or QS advice, and it won’t issue notices, calculate entitlement, or claim money for you. The decision and the risk stay with you.

Processed locally · never used to train any model · a dated audit trail of everything done. SOC 2 / ISO 27001 on the roadmap.

Questions

Asked on every call so far.

How long does it take?+

The read takes a couple of minutes. Human review takes your team an hour or two, far less than reading 60 pages cold.

Which contract forms does it read?+

NEC4 (validated on a real package), JCT and FIDIC (golden-set proven). Bespoke amendments, Z-clauses and Particular Conditions are extracted and cited too.

How is this different from a general AI assistant?+

A general assistant answers anything, sourced or not. Senedra rejects whatever it can't quote from your contract, and a person reviews every item before it enters the register.

What about amendments or bespoke clauses?+

Upload them. They’re extracted and cited like the rest; anything unusual is flagged for a person to decide, never assumed.

Where does my contract go?+

Your contract is processed locally, never used to train any model, and not kept unless you ask. During the pilot we ask you to redact first.

What if it misses something?+

Human review is the backstop. Uncertain items wait in a review queue for you to confirm; nothing enters the register unseen.

What does the pilot involve?+

You send one subcontract, real or anonymised. We run it, show you the register, and tell you honestly if it fits. No pitch, no commitment.

Does it replace my QS?+

No. It's a clean, source-linked starting point for your QS or commercial team, not a substitute for their judgement, and not legal or QS advice.

Opening a pilot cohort

See it on your own contract.

Send one subcontract, real or anonymised. We’ll show you the register it produces. No pitch, no commitment.

Book a demo

We’re inviting a small group of commercial teams to run Senedra against their own subcontracts. No customer logos yet, by design; we’d rather earn them than borrow them.