Consider a contested contractual notice. A team has spent days examining the sequence of instructions, assessing entitlement and preparing further work. A revised source later shows that the date underlying one of the issues may be wrong. What should happen to the existing analysis?
The useful response is not simply to summarise the replacement PDF. The team needs to understand which parts of the matter's working state rely on the earlier source.
1. An updated document does not erase the earlier evidential record
Older versions, citations and competing material remain relevant. A version relationship should be reviewable and approved, rather than inferred solely from a filename or upload time. The lawyer may need both versions to explain a discrepancy, not just the latest text.
2. Consequences can travel through legal issues
An existing task may not directly cite the document that changed. It may instead be linked to an issue that does. A conventional direct-citation search can overlook that relationship. Document Change Impact extends the review candidate set to tasks indirectly linked through affected legal issues and distinguishes those links from direct documentary support.
3. Identification is not a legal conclusion
Highlighting a task does not show that a notice failed, an extension of time is due or a pleading must change. It creates a review question: does the revised source materially affect the recorded assessment or next action? The answer depends on the contract, complete evidence, and applicable law and procedure.
4. A practical supervised workflow
- Confirm the documented relationship between earlier and later sources.
- Review the predecessor source and the altered passage.
- Inspect affected issue records, direct dependencies and any indirectly connected tasks.
- Test contradictions, missing materials and whether the original assessment remains supportable.
- Record the lawyer's decision and authorise any changes to case work through normal controls.
5. What the implementation has actually demonstrated
In an isolated synthetic test, the R1 A1 impact logic identified two issue-linked tasks that the earlier implementation did not include. Synthetic component and persistence-path checks passed, and a post-release authenticated browser smoke test found the application accessible. A complete populated-matter browser demonstration of those indirect links remains an outstanding acceptance exception. It would be inappropriate to claim universal dependency detection.
Conclusion
For a substantial documentary dispute, evidence management and matter management must remain connected. Finding a document matters; finding the legal work that may need reconsideration can matter just as much. The practitioner remains responsible for verification, completeness and adoption of any change.
Read the practical user guide →
Explore the Document Change Impact feature → · Watch the existing Document Lineage guide →