In a webinar on data-driven asset management hosted by Kanwil DJKN Aceh, DJKN emphasized the importance of valid, integrated data in optimizing asset utilization. This principle is also relevant to companies that still consolidate multiple spreadsheets. Companies need to assess how much time they spend verifying records before making decisions.
The problem is not simply outdated files, but also the lag between asset movements, approvals, and record updates. Understanding this lag can help you assess whether spreadsheets are still adequate or centralized management is needed.
When data updates fall out of sync
Signs in the workflow
Imagine a projector being transferred from the head office to a branch for operational use. The branch team records its receipt in a local file, while the asset manager is still waiting for a handover form by email.
Meanwhile, the finance department retrieves a list from a shared folder to prepare a report. All three parties may be equally diligent, yet use different information because each updates data through a separate workflow.
A spreadsheet can store the latest location, but a change to one cell does not necessarily explain the transfer status. The transfer may have just been requested, already approved, or completed with the item received. Try tracing the most recent transaction: how many files and conversations do you need to check to establish its actual status?
Risks of leaving the problem unresolved
This uncertainty can trigger unnecessary purchases because an item is assumed to be unavailable. Transfer requests can also stall because responsibility is unclear. During an inspection, the team must gather evidence again from several places to explain the changes.
Spreadsheets are not always the problem in these situations. However, if keeping data in order depends on one person constantly reminding everyone else, the company needs to improve its workflow, not simply change its file format.
When a centralized system is more helpful
Requirements to consider
Spreadsheets may still be adequate when transactions are infrequent, only a few people manage them, and the team consistently retains supporting documents. Shared files with access restrictions and version history can also help maintain data for simple needs.
A centralized system is worth considering when you need several of the following controls at the same time:
- A single asset record used as a reference across locations and departments.
- Separate access permissions for submitting requests, approving them, and confirming receipt.
- Transaction statuses that distinguish requests from completed transfers.
- A change history recording who made a change, when, the previous value, and the reason.
- Supporting documents linked directly to asset transactions.
The benefit goes beyond gathering data in one place. With suitable features, asset management software can connect data updates with approvals and supporting evidence. Users no longer need to infer status from cell colors or free-form notes.
An example update workflow
In the projector example, a staff member requests a transfer by selecting the asset, destination, and recipient. An authorized person reviews the request, and the recipient then confirms the item’s arrival according to the established workflow.
Throughout the process, records need to distinguish the asset’s current location from the destination of a transfer that has not yet been completed. This prevents approval of a request from automatically being treated as proof that the item has arrived.
When evaluating asset management software, ask the provider to demonstrate this scenario from start to finish, including rejection and cancellation. Do not assume that all software offers multilevel approvals or equally detailed change histories.
Making a gradual, measurable transition
A readiness checklist before switching
Start by assigning responsibility for data: who is authorized to change locations, set asset statuses, and resolve discrepancies between records. Without a clear division of responsibilities, a new system merely moves old problems somewhere else.
Before migrating data, prepare the following:
- Assign an owner for each data group and a backup when that person is unavailable.
- Resolve duplicate asset identifiers, inconsistent location names, and fields with unclear meanings.
- Separate verified records from data that still needs clarification.
- Select one location or one transfer workflow for a limited pilot.
- Record baseline conditions, such as update times and the number of transactions lacking complete evidence.
Identifiers on physical items must also match digital records so staff do not update the wrong asset. The linked article on durable, easy-to-read asset labeling discusses how to keep asset identifiers legible during use. However, replacing every label does not need to be a prerequisite for data migration.
Transition mistakes
Importing all files at once may seem fast, but it can bring in duplicate data and conflicting statuses. It is safer to start with verified data while documenting unresolved issues and the people responsible for addressing them.
For the pilot, agree on when the new system becomes the primary reference and when spreadsheets will be used only as archives or report outputs. If two data sources remain active without update rules, the team will end up recording the same work twice.
Assess the results by comparing similar transactions before and during the pilot. Check whether updates become available sooner, approvals are easier to trace, and evidence can be found without requesting it again through private messages.
Pitfalls in choosing and using a system
Commonly overlooked risks
A tidy dashboard does not guarantee that its data is trustworthy. If anyone can change a status without a reason or delete history, a centralized system merely collects data without improving its management.
Another risk arises when user responsibilities are unclear. The system administrator should not automatically be responsible for ensuring that every asset movement matches the records. Technical authority is different from operational responsibility.
How to address them
Test permission boundaries, not just ease of data entry. Check whether requesters can approve their own requests, whether important changes are logged, and how staff make corrections without deleting history. Align the settings with company policy rather than simply accepting the defaults.
Also consider how the team works when connectivity is poor, a transaction is urgent, or a recipient has not yet confirmed receipt. Establish temporary recording procedures and identify who must complete them so that exceptional situations remain subject to oversight.
Those responsible for financial control should ensure that the team does not simply equate operational data with accounting records. A location change can help the team determine an asset’s whereabouts, but accounting entries must still follow applicable financial policies and processes.
Choosing the next step based on your needs
The decision to switch should be based on oversight needs, not on the assumption that spreadsheets are always bad or that a new system will solve everything. If every transfer keeps requiring the team to search for files, chase approvals, and gather evidence again, a centralized system pilot can show whether the workflow genuinely improves.
The right tool helps everyone involved understand asset statuses, authority, and history more clearly. Success is measured by the team’s ability to establish an asset’s latest condition and the reasons for changes without relying on one person’s memory.
A transfer workflow that frequently causes problems can be a starting point for assessing your control needs.
Learn more on the official Fisetra website.