Documenting
How to document a car build
What to record per modification, when to record it, and why the receipt matters as much as the part.
- Last reviewed
- 2026-08-15
- Reading time
- 5 min
- Applies to
- Any modified vehicle, any platform. This is method, not specification.
Most builds are documented twice. Once badly, in real time, across a phone camera roll, a forum thread, three vendor order confirmations and a spiral notebook in the garage. Then once properly, in a panic, the week the car goes up for sale, reconstructed from memory and whatever survived.
The second pass is always worse. Part numbers are gone. Install dates become "about two years ago". The receipt that proved a part was genuine is in an inbox nobody can search anymore. The work was real; the record is not.
Documenting a build as it happens is not more work than reconstructing it later. It is less. What follows is the method.
Record the modification, not the purchase
An order confirmation is not a record of a modification. It says money left your account. It does not say what went on the car, when, at what mileage, or whether the part in the box is still the part on the vehicle three years later.
A modification record answers those. At minimum:
- What it is, named the way you would say it out loud rather than the way the invoice lists it.
- Brand and part number. The part number is what turns a mod list from a story into something a buyer or a shop can verify. It is also what you will search for when you need the same part again, or the gasket that goes with it.
- Install date and odometer, together. A date tells you when. Mileage tells you how hard the part has worked. Neither is sufficient alone, and the pair is what lets you answer "how long has that been on there" honestly.
- Cost, split between parts and labor if it went to a shop.
- Who fitted it. This matters at resale and it matters when something needs diagnosing.
Everything else belongs in notes: the reasoning, what it replaced, what it needed alongside it. Notes are where a build record earns its keep.
Capture at the moment of maximum knowledge
You know the most about a modification while the car is still on the stands: which fasteners fought you, what the old part looked like, the supporting piece you had to order mid-job. A week later that detail is compressed to "did the intercooler". A year later it is gone.
So the rule is unromantic: log it before the car comes off the jack stands. A photo of the old part next to the new one, the part number from the box, the odometer reading, and two lines of notes. Three minutes, once, while the information still exists.
If you cannot do it then, do it that evening. The decay curve is steep.
Photograph the things that will be invisible later
Once the car is assembled, most of a build is hidden. Take the photographs that only exist during the work:
- The old part, showing its condition and why it was replaced.
- Anything that will be buried: routing, brackets, the back side of a mount.
- Part numbers, casting marks, and labels, close enough to read.
- The odometer, occasionally, so a photo can be dated by something other than metadata.
A photograph of a finished car is marketing. A photograph of the thing behind the bumper is documentation.
Keep the receipt with the record it proves
A receipt attached to a modification is evidence. A receipt in an email archive is a search problem you have handed to your future self, and one that a buyer cannot verify at all.
Attach it to the record. Photograph paper receipts before the thermal print fades, which it will.
Write down what a modification needed
The single most useful note on a build record is what the modification turned out to require beyond itself: the clamps that did not come in the kit, the coding that had to happen afterward, the alignment the suspension work made necessary, the part you had to buy twice because the first one was wrong for your exact car.
That note is worth money the next time you plan work, and it is the thing forum threads are worst at retaining.
Record the reversal too
A build is not append-only. Parts come off. Something gets sold, or goes back to stock before a sale, or fails and is replaced under warranty.
A record that only ever grows will eventually describe a car that does not exist. When something comes off, say so and say when. A mod list that is honest about what was removed is more credible than one that is merely long.
What "documented" should mean at the end
You have documented a build when someone who has never seen the car can answer, from the record alone:
- what is on it, by brand and part number
- when each thing went on, and at what mileage
- what it cost, in total and per item
- what was done by a shop and what was done at home
- what has been removed since
- and can see the receipt behind any line they doubt
That is also, not coincidentally, the answer set a serious buyer asks for. Builds that can produce it sell differently from builds that cannot.
Where BuildBay fits
This method predates any software and works on paper: the mod list and build sheet template has the columns above, and prints. Keep it in the glovebox if that is what gets it filled in.
BuildBay stores the same fields per vehicle, with photos and receipts attached to the record they belong to rather than in a folder somewhere, and rolls the costs into a build total as you go. The mod tracking page covers what that looks like in the product, and cost tracking is where the build total comes from. When you want to show the car without showing the receipts, a build page publishes a selected view and leaves the private half behind.
The tool matters less than the habit. Log it before the car comes off the stands.
Read next
- How to budget a car build
The cost categories people forget, and why supporting parts are where budgets actually break.
- Keeping maintenance records for a modified car
Why a modified car needs a better record than a stock one, and what to log when the book no longer applies.
In the product
Templates
- Mod listFree
- Maintenance logFree
Keep the record with the car
BuildBay stores maintenance, mods, costs, tools, and performance runs against the vehicle they belong to, private by default.