A practical resource from Jonathan Egelston
Scattered emails, notes, and conversations are easier to review when they follow a consistent structure. Use these three worksheets to build a timeline, preserve a source trail, and keep unanswered questions visible. Copy the fields into your own document or spreadsheet.
1. Event timeline template
Fields: Event date and time | Neutral description | Source ID | Uncertainty | Next check.
Record one event per row. Separate the event date from the date a document was created or received. Label approximate times and record the time zone when it matters. Describe what a source records before adding an interpretation.
Worked example: a delayed delivery
This is a fictional example, not a client case. A customer remembers a Tuesday delivery promise. An order confirmation lists Wednesday. Tracking records delivery on Thursday.
- Monday: Order confirmation created; estimated delivery Wednesday (S01).
- Tuesday: Customer’s recollection of the promised date, recorded in a note on Friday (S02).
- Thursday: Tracking service records delivery at 2:14 p.m. (S03).
The records disagree about the expected date. They do not establish why, whether another promise was made, or whether the intended person received the package. The next useful check is the original message containing the delivery promise.
2. Source log template
Fields: Source ID | Creator and title | Creation date | Access date | URL or file reference | Statement supported | Limitations.
Assign a stable ID such as S01 to each source. Preserve the original when appropriate and keep your commentary separate. A screenshot can preserve visible information but omit surrounding context; record the URL and access date too.
Example: S01 | Retailer order confirmation | Monday | Friday | Original email | Estimated delivery Wednesday | Does not establish later promises or actual receipt.
Three articles repeating one announcement are not necessarily three independent confirmations. Follow their references to the originating document and record that relationship in the log.
3. Open-question template
Fields: Question | Why it matters | Source to check next | Person responsible | Status | Date reviewed.
Example: Was Tuesday promised in writing? | Explains conflicting expected dates | Original email or message | [Name] | Unresolved | [Date].
Keep questions narrow enough to investigate. Replace “What really happened?” with “Which document first states the promised date?” An unanswered question should remain a question until evidence supports an answer.
Review before sharing
- Trace important statements to their sources.
- Distinguish observations, recollections, and interpretations.
- Label approximate dates and missing information.
- Include material that challenges the initial explanation.
- Remove unnecessary personal details from the shared copy.
Save a dated working version. When information changes an entry, record the correction and its source. A useful summary lets another reader understand both the available information and its limits.
Related reading
Explore Finding Clarity in a Difficult Situation, Jonathan Egelston’s research approach, and the article collection. Learn more in the professional biography.
