Documentation guide

How to Build a Timeline for a Contractor or Warranty Dispute

Published September 8, 2026

You probably have the proof. You do not have the thread.

The contractor says the work was finished.

You have photos that say otherwise. A receipt from the first repair. Three emails. A warranty PDF. A text thread somewhere in your phone. Maybe a call note with a date you are no longer sure about.

The problem is not always missing evidence. It is that the evidence does not yet tell a story another person can follow.

A clear timeline changes that. It puts the records in order, separates what happened from what was said about it, and lets every important point lead back to the original source.

This guide shows you a practical way to do that for a contractor or warranty issue. It is not legal advice, and it cannot tell you what result you will get. It can help you make your records easier to review, discuss, and verify.

THE GOAL
Build a record that answers four basic questions: what happened, when did it happen, what supports it, and what happened next?

Start with the originals, not the story

When you are frustrated, it is tempting to begin by writing a long summary. Do not start there.

Start by preserving the materials you already have. Your first job is to keep the original records intact. Your second job is to organize copies for review.

1. Preserve the original records

Create one folder for the issue. Inside it, make a subfolder called Originals — do not edit.

Put copies of the original files there:

Photos and videos of the work, damage, repair attempts, or condition changes
Signed contracts, estimates, invoices, receipts, and warranty documents
Emails saved in their original form when possible, not only pasted into a new document
Screenshots or exports of relevant text conversations, including visible dates and participant names
Call notes, letters, inspection notes, and any messages from the contractor, manufacturer, retailer, or insurer

Do not crop, annotate, rename over, or edit the only copy of an original file. If you want to highlight a crack in a photo or add a note to a PDF, make a working copy first.

For materials that only exist in an app or inbox, save or export a copy while it is still available. Keep the original context visible when you can: the sender, recipient, date, subject line, conversation thread, file name, or photo details can matter when someone is trying to understand the record.

2. Use sensible privacy boundaries

Only collect and share records that are relevant to the issue. Keep your working folder in an account or device you control. Before sharing a packet, check it for unrelated account numbers, health information, addresses, children’s information, or other personal details that do not belong in the conversation.

If you make a redacted copy, label it as a redacted copy and keep the untouched original separately. Do not assume a PDF markup or a black box permanently removes hidden text; use a reliable redaction method when that level of removal matters.

Build a source inventory before you build a timeline

You are about to connect facts to records. That only works if you can find the record again.

Make a simple source inventory: a table with one row for every document, photo set, message export, or note. You can use a spreadsheet, a document, or a folder index. Keep it boring and consistent.

Source ID	Date on source	Source type	From / about	Short description	File name or location
`SRC-001`	May 12, 2026	Contract	Contractor	Signed driveway installation agreement	`2026-05-12_signed-contract.pdf`
`SRC-002`	May 20, 2026	Email	You → contractor	First written report of cracking	`2026-05-20_email-first-report.pdf`
`SRC-003`	May 21, 2026	Photos	Driveway condition	Wide shots and close-ups of cracks	`2026-05-21_driveway-photos/`

Use a stable ID such as SRC-001. The ID is not dramatic. That is the point. It lets you say “see SRC-003” without relying on a vague reference like “those photos from around May.”

Name working copies so time is visible

For your working copies, use a date-first naming pattern:

YYYY-MM-DD_source-or-event_short-description

Examples:

2026-05-12_contractor_signed-agreement.pdf
2026-05-20_email_reported-cracking.pdf
2026-05-21_photo_driveway-east-edge.jpg
2026-06-03_call-note_warranty-representative.md

If the exact date is unknown, do not invent one. Use the best available level of certainty:

2026-05 when you know the month but not the day
Before 2026-06-03 when the source only establishes a sequence
Date not shown when the material has no reliable date

Mark uncertainty clearly. A clean record is more useful than a falsely precise one.

Extract facts without turning guesses into facts

For each source, pull out only the details you can point to. That typically includes:

Date and time: When the source was created, sent, received, or taken
People and organizations: Who sent, signed, attended, inspected, promised, or responded
Work or event: Installation, complaint, inspection, repair visit, denial, follow-up
Amounts: Estimate total, invoice amount, payment, quoted repair cost, warranty term
What the source actually says or shows: A concise neutral description

Keep a hard line between three things:

Observed or documented fact: “Photo shows a crack near the east edge.”
Statement from a person or organization: “Contractor email says the crack is cosmetic.”
Your conclusion or question: “Was the condition reported within the warranty period?”

Those are not interchangeable. A source-backed timeline stays credible because it does not blur them together.

A quick extraction template

For every record, write a short note using the same fields:

SOURCE ID: SRC-003
DATE: May 21, 2026 (photo metadata / visible file date)
TYPE: Photo set
PEOPLE / ORGANIZATIONS: Homeowner
DOCUMENTED DETAIL: Multiple photos show cracks along the east edge of the driveway.
LINK: Folder “2026-05-21_driveway-photos”

If you take a call note, write the date, approximate time, participant, and the substance of the conversation as soon as you can. Label it as a call note. Do not present your note as a recording or a verbatim transcript if it is neither.

Turn sources into events, one line at a time

