NEC4 Deadlines Tracked, Before They're Missed

Not on a named NEC4 project specifically -- this would be Mirage's first UK NEC4 deployment. The discrepancy-flagging and deadline-tracking agents involved are the same ones already running in production for change order and document consistency work at OCBM, applied here to NEC4's early warning and compensation event mechanics.

No. The Project Manager's decisions -- accepting or rejecting a quotation, assessing a compensation event -- stay with the Project Manager. Mirage tracks what's been notified, what's due, and what deadline applies, so those decisions are made with full information instead of a missed notification surfacing after the time-bar has passed.

Yes. Every early warning and compensation event notification is logged against the deadline your contract sets for a response or quotation, and what's approaching or overdue is flagged before it becomes a time-bar dispute rather than after.

Yes, based on how your contract's early warning register and instructions are structured. Anything ambiguous is flagged for the Project Manager to classify rather than decided automatically.

Yes. Programme updates are cross-checked against outstanding compensation events, so an event that should already be reflected in the accepted programme but isn't gets flagged.

Yes. Notifications and deadline tracking connect to the document management and contract administration tools already in place on the project. No new system for the commercial team to learn.

4 to 6 weeks to a production deployment: indexing your contract's deadlines and current early warning register first, then a parallel pilot on one active project.

Pricing starts with a fixed-price pilot run against one active project's early warning register and compensation events, so you see what gets flagged before committing to anything larger. After that, it moves to an annual subscription priced by volume, quoted in your first conversation with us.