NEC and FIDIC Contract Administration Software Problems: The 6 That Cost Real Money, and How to Avoid Them

Why does the notice register get scoped as document management so often?

Because the visible symptom is documents. The commercial team is drowning in correspondence, the shared drive has a folder per contract, and the request that reaches a developer is for somewhere to log notices with a status and a value. That gets built. It looks like progress, because the register is finally in one place, and it changes nothing, because the entitlement was never lost through poor filing.

What a contract administration system has to be is a state machine with timers attached to transitions. The distinction is concrete and it shows up in what the model has to hold.

• Receipt time as a separate fact from the date printed on the document, because the clock starts on receipt.
• A working day calendar defined per contract, since your executed agreement may say fourteen days where the standard form says two weeks, and your jurisdiction's public holidays apply.
• An owner and a deputy on every running clock, so delegation moves the obligation rather than leaving it with someone who is off site.
• Permitted responses per notice type, and the outcome when no response arrives, including a deeming result where the form provides one.
• Escalation that fires before the deadline, not a report that observes afterwards that it passed.

Under NEC4 the mechanics are unforgiving by design: a compensation event notification starts a sequence, a quotation follows within a stated period, the project manager replies within a stated period, and continued silence can result in the quotation being treated as accepted. FIDIC does the same job with different furniture. Build the register and you have a Monday morning snapshot of a contract that is live every hour of every week.

What goes wrong when you roll onto a live contract mid stream?

Nobody gets to start at contract award, and mid contract migration is where these projects lose credibility with the commercial team.

The specific problem is that open events have real clocks running that must be reconstructed accurately, and the evidence is in an inbox. A notification received nine days ago has to be entered with its true receipt date rather than today's, or the system reports a deadline that is wrong in the direction that makes people relaxed. Closed events have no clocks but do have records that matter for the final account, and re keying them wastes weeks.

The pattern that works is to split the migration by state. Open events are re entered by hand with true receipt dates, owners and documents attached, which is a day or two per contract and should be done by the quantity surveyor who knows them rather than an administrator. Closed events are attached as document records without reconstructing transitions. Everything unclassified stays in the inbox until someone decides what it is, and that triage is where teams usually discover two or three items nobody had logged.

Then run in parallel for four to six weeks with the existing register alive alongside, and reconcile them weekly. Waiting for a clean contract start sounds disciplined and usually means waiting a year.

Why do the integrations that matter here break after launch?

Three integrations carry this category and each has its own failure mode once real correspondence starts flowing.

Email ingestion is the first and least understood. Notices arrive as mail with attachments, and the system needs the received timestamp from the mail server rather than the sent header, has to survive an item forwarded three times before anyone logs it, and must handle the same notice arriving twice by different routes without creating two events. Ingestion that depends on someone copying a mailbox address gets bypassed within a month.

Document control is the second. If your project runs Aconex, Asite or Viewpoint, the contractual record has to exist in both places without diverging, and the failure is quiet: a superseded revision in one system is still the current reference in the other. Decide which system is authoritative and make the other reference it rather than copy it.

Programme import is the third. Planners issue revisions monthly from Primavera P6 or Asta Powerproject, activity identifiers get renumbered, and an event referencing an activity on revision nine points at nothing on revision twelve. Keep every accepted revision and hold each reference against the revision it was made on, so that eighteen months later you can state which programme was accepted and which activities the assessment used. Without that, delay arguments become archaeology.

What happens when calendars, delegation and audit integrity are not covered?

These three are treated as detail and they are where systems lose their evidential value.

The calendar first. A reply period expiring at 23:59 on a public holiday has a defined answer in your contract, and a global calendar that assumes one country's holidays will get it wrong on an international portfolio. The calendar has to be per contract, and someone has to configure it at award rather than assume a default.

Delegation second. When the project manager delegates an assessment and the delegate is off site, the running clock needs a new owner and an escalation path. Most teams handle this by one person remembering, which works until the week it does not, and that week is usually a holiday period when several people are away at once.

Audit integrity third, and it decides whether the system is worth anything in a dispute. The record has to be append only, nobody edits history including the commercial director, and receipt timestamps must be immutable. A modified by column is not an audit trail. The system must produce, on demand, a single event exported as a pack a third party can read cold: the instruction, the notification with its receipt time, the stated assumptions, the quotation with its build up, the claimed programme impact, the reply, and what changed between quotations. If that export needs assembling by hand, it will not exist when you need it.

Should you build custom or configure what you already own?

Buy, and we 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. Thinkproject CEMAR, FastDraft and Sypro Contract Manager are real systems built by people who understand this domain, and on an unamended contract they do the job well. CEMAR in particular carries an advantage a bespoke system cannot give you on day one: many UK clients already use it, so the record format is familiar to the person on the other side of the table, and that familiarity has genuine value in a dispute.

Where those products 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 a quotation may be accepted, and sometimes create categories of event that exist nowhere in the standard form. Configuration stops at the boundary the vendor drew, and the workaround becomes a note in a spreadsheet one person remembers to check. You have then paid a licence fee for a system that governs the standard contract you did not sign.

Build when at least two of these hold. Portfolio level exposure matters more to you than any single contract. Your amendments have made the standard workflow a fiction maintained by hand. You need main contract events to cascade automatically into subcontract notices. You are a client organisation on a framework needing consistent data across contractors. Or you run NEC and FIDIC side by side.

How do hidden costs get into the quote?

The bands are $70,000 to $150,000 over 12 to 18 weeks for 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, and $180,000 to $450,000 over 6 to 12 months for a full platform. Estimates get broken by items that sound small in a kickoff meeting.

The largest is supporting several contract forms at once. NEC4 engineering and construction, NEC4 professional services and FIDIC Red are three different state machines, and each is real weeks of work rather than a configuration option. A quote that says supports NEC and FIDIC without pricing them separately has not thought about it. The second is the subcontract cascade, which needs a contract tree rather than a contract. Subcontract notice periods are usually shorter than the main contract, so an event that does not raise matching child notices leaves you carrying risk you had passed down on paper.

The third is programme integration, since P6 and Asta exports are their own discipline. The fourth is document control integration. The fifth is qualified electronic signature where a client demands it. The sixth is multi language and multi currency work. The seventh is offline issuing where site teams have no signal.

What genuinely keeps the number down is 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.

What separates a build that works from one that fails here?

The builds that work are used by the person with 380 unread messages. That means inbound classification has to be assisted rather than manual: a model reads incoming mail and attachments and proposes whether something is an early warning, a compensation event notification, an instruction or general correspondence, and a human confirms in one click. That single feature closes the gap where an event sits unclassified for nine days, which is the gap that started this whole problem. Drafting replies is not a job to hand to a model, because the words carry contractual weight.

The builds that fail were chosen from a demo. Make a prospective developer draw the notice state machine on a whiteboard before you sign anything. Someone who has done this will draw states, permitted transitions, timers attached to transitions and a deeming outcome when a timer expires. Someone 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. Ask how the audit trail resists editing, expecting append only records and immutable receipt timestamps. Ask them to show you a single event exported as a pack a third party could read cold.

Then settle ownership before kickoff. You should hold the repository, the infrastructure accounts and the unrestricted right to bring in another firm. These records may be read by a third party years after the developer relationship ends, and they must remain yours.