Maintenance records
Build a Project-Car Log for Parts, Changes, Costs, and Proof
A useful build log shows what changed, when it changed, what it cost, and what evidence supports the entry. It does not pretend to certify the car.
Published 2026-08-23 ยท 8 minute read
Decide what the build log must answer
A project car can absorb years of parts, experiments, repairs, and half-finished plans. Without a consistent record, the reason behind a change often disappears before the part does.
A useful log is not a photo album or a running total alone. It should let you reconstruct the car at any point in the build and separate what you know from what you were told.
- What was the car before the project began?
- What changed, and why was the change made?
- Which exact parts were installed or removed?
- What did the change cost, including outside work?
- Which receipt, photo, measurement, or note supports the entry?
- What remains unverified, temporary, or due for follow-up?
Capture the car before the first change
Start with a baseline entry. Record the year, make, model, VIN or other useful identifier, current odometer reading, acquisition date, visible condition, known modifications, and documents received with the car.
NHTSA's VIN decoder returns information encoded in the VIN from manufacturer submissions. Use it to check basic identity details, but preserve any mismatch as a note instead of forcing the record to agree.
Take wide photos of the exterior, interior, engine bay, underside when safely accessible, dashboard reading, labels, and notable damage. Add close photos only when they explain a specific condition.
Label seller claims and old paperwork as prior-owner information until other evidence supports them. A stack of receipts may describe work, but it does not prove every part remains on the car.
- Identity: year, make, model, VIN or chassis identifier
- Starting point: odometer, acquisition date, and current condition
- Received evidence: title copy, receipts, manuals, photos, and notes
- Known gaps: missing dates, uncertain mileage, or unverified prior work
Give every meaningful change one record
Create the entry while the parts, packaging, and reason for the job are still in front of you. One record should describe one coherent change or service event.
Write what was completed, not what you intended to complete. Keep planned work in a separate list so an unfinished task cannot be mistaken for an installed part.
If a change spans several days, use one parent job with dated updates. Record the final configuration only after it is installed, checked, and ready for the next step in your process.
For settings such as ride height, alignment, tire pressure, or calibration, record the value, unit, source, and date. A number without context is hard to reuse.
- Date and odometer reading
- Goal, symptom, or reason for the change
- Work completed and who performed it
- Installed and removed parts with identifiers
- Measurements, settings, and source notes
- Receipts, invoices, and useful before-and-after photos
- Result, unresolved issue, and next check
Keep provenance and costs honest
For an important part, record the manufacturer, part number, supplier, purchase date, price, and any serial or batch number that matters. Photograph the label before installation hides it.
Note whether an original component was retained, sold, discarded, or transferred with the car. Do not call a component original, numbers-matching, period-correct, or authentic without evidence for that exact claim.
Choose one cost rule and keep it consistent. State whether totals include tax, shipping, tools, labor, machining, paint, tuning, alignment, and rework.
Project spend is not the same as market value. A complete cost history can explain where money went, but it cannot establish what another person will pay.
- Part cost
- Tax and shipping
- Outside labor or specialist work
- Consumables and machine work
- Rework, returns, refunds, and credits
Use this compact change-record template
Copy this block for each meaningful event. Leave a field blank or mark it unknown rather than inventing a detail later.
The final line matters. It keeps a completed entry from hiding the inspection, retorque, leak check, alignment, road test, or other follow-up that still belongs to your process.
- CHANGE: plain-language name
- WHEN: completion date and odometer
- WHY: goal, symptom, failure, or planned stage
- BEFORE: relevant condition, part, setting, or measurement
- WORK: completed actions and person or shop
- PARTS IN: maker, part number, supplier, and identifier
- PARTS OUT: retained, sold, discarded, or unknown
- COST: parts, shipping, tax, labor, outside work, credits
- PROOF: receipt, invoice, labeled photos, and source
- RESULT: observed outcome without a safety claim
- NEXT: unresolved item, next check, and due signal
- CORRECTION: later change that supersedes this entry
Correct the history without erasing it
Builds change direction. A part may fail, a measurement may be wrong, or an early note may turn out to describe another car. Preserve the old entry and add a dated correction.
A correction should name the earlier entry, state what was wrong, show the new evidence, and explain what changed in the current configuration.
For repeated tuning or setup work, save versions. A short sequence such as setup 1, test result, setup 2, and current choice is more useful than one note that gets overwritten.
At major milestones, export a snapshot of the history. Useful moments include acquisition, first start, first drive, paint completion, major inspection, sale, or long-term storage.
Know what the log cannot prove
A build log can preserve owner evidence. It cannot certify workmanship, roadworthiness, emissions compliance, legal registration, originality, title status, or value.
EPA policy states that federal prohibitions on emissions tampering and defeat devices apply for the life of covered vehicles and engines. State and local requirements may also apply.
Check safety recalls through NHTSA. Its VIN search has stated coverage limits, so a private note or an empty result should not be treated as a complete safety record.
An NMVTIS report covers title, brand, odometer, total-loss, and salvage indicators. The Justice Department notes that maintenance and recall information are outside its intended scope.
Use the applicable manufacturer instructions and qualified inspection for safety-critical work. Keep legal, title, recall, and inspection records beside the build log without presenting them as interchangeable.
ServiceVault is being built to group asset records, readings, parts, costs, receipts, photos, notes, and exportable history. It organizes owner evidence; it does not verify the car or the work.
Frequently asked questions
What should a project-car build log include?
Include the baseline identity and condition, then record each completed change with its date, odometer, reason, work, parts, cost, proof, result, and next check.
Should I record parts that I remove?
Yes when they affect configuration, provenance, safety, fitment, or future reassembly. Note whether each part was retained, sold, discarded, or is no longer accounted for.
Does a build log prove that a restoration is authentic or safe?
No. It preserves the evidence you entered. Authenticity, condition, safety, legality, and value require their own evidence and, when appropriate, qualified review.
Can I use a spreadsheet for a project-car log?
Yes. A spreadsheet can work if records stay linked to the correct car, files remain retrievable, corrections are visible, and backups preserve the history.
Sources and further reading
Related guides
Keep the next receipt with the job it proves.
Join the ServiceVault iPhone beta list for occasional product updates and small-batch TestFlight invitations.