NEC and FIDIC Contract Administration Software: Who Is Actually Counting Your Reply Periods?

Why contract administration is the one system a major contract cannot improvise

It is 4:40pm on a Friday on a highways package. The assistant project manager is working through an inbox with 380 unread messages. Somewhere in it is a mail from the contractor's site agent, sent nine days ago, subject line ground conditions at chainage 2400, with a PDF attached. Nobody logged it. Nobody decided whether it was an early warning, a compensation event notification, or just a site agent thinking out loud. The contract does not care what anyone decided. If that mail was a notification, the clock started when it arrived, and it kept running through a bank holiday and through the fact that the person who owned it was on leave in Portugal.

Six months later the quantity surveyor reconciles the account and finds the gap. The contractor's assessment stands because no reply was issued in time. On a large infrastructure contract that single lapse can be worth more than the entire cost of the system that would have prevented it. This is the specific reason contract administration is not a document management problem dressed up in construction language. It is a clock engine with legal consequences, and email has no clock.

Most commercial teams run this on Outlook, a shared drive with a folder per contract, a compensation event register in Excel that one person updates on Monday mornings, and a weekly commercial meeting where somebody reads the register aloud. The register is a snapshot of what was true last Monday. The contract is live every hour of every day. That gap is where deemed acceptances live.

Problem 1: the contractual clock belongs to nobody

Under NEC4 the mechanics are unforgiving by design. A compensation event notification starts a sequence, the quotation follows within a stated period, and the project manager replies within a stated period. If the reply does not come, the contractor can notify that failure, and if silence continues the quotation is treated as accepted. FIDIC does the same job with different furniture: notice periods, a fully detailed claim, and an engineer's determination window. The periods differ by form, by edition and by whatever your particular contract was amended to say, which is exactly why a generic reminder in Outlook does not solve this.

The failure is never that somebody did not know the rule. It is that the rule lives in a document and the work lives in an inbox, and nothing joins them. Delegation makes it worse. When the project manager delegates an assessment and the delegate is off site, there is no mechanism that reassigns the running clock. A build fixes this by making the clock a first class object with an owner, a deputy, a working day calendar that knows your contract's definition of a week and your jurisdiction's public holidays, and an escalation that fires before the deadline rather than after the account is reconciled.

Problem 2: your Z clauses are not in anybody's product

Thinkproject CEMAR, FastDraft and Sypro Contract Manager are real systems built by people who understand NEC, and on a standard unamended contract they do the job well. Where they strain is amendment. Almost no serious infrastructure contract goes to signature unamended. Z clauses change reply periods, add notice types, insert client approval gates before the project manager may accept a quotation, and sometimes create bespoke categories of event that exist nowhere in the standard form.

Configuration in an off the shelf tool goes a certain distance and then stops at the boundary the vendor drew. When your executed contract says fourteen days rather than two weeks, and your programme of works counts days differently again, the workaround becomes a note in a spreadsheet that a specific person remembers to check. You have then paid a licence fee for a system that governs the standard contract you did not sign.

A custom build treats the contract as configuration data, not code. Notice types, permitted responses, reply periods, deeming outcomes, escalation paths and required attachments are set up per executed contract at award, by a commercial person, in an admin screen. Adding contract number 41 with its own amended clause set is an afternoon of setup, not a change request to a vendor roadmap.

Problem 3: the compensation event record is a folder, not a chain

When an event is finally argued, whether in a dispute board, an adjudication or just a hard meeting with the client, the question is always the same. Show me the chain. Show me the instruction, the notification and its timestamp, the assumptions the project manager stated, the quotation with its build up, the programme impact you claimed at the time, the reply, and what changed between the first quotation and the accepted one.

Folder structures cannot answer that. Neither can a register whose columns are status and value, because the interesting evidence is in the transitions. What a build must hold is a linked chain per event: every document version, who issued it, when it was received rather than when it was dated, which activity on the accepted programme it hit, and which defined cost records support it. That record is append only. Nobody edits history, including the commercial director, and that constraint is precisely what makes the export defensible when a third party reads it.

Problem 4: main contract and subcontract clocks run out of step

