Kuper reads the live project record — site diaries, correspondence, RFIs, instructions, revised drawings, programme — against your contract baseline. It connects related records into one developing contractual event and surfaces it while there is still time to act.
Stop leaving entitlement on the table, and stop walking into liabilities you could have answered. Most of what gets lost on a project is lost on process, not on merits.
Variations, extensions of time and disruption recognised, notified and substantiated while the event is still happening — not rebuilt at final account.
Employer and Engineer notices answered on time, delay damages exposure watched, out-of-spec work queried before it's built.
of project budgets in dispute, across 2,200+ projects in 114 countries
HKA, CRUX Insight 8th Annual Reportto notify a claim under FIDIC before entitlement is at risk; some bespoke Gulf forms allow five
FIDIC; Fenwick Elliottcause of construction disputes: failure to properly administer the contract
Arcadis, Global Construction Disputes ReportA contract manager with perfect recall, reading every document the project produces, every hour the project runs.
Every notice, time bar, variation route and programme obligation, clause-linked. Particular conditions are compared with the standard form, so the five-day notice hiding where FIDIC says 28 is caught before it bites.
Project mail, the document platform, SharePoint and the programme, plus diaries, minutes, RFIs and transmittals. Kuper reads it all where it already lives. Nothing changes for the site team.
Drift rarely lives in one email. It builds across three to six documents over several weeks. Kuper reasons across the whole chronology, not message by message.
Specifications, Employer's Requirements and the drawing register are indexed, so a flag arrives with the spec clause and the baseline comparison already attached.
Obligations owed to the contractor as well as by it: the Engineer's response periods, determinations, DAAB windows, and subcontract notices that must travel up the chain faster than they arrived.
Every running clock on the project in one place, with a first-draft notice citing the right sub-clause, ready for the contract manager to review and serve.
Site teams message a project assistant by WhatsApp or email as they work. Every message is read against the contract underneath — and an instruction that may be outside scope gets a simple answer: get it in writing.
Where entitlement is at risk across every project, and a final-account sweep of every flag never actioned, before anything is signed away.
Kuper is built around the life of one contractual event, not around claims. A claim is usually a variation that wasn't handled while there was still time. Money leaks at every stage, and Kuper is at every stage.
Your legwork done before you open the flag.
Each flag arrives as an investigation file: contract clause, spec reference and baseline comparison already attached. You confirm or dismiss.
Know when you're being asked for something extra, before you build it.
A narrow check: this may be outside scope, get it in writing. Never what or how to build — that stays with the drawings and the Engineer.
The substantiation is built as the event happens.
Contemporaneous records linked to each event, ready to value — not reconstructed at final account.
See the entitlement you're carrying, and how much of it is at risk of lapsing.
Open events, exposure and ageing across the portfolio.
Every event is linked to the clause, the specification, the correspondence and the decision taken — including the flags you dismissed, and why. That's the record an adjudicator, an auditor or the next contract manager inherits.
Kuper analyses project correspondence, forwarded or shared, against the contract. It doesn't score staff or measure individual response times.
Kuper doesn't decide something is a variation. The contract manager does. A dismissable flag costs seconds; a missed event costs the entitlement.
Claims are the failure mode. Commercial and contracts functions are reactive by design; Kuper gives them the event while there's still time to act on it.
It does not decide whether a claim exists. It makes sure the decision is taken while it can still be acted on. It is not a document repository, and not a general AI chat: it runs against a live project's own contract, continuously.
Your contract suite becomes a rulebook, amendments and all, checked with your contracts team.
Kuper connects to the project's mail, document platform and programme inside your environment.
Continuously, for the life of the project, through to final account.
Put Kuper on one of your live FIDIC projects and shape what it flags.