SteadyFile
Back to blog
timelinesrecordsdisputes

How to document a dispute: a neutral method for any situation

A plain method for documenting any dispute, at work, in a rental, with a business or over an agreement: dated entries, a timeline, an index and a packet.

9 min read

Quick answer

To document a dispute, keep one private file with a dated entry for each event, written soon after it happens and limited to what you saw, heard, sent and received. Give every document an ID in a records index, list the people involved by role, and arrange the entries into a single timeline. The method is the same whether the record involves an employer, a landlord, a business or someone you made an agreement with.

Then write down what is missing and what you want to ask, and assemble the entries, index and questions into a short packet that a lawyer, legal clinic, union rep, mediator or advisor can read in minutes. Documenting a dispute does not mean deciding who is right. It means making the facts easy to find, check and understand.

Why one party usually keeps the fuller file

In most disputes one party keeps records as a matter of routine. An employer has the personnel file, the scheduling system and HR notes. A property manager has the lease, the rent ledger and the maintenance tickets. A company has its account history and call logs. You probably have scattered texts, a few emails and a memory of what was said.

That imbalance is the reason to keep your own record. The point is not to build a weapon. It is to be able to answer simple questions accurately later: when did this start, who was there, what did you send, and what came back. Without notes, those answers drift within weeks.

  • Work: pay stubs, schedules, performance reviews, messages you received personally, and your own notes of meetings.
  • Rental housing: the lease, rent receipts, repair requests, photos of the unit, and notices you were given.
  • A business or company: receipts, order confirmations, account statements, chat transcripts and complaint reference numbers.
  • An agreement between people: the texts or emails where terms were discussed, transfers or payments, and anything either side signed.

The seven parts of a dispute record

Every useful dispute file has the same seven parts. You can keep them in a notebook, a folder and a spreadsheet, or in a single app. What matters is that each part exists and that the parts point to each other.

  • Dated entries: one per event, written as close to the event as you can, each showing the date it happened and the date you wrote it.
  • A timeline: the entries in date order, so a reader sees the sequence without having to assemble it.
  • A records index: a numbered list of every document, photo, message and receipt, with what it is and where the original is kept.
  • People by role: everyone who appears in the file, described by role (the supervisor, the property manager, the site lead) rather than by personal details.
  • A gap list: things you know happened but cannot yet support with a record, and records you know exist but do not have.
  • Questions for a reviewer: what you want a qualified person to help you understand.
  • A packet: a short, ordered export of all of the above that someone else can read without you explaining it.

Setting up the file, step by step

  1. Pick one place for the file and keep it out of any account someone else controls, such as a work laptop, a work email address or a shared tenant portal.
  2. Write a one-paragraph summary of the situation as it stands today, in plain words. You will revise it later; it helps you see the shape of the dispute.
  3. List the events you remember, oldest first, with a best-guess date for each. Mark estimated dates as approximate rather than inventing precision.
  4. Turn each event into a dated entry: what happened, where, who was present by role, what was said in close paraphrase, and which records relate to it.
  5. Gather the records you already have, give each an ID (R-01, R-02 and so on), and note in the index where the original lives.
  6. Link entries to records by ID, so a reader can go from a meeting on a given date straight to the email that followed it.
  7. Write the gap list and your questions as you go, instead of trying to fill every hole yourself.
  8. From now on, add a new entry the same day something happens, and never rewrite an old one without a dated note explaining the change.

Writing an entry a stranger can rely on

A reviewer reads your entries knowing they are your account. What makes them easier to rely on is restraint: specific times, direct observations, and a clear line between what happened and what you think it means. Short entries written the same day usually read better than long ones written a month later.

Sample entry for a rental repair dispute. Date of event: March 3, about 8:15 a.m. Written: March 3, 7:40 p.m. Place: kitchen of the unit. Present: me and the building superintendent. What happened: water was dripping from the ceiling light fixture into a pot. I showed the superintendent the fixture. He said he would send a plumber the following week. Records: R-07 (photo of the fixture, 8:20 a.m.), R-08 (text to the property manager, 8:45 a.m.).

  • Quote or closely paraphrase words. Instead of labels like rude or threatening, describe what was said or done.
  • Separate facts from impact. A short line such as Effect on me: missed two hours of work is fine, kept apart from the facts.
  • Write approximate when you are unsure of a time, and never fill a gap by guessing.
  • Leave out conclusions about motives or the law. The reviewer will form their own view.

Index the records and list people by role

