Free resources · commercial control for subcontractors

Flagship tool

Final Account Readiness Scorecard

Eight questions on how well your live jobs would stand up if challenged. Tick what's true. You'll get a score and see where the gaps sit. Nothing is sent anywhere; it runs in your browser.

Every variation on your live jobs is written down with a date and a reference, not just in someone's head or a WhatsApp thread. For each variation you can point to the instruction that triggered it (email, site instruction, minute). You know which variations have been notified in time, and which haven't gone in yet. Your payment applications line up with the contract's payment terms, not just with your costs. You can show retention held, and when each half is due back, per the contract. Your notices (payment, delay, claims for time and money) are logged with the clause they answer to. If your QS left tomorrow, the next person could pick up where the job stands from the records alone. You could assemble the evidence for your final account this week, not scramble for it later.

0 / 20: tick the statements that are true today

Gaps showing up? A Commercial Control Diagnostic reads one of your contracts and turns it into a register where every item is quoted and cited to its clause and page. Book a demo →

The library

Checklist · PDF

Variation Evidence Gap Checklist

The documents that decide whether a variation survives to the final account, and where they usually go missing. Print it and work through one variation at a time.

Download the checklist →

Checklist · PDF

Payment Application Evidence Checklist

What to have attached before you submit, so a pay-less notice (the letter that cuts your payment) has nothing to bite on.

Download the checklist →

Template · Excel

Variation Record Template

A blank capture sheet with the same columns Senedra’s own variation register uses. Record what happened, when, and what evidence exists for it.

Download the template →

Template · Excel

Notice and Deadline Log

One sheet for what was sent and received, and which clause it answers to. It logs; it does not calculate a date or judge whether a notice was in time.

Download the log →

Coming soon

QS Handover Checklist

If your QS leaves mid-job: where the job stands, captured, so the next person doesn’t start blind.

In progress

Every tool here is about visibility and capture: what the contract says, where the source is, and what needs review. None of it tells you a date to rely on or a sum you're owed; those stay with your QS and commercial team.

Guides

Reading on the money side of the job

Written for the people who run subcontracts, from sources we name. No product pitch inside.

Applied, certified, paid: the gap that decides your month

Three figures decide a subcontractor's month. The distance between them is where margin quietly leaks away, and most firms never line them up.

For MDs and commercial managers of specialist subcontractors

The retention ledger: money with two release dates and no reminder

Retention is deducted automatically and released only when someone asks. A ledger of what's held, where, and when it falls due is the simplest money recovery there is.

For MDs and finance leads of specialist subcontractors

The time-bar board: the deadlines your contract started counting

Notice windows start counting from events on site, not from when someone reads the clause. A visible board of live windows is the cheapest insurance a commercial team can run.

For QSs and commercial managers on NEC4 and JCT subcontracts

How we check it,
rather than how we describe it.

97.9%

Terms found correctly

Measured against contracts our own team had marked up by hand first.

Contract types tested

It reads NEC4, JCT, FIDIC and AIA.

100%

Every line in the register carries the contract's own words and its clause reference. Anything the engine cannot quote is rejected before the register exists, so the figure is true by construction rather than by measurement.

These are our own test contracts, not customer results.

Why not just paste the contract into a chatbot?

Try it side by side on one contract. The differences show up fast, and they're the ones that cost money.

On a real subcontract	A general AI chatbot	Senedra
A clause it can't find	Answers anyway. You may get a confident answer the contract never says.	No quote, no row. If it can't quote the clause, nothing goes in the register.
Backing an answer up	Prose, with nothing you can put in front of the other side's QS.	Every line carries its clause and page. Check any item in one click.
The term it missed	Simply isn't there, and nothing tells you it's missing.	The register is the checklist: payment, retention, notices, risk, each accounted for.
Sixty pages plus amendments	Gets skimmed. Long documents are where answers quietly degrade.	Reads every page, including the schedule of amendments, and a person reviews the result.
The deadline buried in clause 61.3	Mentioned if you ask exactly the right question.	Surfaced on its own row with the wording quoted, for your QS to act on.

How we keep the read honest

We keep contracts we've marked up by hand for every form we read (NEC4, JCT, FIDIC and more). Every change to the engine is re-run against those sets before it ships, and it has to clear fixed accuracy floors to get through. When a human review catches something on a real job, that correction goes back into the test sets, so the read improves and can't quietly get worse. Those are our own test figures on our own marked-up contracts, not customer results.

How to test it yourself: take one closed job. Ask a general AI three questions about it: the payment terms, the notice deadlines, what was amended off the standard form. Then run the same contract through Senedra and compare what you can actually prove.

Everything people ask.

How long does it take?+

The read takes a couple of minutes; going through the result takes an hour or two, far less than reading 60 pages cold.

Which contract forms does it read?+

It reads NEC4 (validated on a real package), plus JCT and FIDIC, and it's tested against contracts we marked up by hand. The changes the other side made to the standard form (Z-clauses, Particular Conditions) are read and cited too.

Where does my contract go?+

The read runs on our own machines and your contract text is never sent to a third-party AI model. Where documents and registers are stored, they are held encrypted in the UK or EU, never used to train anything, and deleted or returned at the end of the engagement, or sooner if you ask. During the pilot we ask you to redact first.

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.

How is this different from a general AI assistant?+

A general assistant will answer anything, backed up or not. Senedra only keeps what it can quote from your contract; anything it cannot quote never enters the register.

What about amendments or bespoke clauses?+

Upload them. They’re read and cited like the rest; anything unusual is flagged rather than assumed.

Can it check a payment application?+

It lines up what you applied for, what was certified and what was paid, from your own records, and shows where the numbers part company. What you do about a gap stays with you and your QS.

What if it misses something?+

Uncertain items are held in a queue and flagged; nothing enters the register by guesswork. You see exactly what was held back and why.

What is it, and what isn’t it?+

It is a record where every item is quoted word for word from your contract, with the clause and page next to it: a clean foundation for control and dispute preparation. It is not 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.

Does it replace my QS?+

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