Dispute Evidence Timeline
Dispute Evidence Timeline assembles a chronological evidence record from the full project archive — emails, meeting minutes, RFIs, model revisions, and contract notices — for delay claims, scope disputes, and defect-liability questions. It walks the record, surfaces claim-relevant events, and emits a cited timeline ready for counsel, available now as a Labs engagement under MSA + Appendix.
- Chronological evidence timeline assembled from the full project record.
- Every event cited to its source document, email, or model revision.
- Timeline format calibrated for legal review (counsel-friendly, claim-ready).
From reconstruct-the-record to read-the-record.
Workflow today
-
01
Dispute arises
Month 6+. An owner files a delay claim or raises a scope dispute. Internal and external counsel ask for the full project record: emails, RFIs, meeting minutes, model revisions, change orders, and contract notices. The team realises the “record” lives across personal inboxes, shared drives, CDEs, and the model server, with no single dispute evidence timeline in view.
Month 6+ -
02
Junior staff trawl the archive
Week 1–4. Junior staff export email threads, scrape RFI logs, copy meeting minutes, and track model revisions by hand. They try to reconstruct who decided what, when, and based on which drawing or instruction. Hundreds of senior-staff review hours disappear into checking whether a single event is documented or buried in an inbox.
Week 1–4 -
03
Counsel reviews thin evidence
Week 4+. Counsel receives a spreadsheet or slide deck with obvious gaps. Some RFIs do not match the drawings on file, some design decisions lack meeting notes, and some change orders do not line up with contract obligations. Emails in personal mailboxes or chat logs never make it into the file, so the legal position looks weaker than the actual record.
Week 4+ -
04
Settlement under-resourced
Month 8+. The firm negotiates or litigates from a partial view of the project history. Delay responsibility, scope creep, and defect-liability arguments rely on memory instead of a complete archive. Claims teams know the evidence exists somewhere in the project memory, but reconstructing it for each dispute is too slow and expensive to repeat.
Month 8+
Workflow with VitruAI
-
01
Run the agent against the project archive
Week 1, ~3 days. The firm’s team points the dispute evidence timeline workflow at the full archive: email exports, CDE folders, RFI and submittal systems, meeting minutes, model version history, change-order logs, and contract notices. The underlying Project Memory Agent indexes artefacts and aligns them by project, package, and date so that disputes can be read as a single record.
Week 1, ~3 days -
02
Agent assembles the timeline
Week 1–2. The workflow walks the indexed record and assembles a chronological event list. Each entry carries a timestamp, responsible party, short description, and a direct citation to the source artefact, including specific RFIs, drawing revisions, or minutes. Claim-relevant events are flagged, while routine or duplicate traffic is down-ranked so counsel can focus on the decisions that move time, scope, or cost.
Week 1–2 -
03
Counsel reviews flagged decisions
Week 2. Internal or external counsel reviews the agent’s relevance flags and confidence scores, editing or reclassifying where needed. They can jump from a disputed delay milestone to the underlying RFIs, contract-clause monitoring history, and any related scope drift detection events. The review focuses on judgement, not hunting for documents.
Week 2 -
04
Timeline ready for filing
Week 2–3. The team exports a cited timeline in the format counsel prefers, aligned with the construction programme and any project timeline drift analysis already completed. Each row points back to the original email, meeting minute, model revision, or notice, so the evidence pack is traceable for disclosure and cross-examination. The firm enters negotiation or litigation with a claim-ready, audit-friendly record.
Week 2–3
Dispute Evidence Timeline — common questions
-
Is this admissible as evidence?
The workflow assembles a structured timeline; admissibility always tracks the original artefacts, not the compilation step. Each event in the dispute evidence timeline cites back to the source email, RFI, meeting minute, model revision, or contract notice. Counsel decides which underlying documents to disclose or submit, just as they would with a manually assembled chronology.
-
What about privileged communications?
Privileged communications, such as attorney–client email threads or counsel-marked memos, are excluded using a configurable filter. Each Labs engagement starts by encoding the firm’s privilege rules, folder structures, and sender domains so the agent reads only with explicit permission. The configuration can treat legal-mailboxes, marked documents, and counsel notes differently from general project correspondence.
-
How does this fit with the contract, scope, and timeline use cases?
Contract, scope, and programme workflows run during the project to prevent disputes, while Dispute Evidence Timeline runs after a claim appears to assemble evidence. It shares the same memory backbone as the Project Memory Agent and the Contract Agent, but exposes a different surface for counsel and claims teams. You can cross-reference contract clause monitoring, scope drift detection, and project timeline drift outputs directly inside the dispute record.
-
How does a Labs engagement work?
Labs engagements typically run 4–8 weeks under MSA + Appendix, scoped to one live or historic dispute. The VitruAI team calibrates the workflow against the firm’s privilege rules, archive layout, and counsel-preferred timeline format, including any specific columns or codes already used in claims schedules. The engagement ships a working agent for that dispute and folds the configuration and lessons into the productised release path for future projects.