Academy

Run the workflow properly

Practitioner guides for every workflow ControlsIQ carries — contract mechanics and programme forensics first, then where the platform takes each step. Written for QSs, planners and claims professionals.

How to run an EOT claim properly under FIDIC 2017Contract8 min read

From the delay event to a defensible Extension of Time submission: entitlement, the Sub-Clause 20.2 clock, records, analysis method, and how to structure the claim.

Notices that survive scrutiny: FIDIC time bars in practiceContract6 min read

The 28-day Notice of Claim is where entitlements die. What counts as awareness, what a valid Notice must contain, the follow-on duties, and the Particular Conditions traps.

Health-check your programme before you submit itSchedule7 min read

A DCMA 14-point assessment read contractually: what each check means, the thresholds, and why a clean programme is a claims asset long before any dispute.

Read your Particular Conditions before they read youContract6 min read

The Particular Conditions outrank the printed form. How to build a clause-by-clause amendment register, which amendments decide claims, and how to use the register at claim time.

From .xer to a contractual Key Dates RegisterSchedule5 min read

The programme is a contract deliverable, not just a planning file. Parsing P6 and MS Project natively, lifting milestones into a Key Dates Register, and keeping both honest at every update.

Baseline vs update: find what really movedSchedule5 min read

Updates hide drift. Comparing two programmes properly — finish, duration, float, logic, effort and cost variance — and turning what moved into attribution rather than argument.

Demonstrating delay: the longest path, evidencedSchedule6 min read

A delay claim must show completion moved, on the critical path, because of the event. Longest-path tracing, correlating events to windows, and handling concurrency without hand-waving.

From risk register to P80: schedule risk you can defendRisk6 min read

A register that lives with the programme, probability and impact set honestly, and Monte Carlo outputs — S-curve, tornado, pre vs post mitigation — read as decisions, not decoration.

Educational content for construction professionals. Not legal advice — see each guide’s closing note.