Cross-department admin follow-up when several teams are involved

Multi-team work needs one owner for the outcome

Cross-department admin follow-up works when one person owns the overall outcome, each team owns its own piece, and every handover between teams is recorded in a place everyone can see. When several teams are involved and nobody holds the whole picture, each department finishes its part and assumes someone else is checking the rest.

Take a new joiner starting at a regional office. HR confirms the start date, facilities prepares a desk, IT sets up a laptop and accounts, security issues an access card, and admin arranges parking. Each team may do its part well, yet the new joiner still arrives to find no access card, because the request reached security a day late and nobody noticed.

Offboarding shows the same pattern in reverse. Laptops, access cards and system accounts each belong to a different team, and one missed step leaves equipment unreturned or access still active after the person has gone.

The gaps sit at the handovers. A request moves from one team's system to another's by email, and the receiving team logs it differently or not at all. Dependencies are implicit: IT cannot set up email until HR confirms the employee ID, but HR does not know IT is waiting.

Each department also measures itself on its own queue. Facilities closes its ticket when the desk is ready, regardless of whether the rest of the onboarding is on track. Nobody is wrong by their own measure, and the combined result still fails.

Naming the lead owner and the contributing teams

For each recurring multi-team process, decide in advance which team leads. Onboarding is often led by HR or admin; office moves by facilities; event logistics by admin. The lead owner is not responsible for doing every task, only for knowing the state of each one and chasing when something stalls.

Contributing teams commit to a response time for their part and to updating the shared record when they finish or hit a blocker. Agree this with each department head, not just with individual staff, so it survives turnover.

The lead owner also needs the standing to chase other departments. If the person given the role is too junior to question a delay in IT or security, the role exists on paper only. Department heads should tell their teams that requests from the lead owner carry the same weight as their own.

What a handover note between teams should contain

A handover that only says please action wastes a day while the receiving team asks questions. A standard message for each recurring process means nobody has to remember what to include, and the receiving team learns to expect the same details in the same order. A useful note between departments carries:

• The overall outcome and the date it must be achieved
• The specific task the receiving team is asked to do
• Anything it depends on and whether that is already done
• Who the lead owner is and how to reach them
• Relevant details such as employee name, site, room or cost centre
• What the receiving team should do when finished, such as update the record or notify the next team

Making progress visible to everyone involved

The lead owner needs a single view of all the parts. At minimum this is a shared checklist per case listing each team's task, its status and the date it is due. Better still, each team's task is linked to the same case so updates appear without the lead owner asking for them.

Hold a short weekly check for processes that run often, such as onboarding, where the lead owner walks through open cases with a representative from each team. Cases with a blocked or overdue task get attention there, before the start date arrives.

Keep each case record after it closes. When the same handover fails repeatedly, for instance access cards arriving late at one site, the closed cases show the pattern and give the lead owner evidence to raise with the department concerned. Keep personal data in these records to what each team needs, and confirm handling requirements under the Personal Data Protection Act with your adviser.

Supporting cross-team follow-up with the right tools

Pick one recurring process that runs often enough to learn from quickly, such as onboarding or office moves. Map its teams and handovers, agree the lead owner, handover note and weekly check with every department involved, and run it with a shared checklist for a few weeks before buying anything.

Cross-team follow-up is one of the areas Fasttrade's BukuAdmin is built around, together with company documents, internal requests and bookings; talk to Fasttrade to confirm whether it fits your processes.

Frequently asked questions