Resection reads every sheet, every revision, every schedule, and shows you exactly where it found what it found.
For UK subcontractors and contractors · NEC, JCT, FIDIC and bespoke
A busy project generates hundreds of documents, letters, revisions and minutes every month. Somewhere in there is the change that needed an instruction and the condition that needed an early warning. Resection reads all of it, every week, and comes back with the short list.

Three of those, in full
A compensation event notification window three days from closing. Nobody had typed it anywhere. The sweep found it in the documents.
In buildA subcontract amended to four weeks to notify, against a main contract running on eight. Notices sent after week four may already be out of time.
In buildAn instruction that arrived in meeting minutes. Under NEC4 only the Project Manager can instruct, so the work it authorised had no authority behind it.
In buildSynthetic project, invented numbers and drawings. The findings are real classes, and each is marked with where it is in the build, because an example without its status is just a claim.
Three things that hold whether the question is asked this afternoon or in an adjudication next year.
When Resection says it found nothing, that means it checked everything and found nothing. Each sheet is either read, or listed as not read with the reason it was not. You always know the size of the set the answer came from.
Not a page number. The exact wording, where it sits on the sheet, and which revision it was on, so you can check any answer against the drawing yourself. Anything that cannot show where it came from is rejected rather than stored.
The reading happens once into a permanent record. The answer you relied on in March is the answer you can still produce, with the same evidence attached, when it is questioned in September.
A resection, in surveying, is how you fix your position from known points. You do not estimate it, and you can show your working afterwards. That is the whole idea, applied to what your drawings say.
Developed on live NEC and JCT contracts, from the subcontractor's side of the table.
The working methodology behind Resection comes from real delivery-stage commercial work: technical queries, early warnings, compensation events, and the registers behind them.
Built by people who run NEC contracts for a living. 25 years of tier 1 construction management experience, and every worked example on this site comes from that.
Not a generic template. Whether you are the main contractor or a subcontractor on a back-to-back deal, tell Resection the form, or upload the executed contract and its amendments. It reads the terms that matter, from notification windows to conditions precedent, and you confirm them once.
Full contract engines run on NEC4 ECC, the ECS and JCT Design & Build today. Every other form, including your amended and back-to-back subcontract, runs on the clocks, deadlines and notice periods read from your executed contract and confirmed by you once. Every assessment cites the clause it relies on.
Each part below does a specific piece of the work, and they share one growing picture of your project. It leads with what the Sweep found and what needs a decision. Every output is a cited draft you verify. You always issue the notice.

Turn a site issue into a formal technical query in your own template, ready to sign. Or point TQ Finder at a drawing, a package or the whole project and it returns a short list of candidate issues, cheap to scan, so you draft the formal query only on the ones worth raising. Each one is assessed for its CE, SI and EWN implications in the same motion.

Revisions, annotations, markups and section marks, read from the PDF itself. Compare Rev C to Rev D and see what changed, and whether it is a compensation event or needs an instruction before you proceed. Sufficiency checks tell you what you can start and what you can't finish.

Every compensation event, site instruction and early warning with its entitlement, clause basis, deadline and value from your own numbers. The strategy layer works the detail a busy team misses: whether to keep events discrete or bundle them for the time-bar, which anchor date to run from, and a 10-day trigger to escalate an open query to an early warning.

Reads Asta Powerproject, Primavera P6 and MS Project, links the construction sequence to compensation-event impact, and runs critical-path and Key Date analysis. It is honest about its limits: true critical-path needs a native file, and an Excel look-ahead gives tasks and dates only, flagged best-effort.
A live compliance calendar tracking every notice window and key date.
Catch the mismatched notice period that would time-bar you against the main contract, before it does.
Weekly and monthly reports in a controlled-disclosure tone, drafted to issue standard.
Plain-English answers from your own documents, every one cited. A supporting tool, not the headline.
Run it on demand or on a schedule. Resection reads everything new across the project: documents, TQs, register changes and deadlines. It returns a prioritised list of what needs commercial action, each item traced back to its source.

