Mod list guide

How to Organize a Car Modification List

A practical guide to organizing a car mod list by category, status, evidence, and sequence using PinkSlips build workflows.

• A modification list should read like a map of the car. Start with what is installed, group it by the area it changes, and add the context a future owner or fellow enthusiast would need to understand the setup.
• Use categories as signposts
• Put each installed part where a reader expects to find it: intake and exhaust, tune, cooling, forced induction, engine, suspension and handling, aerodynamics, exterior, interior, or brakes. Category structure lets a visitor scan the build before opening every line.
• Keep the part name specific enough to identify it. Include the brand and model when known, then use the notes field for finish, revision, or installation context rather than packing every detail into the title. Consistent categories also make it easier to notice a missing supporting component or a duplicate entry.
• Every installed part has a category
• Names identify the actual product or component
• Planned and removed work is not presented as current
• Record the setup, not just the shopping list
• A turbo, tune, brake kit, or wheel is meaningful in relation to the rest of the car. Add a short note about its role, supporting hardware, or the stage when it was installed. If a part was removed, say so in the history rather than silently rewriting the past.
• Link brands or shops when the product record supports it, and attach a photo when the detail matters. The goal is a readable record that can be checked against the car, not a catalog of guesses. A short installation note can explain more than a long list of marketing terms.
• Add the supporting context
• Attach evidence for unusual details
• Preserve removed parts in history
• Keep status and sequence truthful
• Only mark a part installed when it is on the car. Put planned work in the project description or a dated note until it happens. When several parts were installed together, one timeline entry can explain the sequence while the mod list stays clean.
• Hanzo is a useful owner-recorded example of category structure: its public build groups 25 mods across power, cooling, chassis, aero, interior, and brakes. That organization describes one build's record; it is not a universal parts recipe. Treat every public setup as evidence of one vehicle's configuration.
• Label planned work as planned
• Use dates for installation stages
• Do not imply a recommendation from an example
• A review pass before sharing
• Read the list as someone seeing the car for the first time. Can they tell what is installed, where it belongs, and what evidence supports it? Remove duplicates, fix category drift, and update the cover image after major changes. Review brand spelling and product names so searches and future edits remain useful.
• Compare the list with the current photos and the latest history entry. If a component is visible but undocumented, add it or explain why it is unknown. If the list claims a part that is no longer present, move that context into history. This review keeps a polished page from becoming misleading.
• Photos or notes support unusual details
• Category names are consistent
• The current list matches the car
• Make long lists easy to scan
• Use the same naming order for every entry: brand, product, and the specific variant. Put measurements, finish, and supporting notes after the identifying name. Readers can then compare entries without decoding a different writing style in each category.
• When a build has many changes, give the major systems a clear sequence in history and let the modification list remain a current inventory. A reader should be able to answer both what is installed and how the setup arrived there. Those are related questions, but they need different fields and different levels of detail.
• Document uncertainty with precision
• Some cars have inherited parts, unknown revisions, or components whose exact model is difficult to identify. Use a broad but accurate label, explain what is known, and leave the uncertain field open. Do not turn a visual guess into a precise specification.
• If another owner later supplies a correction, update the current record and add a note about the source when useful. Accuracy improves through clear revision, not through pretending the first entry was final. A trustworthy mod list tells readers where confidence ends.