Map who reports to whom, and work finds the right head
Set up each reporting head and the people who report to them. Heads see their direct and indirect reportees and their team’s tasks, schedules, meetings and boards — and approvals, goals, policies and time follow the same reporting line across the AI Office.
Reporting structure
Northwind Labs · hover a person
Sam T
No reportees
Reports to Dev K, who reports to Priya S.
Leave request
Started by Sam T
Approve
The requester’s reporting head
Resolved when the step starts — nearest head first — so it follows the org chart as it is that day.
Approvals that follow the reporting line
When the agent designs a workflow from your description, it names approvers by their place in the company, and the engine finds the person when each step starts.
- 01
“Their manager approves” is one rule
Describe a leave or expense process and the agent routes the approval to the requester’s reporting head — with the room’s approvers as the fallback for anyone whose head is not set.
- 02
Job titles, checked first
When a step is for “the IT Head” or “the Finance Manager”, the agent checks your designations and routes to whoever holds that title today.
- 03
Resolved when the step starts
The reporting line is read the moment a step activates, nearest head first, so each step reaches whoever heads the requester at that moment.
One reporting structure, read by the whole office
Reporting heads live in company settings beside departments and designations. Owners and admins set them up; every head gets a view of their own team.
Heads and their reportees
Add a reporting head, then add the people who report to them. The reporting hierarchy lists every head with their team.
Direct and indirect
Each head’s card counts direct reportees and indirect reportees — the teams of the people who report to them, grouped by who they come through.
Heads see their team’s work
A reporting head sees their reportees’ tasks, schedules, meetings and boards, and opens My reportees for their own part of the org chart.
Time follows the reporting line
In company TimeTrack, a head sees the people who report to them, grouped under who they report to. Owners and admins see everyone.
Designations
Give each member a job title from a shared list, with AI suggestions as you type. Import titles for existing members from Google Workspace or Microsoft.
Approvals that route themselves
Workflow steps name the requester’s reporting head, their head’s head, a department head or a job title, and reach the right person when the step starts.
Name the role, and the step finds the person
Approval and task steps in a workflow name people by rule. Each rule is resolved against your reporting heads, departments and designations when the step starts.
The requester’s reporting head
The nearest head of whoever started the case. Their reporting head’s head is one rule more — the skip level.
Escalation up the chain
Set a time on a step and, if it is still waiting, it escalates — to the skip-level head by default.
A department head or a job title
Route to whoever heads a named department, or whoever holds a designation like IT Head, at the moment the step starts.
A fallback when nobody is set
A step with no head to find uses its fallback, such as the room’s approvers, then the room owner — and a case that still has nobody is marked as needing attention.
Expense request · Approve
Started by Sam T · Software engineer, Engineering
Who
Resolves to
Sam T reports to Dev K.
Fallback: the room’s approvers, if no head is set.
From the org chart to a decision
The reporting line is set once in company settings. Every request after that knows whose desk it goes to.
Set reporting heads
Owners and admins add each head and the people who report to them, and check it on the org chart.
A request starts a case
Someone submits a leave or expense request, and its approval step names the requester’s reporting head.
The head decides
The approval reaches their head with the submission and the case timeline, ready to act on.
Heads keep an eye on time
Company TimeTrack shows each head the time of the people who report to them.
Who runs on Reporting heads
Your whole team in one view
Direct and indirect reportees on one card, with their tasks, schedules, meetings and boards a click away.
Leave requests that route themselves
One leave workflow for the whole company, with every request going to the requester’s own reporting head.
Expenses up the chain
The reporting head approves first, and a request that waits too long escalates to the head above them.
One company, one office, one shared state
Reporting heads, answered
Company owners and admins add heads and reportees. A reporting head who is not an admin opens My reportees and sees their own team, view-only.
Direct reportees report to the head themselves. Indirect reportees report to one of those people, or further down — the head sees them grouped by the reportee they come through.
The approval opens the workflow case itself, with the submission, the timeline and the actions, so a reporting head can decide from wherever they are.
The step uses its fallback — for “their reporting head approves”, the room’s approvers — and then the room owner. A case that still has nobody is marked as needing attention.
A reporting head can set goals for themselves and everyone under them. A policy linked to a head applies to everyone under that head, and the agents working for those people read it too.
Deploy AI project managers across your office
Unlimited agentic rooms and AI project managers on every plan. Start free, or walk through your office with us.