Everything the project produced, read for you. The handful of things that need a decision, in priority order.
Plain-English answers from your own documents, with the source cited every time.
Raise the query, assess the CE, request the instruction. One motion, straight to the register.
Rev C to Rev D in ninety seconds. Every change found. The commercial ones flagged.
The week's registers, activity and your notes, drafted to issue standard. Add your voice. Send. Go home.
Your notice period and the contractor's are set to interlock, and an amendment to either one breaks the interlock without saying so. The gap is invisible until the day you need it. Resection reads both documents and puts the two periods side by side, clause against clause.
Upload the subcontract and the main contract terms you are bound to. Notice periods, conditions precedent and time-bars are read from each and lined up against each other.
Where your obligation runs shorter than the one above you, the difference is stated plainly, with the clause reference from both documents so you can check it.
The check runs when the documents go in, so the shorter clock is a known number from week one rather than a discovery on the day you try to notify.
Whatever you run for contract admin, keep running it. Resection reads what the project produces and hands findings over properly assessed and properly drafted, ready to file where you file everything else. Nothing to migrate. Nothing to rip out.
Resection reads the drawings, TQs, letters and site diaries your project is already producing. Your admin system carries on doing its job unchanged.
Assessed events export in a ready-to-file format with the clause basis and supporting narrative attached.
No implementation project, no procurement marathon. Your team is working in it the first week.
It usually happens on a walkaround. Somebody senior from the main contractor stops, looks at the work, says something like "that'll need to come out and go back in the other way round, crack on and we'll sort the paperwork", then walks on to the next thing.
Read essay →There's a document on every NEC job that quietly decides who holds the whip hand over money and time. Most people would guess the contract itself.
Read essay →Here's a question that decides more money than almost anyone realises: when your work has to land on somebody else's work, do the two specifications actually agree on what close enough means?
Read essay →Long-form essays, practitioner-written. Free.
Long-form, practitioner-written, no news aggregation. Read by PMs, commercial managers and directors across UK construction.
You will be putting contracts, drawings and live commercial positions into Resection. That data has to be protected, and you have to be able to prove it to your client and your IT team. Security is built in from the first line of code, and we put our security overview in front of your IT team before you commit.
Your documents and data are stored entirely in UK and EU regions and never stored outside them. AI analysis is performed by our AI provider as a disclosed US subprocessor: in memory, for processing only, never stored abroad, never used for training. The full data-flow map is in the security overview your IT team gets before you commit.
Your content produces your result and is never used to train any AI model. That is a contractual commitment with our AI provider, not a setting. Inline processing is retained by our AI provider for up to 30 days for abuse monitoring, then deleted. Nothing is retained for training, contractually. A zero-retention agreement is on our roadmap.
Your data is yours alone. Every company is separated at the database level, enforced by the database itself rather than by application code, so there is no shared visibility, ever. An independent security review is on the roadmap before any pilot data goes in.
Nothing is ever silently changed. Every action is recorded, and records can be added but never edited or removed, so the history stands up as evidence in a dispute.
You set retention. Delete a document, or your whole account, and it is gone.
Cyber Essentials and ISO 27001 are both on the roadmap, not held today. A written security overview for your IT team on request.
Mostly by people who have already tried doing this another way, which is the right instinct. Straight answers, including where the answer is no.
You can, and for a quick question across a few sheets it works well. We use those tools daily.
The difference shows up when the answer has to hold. A chat tool retrieves the parts of your drawings that look relevant to the question and answers from those, which is the right design for a conversation. It means the answer is drawn from a sample, and you cannot see how big that sample was. Resection reads for a different purpose: it accounts for every sheet, cites the exact text behind every fact, and stores the reading so the same question returns the same answer months later.
Curiosity and evidence are different jobs. If you are going to stake a notice on it, you need the second one.
It means the set is closed. Every sheet you upload is either read, or listed as not read with the reason, and that list is derived from the data rather than maintained by hand.
So when an answer says nothing was found, you can tell the difference between “nothing is there” and “nothing was in the part I looked at”. Every answer carries that boundary with it.
Follow the citation. Every fact carries the wording it came from, where that wording sits on the sheet, and the revision it was on, so you can put the drawing next to the answer and confirm it in seconds.
That is also the internal test: anything the system cannot tie back to specific source text is rejected rather than stored. You should never have to take an answer on trust, because a claim you cannot check is not worth having in a commercial argument.
Yes. The reading is done once and kept, and later questions run against that stored record rather than re-reading from scratch.
This matters most at the point it is challenged. An assessment you made in the spring can be produced again in the autumn, with the same citations, rather than being re-derived and coming out slightly differently.
No, and it never will. Resection checks consistency and coordination: whether two documents say the same thing, whether a reference points at something that exists, whether a revision changed something that affects you.
Whether the design is adequate is engineering judgement, and that stays with your engineer. We are careful about this line because a tool that blurred it would be dangerous.
It says so, in the answer, rather than filling the gap with something plausible.
Scanned sheets, hand mark-ups and drawn detail with no written label are all real. Where something has not been read it appears on the list of what was not covered, instead of quietly shrinking the set the answer came from.
Founding pilots get preferential pricing locked in for the term, and direct influence over what gets built next. Both of those are only possible while the group is small, which is why it is small. Tell us about your project and we will say honestly whether it is a fit.
No mailing list games. One reply, from the founder.
Not ready for that? The journal goes out to people doing this work: practitioner-written, no news, and one click unsubscribes you.