01
The register
Every one sided clause found, ranked by tier. Each carries the sentence quoted from your contract, what it does to you, and the amendment to ask for.
The engine
A contract is a set of clocks. Most of them are running against you.
The engine reads the subcontract and compiles every clock, gate, threshold and forfeiture it imposes, as rules a machine can run. Then it keeps that plan running against what actually happens on site.
527checks passing
0runtime dependencies
30trap patterns
0network calls while it reads a contract
What it produces
Three things, from one reading.
02
The clocks
Every notice window, particulars interval and payment gate, compiled as rules. The ones where missing the date destroys the entitlement are separated out.
03
The plan, running
Feed it a delay and it opens every obligation that event triggered, tracks which were served, and tells you what is still recoverable.
The difference it makes
One delay event. Two outcomes.
Eighty one days of restricted access, on the same contract, with the same facts. The only difference is whether anyone was counting.
ENTITLEMENT LOST
Nothing served. One event opened eight obligations and every one of them passed. The claim dies on the calendar, not on the facts.
SLIPPING, zero forfeited
Notice served on day five, particulars kept running. Some beats were still missed, but none of them forfeits anything. The claim survives.
This is the worked example that ships with the software, run on the demo contract. It is in the manual.
It refuses rather than guesses
The answer we will not give you is a wrong one.
A tool that quietly picks the wrong number is worse than no tool. Three conditions are enforced in code and tested on every build.
COMMERCIAL TERMS
Retention 10% [HIGH]
Advance payment 20% [HIGH]
Performance security 10% [HIGH]
Defects liability period 2412 months [COLLIDED] either 24 or 12
! Reads as "2412 months", which is not a real value. Two figures are printed
on top of each other: it is either 24 or 12 months. Confirm from the
executed original.
Payment period 3010 days [COLLIDED] either 30 or 10
| Condition | What it means on your contract |
|---|---|
| It never resolves a value it cannot read | A revised figure printed over the one it replaced is reported with both candidates. The difference between 24 and 12 months is a year of liability, and we will not choose it for you |
| No clause verdict on an unsigned document | Drafts and comparisons are detected. The plan still compiles, so the work is not wasted, but nothing is presented as settled |
| The Appendix governs | It is the negotiated document. Where it disagrees with the printed conditions, it wins |
Tested on documents it had never seen
Eight unrelated documents. No crash, no false answer.
Pulled from live business files and put through the engine cold. The failure that destroys trust in this category is a confident wrong reading, not a refusal.
| Document | What it returned |
|---|---|
| Adversarial fit out subcontract | Contract at 89 per cent. 17 findings, 6 critical. Do not sign without negotiation |
| Unfilled supply template | Recognised as a template. Deferred terms raised as critical |
| Services facilitation agreement | Contract at 76 per cent, no findings, and said so: nothing flagged is unusual, read it yourself |
| Saudi labour contract | Contract at 53 per cent, read and covered by tests |
| Joint venture agreement | Partial. Asserted nothing |
| A curriculum vitae | Not a contract. Said the wrong document had been supplied |
| Signed contract, scanned | Unreadable. Asked for a text layer before anything else |
| Unseen tender pack | Classified it, pulled the reference, five dates and nine requirements, and flagged that every deadline had passed |
Where it stands
What runs today, and what does not.
Stated plainly, because you will find out either way and it is better coming from us.
| Capability | State | Detail |
|---|---|---|
| Reading the contract | Live | Word, Excel, PDF, HTML and email, read natively |
| The risk register | Live | 30 trap patterns, each quoted and answered with what to ask for |
| The compliance plan | Live | Clocks, gates, thresholds and the forfeiture register |
| Running a live event | Live | Obligations opened, served, missed, and what is salvageable |
| Saudi Labour Law pack | Live | Articles 80(7) and 117, leave, absence and sick pay banding |
| Tender intake | Live | Bid clock, requirements, bill, scope drift, drafted proposal |
| Arabic | Live | Arabic documents, dates and mixed language packs |
| The console | Live | Installed on your own computers, opened from a desktop shortcut |
| Scanned documents | Opt in | Refused by the console. On the command line an opt in reader can transcribe a scan, but it sends page images to an outside service, so it is off unless you ask |
| Separate user accounts and roles | Not built | No sign in of its own today, and no audit trail yet |
Everything marked live is covered by the test report and documented in the manual.
Coming next, not on sale yet
A Tenders pack that reads an RFP and lists every returnable and date, and a Labour pack for Saudi Labour Law deadlines and procedures for your staff. Same engine, same console. Both build on readers that already pass the test report. No date and no price yet.
Put Kontra+ on your own computers.
The NDA is signed before anything is sent. We reply the same working day.