Give every asset a maintenance record your team can use.

In this guide

Make the asset record a reliable maintenance reference

An asset register becomes useful when it connects equipment identity to work, procedures and history. More fields do not automatically make the register more trustworthy. Start with identifiers that the people finding and repairing equipment can recognize, then add information needed for service decisions.

AI-generated editorial illustration; not a customer photograph or product screenshot.

Choose one durable asset code and keep it distinct from the equipment name. “Compressor” is a description; “CMP-02” is an identifier. Two compressors can share a model and still need separate histories. A serial number can support identity, but it should not be the only field technicians can search when the nameplate is hard to reach.

Clean the register before you import

The asset migration guide explains the accepted fields. Test your difficult records in a small preview before importing a whole register. An import passing validation establishes structural validity; it does not establish that the equipment is correctly identified.

Choose criticality for a decision, not decoration

If every asset is critical, the label cannot help prioritize work. Describe the consequence of losing the asset, the availability of a substitute, the expected recovery time and who approves the rating. Two identical pumps may have different operational consequences if one is a standby unit and the other is the only unit serving a process.

Criticality is not a substitute for a site risk assessment. It is a way to make an agreed prioritization visible in the maintenance record. Revisit the designation when the operating arrangement changes.

Prove identity, usage and history together

For a trial asset, record its site and meter unit, create a maintenance task, then inspect the completed job from the asset record. If you use QR labels, scan the physical label and confirm the expected asset code. A QR code that opens a generic list is a weaker handoff than one that identifies the intended equipment.

Use a meter example with a clearly labelled unit. A value of 1,250 means very different things in operating hours and kilometres. If a sensor or counter is replaced, document the baseline decision instead of rewriting history to make the new number fit.

Decide what belongs outside the maintenance register

Warranty records, depreciation, insurance values and maintenance history can refer to the same equipment while serving different purposes. Do not assume a CMMS is an accounting fixed-asset ledger. Decide which application owns financial values and which owns maintenance execution, then reconcile identifiers across them.

Use the QR label workflow and historical work import to test whether your register remains useful beyond its initial upload.

Decide what a useful asset record must answer

An equipment record should support a maintenance decision. The person finding the asset needs a clear identity and location. The planner needs the relevant procedures and current work. The technician needs earlier findings and repairs. A manager needs enough context to understand why work was prioritized or why a record was changed.

Begin with those decisions rather than the maximum number of fields the software offers. A register containing hundreds of incomplete fields may be harder to trust than a smaller record maintained consistently. Establish which information must be present before an asset enters routine maintenance and who owns each category of information afterward.

Use actual equipment during the trial. Walk to the asset, compare its physical identifiers with the record and ask a second person to find it independently. If they select a similarly named machine or need a verbal explanation of the location, improve the naming and hierarchy before importing the full register.

Distinguish physical identity from operating arrangement

A physical asset, its current site and the service it supports are related but different concepts. Equipment can move while retaining its service history. A replacement unit can take over the same operating role while requiring a new physical identity. Decide how your register represents those changes before they occur during an urgent repair.

AI-generated editorial illustration; not a customer photograph or product screenshot.

For an illustrative case, two pumps alternate duty and standby roles. If the record is named only “Duty pump,” its history can become ambiguous when the roles change. Stable physical codes allow the role to change without implying that one machine's earlier repairs happened to the other. Keep the operating arrangement in the appropriate descriptive or procedural context.

Similarly, a replacement motor may require a decision about the level at which the organization maintains history. Some teams track the motor as a separate asset; others treat it as a component of the parent equipment. Choose the convention that matches the maintenance decisions and supported record structure. Do not create a complex component hierarchy merely because it seems comprehensive.

Write the convention down with examples. Consistency across the register helps future users interpret the record, while undocumented exceptions recreate the same dependence on memory that the software is supposed to reduce.

Choose identifiers that survive ordinary changes

Use a stable internal asset code where possible. Descriptions can change as staff improve naming, and equipment can move between locations. A code should remain recognizable enough for the team to reference in a work order, import file or physical label.

AI-generated editorial illustration; not a customer photograph or product screenshot.

