Why cross-unit work loses its owner
When operations work crosses business units, admin can keep it moving by acting as a neutral follow-up function: tracking each handover between units, chasing the next owner, and escalating through an agreed sequence when work stalls. Admin does not take over the work itself. It makes sure someone in each unit has visibly accepted their part.
Groups with several business units, such as a manufacturing arm, a logistics company and a trading company under one holding, pass work between units all the time. A customer order is produced by one unit, shipped by another and invoiced by a third. Each unit has its own head, its own priorities and often its own systems. At every boundary, the work can sit in limbo because the sending unit thinks it is done and the receiving unit has not noticed it arrived.
Unit heads rarely chase each other's teams, because doing so feels like overstepping. A shared admin function has no such awkwardness. Inter-company charges add another layer, because finance in each unit also needs to know when work changed hands.
What admin follow-up covers and what it leaves alone
Keep the remit narrow so admin does not become a project management office by accident. Admin follow-up covers confirming that a handover was received, recording who accepted it, reminding owners when an agreed date passes, collecting the reason when something is stuck, and escalating when reminders do not work.
It does not cover deciding priorities between units, changing technical plans, approving spend or negotiating with customers. Those stay with the business unit heads and their operations managers. Write that boundary into the follow-up procedure so admin staff can point to it when someone asks them to make a call that is not theirs.
A practical test helps. If a task needs knowledge of the product, the customer or the plant, it belongs to operations. If it needs persistence, a record and a neutral voice, it belongs to admin follow-up.
An escalation sequence for stalled cross-unit work
An escalation path agreed in advance removes the politics from chasing. Each step should be quick, written and visible to both units. Agree it with every unit head before using it, and apply it the same way to all units.
- Admin confirms the handover with the receiving unit's named contact and records acceptance
- If the agreed date passes, admin asks the current owner for a status and a new date
- If no new date is given, admin notifies the receiving unit's operations manager
- If the work is still stuck, admin raises it with both units' operations managers together
- Unresolved items go on the agenda of the regular cross-unit operations meeting
- Only items that meeting cannot settle go to the group executive, with the history attached
Running admin and operations systems as one programme
Cross-unit follow-up depends on two kinds of record: the operations work item, which says what is being done and by whom, and the admin follow-up record, which says what has been chased and when. If those live in different places with no shared reference, admin ends up chasing from memory.
When a group decides to put both on proper systems, introduce operations tracking first, at least for the work types that cross units. Each work item needs a reference, an owning unit and a handoff point. Then set up admin's follow-up queue so every chase points at a work item reference. Roll out to one cross-unit flow first, such as order fulfilment between manufacturing and logistics, before adding others.
Agree data ownership at the start. Each business unit owns its own work items. Admin owns the follow-up history. The group operations lead owns the handoff definitions, meaning which work types cross which units and what counts as accepted.
Keeping the follow-up role credible
Admin follow-up only works if unit heads see it as fair. Report on all units the same way, including the unit admin reports into. Share a short monthly summary of handovers chased, items escalated and recurring causes, without naming individuals.
Use the recurring causes to fix the handoff design. If logistics keeps receiving orders without delivery addresses confirmed, the fix belongs in the manufacturing unit's release step, not in more chasing.
Admin staff doing follow-up also need standing. Introduce the role formally at a meeting of unit heads, so the first reminder from admin is not treated as an intrusion.
Talking to Fasttrade about it
Fasttrade's BukuOP covers work and task tracking, handoffs between teams, status and exceptions, and operating rhythm. BukuAdmin covers internal requests and cross-team follow-up. For groups with several business units, we scope with you how follow-up records relate to operations work, and whether anything should pass between the two systems.
Frequently asked questions
Which admin team should own cross-unit follow-up in a group?
Usually a group or shared services admin team rather than one unit's admin staff, so the role is seen as neutral. If no shared team exists, assign the role to the admin team of the unit that coordinates most handovers, and make its reporting cover all units the same way, including its own.
Does admin follow-up replace an operations manager?
No. Operations managers still plan, prioritise and resolve problems within and between units. Admin follow-up handles the routine work of confirming handovers, chasing dates and running the escalation sequence, which frees managers from chasing and gives them a clear record when they do need to intervene.
How do we stop follow-up becoming nagging that people ignore?
Keep reminders tied to agreed dates rather than sent on a fixed timer, make every message specific to one item, and move to the next escalation step when a reminder is ignored rather than repeating it. People respond when they know the next step is a conversation with their manager.
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.