Practical evaluation guide · Updated 7 September 2026
In this guide
Keep identity, service history and due work separate
Use one asset code consistently across the vehicle register, service log and work orders. Registration plates can change; the internal asset code should remain stable. The downloadable service log records the service date, meter unit, reading, observation, action, next due date and responsible person. It is a blank working structure, not an OEM service schedule.
Establish a reliable meter baseline
Choose miles, kilometres or operating hours for each vehicle. Confirm that historical readings use the same unit and distinguish a meter replacement from an ordinary reading. In PreventiveHQ, import the base asset and create its vehicle profile separately. Manual fuel entries can retain receipt cost and a meter reading; this is not a fuel-card or telematics connection.
Turn a row into owned work
A spreadsheet reminder has value only when someone acts on it. For each open defect, record an owner and a required action. Use the vehicle inspection template to record observations. Keep unsafe vehicles out of service until the repair has been verified. Establish service intervals from the vehicle instructions and operating conditions.
Move across in a controlled batch
Download the asset register CSV for the actual import. The separate fleet service log is a reference workbook and is not accepted as service-history import data. Pilot a few vehicles, reconcile their identifiers and meter values, then create their schedules and run one real job. Keep the previous service history available while you validate the new process.
Use the spreadsheet to make service history understandable
A fleet maintenance spreadsheet is useful when it connects a vehicle, a service event and the next action. It can give a small team a shared record before a more structured system is justified. Its value depends on consistent identifiers, dates and ownership, not on the number of coloured tabs in the workbook.
AI-generated editorial illustration; not a customer photograph or product screenshot.
PreventiveHQ's fleet service log download provides a blank CSV structure for recording those essentials. It opens in spreadsheet applications, but it is not a preconfigured workbook with automated formulas, reminders or dashboards. Use it as a working log and adapt the surrounding process to the fleet's approved maintenance requirements.
Start with a few vehicles and record recent service events from reliable source documents. Ask another person to interpret the resulting rows. They should be able to identify what happened, which vehicle it affected and what remains due without calling the person who entered the data. That is a useful first test of the spreadsheet's quality.
Understand each column before filling the log
The download contains asset_code, service_date, meter_unit, meter_reading, observation, action_taken, next_due_date, next_due_meter, responsible_person and source_reference. Each column has a different purpose. Keeping those purposes distinct prevents a row from becoming a long note that is difficult to review or migrate later.
AI-generated editorial illustration; not a customer photograph or product screenshot.
The asset code connects the event to the vehicle register. The service date identifies when the recorded work occurred. The meter fields preserve the usage context. Observation describes the condition reported or found, while action_taken records what was done. The next-due fields support the future maintenance decision, and the final fields preserve responsibility and the source reference.
Do not force unknown information into a plausible-looking value. If a historical document does not include a meter reading, retain that uncertainty rather than copying the current reading into an old event. A complete-looking sheet can be less trustworthy than one that clearly distinguishes known values from missing evidence.
Keep the vehicle register separate from the service log
The register describes the vehicle's identity and current context. The service log records events over time. One vehicle can therefore have one stable register identity and many service rows. Repeating the entire vehicle description in every service row makes it harder to update information consistently and can create several apparent versions of the same asset.
Use the same internal asset code across the register and log. Registration plates, depot assignments and local nicknames may change, so they should not be the only link between historical events and the vehicle. Keep a reviewed mapping if older documents use a different identifier.
Before adding a service row, check that the asset code belongs to the intended vehicle. This matters when several vehicles share a model or when a fleet number has been reused. A mistaken event can distort later maintenance review even though the description and date look reasonable on their own.
Record dates consistently and preserve their meaning
Use a consistent date format such as YYYY-MM-DD in the working log so that day and month are not easily confused. Check how the spreadsheet application interprets imported dates, especially when files move between regional settings. A displayed date is not proof that the underlying value matches the source document.
The service date should represent the event your process intends to record, usually the actual service occurrence. Do not silently substitute invoice date, data-entry date or planned date when those differ. If the source only provides one of those dates, keep the limitation understandable in the source reference or preparation notes.
When migrating to a dedicated history import, follow that import's date contract rather than assuming the working log's format is accepted unchanged. PreventiveHQ's completed-history flow uses its own validated schema and UTC dates. Prepare the destination file deliberately and retain the original log as supporting evidence.
Establish one meter unit for each vehicle context
A vehicle's distance and an engine's operating hours describe different kinds of use. Choose the relevant unit for the event and make it explicit in meter_unit. Do not combine miles and kilometres in a single sequence of readings without a reviewed conversion, and do not treat runtime as another distance field.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Review the source when a reading falls below a previous cumulative value. It may indicate a data-entry error, a changed unit, a replaced meter or a different vehicle. A spreadsheet will happily store the value, so the team needs a process for recognizing the inconsistency and recording the decision.
For an illustrative vehicle, a service at 82,400 kilometres followed by a later reading of 83,100 kilometres represents 700 kilometres of recorded distance. If the later entry is actually in miles, that subtraction is not meaningful. The unit check comes before the calculation, not after an unusual result appears in a summary.
Separate the observation from the work performed
The observation column preserves what was reported or found. The action column preserves the response. A row that contains only “service done” may not explain why the vehicle was attended to or what the technician actually completed. Use enough detail that a later reviewer can distinguish a routine service from investigation of a recurring defect.
Avoid turning an initial symptom into an unverified diagnosis. A driver may report a noise accurately without knowing its cause. The service record can preserve that observation and separately record the technician's findings and approved action. This makes the history more useful when a similar symptom appears later.
If several unrelated tasks are recorded in one visit, decide how your log represents them consistently. You may use separate rows sharing a source reference or a clear summary supported by the original work document. The important point is that later review should not depend on remembering an undocumented convention.
Treat next-due values as maintenance decisions
The log includes next_due_date and next_due_meter, but the presence of those columns does not establish a suitable service interval. Use the vehicle guidance, operating context and the team's approved maintenance plan to determine the next action. A blank template should never be mistaken for an OEM schedule.
Where both time and usage matter, record the rule clearly in the supporting maintenance process. A reader should understand whether either threshold can make work due and how the team reviews the result. Do not rely on two populated cells to communicate a rule that was never agreed.
Check the next-due value after completing service, especially if the work occurred earlier or later than planned. The baseline convention should be deliberate and consistent with the maintenance requirement. Copying the previous row and changing only the date can carry an incorrect threshold forward for months.
Keep source references useful without overloading the sheet
A source reference links the summary row to the underlying service evidence, such as a work-order number or supplier document reference. Use a convention that the team can retrieve later. A reference such as “email” is much less useful than an identifiable document or job number stored in the agreed location.
AI-generated editorial illustration; not a customer photograph or product screenshot.
The CSV does not embed attachments. If supporting files live elsewhere, maintain that archive with appropriate access and a clear naming method. Moving a file or changing a folder structure can break an informal retrieval process, so include document handling in the team's routine rather than leaving it to one person's inbox.
Avoid placing credentials, unnecessary personal information or unrelated confidential detail in the service log. The spreadsheet may be copied for planning or migration. Keep its content focused on the operational record and use the organization's established controls for the supporting documents.
Make the weekly review a repeatable task
A log becomes useful when somebody reviews it. Assign an owner for checking new service rows, upcoming due work and unresolved observations. The review should identify a next action and responsible person, not merely confirm that the spreadsheet has been updated.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Start with a small set of questions: which vehicles have due work, which entries lack evidence, which defects remain unresolved and which readings need clarification? Use filters or a separate working view if helpful, but keep the underlying records stable. Avoid sorting only part of a table, which can separate an asset code from the event that belongs to it.
Record decisions in a consistent place. If the review leads to a new job, make its ownership and reference clear. If no action is required after assessment, preserve the reason where the team expects to find it. The spreadsheet should support an accountable handoff rather than becoming an archive of observations without outcomes.
Recognize the limits of a shared workbook
Spreadsheets can be flexible and familiar, but that flexibility also allows inconsistent values, overwritten formulas and competing copies. The practical limit depends on the team's workflow. A small, disciplined log may serve a few vehicles well, while a larger group with multiple contributors may struggle to maintain reliable ownership and history.
Look for concrete symptoms before choosing a replacement: repeated duplicate records, missed handoffs, time spent reconciling versions or difficulty finding the latest service evidence. These are better reasons to evaluate software than a general belief that every spreadsheet is inadequate. They also become measurable acceptance criteria for a trial.
A CMMS should solve the identified workflow problem. Importing the same ambiguous data into a new application will not automatically improve it. Clean the register and clarify the maintenance process first, then test whether the software makes that process easier to execute and review.
Compare free templates by what they actually provide
Free fleet templates vary. Some are simple logs, while others include multiple worksheets, formulas or calculated cost summaries. Fleetio's published spreadsheet offer, for example, describes maintenance records, vehicle information and cost-per-mile tracking. Its page also uses a form to provide the download. See Fleetio's fleet maintenance spreadsheet.
PreventiveHQ's downloadable CSV is a blank service-log structure with direct access. It does not include a cost-per-mile calculator or automatic reminder engine. If you add formulas or cost columns in your spreadsheet application, validate those additions separately and keep their definitions visible to the people using the workbook.
Choose the structure that supports your immediate task and future migration. A sophisticated workbook is only helpful if the team understands its inputs and maintains them consistently. A simpler log can be appropriate when the main need is reliable identity, service evidence and ownership of next-due work.
Prepare the register for a controlled migration
When the team is ready to evaluate PreventiveHQ, use the separate asset-register CSV for the actual asset import. The fleet service log is not accepted directly as an asset file or as the completed-history import schema. Map the relevant data into each documented destination rather than renaming the file and hoping the columns match.
Create active sites, reconcile unique asset codes and verify meter baselines before previewing the register. Import a few representative vehicles and inspect the resulting asset records. Vehicle profiles are created separately from the base asset import, so include that step in the pilot plan where the fleet workflow requires it.
Keep the service log available while preparing historical data. The work-order history guide explains the separate completed-record contract. The Excel-to-CMMS guide covers register preparation, preview and reconciliation. These are connected steps with different data requirements.
Test one complete vehicle maintenance cycle
Choose a vehicle with a clear service requirement and reliable source information. Create or import its asset identity, establish the relevant schedule and run one real maintenance job through the proposed workflow. Check that the team can find the vehicle, understand the task and record the completion evidence.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Include one realistic exception, such as a reading needing clarification or a defect that requires follow-up work. A pilot consisting only of ideal records may miss the situations that consume most administrative effort. Record what remained manual and whether the responsible person could complete it consistently.
At the end, compare the workflow with the original spreadsheet process. Measure lookup effort, missing evidence and clarity of ownership using the same task boundary. Do not claim lower breakdown rates from a short administrative pilot. The immediate purchase decision is whether the team can maintain a more trustworthy and usable service record.
Keep the log maintainable after the initial cleanup
Set a regular review for the data conventions as the fleet changes. New vehicle types, outsourced service providers and meter replacements can introduce information that the original sheet did not anticipate. Update the process deliberately and explain the change to contributors instead of allowing each person to create a separate convention.
Retain a recoverable copy before major restructuring. If you add formulas, test them with known examples and make it clear which cells are inputs. If the workbook becomes an archive after migration, mark the cutover date and identify the system used for new operational records.
Use the vehicle inspection template to organize approved observations and the fleet maintenance software guide to evaluate the connected workflow. The spreadsheet is worth using when it helps the team make the next maintenance decision with clear evidence and responsibility.
A worked review of one service row
Imagine a van identified as VAN-014 has a recorded service date of 2026-08-14 and a reading of 64,200 kilometres. The observation states that the visit was scheduled maintenance, and the action refers to the completed approved service document. The source reference identifies that document, while the next-due fields reflect the reviewed maintenance plan. A later reader can now distinguish the event, its evidence and the future requirement.
If the next row shows a lower reading, investigate before using it in a distance calculation. The problem may be a unit change, typing error or counter event. Preserve the original entry in the preparation history and record the correction's basis. Do not erase the discrepancy without understanding it.
What should we review before sharing the workbook?
Confirm that the recipient understands the date convention, meter units, asset-code scheme and meaning of blank values. State whether the file is a current working copy or an archived snapshot. If it includes links or references to supporting records, check that the intended recipient can access those records appropriately. A shared file is useful only when its context travels with it.