Aven-AI for contract administration

Know which contractual notice a programme slip just created — before the deadline passes.

A signed contract is a hundred obligations with clocks attached. The programme moves every week, and each slip can start a notice clock nobody is watching. The register shows the contract is “in place.” It does not tell you that an activity that slipped on Tuesday just opened a 28-day notice window that closes whether or not anyone noticed. That gap is where entitlement quietly dies.

What a contract register doesn’t close

Every project keeps the executed contract on file. Storing it answers “do we have the contract?” It does not answer the question that decides entitlement: which obligation is now live, against what the programme actually did this week, and which deadline is running today? Document control preserves and retrieves. It does not read the contract against the programme and tell you what just became due. (Why document control isn’t a reasoning layer.)

And what a notice workflow doesn’t close either

There is a stronger objection than storage: the contract-administration system that already routes your notices and counts down your deadlines. Those systems are good at what they do. But look at the order of events. The workflow begins the moment a person has already recognised that something happened and decided it matters — then it produces the compliant communication, logs it to the register, and runs the clock. It is the register you write into. It administers the notice you have spotted. It does not watch the programme and tell you an obligation just came alive that nobody has registered yet. That gap — between an event moving on the programme and a person realising it created a contractual duty — is upstream of any workflow tool, and it is exactly where entitlement is lost. Aven-AI works that gap: it reads the live programme against the contract and surfaces the notice before it reaches anyone’s register. Detection, not administration — it sits above the process, not inside it.

What Aven-AI does with your contract

Aven-AI reads your executed contract — including the bespoke and amended FIDIC and NEC4 forms used on real projects, not just the standard books — and extracts the notice obligations and their deadlines. It connects to the live P6 or MS Project programme and watches those time-bars for the life of the project. When an activity slips, it flags the specific contractual notice that slip just created, cites the clause, and drafts the notice grounded in that clause for your team to review. Not in the dispute. Not in the post-mortem. While the window is still open. (How a programme slip becomes a notice.)

What it does not do — on purpose

Aven-AI does not serve or submit notices, does not make the claim or entitlement decision, and does not replace your commercial team or legal advice. It is not a pre-signature review or negotiation tool — it administers the contract you have already signed. It flags that a deadline is running and cites the exact clause; a competent person decides and serves. That boundary is the point: an advisory layer that never actions is one you can trust across the whole contract without it taking authority from your contracts manager or QS.

Built for FIDIC and NEC4 as they’re really used

FIDIC runs across the Middle East, Africa, Asia, Europe and Latin America; NEC4 across the UK, Hong Kong, New Zealand and South Africa. Aven-AI is built for the amended and bespoke versions of those forms real projects actually run on — anywhere they’re used. It comes from a professional with nineteen years on construction sites across QHSE, FIDIC and NEC4, and the hard-won truth that a contract on file is not the same as its obligations being watched.

The subjects it governs

Aven-AI reads across the obligations these come from — each explained in depth in the cluster below:

One platform, two halves

Contract administration is the primary layer; QHSE is the wedge that shares the same advisory core. If your risk lives on the safety side too, the HSE platform reads high-risk-work readiness, permits and method statements the same way — cited, advisory, before the work starts.