Core systems
Use the handbook to point employees to one clear system per task.
| Need | System | Owner |
|---|---|---|
| Personal details and leave | HR Portal | People Operations |
| Receipts and reimbursements | Expense Portal | Finance |
| Payslips and tax documents | Payroll Portal | Finance |
| Passwords and secrets | Password Manager | IT / Security |
| Tickets and issue tracking | Project Tool | Team Leads |
| Laptop and account help | IT Helpdesk | Internal IT |
| Security incidents | Incident Channel | Security / IT |
| Day-to-day coordination | Slack | Everyone |
Support channels
Use clear rules for where support should start:
- HR questions: submit through the HR portal or People Operations channel.
- Expense questions: comment on the claim first, then contact finance if blocked.
- IT issues: open a helpdesk ticket instead of posting only in a team chat.
- Security concerns: use the incident route immediately if data or account risk is involved.
- Urgent access issues on day one: contact your manager and IT immediately.
Useful response expectations
This sample handbook uses simple expectations:
| Issue type | Expected first response |
|---|---|
| Access blocked on first day | Same business day |
| Normal IT request | Within 1 business day |
| Expense question | Within 2 business days |
| HR policy question | Within 2 business days |
Keep the handbook trustworthy
This page is only useful if the tool names and owners stay current. When a system changes, update the handbook at the same time rather than relying on people to discover the new process informally.