Keep external identifiers distinct. A manufacturer serial number, supplier reference or fleet registration can help identify equipment, but each has its own meaning. If a field is unknown, avoid inventing a value that looks authoritative. Record what is known and establish who will verify the missing information.

Preserve formatting during migration. Spreadsheet software can remove leading zeros or interpret an identifier as a date. Treat identifier columns as text and compare the exported CSV with the original source. A code that looks nearly correct can still break the link between the asset and its imported service history.

For a trial, include two assets with similar names and one code with leading zeros. Search and open the records as another user. Then use the same codes in a small completed-work import. This tests whether identity remains consistent across the operations that depend on it.

Make location information useful to the person finding equipment

Location descriptions should reflect how staff navigate the site. A building, room and recognizable asset code can be more useful than an informal nickname known only to a senior technician. Where room numbers repeat across buildings, include enough context to distinguish them.

Decide which location information belongs to the site or space hierarchy and which belongs in the asset's descriptive record. Avoid creating several competing spellings of the same place. During setup, agree on a small set of examples and review new records against them.

Moving equipment raises a history question. Confirm the new location and retain relevant evidence of the move through the organization's process. Do not infer that old work occurred at the asset's current location merely because the current record changed. If detailed location history is a mandatory requirement, demonstrate how the chosen product preserves it.

Walk through one request or work order using only the location information in the system. The tester should be able to identify the intended equipment without calling the record's author. That physical acceptance check is stronger evidence than a register that merely passes field validation.

Review criticality with the people who own the consequence

Criticality can help prioritize maintenance when its meaning is shared. It should reflect an agreed assessment of what happens if the asset cannot perform its required role. The same model of equipment can have different operational consequences in different locations.

Consider availability of a substitute, recovery time, the service supported and dependencies on other equipment. A standby arrangement may change the immediate consequence of a failure, while a long replacement lead time can still matter for planning. Keep the reasoning understandable rather than reducing the decision to an unexplained colored label.

The maintenance record does not replace the organization's risk-management process. Use the rating to make an approved prioritization visible. If the site arrangement changes, review whether the rating still supports the intended decisions. A criticality field that is never revisited can become stale while appearing precise.

During a pilot, ask the relevant operational and maintenance owners to review a small sample together. Discuss disagreements before applying the labels to the entire register. The objective is a repeatable decision that helps allocate attention, not simply a more colorful dashboard.

Link procedures without assuming every asset is identical

Two assets in the same category may have different models, operating conditions or approved maintenance requirements. A template can provide a useful starting structure, but the procedure and interval should be reviewed for the actual equipment.

Record the procedure reference and identify who maintains it. When a procedure changes, the organization needs to understand which assets it applies to and how completed work is interpreted afterward. Do not assume the current template alone proves what instructions were used for a historical inspection.

Test the link by creating a work item from the intended asset and reviewing the resulting instructions. A technician should be able to confirm both equipment identity and scope before starting. If the workflow requires a separate manual or site procedure, make that reference usable in the working environment.

Keep the approved technical instructions distinct from editorial examples on a software website. A generic pump or generator checklist cannot establish the safe method or acceptance criteria for every installation. Use the template library as an editable structure and retain the actual maintenance authority with the responsible organization.

Keep usage records compatible with the asset

A cumulative meter can support maintenance timing only when its unit and source are clear. Engine hours, kilometres and miles should not be mixed because they happen to be numeric. Review the asset configuration before recording a baseline or connecting an external source.

AI-generated editorial illustration; not a customer photograph or product screenshot.

For an illustrative hour-metered asset, a change from 2,450 to 2,480 represents thirty hours of recorded use. If a replacement counter begins at zero, accepting the new number without a baseline decision can make the service position misleading. Document how the organization reconciles lifetime use and the new counter.

Automatic integration adds mapping and freshness questions. Confirm the provider identifier, supported statistic and compatible unit. A successful connection does not prove that every asset received a current sample. Know who reviews stale or unexpected readings and what operational process applies while they are investigated.

Use the meter-based maintenance guide to test repeated, older and lower readings. The acceptance test should establish that the asset history remains interpretable, not merely that an integration logo appears in settings.

