Asset Management across departments: who sees what?
For physical assets, give each team the information it needs and limit edits to the people responsible for those details. Procurement needs the purchase history of a construction excavator; the site manager needs its location and availability; maintenance needs its service history. All three can use the same record without having the same edit rights.
Asset management across departments gets easier when you name the owner, the person holding the asset today and the people allowed to edit its record. If a tool goes missing, you know whom to ask. A technician logging a repair has no reason to change its purchase price.
Start with one shared record, not one shared permission
A useful physical-asset record connects an identifier (such as a tag or serial number), category, current location, assigned user or team, condition, availability, purchase details, service work and retirement status. Attach warranties and inspection certificates to the item. For stock or PPE, record quantities and movements at the level your team manages.
Say a facilities company maintains air-handling units in three buildings. A technician needs the unit ID, location, fault history and next service task; procurement needs the supplier and warranty. The building manager wants to know whether the unit can run and when it will be back. Separate spreadsheets can give them different answers. A common record lets each team see current details and edit its own part. Bulbthings has more on why equipment inventory spreadsheets fail.
Ownership is not custody. A department can own the budget for a vehicle while a depot looks after it and a driver has it for the day. Name a business owner for replacement and disposal decisions, a current custodian who knows where it is, and a record steward who corrects core details. One person can hold more than one of those jobs.
Who should see what? A starter access map
Adapt this access map to your own approval rules. “Edit” means permission to change the named information; it does not give someone control of the whole asset record.
| Team or role | See | Change or approve | Example |
|---|---|---|---|
| Operations or site lead | Assets in their area, location, status, assignments and open work | Assign custody, record moves and flag an item unavailable | Move a construction generator from yard to site |
| Maintenance or technician | Assigned equipment, instructions, fault reports and service history | Log inspections, parts used, repairs and return-to-service evidence | Service a manufacturing conveyor motor |
| Procurement | Purchase requests, suppliers, warranty, replacement needs and authorized costs | Enter purchase and warranty details; approve purchases under the company's policy | Order a replacement lab centrifuge |
| Finance or asset owner | Purchase and disposal evidence, costs and lifecycle status | Approve financial or disposal decisions within their remit | Retire an old delivery van |
| Employee, contractor or guest | Only the item details needed for their task | Report a fault, acknowledge receipt or submit a permitted status update | Scan a venue lighting rig's tag to report damage |
| System administrator | Access settings needed to support the workspace | Assign and remove access under an agreed policy | Remove a departed contractor's access |
Use the map to find gaps in responsibility. If maintenance can mark a machine ready, decide who signs off before anyone uses it. If procurement updates a supplier, operations should see the change in the shared record rather than copy it into another tracker.
Layer role, location and field access
A role sets the actions a person can take. Location limits the assets they can access, and field rules limit the details they can see or edit. Use all three when your business crosses sites.
A maintenance contractor at a hospital may need to view a pump’s ID and service instructions at one site, then log a repair. Keep purchase prices from other hospitals out of that view. A regional operations lead may need to see assets across sites without being able to rewrite repair notes.
Start with the least access that lets each person finish the job. Sign in as a London technician and try to find a London pump, view one at another facility and edit its supplier. Repeat with a temporary worker and someone who has changed jobs. The results tell you more than the role names do.
For temporary cover, assign an end date and a named approver rather than making the person an administrator. When they switch sites or leave, remove the extra access. If a site manager needs to see a repair record from another region, give them access to that work rather than opening every asset and cost field across the company.
A QR code on a tool can take a worker to a permitted action without exposing private fields. Decide which details an outside person may see and which actions they may submit before sharing access beyond your team. Bulbthings explains its role, location and field permissions on its collaboration page.
Make handoffs part of the record
For each handoff, record who sent the item, who received it and what changed. A tool can sit in a van headed to another site long after the record says “at site.”
- Purchase and receipt: Procurement adds the purchase and warranty details. The receiving team confirms that the item arrived, records its identifier and condition, and assigns an initial location. A construction business could do this for a new compact excavator delivered to the central yard.
- Issue and transfer: The current custodian records the move and the next custodian acknowledges it. For an entertainment company, that might be a wireless microphone kit moving from the equipment room to an event crew. Record where it came from, where it went, who took it and when.
- Fault and repair: A user reports the issue; operations marks the item unavailable; maintenance documents the inspection and work done. If a manufacturing forklift needs a safety repair, nobody should book it while its status says out of service.
- Return, replacement or disposal: An authorized person approves a return to use or a retirement. Keep the final condition, supporting document and decision on the same record so procurement can see whether repair or replacement makes sense next time.
When a handoff stalls, assign one team to chase it. Keep unacknowledged moves distinct from completed transfers. In a lab, the next team may have booked a shared instrument while the last team still has it in another room.
What makes the record audit-friendly?
An auditor or manager should be able to follow an item from receipt to its current state without piecing together email threads. Keep its ID, location and custodian, transfer dates, fault reports, work completed, supporting files and return or disposal approval together. Attach inspection or calibration evidence where the equipment calls for it.
For UK work equipment that requires inspection, the Health and Safety Executive says:
“The result of the inspection should be recorded and this record should be kept at least until the next inspection of that equipment.” – Health and Safety Executive
Decide who may correct mistakes and how to keep the old value or an explanatory note. If someone overwrites a location without a reason, you lose a useful clue when a construction tool goes missing. Review overdue handoffs, unassigned assets, incomplete repairs and former staff access. You need to set up these checks; they are not a claim that any app creates an immutable audit trail.
Keep physical assets separate from other kinds of asset management
Physical-asset workflows follow things that can be received, moved, used, serviced and retired: a vehicle, PPE kit, machine, stage light or refrigerator. IT asset management focuses on devices and software, including questions such as licenses and access to systems. Digital asset management organizes files such as photos, artwork and video, with rights and versions attached.
The boundaries overlap sometimes. A tablet in a warehouse can go missing, and IT still needs to manage its software. Let each team handle its part; the physical-asset record does not have to replace the IT system.
Put the policy to work without creating extra admin
Start with one asset category and a handoff your team regularly struggles with. A facilities team could use portable generators moving between buildings. Give each generator a stable ID and name its owner and custodian. Decide who can see each field, change its location, log a fault and approve its return to use. Try the process with real users before adding more categories.
Bulbthings keeps physical-asset inventory, tracking, maintenance and financial information together. You can customize its predefined roles with restrictions by location, asset category or profile field. From the mobile app, users can look up items with QR codes and take actions suited to their role. You can also share selected fields with non-users for limited actions such as logging an issue. For a mid-size team working across sites, that can replace a tangle of spreadsheets. You still need to decide who approves a disposal before setting up the roles.
Share the asset record with the teams doing the work, while limiting what each person can see and change. Give them clear responsibility for transfers and decisions, too. If your site teams still reconcile spreadsheets after every move or repair, try Bulbthings with one category and a few real handoffs, then expand what works.
Ready to simplify asset handoffs? Start your 14-day free trial of Bulbthings and see how one shared record works across your teams.