> ## Documentation Index > Fetch the complete documentation index at: https://docs.loadmate.io/llms.txt > Use this file to discover all available pages before exploring further. # Track a warranty claim > Keep a dated record of a warranty problem — log every call, email, and visit, note what was promised, set the status, and build the evidence trail you may need if a claim turns into a dispute. Logging a problem is the first step. What usually decides a warranty dispute is everything that happens after it: the call where the dealer said they would look into it, the email that promised a part "next week", the visit where nothing actually got fixed. Each of those is easy to forget and hard to prove later. loadmate now lets you keep a dated record of the lot. Each time you speak to someone or send an email, you add a short update, and it joins a running timeline on the issue. When a claim drags on, you can show exactly what was said, and when — from a record you made at the time, not from memory. ## Your correspondence timeline Open any logged issue and you will see its timeline: a dated list of everything you have recorded about that one problem, newest at the top. Each update you add — a call, an email, a visit — becomes an entry, so the whole story reads in order, from the latest development right back to the day you first noticed the fault. A dated record matters most when a claim turns into a disagreement. Six months on, "they told me it would be sorted before winter" means little on its own. A line that reads "Phone call, 14 March — Sam at the dealership said the part was on order and would arrive within two weeks" is the kind of detail that settles an argument. The timeline turns a string of half-remembered conversations into something you can stand behind. ## Log an update Add an update while it is fresh, ideally the same day. Open the issue, tap **Log an update**, and choose what kind of contact it was. Choose the type of update: a **phone call**, an **email sent** or **email received**, an **in-person visit**, an **inspection**, **parts ordered**, **work completed**, a **letter** or other written correspondence, or a plain **note** for anything that does not fit the rest. The date defaults to today. If you are catching up on something from earlier in the week, change it to the day it actually happened, so the timeline stays true to events. Record the person's name and the dealer or company they work for. Months later, "Sam at the dealership" is far more useful than "someone at the shop", especially once staff have moved on. In your own words, put down what happened: what you asked for, what they told you, what was agreed. Keep it plain and factual — it is a note to yourself first, and evidence second. If they promised something — a callback, a part, a repair booking — note it and add a **by-when date**. loadmate then reminds you when it falls due, so a "we'll call you back next week" does not quietly slip past. Got a receipt, a quote, or a screenshot of an email? Attach it to the update, and it sits with that entry as part of the record. Save it, and the update appears at the top of the timeline. The by-when date is the quiet workhorse here. When a dealer says "give us a fortnight", set that date on the update, and loadmate surfaces it in your [activity and alerts](/tools/activity-and-alerts) when it is due or overdue — in the same place as your other reminders. There is nothing new to set up, and nothing to keep in your own head. ## The "Issue noticed" anchor Every timeline ends the same way: with an **Issue noticed** entry at the very bottom, built from the problem you first logged. It carries the original date you recorded and any photos you added at the time, so the starting point of the story is always in view beneath everything that came after. You do not add this entry, and you cannot lose it by logging updates — it simply anchors the record. However long the timeline grows, the first thing that ever happened stays put at its foot. ## Set the status Alongside the timeline, each issue carries a **status** that shows where the claim stands at a glance. You set it yourself, and every change is added to the timeline, so you can see when things moved. There are four to choose from: * **Open** — logged, but nothing has happened yet. * **In progress** — you are in contact and the claim is moving along. * **Resolved** — sorted out. loadmate lets you add a short note on how it was settled, which is worth doing while it is fresh. * **Disputed** — for when a dealer or maker will not help, or turns down a claim you believe is fair. Marking it **Disputed** flags the claim for follow-up, and it is your cue to lean on the record you have built. Changing the status never rewrites your history; it just adds a dated line noting the change, so the timeline stays complete. ## Remove an update Logged the wrong thing, or added an update twice? Press and hold the entry on the timeline and confirm to remove it. As with deleting anything in loadmate, it cannot be undone, so remove an entry only when you are sure it does not belong. The **Issue noticed** anchor stays put — it is part of the original issue, not a logged update, so it is not removed this way. To change the original problem or its date, edit the issue itself. Reading a claim's history is free for everyone, including demo and lapsed users: open any issue and view its whole timeline and status without Pro. Logging an update, changing the status, and saving the evidence PDF each require Pro. Demo data stays visible so you can see how a tracked claim looks, but it cannot be changed or exported. ## Where to go next Turn the whole dated record into a tidy, branded PDF you can hand to a dealer, maker, or consumer-protection body. Open a logged issue to read or change its details, manage its photos, or remove it. Capture a problem the day you notice it, with the date and a photo, and link it to the cover that applies.