Resources that end up shared between sites
Multi-site operations teams can share vehicles, equipment and rooms without constant clashes if admin keeps one booking register covering every site and both departments sign up to the same booking rules. Operations decides what work needs the resource; admin owns the register, the rules and the condition of the asset between bookings.
Sharing happens for good reasons. A company with a plant in Sendayan, a warehouse in Shah Alam and a service branch in Penang cannot justify a lorry, a forklift trainer or a set of test instruments at every location. So one site owns the asset on paper and the others borrow it. Over time, borrowing becomes informal: a phone call between supervisors, a note on a whiteboard, a WhatsApp message that the van is coming back on Thursday.
The informal system breaks when two sites need the same resource on the same day, or when an asset comes back damaged and nobody knows who had it last.
One register covering every site
Each site keeping its own booking sheet is the root of most clashes. A single register, readable by every site and edited under admin's control, removes the guesswork. Each entry should show the asset, its home site, where it is now, who has it booked and for what job, and when it is due back. Use the identifier painted or tagged on the equipment rather than a nickname, so the driver at the gate and the planner at the desk are talking about the same unit.
Admin owns the register because admin usually holds the ownership documents, insurance, road tax and service contracts for these assets. Operations planners at each site get permission to request and view bookings, and site supervisors confirm handover and return. That gives the register a clear chain: request, approval, handover, return, inspection.
Booking rules every site agrees to
The rules matter more than the tool. Agree them at a meeting of site heads and the admin lead, publish them, and apply them the same way everywhere.
- The home site has first call on its own assets, but must book them in the register like everyone else
- Customer-committed work outranks internal work, and safety-critical work outranks both
- Every booking names a job or work order, a responsible person and a return date
- Cross-site bookings include who arranges transport of the asset and who pays for it
- Handover and return are both confirmed in the register, with a note on condition
- Damage or faults found on return are logged before the next booking can start
- Unused bookings are released as soon as the job moves, not left to expire
Maintenance holds, breakdowns and inspections
Admin should block maintenance and inspection windows in the register before anyone else books those dates. Vehicles need servicing, lifting equipment needs periodic inspection under occupational safety rules, and measuring instruments need calibration. Confirm the inspection obligations for your equipment with DOSH or your safety adviser, and put each due date in the register as a hold.
Breakdowns need a fast path. When a booked asset fails, the site using it reports the fault through the register, admin marks the asset unavailable, and every affected booking is flagged to the planners concerned. Operations then decides which jobs to move and which need a substitute, while admin arranges the repair.
Keep the fault history on the asset record. A forklift that breaks every time it moves between sites tells you something about transport, handling or the asset itself.
Reviewing use and conflicts across sites
Once a quarter, admin and the operations heads should look at the register together. Which assets were booked most, which sat idle, where did clashes happen and how were they settled? An asset constantly fought over may justify a second unit; one that sits idle at its home site may be better relocated.
Look also at the conflicts that escalated. If the same two sites clash repeatedly, the rule set may need a specific clause for them, or their planners may need to share forward schedules earlier.
Record the decisions with an owner. Relocating an asset touches insurance, registration addresses and sometimes local permits, so admin needs time to process the change properly. Share the review notes with finance too, since relocations and new purchases change depreciation and insurance figures.
Moving the register into a shared system
A shared spreadsheet can carry a small fleet for a while. Beyond that, BukuAdmin can hold shared calendars and bookings alongside company documents, and BukuOP can track the operations work, handoffs and exceptions those bookings support. Fasttrade will work out with you whether bookings should reference work orders directly, and how any exchange between the two would be set up.
Frequently asked questions
Should each site own its own assets or should admin own them all?
Legal and financial ownership usually sits with the company, and admin holds the paperwork. Operational custody can stay with a home site, which looks after day-to-day care. The register should record both: who is responsible for the asset's documents and who is responsible for its physical condition. That avoids disputes when something is damaged on loan.
Who pays for moving equipment between sites?
Decide it in the booking rules rather than case by case. A common approach charges transport to the borrowing site's cost centre, since that site benefits from the job. Whatever you choose, the booking should record who arranges and pays for transport, so finance does not receive an unexplained lorry or courier bill.
How do we stop supervisors swapping assets informally?
Make the register the only accepted evidence of who had an asset. If damage or loss is traced to an informal swap, the sites involved explain it at the quarterly review. Pair that with a quick booking route that works from a phone on site, so the formal method is not slower than a call between supervisors.
Next step
Explore BukuAdmin or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.