Add-on module · needs Planning
Contract
Keep the registers your contract asks for, see every time bar before it falls, and show the delay from the programme you already keep.
- Add-on, needs Planning
- JBCC · GCC · NEC · FIDIC
- Nine delay methods
Choose the form of contract, and the registers, steps and periods follow it. Every rule can then be changed for the programme in hand.
Forms of contract
- JBCC Principal Building Agreement
- GCC 2015
- NEC3 ECC
- NEC4 ECC
- FIDIC 1999 Red and Yellow
- FIDIC 2017 Red and Yellow
- Other
The letters use the form’s own title for the administrator: Principal Agent under JBCC, Employer’s Agent under GCC 2015, Project Manager under NEC and Engineer under FIDIC.
Keep the registers
One register per kind of entry, numbered and dated, each against the same programme.
- Early warnings, on the forms that have them (not JBCC or GCC 2015)
- Notices of delay
- Compensation events
- EOT claims
- A fragnet for each entry
Watch the time bars
Each step has a period and a consequence, so you see which date matters and what happens if it passes.
- Periods in days, working days, weeks, calendar days less holidays, or months
- Consequences: time bar, deemed accepted, deemed refused, or a reminder
- “Due soon” from 10 working days before, unless you change it
Put deadlines in the diary
Write the register’s deadlines to an iCalendar file, for the calendar you already use.
Record the weather
A weather register measured against the contract’s allowance, and a rain allowance activity in the programme.
Draft the letters
Seven kinds of letter drafted from a register entry as Word documents, for you to edit before they go out.
- Early warning; notice of delay and intention to claim
- Compensation event notification
- Quotation, claim and interim claim covering letters
- Notification of failure to reply
Draft the narrative
Draft Narrative uses AI, with your own key, to write from the programme’s facts.
- Monthly progress
- Delay narrative
- Revision change summary
- Quality findings
Delay analysis
Run the methods the contract and the event call for, side by side, on the programme and its updates.
| Method | What it shows |
|---|---|
| Time impact, each event alone | The fragnet of one event added to the programme on its own. |
| Time impact, events added in date order | Events added one after another, in the order they happened. |
| Impacted as-planned | Every event added to the as-planned programme. |
| Windows | Each update period’s slip, shared out between the events in it. |
| Half-step | Each update period split into progress and revisions; an event gets the progress delay on its own activities and the effect of revisions to them. |
| As-planned vs as-built | The overrun on the critical work. |
| Collapsed as-built, each event alone | One event taken out of the as-built programme. |
| Collapsed as-built, events in turn | Events taken out of the as-built programme one after another. |
| Weather register | Days beyond the allowance that fell on critical work (and, once activities are marked weather-sensitive, only on those). |
- Concurrency counted once
- Pacing candidates listed
- An as-built record of the actual dates at every update
- A run fingerprint, so a run can be shown to reproduce
- Save any analysis view as a programme
Time bars
These are the defaults Gantt CSS starts from for NEC and FIDIC. Every one can be changed per programme: check them against your contract.
| Form | Step | Default | If it passes |
|---|---|---|---|
| NEC3 and NEC4 | Contractor notifies a compensation event | 8 weeks | Time bar |
| NEC3 and NEC4 | Project Manager replies to the notification | 1 week | Reminder |
| NEC3 and NEC4 | Contractor submits the quotation | 3 weeks | Reminder |
| NEC3 and NEC4 | No reply after the contractor’s notice of failure to reply | 2 weeks | Deemed accepted |
| FIDIC 2017 | Notice of claim | 28 days | Time bar |
| FIDIC 2017 | Fully detailed claim | 84 days | Time bar |
| FIDIC 2017 | Engineer’s agreement, then determination | 42 + 42 days | Deemed refused |
| FIDIC 2017 | Notice of dissatisfaction | 28 days | Time bar |
| FIDIC 1999 | Notice of claim | 28 days | Time bar |
| FIDIC 1999 | Fully detailed claim | 42 days | Reminder |
JBCC and GCC 2015 have their own steps in the app. Set their periods from your edition of the contract. More in the contract time bars guide.
In and out
The add-on works on the programme Planning keeps: the baseline, the updates and the as-built dates.
| Output | Format | What it holds |
|---|---|---|
| Overall delay register | Excel and A3 PDF | Every method’s days, reconciliation against the windows, an event by window matrix, a Scott schedule and a guide to the methods. |
| Combined EOT report | A4 PDF | The contract, the events and whether their notices were in time, the weather, the delay analyses, and the programme as an appendix. |
| Claim pack | A folder | A claim’s submission set: the as-built, the programmes behind the analysis and its report. Packing again starts the next revision. |
| Letters | Word | Seven kinds of draft, from the register entries. |
| Deadlines | iCalendar file | The register’s due dates, for your calendar. |
| Analysis programmes | Gantt CSS programme | Any analysis view, saved as a programme of its own. |
Before you buy
| Licence | Planning. This is an add-on: every order includes Planning, and add-ons are bought on top of it. |
|---|---|
| Sold | Per named user, per year. |
| PCs | Windows 10 or later. Gantt Planning issues a licence for each of up to two PCs per named user; to move one, choose Release licence in the app and ask us for a new one. |
See Gantt CSS on a programme like yours.
We will walk you through Gantt CSS on the sample programme or on a file of yours.