Facilities and asset requests that block delivery work

How a missing asset stops a delivery job

Facilities and asset requests block delivery work when admin treats them as a general queue while operations has a customer job waiting on the outcome. The fix is to make every operations request to admin name the job it blocks, and to give blocked jobs a distinct status that both teams can see and act on.

The pattern is familiar. A new field engineer starts on Monday, but the laptop, access card and safety boots were never requested. A company van fails its inspection and the replacement booking sits in admin's inbox. The warehouse forklift needs a part and the repair purchase is waiting for a third quotation. Each item looks small to admin. To operations, each one has a customer, a promised date and a team standing idle. Neither team is careless. They work from different queues with different ideas of what counts as urgent.

Make every request name the work it blocks

Admin cannot prioritise what it cannot see. A request that says replace van tyres gives admin no reason to move it ahead of a meeting room repair. The same request saying the van is assigned to tomorrow's installation at a customer site in Seremban tells admin exactly what is at stake.

Take a cracked handheld scanner. Logged without context, its replacement waits behind routine items. Logged with the job reference, admin sees it is the only scanner on a picking line due to ship a customer order, and borrows a spare from another site the same afternoon.

Operations should mark the request as blocking and record the job reference. Admin should treat blocking requests as a separate lane, reviewed daily, with its own target agreed between the two department heads. Non-blocking requests continue in the normal queue.

This only works if operations is honest about what is blocking. If everything is flagged, nothing is. The operations head should review the blocking lane weekly and challenge flags that were really convenience.

Fields an operations request should carry to admin

Keep the form short, but make these fields required so admin never has to call back for basics. If it takes more than a minute to complete, supervisors on site will skip it and phone instead.

• Item or service needed, with model, specification or location of the fault
• Job, work order or project reference that is blocked or at risk
• Date the job needs the item, as promised to the customer or planned internally
• Person on site who will receive or use the item
• Whether a temporary workaround exists, such as a pool vehicle or loan laptop
• Cost centre and the operations approver for any spend involved

Triage on the admin side

When a blocking request arrives, admin first checks for a quick route: a spare from the pool, a loan from another site, an existing contract with a repair supplier. Most blocks clear this way if admin keeps an up-to-date asset register showing what is available and where.

If the request needs a purchase, admin applies the normal procurement rules but tells operations immediately how long it will take. Some companies allow a lighter quotation process for blocking requests below a set value; if you adopt that, write the rule down with finance and review its use.

Admin should also update the request status at each step: acknowledged, sourcing, ordered, ready for collection, delivered. Operations planners can then move job dates with confidence instead of guessing.

When admin cannot meet the date, operations needs to know early enough to reschedule the customer, not on the morning of the job.

Preventing the same block next time

Many blocks are predictable. New hires need equipment on day one, so link asset requests to the onboarding process HR already runs. Vehicles need servicing and inspection, so admin should keep a maintenance calendar and share it with operations planners. Tools and protective equipment wear out, so operations should report stock levels before they hit zero.

Hold a short monthly review of closed blocking requests. Group them by cause and pick one cause each month to remove. Over time the blocking lane should get quieter, which is the real measure of whether the handoff works. Share findings with HR and finance where they own part of the cause, such as late hiring notices or slow approval of repair spend.

Systems for requests and delivery work

With the blocking lane and request fields agreed, BukuOP can track operations work, status and exceptions, and BukuAdmin can run internal requests and cross-team follow-up. Fasttrade scopes with you whether a blocked job in operations should raise or link to an admin request, and how that exchange would work.

Frequently asked questions