# How to reconstruct project history before discussing a disputed milestone When you and a client remember a milestone differently, start with a shared chronology. Gather the scope, requests, deliveries, reviews and decisions that relate to the question, and make it possible for both sides to find the original records. Canonical: https://areinum.com/guides/reconstruct-project-history-disputed-milestone/ Language: en Updated: 2026-10-31 ## Set the question and date range Name the milestone and a question narrow enough to investigate, such as which version was sent or whether a later request affected the planned work. Decide which period and sources belong in the chronology. Include relevant email, chat, files, meeting notes, invoices and written approvals. Leave unrelated material out. Questions about fault, payment or legal rights may need a separate discussion. ## Record events alongside their sources Start with the earliest relevant scope, then add dated requests, deliveries, reviews and changes. Record the source type and an exact reference, such as an email subject and date. A saved file, a sent email and someone's memory are different kinds of evidence. Describe what the record actually shows. Receipt of a file is a different event from approval of it. If accounts conflict, keep both descriptions and references visible rather than choosing the one that best fits your position. 1. List the dated records and where to find them. 2. Mark a date as estimated when it comes from a recollection. 3. Name missing records or questions for the people who can help resolve them. ## A fictional milestone timeline In the fictional project, the client approved a brief on April 2, requested an additional homepage section on April 15 and received version 1 on April 25. A reply on April 26 confirms receipt. The project owner recalls verbal approval on April 28, but no supporting record has been found. The timeline records the reply as receipt and the later approval as a recollection. The next useful question is whether either side can locate a dated note or confirmation. The original worksheet preserves the complete fictional chronology. ## Review the chronology together Use labels such as source located, reported but undocumented, conflicting records and awaiting confirmation. Share the chronology with people who can correct it, and add a source for each correction. Record the remaining disagreement and who will handle the next question. The chronology helps prepare a factual discussion. If the parties need advice about rights or deadlines, refer them to the relevant agreement and qualified advice. ## Prepare the timeline with Areinum Ask Areinum Assistant to arrange the records you provide by date and identify gaps or conflicting descriptions. Check every event against its source before using the timeline in a discussion. ## Questions you may have ### Should I include a verbal recollection? Yes, if it is relevant. Label it as a recollection, record who supplied it and distinguish the reported date from the date it was documented. ### Does a receipt confirmation mean the milestone was accepted? Record what the reply says. Acknowledging receipt alone does not establish approval. ### What if two sources disagree? Keep both references and state the factual question. Ask the relevant people for additional context rather than silently choosing one. ## Sources and further reading - [Nightmare Client From Hell, r/freelance](https://www.reddit.com/r/freelance/comments/1to9m9h/nightmare_client_from_hell_please_help/): One freelancer describes conflicting accounts of scope, milestones, delivery and communication. The post presents one side of a particular project. Identity and events are not independently confirmed; the account does not determine legal rights. One freelancer describes conflicting accounts of scope, milestones, delivery, and communication in a specific project. This is a single self-authored Reddit account with unverified identity and one-sided claims. It does not establish what happened independently, typical industry practice, or legal rights. (2026-10-18) Download the original worksheet: https://areinum.com/guides/reconstruct-project-history-disputed-milestone/milestone-chronology.csv ## Milestone chronology register All people, dates, organizations, and project details in the worked example are fictional. | Event date | Event or record | Source reference | Record status | Milestone link | Open question | | --- | --- | --- | --- | --- | --- | | 2026-04-02 | Project brief approved by the client | Fictional email thread A, 2 April | Original record located | Milestone 1 scope | Does the brief name every deliverable? | | 2026-04-15 | Additional homepage section requested | Fictional email thread B, 15 April | Request recorded | Milestone 1 scope | Was a timing or fee change confirmed? | | 2026-04-25 | Version 1 sent for review | Fictional project folder, delivery note | Delivery record located | Milestone 1 | Is there a separate approval? | | 2026-04-26 | Client confirms receiving version 1 | Fictional reply to delivery email, 26 April | Receipt only; approval not located | Milestone 1 | Was an explicit decision recorded elsewhere? | | 2026-04-28 (reported) | Project owner recalls verbal approval | Fictional owner recollection logged 30 April | Reported but undocumented | Milestone 1 | Can either side locate a dated note or confirmation? | 1. Create one row for each dated event that could affect the milestone. Make the source reference specific enough for another person to find the original. 2. Record status describes the evidence available, not who is right. Keep recollections distinct from located messages and files. 3. Write unresolved factual questions in Open question. Leave the answer open until a source or named person resolves it. 4. The sample project and dates are fictional. This register organizes records for discussion and does not determine legal rights. ### Limits of this method - The source is an individual account, so it supports a recordkeeping example rather than a claim about how often milestone disputes occur. - This chronology is an administrative aid, not a legal assessment. Seek qualified advice for rights, deadlines, or dispute strategy. ## Related reading - [How to compare a client request with the original scope](https://areinum.com/guides/compare-client-request-with-original-scope/) - [How to separate feedback from approval of a specific version](https://areinum.com/guides/separate-client-feedback-from-version-approval/) Explore the demo: https://platform.areinum.com/ The demo is in English. Access may need to be arranged.