Migrate completed work after identity is stable

Historical maintenance becomes useful when the reader can connect it confidently to the intended equipment. Prepare the asset mapping before importing old work. A duplicated asset code or an unresolved name change can attach technically valid rows to the wrong history.

Preserve an unchanged source file and retain original record identifiers where available. The completed-work importer uses a separate format from the asset register. That distinction helps avoid turning an old service record into new operational work or losing the original date in a current activity report.

Test a small batch with an ordinary record, a retired asset and a duplicate source identifier. Review the preview and inspect the resulting work from the asset record. Compare titles, dates and source identity with the source file, rather than checking only the total number imported.

PreventiveHQ preserves the supported completed-work fields and provenance through its dedicated importer. It does not reconstruct every historical attachment, user identity or stock transaction from a summary CSV. Use the history migration guide to establish the exact contract and document any information retained in a separate archive.

Plan what happens when equipment is retired or replaced

Retired equipment can still have useful history. The organization may need to investigate an earlier failure, compare a replacement decision or retain service evidence. Decide how the record remains distinguishable from equipment currently available for routine work.

AI-generated editorial illustration; not a customer photograph or product screenshot.

When a new unit replaces an old one, establish whether it receives a new physical asset code and how the operating role is transferred. Do not automatically merge the histories merely because the replacement occupies the same position. A new serial number and different maintenance requirements can make that distinction important.

Review related schedules and labels as part of the retirement process. An obsolete active plan can generate unwanted work, and a physical label pointing at the wrong record can misdirect future reports. Keep the organization's changeover checklist explicit rather than assuming one status update completes every related action.

During a trial, use a fictitious retired record and verify how it appears during migration and ordinary maintenance navigation. The test should show that useful history remains identifiable without implying that the equipment is still operational.

Separate maintenance records from financial asset accounting

Maintenance and finance can refer to the same equipment while using different definitions and controls. A maintenance team needs work, condition and service history. Finance may need acquisition value, depreciation, disposal treatment and accounting ownership. Decide which application is authoritative for each purpose.

A maintenance record is not automatically a complete fixed-asset ledger. If financial reconciliation is required, use stable cross-references and demonstrate the proposed exchange. Avoid assuming that an accounting integration supporting purchase orders also synchronizes all asset values or depreciation entries.

Include that boundary in the purchase decision. A product can fit a maintenance workflow while leaving an appropriate finance process in another system. What matters is that the team understands the remaining work and can reconcile references without ambiguity.

Use a measurable register-cleanup pilot

Select a representative sample rather than the easiest records. Include similar equipment names, a moved asset, a retired unit, a meter and a record with incomplete identification. Ask the people who find and maintain the equipment to participate.

AI-generated editorial illustration; not a customer photograph or product screenshot.

Measure whether a second person can find the intended equipment, whether required identity fields are verified and whether recent work can be reconstructed. Count duplicate or ambiguous records in the selected sample before and after cleanup. State the sample and review method so the result can be interpreted honestly.

A cleaner register does not by itself prove lower maintenance cost or fewer breakdowns. It establishes a better basis for work and analysis. Once the records are dependable, the organization can investigate longer-term outcomes using defined populations and observation windows.

Use the asset CSV guide, QR label workflow and work-order guide together. The complete acceptance test is an asset that can be found physically, identified digitally and understood through its maintenance history.

How many fields should be mandatory at launch?

Require the information needed to identify the equipment and operate the chosen maintenance workflow reliably. Treat additional enrichment as owned work with a clear purpose. Making every available field mandatory can encourage guesses, while making nothing mandatory leaves the next user without enough context. Review the first sample with the people who will use it and adjust the convention before the full import.

Should we finish cleaning the whole register before trying the software?

You can test the workflow with a representative cleaned sample while the larger register is being reviewed. Keep the pilot boundary clear and avoid treating unverified records as accepted production data. The pilot should reveal whether the chosen identifiers, locations and history structure work for the team. Use that evidence to improve the remaining cleanup, rather than multiplying an untested convention across every asset.