Now build the timeline. Each row should describe a single event and point to the source or sources behind it.

Date	Event	Neutral detail	Sources
May 12, 2026	Agreement signed	Contract identifies scope of driveway installation and warranty terms.	`SRC-001`
May 20, 2026	First written report	Email reports cracking and asks contractor to review.	`SRC-002`
May 21, 2026	Condition documented	Photo set documents cracks described in the prior email.	`SRC-003`
June 3, 2026	Warranty call	Call note records a conversation with the warranty representative.	`SRC-004`

Write the event in plain language. Keep the sentence short enough that a stranger can scan it quickly. If the event involves a dispute, do not write the conclusion as if it has already been proven.

Use: “Contractor email states that the issue is cosmetic.”
Not: “Contractor falsely denied the defect.”

The first statement tells the reader what the source says. The second statement asks the reader to accept a conclusion. Your record will be stronger if the reader can make their own connection from the source.

If dates conflict, show the conflict

Records do not always line up neatly. A photo may have an unclear metadata date. A call note may be written the next day. An invoice may list one date while an email describes a visit on another.

Do not force conflicting records into a clean sequence. Add an uncertainty note instead:

DATE TO VERIFY — Invoice lists June 8; email references a June 7 visit. See SRC-008 and SRC-009.

That is not a weakness. It tells the next reviewer exactly where to look.

Make every important claim source-backed

This is the standard that keeps a timeline useful: every meaningful statement should connect to the record that supports it.

Before leaving a line in your summary, ask: “Could someone open a file and see why I wrote this?”

If yes, add the source ID. If no, do one of three things:

Find the record that supports it.
Rewrite the line as a question or a personal note.
Remove it from the factual timeline.

Here is the difference:

Weak	Source-backed
The contractor ignored me for weeks.	No written response appears in the email chain from May 20 to June 2. See `SRC-002`, `SRC-005`.
The repair failed immediately.	Photos dated June 18 show the same area after the June 15 repair visit. See `SRC-011`, `SRC-012`.
The warranty should cover this.	Warranty document includes a section titled “Coverage.” See `SRC-006`.

The source-backed version is calmer, clearer, and easier to check. It also helps you see what you still need to find.

Prepare a packet someone can understand in ten minutes

You do not need to send every file you own. A useful packet is selected, chronological, and easy to navigate.

Start with a working packet in this order:

Cover page — Issue name, property or project reference if needed, and the date you prepared the packet.
One-page summary — A neutral overview of the timeline. Keep it factual and cite the source IDs used.
Chronological timeline — The event table, including date uncertainty notes where needed.
Evidence index — A list of every source ID, title, date, and one-line description.
Selected records — The contract, warranty, key emails, invoices, photos, inspection notes, and call notes that support the timeline.

Place a source label on each selected record in the working packet, such as SRC-003 — Photos, May 21, 2026. Keep the original file untouched in your originals folder; the label belongs on the copy you are organizing for review.

Keep the packet navigable

Someone reviewing your record should not have to hunt for the reason a document is included. Use a table of contents and page numbers. Keep photos near the event they document or group them under a clearly labeled photo exhibit. If a photo needs context, add a short caption on the working copy: what it shows, when it was taken if known, and which timeline event it supports.

Do not bury the reader in repetition. If ten emails say the same thing, lead with the key one and include the others only if they add a new date, response, promise, or detail.

Avoid these five record-killing mistakes

1. Editing the only copy

Preserve originals first. Annotate, crop, or redact only a working copy.

2. Letting memory replace the record

Write what the source shows or says. Label your own recollection as a note, and do not treat it like a contemporaneous document.

3. Mixing different issues into one timeline

Keep the contractor, warranty, insurance, and payment threads distinct unless a specific event connects them. A timeline is supposed to reduce noise.

4. Hiding uncertainty

If a date, sender, or event sequence is unclear, say so. Mark what you need to verify and cite the records that conflict.

5. Sending a folder dump

A folder full of unnamed files may contain the proof, but it makes the next person do all the work. Give them a timeline, an index, and selected sources.

Your next hour: a practical checklist

You do not have to finish the entire record tonight. Do this first:

Make an Originals — do not edit folder and save copies of the key records.
List every relevant file, photo set, email chain, text thread, and note in a source inventory.
Assign each source a simple ID: SRC-001, SRC-002, and so on.
Identify the earliest event, the first problem report, every response, and the latest update.
Add one timeline row per event, with a source ID on every row.
Flag gaps, conflicts, and missing dates instead of guessing.
Assemble a short working packet: summary, timeline, index, and selected records.

The point is not to make the record look dramatic. The point is to make it clear.

Founding beta: see the direction, help shape the workflow

Proofline is early. We are learning which record-heavy workflow to build first: contractor and warranty issues, insurance claims, medical advocacy, workplace documentation, or something else.

The current driveway-warranty demo is a fictional interactive example. It does not accept, retain, or analyze your files, and it is not a live case workflow. It is there to show the direction: a clear timeline with every important point linked back to a source.

If that is the kind of record you wish you had before your next call, explore the fictional demo and join the early-access list. For the planned offer structure, see Proofline pricing. Proofline helps organize records; it does not provide legal advice or guarantee an outcome.