Five steps in, one structured claim out: contractual basis, facts, cause and effect, time impact, cost reservation, annexures. Every sentence traceable to an input, every gap marked, every page stamped draft for expert review.
The objection is fair: nobody should trust a robot with a claim worth crores. So the drafting engine is fenced in, and the fences are the product.
The system prompt permits only the dates, events, clause references, and evidence you entered in the wizard. It cannot state a fact you did not give it.
Each factual sentence cites the evidence reference it was built from, in the form (E-041), and the annexure list is assembled from those references automatically.
Where a fact needed for a paragraph is missing, the draft inserts a bracketed gap describing what is needed. Where two inputs conflict, it flags the conflict rather than picking one.
| Step | What you do | What the engine does |
|---|---|---|
| 1. Contract basis | Tick the EOT grounds you rely on from the confirmed extraction | Carries the confirmed clause references into the draft |
| 2. Events | Select one or more delay events from the register | Builds the chronology from event and awareness dates |
| 3. Evidence | Check linked evidence and the gap checklist, attach more | Assigns reference numbers and prepares the annexure list |
| 4. Time impact | Enter affected activities, days claimed, and a short explanation per event | Writes the time impact section from your figures only; no programme parsing in the current version |
| 5. Generate | Review the draft, edit in the rich-text view, export | Produces the structured claim with the draft-for-expert-review banner on every page |
Introduction, contractual basis, statement of facts, cause and effect, time impact, reservation regarding cost or a prolongation cost section, conclusion, annexure list.
Every included event graded as served in time, window open, or window closed, with dates shown. A time-barred event is never dressed up as compliant.
Which of the thirteen evidence categories are covered for each event and which are missing, so site can be tasked while records can still be created.
Company letterhead text, numbered paragraphs, and an annexure list that matches the evidence locker. Word-safe fonts so it opens identically on the Engineer's machine.
Site establishment, idle plant, staff retention, and other direct costs entered line by line. Overhead formulas (Hudson, Emden, Eichleay) are offered as options for your expert to choose, never calculated by the app.
Upload the Engineer's rejection. Each ground is mapped to existing facts and evidence or marked as needing new evidence, and a response letter is drafted in the same register.
English and Arabic side by side for KSA and Qatar facing submissions, with the English version stated as prevailing and the draft banner in both languages.
DraftMyEOT 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.