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.
Forward an email. Get triage 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.
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.
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.
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.
One click. A solicitor-ready PDF.
When a project goes to dispute, you click Export Dispute Pack and get a Warm Editorial-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.
