Excel for the register, Primavera for the programme, Word with last year's claim as a template, WhatsApp for the photos. It works, until a notice deadline passes unnoticed or a claim needs to be rebuilt from months of scattered records.
The tools are fine. The gaps are in the joins between them, and in the fact that none of them knows what your contract says.
The right tool for the programme, and mandated on most NHAI, metro, and Gulf mega-projects. Keep it. Attach extracts as evidence; enter time impact figures from it.
Where the submission lives and where the Engineer reads it. DraftMyEOT exports to Word, with numbered paragraphs and an annexure list, precisely so nothing changes at that end.
A perfectly good register, if it is started on day one, if the awareness dates are captured, and if someone computes the deadlines in the right working week. Usually two of those three fail.
| Job | Excel, P6, Word, WhatsApp | DraftMyEOT |
|---|---|---|
| Knowing your notice period | Someone reads the Particular Conditions and remembers | Extraction quotes the clause and diffs it against the standard form; you confirm before anything activates |
| Starting the register | Usually after slippage is visible | Under a minute per event on a phone, from day one, with event and awareness dates separate |
| Computing deadlines | Formula in a spreadsheet, calendar days, one weekend profile | Per-project weekend profile and holidays, calendar or working days, alerts at 7, 3, and 1 days |
| Keeping evidence | Phones, binders, Aconex exports, inboxes | Per-event locker with reference numbers, WhatsApp parsing, diary photo transcription, bulk correspondence import, gap checklist |
| Writing the notice | Copy last project's letter, edit by hand | Three-step generator, clause cited from your contract, numbered per your convention, logged against the event |
| Writing the claim | Rebuild from the last claim, weeks of nights | Five-step wizard, structured draft from your inputs only, gaps flagged, annexures auto-built |
| Proving what was sent when | Sent-items folder and memory | Status only advances when a letter is marked sent; drafted is never shown as served |
| Cost | Staff time, mostly unpaid overtime | USD 750 per pilot draft; per company or per project plans; never per seat |
Notice periods, time-bar wording, and LD terms extracted with the quoted clause; Particular Conditions diffs shown against the family baseline.
ProfiledEvent date and awareness date captured separately; diary photos and WhatsApp exports become dated, referenced evidence.
FiledDeadlines counted in the project's own working week; alerts at 7, 3, and 1 days to every admin and contracts manager.
Served in timeFamily-correct claim or notice drafted from your inputs only, exported to Word and PDF with a draft-for-expert-review banner.
IssuedDraftMyEOT is not a law firm and never claims to be. Every output is a draft, built to be reviewed and signed by your contracts lead or consultant.
No dates, events, or clause numbers appear that you did not supply. Every paragraph shows the evidence reference it was built from.
Each company's workspace is isolated, documents sit in private storage, and consultants see only the project they were invited to.
Send a contract, your delay events, and whatever records exist, tidy or not. A structured draft comes back in 48 hours. Not useful? Keep it, owe nothing.