←
Directory People & org chart

Employee directory

185 employees

Showing 15 of 15 in this sample.

This is a sample of 15, not your directory Your company is 185 people — 155 field, 30 office. Fifteen invented ones are shown here so the screen has something to filter. Everyone below is fictional.

Reporting chain

North division · 8 levels

One slice, top to bottom. This is the shape your org export actually has — a single root, thirty-seven supervisors, and eight levels between the owner and an apprentice.

  1. Level 1 Taylor Voltz Owner & president · 1 direct report
  2. Level 2 Quinn Breaker General manager · 1 direct report
  3. Level 3 Harper Dynamo Operations director · 5 direct reports
  4. Level 4 Sloane Amperage Division lead, North · 7 direct reports
  5. Level 5 Morgan Kilowatt Project manager · 5 direct reports
  6. Level 6 Riley Ohm Field supervisor · 22 direct reports Bulk views exist because of this
  7. Level 7 Alex Voltner Journeyman electrician · 3 direct reports
  8. Level 8 Sam Ampère Apprentice electrician · no direct reports
8
Levels deep
37
Supervisors
22
Widest span

The South chain runs one level shallower, and its approvals run through different people. That is why a division is an attribute the approval engine reads, not a label on a report.

What a 22-person span costs

Design consequence

Twenty-two timesheets, every two weeks, on one person’s phone. Approving them one at a time is twenty-two taps that all say yes — which is how a wrong one gets approved. So the approval screen shows the exceptions first and lets the clean ones go in a single action, with each approval still recorded individually.

Exception-first ordering Bulk approve Per-row audit record

See it in WE Time →

Still open, and it changes this screen. Who sees whom is a setting — whether a field supervisor sees only their own crew, their division, or everyone. We have not assumed an answer, so the sample above shows everything.
What this screen teaches. Depth and span are not trivia. Eight levels means an approval can stall on one person’s day off, so delegation and out-of-office coverage are requirements rather than polish. A 22-person span means bulk and exception views are requirements too. Both facts came out of your own org export — neither was in the scope document.