The records index is what turns a pile of screenshots into something a reviewer can navigate. Each row needs an ID, a date, a short description, the source, and where the original is kept. A sample row: R-12, June 14, email from the account manager confirming the revised delivery date, received in personal email, original in an inbox folder named Dispute with a PDF copy in the file.

For people, write roles rather than biographies: the shift supervisor, the tenant in the unit above, the customer service agent who gave reference number 4471. Add how each person connects to the events and which entries they appear in. Keep personal details about others to the minimum the record needs, and leave out anything you obtained in a way you should not have.

What this looks like in four kinds of disputes

At work: your manager moves you to a new schedule after you raise a pay question. Your entries cover the conversation about pay, the email announcing the change, and the shift you missed because of short notice. Your index holds pay stubs and the schedule notice you received personally. Documents from employer systems that you were not meant to keep stay out.

In rental housing: a repair request goes unanswered for weeks. Entries track each request, each visit and each change in the condition of the unit. Photos are dated and indexed, and the gap list notes that one request was made by phone and has no written copy.

With a business: a subscription keeps billing you after you cancelled. Entries record the cancellation, each charge, and each call to customer service with the agent's first name or ID and the reference number. The index holds the confirmation screen, card statements and chat transcripts.

Over an agreement: a friend borrowed money for a car repair and agreed by text to repay it in monthly amounts. Entries record the conversation, the transfer, each payment received and each reminder. The index holds an export of the text thread and bank statements showing the transfers.

Gaps and questions: the part most people skip

A gap list is honest bookkeeping. It shows a reviewer what you know is missing, which is far more useful than a file that looks complete and hides holes. It also keeps you from chasing records you are not entitled to.

  • Records that exist but you do not have: a meeting summary someone said they would send, an inspection report, a supplier invoice.
  • Events with no written trace: a phone call, a hallway conversation, a payment made in cash.
  • Dates you can only estimate, and what might confirm them, such as a calendar entry or your phone's call log.
  • Questions for a reviewer, written neutrally: which records would be most useful to request, whether any time limits apply to my situation, and what options exist besides going to court.

Putting the packet together

A packet is the file presented for someone else. It should be readable in a few minutes, so keep this order and resist adding commentary.

  1. A one-page summary: the parties by role, what the dispute is about in one or two sentences, and the date range.
  2. The timeline of entries, oldest first.
  3. The records index, with copies of key records attached and labelled by ID.
  4. The people list by role.
  5. The gap list and your questions.

Share copies, never originals, and keep a note of exactly what you shared, with whom and on what date. The Department of Justice Canada describes negotiation, mediation and arbitration as alternatives to court, and each of those works better when the facts are laid out clearly. In the US, USAGov and the Legal Services Corporation list free and low-cost legal help if you want someone to review your packet.

Common questions

Is it too late to start if the dispute began months ago? No. Write entries for past events now, show the date you are writing each one, and be clear about which event dates are approximate. A late record that is honest about its timing is more useful than none.

Should I tell the other person or organization that I am keeping a record? That depends on your situation and is a good question for a reviewer. Keeping private notes of your own experience is different from collecting other people's information, which you should not do without permission.

Can I include messages other people sent me? Messages you received personally are usually part of your own records. Be careful with documents from an employer's systems or someone else's accounts, and ask a qualified person before using anything you are unsure about.

How much detail is too much? If a detail helps someone understand when, where, who or what, include it. If it is mainly about how upset you felt, keep it to a short impact line at the end of the entry.

Does a well-kept file guarantee a particular result? No. A record makes your account clearer and easier to check. It does not decide anything, and only a qualified person can help you understand your options.

Where SteadyFile fits

SteadyFile is built around this method. You can start a private file in the browser at app.steadyfile.com, on phone or desktop, without an account, and pick a file type: work, rental housing, or something else for a business, an agreement or money owed. Guided prompts help you write neutral dated entries, each record gets an ID in the index, people are listed by role, and the gap list, questions and readiness checklist sit alongside. With an account, the creation time of each entry is recorded and edit history stays visible. When you are ready, it exports a chronological PDF packet. No one else has access to your file, and the tool organizes facts without ever judging your situation.

Sources and further reading

These links informed the topic framing. They are provided for general information; SteadyFile does not endorse or control third-party sites.

Prepare the file, then get qualified advice

When a situation is sensitive, organize the facts and questions first. Then bring the packet to the person who can help: a lawyer, a legal clinic, a union rep, HR or another advisor.

Translations are provided to make SteadyFile easier to use. Legal terms may vary by location. SteadyFile does not provide legal advice.