Features

Five things Shield does that your inbox doesn't.

A walk through the demo, then an honest look at the roadmap. Every section here is in the product today.

Demo moment 01

Forward an email. Get the risk read in 30 seconds.

Forward any project email to your Shield address — or set up the Gmail filter and never click forward again. Within a minute, the email shows up classified, sentence-highlighted and severity-tagged.

21 commercial risk triggers, four severity levels (critical, high, medium, low), four tone shifts. The classification is enforced through a tool-use schema so the AI cannot return malformed output, and critical-severity items are voted on three times in parallel to eliminate flicker.

An AI that thinks like a QS, not a chatbot.

Shield's engine is trained on the language of UK subcontract correspondence — JCT, NEC, and the way main contractors actually write. It doesn't summarise your inbox. It reads it for danger.

21 commercial risk triggers

Variations, time-bars, pay-when-paid, contra-charges, EOT events, scope creep, payment pressure — every trigger built from real subcontract disputes, not generic AI summarisation.

Tone-shift detection

The AI catches the diplomatic opening that buries a threat, false reasonableness, and escalation signals — the bits a solicitor would highlight in yellow.

Time-bar awareness

JCT 4.21 notice periods, NEC compensation event windows. If a clause deadline is approaching, the AI raises it before the clock runs out — because entitlement you notify late is entitlement you lose.

Clause-cited drafting

Every suggested reply and notice cites the clause it stands on. Severity is set by fixed rules, not AI mood — the same email gets the same flag every time. And every result says what it is: AI-generated, not legal advice.

Shield Index projects board — every project scored by risk, with unhandled and unanswered counts

Demo moment 02

One dashboard. Every project. Every risk.

Directors and commercial managers see every critical and high-severity signal across every active project, sorted by severity. Filter by team member, project, severity or date range. The view a QS opens first thing Monday morning.

Every email gets a "raised by" stamp showing which staff member forwarded it — so when someone says "nobody told me about that variation," you can show that Joe forwarded it three weeks ago.

Demo moment 03

Drop in a subcontract. See the dangerous clauses.

Upload the subcontract PDF when the project starts. Shield runs a structured contract analysis — pay-when-paid clauses, notice periods, liability caps, retention terms, set-off rights. Findings are cached so the classifier knows what contract you're operating under when new emails arrive.

The output is structured: dangerous clauses are flagged with location, plain-English explanation and the contractual consequence. Not a generic legal summary — a working playbook for the project.

Subcontract PDF open in Shield with contract scan findings: 2 critical, 2 high, 2 medium

Auto-drafted Extension of Time notice citing the delay event, days claimed and source email evidence

Demo moment 04

EOT notices, drafted for you.

When Shield detects a delay notification plus a programme impact on the same project, it auto-drafts an Extension of Time notice referencing the specific Relevant Event, the affected clause and the source emails. You review, edit, send.

Four document templates ship with the product: late payment, variation confirmation, delay notification and EOT claim. All filled from project context, all editable before they leave.

Demo moment 05

One click. A solicitor-ready PDF.

When a project goes to dispute, you click Export Dispute Pack and get a cleanly styled PDF with cover page, dispute-strength grade (A–F), evidence timeline, variation log, payment history and a hash-integrity statement at the back. It's the document your solicitor asked for in their first email.

Every email cited carries its SHA-256 hash. The integrity statement explains the chain-of-custody so a third party can verify nothing was altered between capture and export.

Dispute pack PDF chronological timeline — severity-tagged emails, detected signals and SHA-256 hashes

Eight tools, one project workspace.

Behind that board, every project ships with the full toolkit — from contract scanning to board reports. Hover any tool to see how it behaves in the app.