Image
Workflow
Back office

Onboarding coordination across IT, payroll, and facilities

The offer is signed, and now four teams each need to do something before day one, and nobody is watching all four. An agent opens every setup request with an owner and a date, chases the stragglers, and reports what is ready. Access and document checks stay with people.

The short answer

Short answer

An agent gets a new hire ready for day one by opening every setup request at once: accounts and equipment with IT, setup with payroll, a desk or badge with facilities.

Each request has an owner and a due date. It tracks them, chases what is late and reports readiness. People grant access and verify identity documents.

Today

Why is the new hire's laptop never ready on day one?

The offer is signed and the start date is set. Then the hiring manager emails IT about a laptop, forwards the details to whoever runs payroll, and asks the office manager about a desk. Each team works its own queue at its own pace. Nobody holds the whole list, so the gap shows up on the first morning: no login, no badge, a payroll record missing a field, and a new employee sitting in reception.

Who is this for?

An office manager, operations lead or people lead who coordinates new-hire setup across several teams, often by email and memory. It suits companies hiring regularly enough that setup is a pattern, with teams that already take requests through a ticket queue or a shared inbox. The paperwork the new hire fills in is a neighbouring job with its own page.

What changes when one agent holds the whole setup list?

Part of the jobCoordinated by emailWith an agent coordinating
The requestsSent one at a time as someone remembersOpened together from your setup template
OwnershipImpliedA named owner and due date on every item
Late itemsFound on day oneChased before the start date and escalated if stuck
AccessCopied from the last hire's accountRequested per role and granted by IT
ReadinessAssumedA day-one readiness report the hiring manager can read

How it works, step by step

The agent opens, tracks and chases requests. The teams that own each piece do the work and make the decisions in it.

01

Start from the accepted offer

When an offer is marked accepted, the agent reads the role, start date, location and manager from the hiring record you authorize.
02

Open every request from your template

It opens the setup requests your template lists for that role: accounts and equipment with IT, the new-hire record with payroll, a desk, badge or shipping address with facilities. Each request goes into that team's own queue with an owner and a due date.
03

Ask for access by role, not by copy

Account requests list the access the role needs, taken from the role definitions you keep. Copying a colleague's access is the habit this replaces. NIST defines least privilege as the principle that a system should restrict users' access privileges to the minimum necessary to accomplish assigned tasks.
04

Track and chase

It watches each request against its due date, reminds the owner when one slips and tells the hiring manager when something is stuck.
05

Human gate: each team grants, and people verify documents

IT grants accounts, payroll creates the pay record and facilities assigns the space. The agent requests and tracks, and grants nothing itself. Identity and work-authorization documents are checked by a person at your company. For example, USCIS states that the employer must examine these documents to determine whether they reasonably appear to be genuine and relate to the employee, then record the document information on the employee's Form I-9.
06

Report day-one readiness

Before the start date it sends the hiring manager a readiness report: what is done, what is late and who owns each open item.
07

Close the setup record

After the first week it closes the record, listing anything still open as a request with its owner, so nothing quietly drops.

Left to people

What does the agent leave to people?

Granting access

IT grants every account and permission.

Document checks. Identity and work-authorization documents are reviewed by a person.

Pay details

Payroll enters and confirms pay information.

Exceptions

A request outside the template goes to the hiring manager to approve.

The welcome. First-day plans, introductions and the human side of starting stay with the manager.

Where this fits

Workflow / Automate a Workflow

Getting one new hire ready is a single process with a fixed end date, the scope of Tier 1, Automate a Workflow. Your setup template and role definitions are what the readiness checklist will test first. The new hire's own forms and acknowledgements are handled in onboarding paperwork and checklist coordination, and requests that land in shared queues follow internal request routing and triage. The approval gates page explains why granting access stays a named person's decision. Browse the use case library for more.

How does setup coordination differ from onboarding paperwork?

QuestionOnboarding paperworkSetup coordination
Who does the workThe new hire, filling in formsYour internal teams, preparing for them
What is trackedForms and acknowledgementsAccounts, equipment, pay record, workspace
When it must finishBy the deadlines on each formBefore the first morning
Who decidesThe person reviewing the formsEach team owning its piece
Tier 1 / Prove
How It Works

Questions, answered

No. It opens the request in IT's queue with the access the role needs. IT reviews and grants it.
AI Opportunity Audit · Onboarding

Get day one ready before day one

Bring the last new hire whose first day did not go to plan and find the request that slipped.