This is where the money quietly leaves. You receive a compensation event under the main contract. Your subcontract, whether it is an NEC subcontract form or a bespoke agreement, has its own notice periods, and they are usually shorter because whoever drafted them wanted headroom. If the main contract event does not automatically raise the matching subcontract notices, you carry the risk yourself and only find out at final account.

None of the standard tools model that cascade well, because they were designed around a single contract as the unit of work. A build models the contract tree. One event at the top generates linked child notices at each tier, with each tier's own period and its own owner, and a single dashboard shows where the chain is broken. On a project with fifteen packages that view is the difference between passing risk down and absorbing it.

Problem 5: the programme is the evidence, and it lives somewhere else

Time entitlement arguments are won and lost on the accepted programme. Your planners work in Primavera P6 or Asta Powerproject and issue revisions monthly. Your commercial team argues about events weekly. If the link between an event and the activities it affected is a sentence typed into a text box, then every delay argument becomes an archaeology exercise.

A serious build imports the programme, keeps every accepted revision, and lets an event reference specific activity identifiers on a specific revision. When the argument arrives eighteen months later, the system can state which programme was accepted at the time and which activities the assessment was based on. That is not a nice reporting feature. It is the difference between a priced position and an opinion.

What this costs and how long it takes

Across the 2,000 plus projects Digital Heroes has delivered, here is the honest shape. A first release covering the notice and correspondence register, configurable clocks with delegation and escalation, and the full compensation event chain for one contract form runs $70,000 to $150,000 and ships in 12 to 18 weeks. That is a system your commercial team runs live contracts on, not a pilot.

A full platform adding the subcontract cascade, programme import and activity linkage, defined cost and records management, client and framework portfolio reporting, and an adjudication export pack runs $180,000 to $450,000 phased over 6 to 12 months.

What pushes the number up in this category: supporting several contract forms at once, because NEC4 ECC, NEC4 PSC and FIDIC Red are three different state machines and each is real weeks. Programme integration, since P6 and Asta exports are their own discipline. Document control integration with Aconex, Asite or Viewpoint, because the record has to live in both places without divergence. Qualified electronic signature where the client demands it. Multi language and multi currency for international FIDIC work. And offline capability, if your site teams issue notices from places with no signal.

What keeps the number down: starting with one contract form, one live project, and the notice plus compensation event flow only. Reporting can wait. Nobody ever lost an entitlement because a dashboard was ugly.

Build versus buy, and when buying is the right call

Buy, and we will say this plainly, if you run fewer than about ten live contracts on largely standard NEC forms and your Z clauses do not move the reply periods. CEMAR in particular has the advantage that many UK clients already use it, which means the record format is familiar to the person on the other side of the table. That familiarity has real value in a dispute and it is not something a bespoke system gives you on day one.

Build when at least two of these are true. You run a portfolio large enough that portfolio level exposure matters more than any single contract. Your contracts are amended to the point where the standard workflow is a fiction maintained by hand. You need main contract events to cascade into subcontract notices automatically. You are the client organisation on a framework and you need consistent data across contractors, not a per contractor system each of them chose. Or your business is international and you run NEC and FIDIC side by side with different teams and different languages.

How to choose a developer for contract administration software

Ask them to draw the notice state machine on a whiteboard before you sign anything. A developer who has done this will draw states, permitted transitions, timers attached to transitions, and a deeming outcome when a timer expires. A developer who draws a form and an approval chain has built a leave request system and is about to learn contract law with your entitlement as the tuition fee.

Ask what happens when a reply period expires at 23:59 on a public holiday, and whether the calendar is per contract or global. If they have not thought about it, they have not read a contract.

Ask how the audit trail resists editing. The correct answer involves append only records and immutable timestamps for receipt, not just a modified by column. Ask to see how they would export a single event as a pack a third party could read cold.

Ask about programme import specifically, naming P6 or Asta, and ask who owns the code. You should hold the repository, the infrastructure accounts and the unrestricted right to bring in another firm. At Digital Heroes the client owns the code from the first commit, and we would tell you to walk away from anyone who hedges on that.