Know which equipment you are servicing and what happened before

WorkOrderPro product guide · Updated 12 September 2026.

What an equipment registry does for a service business

An equipment registry records which maintained item belongs at which customer site. It gives the office and technician a stable point of reference across visits. Instead of repeatedly asking which unit a customer means, the team can look for identifying information and review the associated service history. This is particularly useful when one property contains several similar items or a customer operates multiple premises.

WorkOrderPro's equipment record contains the site, equipment type, make, model, serial number, installation date and warranty expiry where known. The equipment detail connects to service-history entries and their work orders. These records support a practical question: what do we know about this particular item before arranging or completing its next service?

A registry becomes useful through consistent identification and readable history. A long list of poorly described equipment is difficult to trust. Start with the items your business actually maintains, record what you can verify, and keep unknown information visibly unknown. The aim is to help the next person recognise the right equipment and understand the relevant previous work.

Start with the customer site

A site supplies the location context for an equipment record. Confirm the customer relationship and physical service location before registering an item. This matters when the billing address differs from the place of attendance or when a facilities contact looks after several properties. The same make and model can appear at several sites, so those details alone cannot reliably identify the intended item.

Use a site name that the office and attending team recognise. An ambiguous label such as “office” may work for one customer until a second branch is added. Include clear site information in the wider job brief so a technician can reach the correct place and then locate the equipment within it. The registry and the dispatch instruction should support the same understanding.

During setup, check a small sample of equipment against the physical location or existing trustworthy records. This is more useful than importing or copying a large list without review. A mistaken site association can send future service history into the wrong context, making the record harder to repair after several visits have relied on it.

Capture identifiers that distinguish similar items

Type explains the kind of equipment. Make and model describe the product family. A serial number, where available and legible, helps distinguish a particular item from other units of the same model. Capture these details carefully rather than assuming that a familiar appearance establishes identity. A transposed character can make a later search or parts enquiry unnecessarily difficult.

Where a label is unreadable, record only the information you can establish and explain the uncertainty through the appropriate service context. Do not invent a serial number to make the record appear complete. If the team uses a separate site label in its operating process, make sure staff understand how that label relates to the registered equipment and available fields.

Ask another colleague to identify the intended item from the saved record. If they still need to telephone the original technician for basic identification, improve the information before treating the registry as ready. The test is practical recognition across people and visits, rather than the percentage of fields containing some text.

Use dates as recorded information, not assumptions

Installation and warranty-expiry dates can be valuable, but their source matters. A date read from a reliable installation record is different from an estimate based on how old the equipment looks. Enter confirmed information where available and keep supporting context in the relevant job or service record. Unknown dates are more honest than a guessed value that later appears authoritative.

WorkOrderPro distinguishes equipment with recorded active, expired or unknown warranty information in the registry view. That classification follows the saved date. It does not determine whether a manufacturer, supplier or insurer will accept a claim. Coverage can depend on terms and circumstances beyond an expiry field, so the responsible person should review the actual agreement before making a customer promise.

For installation dates, decide how your team handles historical information discovered during later visits. The office should know who checks the source and updates the working record through the available process. Consistency is especially useful when older customer records use different date conventions or describe a replacement component rather than the original equipment installation.

Build a first register from a useful sample

Begin with a limited group of customer sites where repeat service already matters. Choose enough equipment to expose realistic identification problems, such as two similar units at one property and the same model at different properties. This gives the team a meaningful trial without spending the entire evaluation period collecting a large catalogue.

Prepare a simple source checklist: intended site, type, make, model, serial number and any verified dates. Check the information with the person who knows the equipment or the existing records. When details conflict, resolve the discrepancy or preserve the uncertainty rather than choosing whichever value makes data entry faster.

Find equipment before preparing a visit

The registry supports searches across make, model, serial number and type, with type and warranty filters. These are useful when a customer quotes a label, the office needs to locate a previous record or a technician is preparing for attendance. Use the search result as the start of verification, then inspect the site and history before assuming that the first match is correct.

For repeated work at the same property, review the relevant equipment before creating the field brief. A previous service note may explain an unresolved observation, a changed component or an access arrangement. Give the attending person the useful context without requiring them to read every historical entry during a busy visit.

Search quality depends on consistent source information. If people use several spellings for the same equipment type or copy model numbers inconsistently, retrieval becomes harder. Agree a small set of naming conventions that reflect your trade. Keep them simple enough that staff can apply them during ordinary work without needing a separate catalogue-management exercise.

Record service history against the correct work order

WorkOrderPro provides a service-history entry linked to equipment and a work order, with a note describing the service event. This connects the item-level story with the wider attendance record. The equipment history tells you what happened to the item, while the work order contains the customer, site, workflow and commercial context of the visit.

Before saving an entry, check the equipment and work-order references. Similar items can make it easy to attach a useful note to the wrong record. Explain the work or observation in a way that another technician can use. “Serviced” provides little help if the next person needs to know what was checked, what changed and what remains unresolved.

The visible service-history workflow adds entries rather than presenting a general edit-and-delete process. Treat each saved entry as something that deserves review before submission. Do not describe the history as legally immutable or as a substitute for a required technical certificate. It is an operational record whose usefulness depends on the accuracy and clarity of the information entered.

Write history for the next attending technician

A useful history note explains the reason for the visit, the relevant finding and the work performed within the author's competence. It should identify any unresolved next step that affects future attendance. Avoid shorthand that only the original technician understands, especially where another crew may return months later.

