Stop 6 of 9 · Weekly
The claim package
Entitlement, causation and quantum in one package, with every clause verified against the printed page and every assertion pointing at a numbered exhibit.
Three sections and a rule
Entitlement is the contract question: which clause grants relief for this kind of event, and were its conditions met. Causation is the factual question: what happened and how did it reach the completion date. Quantum is the money. Karim writes the first two and supplies the schedule findings that the third rests on. He does not write the third, and he does not write the legal characterisation of any of them.
The rule that keeps the package intact: every assertion has an exhibit, every clause has a page, every number has a source that is not a chat.
Notice comes first
Most claims that fail on public works fail on notice, not on merit, and they fail because the letter went to the wrong title, or went four days late, or described the event without invoking the clause. It is the cheapest section to get right and the one nobody checks twice.
From the contract and general conditions in this Project, and the correspondence I have uploaded, build the notice compliance table for the north headwall condition. Columns: the clause and page, what event starts the clock, the date I say it started, the deadline that produces, the letter that was served with its date and reference, and whether it is inside or outside. Add a row for every notice provision that could apply, including any in the special provisions. Where I have not given you a letter for a clause, say so plainly rather than assuming one exists.
Entitlement and causation
Draft the entitlement section for this claim from the contract in this Project. For each ground: the clause number and page, the operative words as printed, the conditions the clause requires, and against each condition the fact from my record that engages it with the document reference. Where a condition has no supporting fact, leave it in the list marked unsupported. Do not conclude that entitlement exists and do not use the words excusable or compensable.
[paste the chronology, the fragnet and the P6 run results] Build the causation chain as a numbered table: event, effect on the affected activity, effect on the path, effect on completion. One row per link. Against each row, the exhibit that proves it and the exhibit number. Mark every link where the only support is my own analysis rather than a project document, because those are the ones that will be attacked first.
The verification pass
The last thing Karim does before the package leaves is check it against the paper. Every clause number, every quoted phrase, every exhibit reference. This is the pass where a package that reads well becomes a package that survives being read by someone looking for a reason to reject it.
[upload the final package draft and the contract with all special provisions] For every contract citation in this draft, quote the words as they appear in the contract file, give the page, and say whether the draft has quoted or paraphrased them accurately. Flag any citation you cannot locate, any clause that a special provision amends, and any place where the draft relies on a clause that says something narrower than the draft suggests. Then list every exhibit referenced in the text that is missing from the exhibit list, and every exhibit in the list that nothing refers to.