The Commercial Control Loop

A commercially significant event — a latent condition, a directed change, a delay — starts a race the moment it happens. The contract's notice clock is already running; the evidence is already going stale; and every day the event stays undocumented, it drifts closer to becoming free work. The features described across these docs are links in one chain built for that race:

1. 1

   Capture

   The event is caught where it first appears — a meeting, a knock-off call, an email, a document received through Exchange — in the words it arrived in.

2. 2

   Clock

   The contract clause it engages and the notice period it starts are identified while there is still time to act, and surface on Today with the deadline visible.

3. 3

   Paperwork

   The notice or variation is drafted from the record, in your own templates, every factual line cited — and waits at a gate for a human.

4. 4

   Proof

   The send leaves a receipt, the variation enters the register, and the record carries the event through claim, certification and payment — every transition stamped.

Nothing in the loop is automatic past the gate: Alloovium prepares, you approve. What the loop guarantees is that nothing expires quietly — if a clock is running, you can see it, and if paperwork is owed, it is already drafted.

Commercial events almost never arrive labelled. They surface as a sentence in a meeting, a remark on the knock-off call, a request buried in an email thread, or a document received through Exchange before anyone has filed it. Each of those surfaces feeds the same record: the meeting review queue tags the instruction that is really a variation, the site call drafts the latent-condition entry while the evidence is hours old, and email and Exchange keep the cross-company facts searchable and citable even when they never reach the formal document system.

Once an event is on the record, the question is contractual: what does it engage, and how long do you have? Ask the contract directly — “what must we notify within ten business days?” — and the clauses come back cited. When an event carries a notice obligation, the deadline surfaces on Today as a card with the clause behind it and the days remaining in front of you, while there is still time to do something with them.

The notice, the variation, the show-cause response — Alloovium drafts them from the record: the facts from the diaries and correspondence, the clause references from this contract, the format from your own library templates. Every factual line carries a citation, so reviewing the draft means checking receipts, not re-deriving facts. And the draft waits at a gate — nothing ships your words without you.

A notice that cannot be proven served is barely a notice. Exchangekeeps the trail on every send: who received what, which version, when it was opened, who signed — hash-bound to the exact content, so “we never got that” stops being an argument anyone can make.

Preserved entitlement still leaks at the back of the loop: the approved variation that never made a claim, the claim certified short that nobody chased. The variations register carries each event with its notice receipts attached, every transition writes to the project timeline, and the claim evidence stays assembled as it happens rather than reconstructed under pressure. Ask for the reconciliation — approved versus claimed versus paid — and the gaps come back as a cited list, so the recovery starts the same afternoon.

The loop holds because routines run it when nobody is looking: the daily check for events that start clocks, the subcontractor chased for the substantiation that is due, the month-end report assembled before the cutoff. Whatever a routine produces waits at the same approval gate — machines do the legwork, you keep the signature.