Separate observations from conclusions. A reported intermittent symptom, a condition observed during attendance and a proposed cause are different statements. Keeping them distinct helps a later technician understand what was actually established. The history should not turn an initial suspicion into a confirmed diagnosis simply because it has been copied into several subsequent notes.

Use concise detail rather than a large unstructured narrative. A future reader usually needs to understand the relevant sequence quickly. Reference the associated work order for the broader visit and use job photographs where the chosen workflow makes visual context useful. Images and timestamps support the account; they do not replace an understandable explanation of what happened.

Keep equipment history distinct from stock control

Customer equipment and the parts held in a vehicle are different operational records. The registry identifies the maintained item at a site. Stock control concerns quantities of parts or materials available for use. Replacing a component may affect both processes, but the equipment record should still describe the customer's item and its service history.

Do not assume that registering a unit automatically creates a stock item, a reorder rule or a purchasing task. Demonstrate the specific connection your business requires between the visit, used materials and any inventory workflow. A clear boundary helps avoid confusing the equipment's model number with the part number of a replacement component.

For office preparation, bring the information together deliberately. The registry can help identify the equipment and earlier work. The job brief can explain the intended attendance. The relevant materials process can address what the technician needs to take. When each record answers its own question clearly, the team can prepare a visit without overloading one screen with unrelated assumptions.

Handle replacement and changed site circumstances carefully

A replacement item should remain distinguishable from the equipment it replaces. Reusing an old identity without a clear process can make the new unit appear to have years of earlier service history. Before making changes, establish how your business will preserve the historical relationship and record the new identifying information through the available workflow.

Changes in customer ownership or site responsibility need similar care. The physical equipment may remain in place while the person authorising work changes. Review the customer and site context with the office rather than assuming that an old relationship remains current. Customer-facing access should follow the authorised account process, particularly when historical records include commercial or contact information.

During evaluation, include one replacement or changed-site scenario. Ask the team how they would represent it and inspect whether the resulting records remain understandable. If a required lifecycle action is not available in the current interface, identify the supported operational process before promising that the registry handles every asset-management scenario automatically.

Use warranty information to prepare the conversation

A recorded expiry date can prompt the office to review the applicable warranty documentation before quoting work. It can help the team ask a better question: should this proposed intervention be discussed with a supplier or manufacturer first? That is more useful than telling the customer they definitely have coverage solely because the registry shows a future date.

Inspect the equipment identity, installation context and service history when preparing an enquiry. These details may help the responsible party understand which item and event are being discussed. Keep any claim decision separate from the date-based status. A warranty that appears current does not prove that a particular fault or intervention is covered.

Connect repeat maintenance without promising sensor monitoring

Equipment identification can improve preparation for planned visits. The technician knows which item the work concerns and can review earlier history before attendance. The maintenance-contract workflow addresses recurring work generation, while the registry addresses identity and service history. Demonstrate how your team uses both in the intended process.

Do not treat a stored equipment record as a live monitoring connection. Recording a generator, pump or other maintained item does not establish that WorkOrderPro reads its operating hours, detects a fault remotely or predicts its next failure. Those capabilities would require a separately demonstrated integration and an appropriate operational response.

Your service interval should come from the relevant agreement and qualified maintenance planning, including manufacturer guidance where applicable. The registry can support the information handover, but it does not prescribe technical work or certify that the equipment meets a particular standard. Keep technical responsibility with the people qualified and authorised to make those decisions.

Review register quality during ordinary work

A useful register is maintained through repeated small checks. At attendance, confirm the item and note discrepancies through the office process. During closeout, review whether the service history describes the correct equipment and work order. This distributes quality control across real work instead of leaving a large cleanup for somebody who has never seen the items.

Choose a small sample for periodic review. Look for ambiguous identities, unknown dates presented as facts, unhelpful service notes and equipment attached to the wrong site. Investigate the cause of repeated problems. Staff may need a clearer naming convention, a better first-visit checklist or an explanation of how the next technician uses the history.

Avoid measuring success only by the number of registered items. A smaller reliable register can be more useful than a large list that nobody trusts. Measure whether the office finds the intended item, whether technicians recognise it and whether previous work informs the next visit. These outcomes relate directly to the service process the registry is meant to support.

Evaluate the complete equipment handover

During a trial, register representative equipment, locate it through search and add a service entry against the appropriate work order. Ask a second person to find the item and explain its latest service context. Include a case with an unknown warranty date and another with two similar units so the team must use the identifying details carefully.

Confirm equipment-registry availability on current pricing. Staff billing includes active administrators, dispatchers and field users, with disabled accounts excluded. Assess the plan around the people who prepare, perform and review the work, rather than only the employee entering the first equipment record.

Start a trial with a customer site where a clear equipment history would help the next visit. The strongest result is a record that another colleague can use without calling the original author for basic identification. Build the register around that standard, then expand it as the working process becomes reliable.

Teach the first service-history handover

During onboarding, have a technician create a sample service entry and then ask a colleague to prepare the next visit from it. The second person should identify the equipment, explain the previous intervention and recognise any unresolved issue. If they need clarification, improve the example together. This makes the expected writing standard tangible instead of relying on a vague instruction to add more detail.

Include a sample with missing identification information. Staff should know how to flag uncertainty and seek the correct source without filling the gap with a guess. Give the office a named contact for questions about site association and historical records. A short, repeatable handover exercise helps the register remain useful as new employees join and experienced technicians move between customers.