Head office wants to compare assets across several branches, but each branch uses the term “active” differently. One branch uses it for items currently in use, while another uses it for all items that have not been removed from its records. This difference makes it difficult to assess operational capacity and make procurement decisions, so branches need shared standards that still accommodate local needs.
When branch data is difficult to compare
Differences in terminology and data details
Complete records are not necessarily comparable. One branch may record locations by building name, while another lists only the organizational unit. As a result, head office cannot identify the physical location of items with the same level of precision.
A similar problem arises when staff combine an item’s condition with its usage status. The label “normal” alone does not explain that a machine is still in good condition but is not currently being used.
In multi-branch asset management, the asset management team first needs to identify terms that affect cross-branch decisions. Start by checking whether two staff members would select the same category when looking at an item in the same circumstances.
The impact on head office decisions
For example, the Bandung branch requests additional laptops, while the Semarang branch’s report lists several “active” laptops. If that label also includes spare devices and devices under repair, head office cannot yet assess how many laptops are available for use.
The solution is not to force both branches to work in exactly the same way. Head office needs to align the meaning of the information used to compare needs, asset availability, and oversight issues.
Develop data standards that are easy for branches to use
Define core data and its format
Head office should develop a data dictionary: a guide explaining the meaning of each field, the required format, and the permitted values. Include examples of correct and incorrect entries so staff do not have to interpret the rules themselves.
- Asset identity: a unique number that is not reused, with the manufacturer’s serial number recorded separately.
- Location: the branch code and physical location at the agreed level of detail.
- Condition: the physical state, such as good, slightly damaged, or severely damaged, with clear assessment criteria.
- Usage status: in use, spare, not in use, or under repair, according to the organization’s definitions.
- Responsible party: the person or unit responsible for the asset’s whereabouts and for updating its information.
If the group includes several legal entities, record the item’s location and its owning entity separately. An item located at a branch is not necessarily owned by the entity operating that location.
Head office also needs to manage changes to definitions. Appoint a standards administrator to assess branch proposals, record the reasons for changes, and set their effective dates so reports from different periods remain understandable.
Separate required data from local details
Required data helps head office compare assets across branches, while local details support work at individual branches. A branch with a workshop may need calibration schedules for certain tools, while a service branch may need to record devices by service room.
Branches may add local details as long as they do not replace core data definitions. If many branches begin to need the same information and that information affects head office decisions, the standards administrator can consider making it part of the shared standard.
For needs that are not yet covered, provide an exception record that includes the reason and the party responsible for reviewing it. Do not allow staff to create new categories without approval, because differences in categories will once again make comparisons difficult.
Create reports that highlight important differences
Compare data on the same basis
Head office reports need to use the same reporting period, asset scope, and definitions. When comparing the number of assets under repair, for example, explain whether the count also includes items awaiting inspection by a technician.
Alongside summaries for each branch, create exception reports listing records that do not comply with data rules or need checking. Examples include missing locations, duplicate identifiers, combinations of condition and status that require review, and information that has not been verified according to the organization’s schedule.
Do not immediately assume that every unusual combination is a recording error. A damaged asset that is still in use may indicate a real operational risk, so the report should request clarification rather than change its status automatically.
Define a follow-up workflow
For each finding, assign a responsible party, an agreed deadline, and evidence of resolution. As an example of a working rule, a branch administrator could be given three working days to check a missing location. If it remains unresolved, escalate the finding to the branch manager.
Separate the authority to update data from the authority to approve significant corrections. Branch staff can update operational information within their responsibilities, while a party appointed by head office reviews changes to an asset’s identity or owning entity.
Reports do not replace physical inspections or supporting documents. The team may only mark a finding as resolved after recording the inspection results, not merely after filling in a previously empty field.
Implement standards in a simple, focused way
Test them across different types of branches
Select branches with different activities, such as service offices, warehouses, and sites with technical equipment. Give staff at each branch the same asset examples, then compare how they record condition, usage status, and location.
This testing helps the team distinguish unclear rules from genuinely different local needs. If staff give different answers because a definition is too broad, improve the guidance before applying it to more branches.
- Make sure staff understand core terms without additional explanations from head office.
- Check whether examples of the same circumstances produce consistent categories.
- Make sure locations and responsible parties are clear enough to support inspections.
- Check whether branches can record specific needs without changing core data.
- Make sure every finding has someone responsible for follow-up and evidence of resolution.
Avoid overly complicated rules
Too many required fields can encourage staff to enter data carelessly. Make information mandatory only if the team needs it to make decisions or carry out oversight, not because it might be useful someday.
Understanding roles also helps staff enter data consistently. The principles of task allocation in the article on preparing finance and administration teams for an asset system change can help branches determine who records, verifies, and approves updates.
If a branch needs an additional category, first check whether that need can be recorded as a local detail. Add a core category only if its meaning is clear, it does not overlap with other categories, and it is genuinely needed for comparisons at head office.
Use the same data reference for decision-making
A single version of the data means that head office and branches use the same official records and definitions, not that they must view identical reports. Branches can still use local details, while head office gets a consistent overview and a list of issues that can be acted on.
During regular reviews, examine one actual decision, such as a procurement approval, and check whether asset definitions, branch updates, and verification results adequately supported it. This way, standards are assessed based on their usefulness in practice, not merely on how completely fields are filled in.
You can start with one cross-branch decision that is most frequently held up by differences in data.
Learn how Fisetra helps with asset control at fisetra.com.