What an HR approval should trigger on the admin side
An HR-to-admin handoff works when every approved people change reaches the admin team as a request with a named owner, an effective date and the details admin needs to act. Leave, transfers, new joiners and exits all create facilities work, and the handoff fails whenever that work depends on someone remembering to forward an email.
Most companies already approve the people side properly. HR checks the leave balance, confirms the transfer letter, issues the offer. The trouble starts afterwards. The admin executive hears about a new joiner from the security guard on the first morning, or learns about a department move when a whole team arrives at a floor with no desks prepared.
Treat the HR approval as the end of one process and the start of another. The second process belongs to admin, and it needs its own request, its own status and its own close-out.
Leave, facilities and people changes create different admin work
Short leave rarely needs admin at all. Long leave does. When someone goes on extended medical or maternity leave, admin may need to reassign a parking bay, pause a company phone line, redirect couriers or hold a locker. If the employee looks after a meeting room schedule or petty cash, those duties need a temporary holder too.
Facilities requests that start in HR usually come from accommodations: an ergonomic chair after a medical review, a ground-floor desk for someone with mobility needs, a private room for a nursing mother. HR knows why the request exists. Admin only needs to know what to provide and by when, and the reason should stay with HR, where the medical or personal detail is protected.
People changes are the heaviest. A new joiner needs a desk, access card, name tag, laptop collection point and perhaps a uniform. A transfer between branches means returning one access card and issuing another. A promotion can change a parking entitlement or an office allocation. Each of these is small, and together they are the reason admin teams feel ambushed.
Details HR should pass to admin with every request
Admin does not need the full employee file. It needs enough to act without chasing anyone. Agree a fixed set of fields and send back requests that arrive without them.
Keep the reason for leave and the medical basis of an accommodation off the request. Under the PDPA, personal data should be used for the purpose it was collected for, and admin rarely needs the why. Check current guidance from the Personal Data Protection Commissioner or your adviser before deciding what your forms collect.
- Employee name, staff ID and department, spelled the way they appear on the access card system
- Type of change: new joiner, transfer, extended leave, return from leave, accommodation or exit
- Effective date, and whether that date is confirmed or still provisional
- Work location, floor or branch, including any change from the current one
- Items or services required, such as desk, access card, parking, phone line or locker
- Name of the line manager who will receive the employee or confirm the arrangement
- HR contact for questions, so admin never has to go through the employee
Closing the loop back to HR and the employee
A handoff is only finished when admin tells HR it is done. Without that confirmation, HR keeps fielding questions it cannot answer: is the desk ready, has the card been activated, where does the new hire collect the laptop.
Give admin requests a short status set that both teams read the same way: received, in progress, ready and closed. Ready means the employee can use the item. Closed means the employee or manager has confirmed it. The gap between those two catches the familiar case where the access card is printed but never collected.
For new joiners, send the line manager a single confirmation listing what is ready and where to find it. The manager then has one message to forward on the first morning instead of three partial replies from different people.
When the change is cancelled, moved or reversed
Offers get withdrawn. Transfer dates slip. Someone returns early from leave. These reversals cause more admin waste than the original requests, because nobody tells admin to stop.
Make HR responsible for sending a change notice against the original request rather than raising a fresh one. Admin can then see the history in one place: what was asked, what was already done, and what needs undoing. A parking bay released for long leave can be reclaimed. A desk prepared for a withdrawn hire goes back into the pool.
Exits deserve their own care. The return of access cards, keys and company items is often where HR and admin each assume the other is collecting. Name one owner for the physical return and record it on the request before the last working day.
Putting the request trail into shared systems
Start with a shared form if you need to prove the process first. Once both teams agree the fields and statuses, people records and approvals can move into BukuHR, and internal requests and follow-up into BukuAdmin. Whether a request raised on the HR side should appear automatically on the admin side is something to scope with Fasttrade, since every company draws the line between these two teams differently.
Whichever tools you use, review open cross-team requests together at a fixed slot each week. The meeting is short when the fields are complete and painful when they are not, which tells you quickly where the handoff still leaks.
Frequently asked questions
Should admin see the reason for an employee's leave?
Usually not. Admin needs the dates, the location and the items affected, such as a parking bay or phone line. The reason for leave, especially medical or family detail, should stay in HR records. Limiting what admin sees keeps the request useful while respecting the purpose for which the data was collected. Confirm your approach against current PDPA guidance or with your adviser.
Who should raise the facilities request for a new joiner, HR or the line manager?
HR is the better trigger because HR knows when the offer is accepted and the start date is confirmed. The line manager adds detail such as seating preference or equipment, but relying on managers alone means some requests are never raised. A workable pattern is HR creating the request and the manager completing a few fields before admin starts work.
How do we stop admin preparing for hires who never join?
Mark the effective date as provisional until the candidate has signed and any pre-employment checks are complete. Admin can reserve a desk against a provisional request but should hold off on items that cost money or take effort to reverse, such as printed access cards. If the offer is withdrawn, HR sends a change notice against the original request so admin can release everything at once.
Next step
Explore BukuHR or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.