CRACTTCreate your instance

Employee directory template: build a who's who your team will actually use

Most directories are a list of names and job titles, which is exactly the thing nobody needs. This one captures what people really ask: who owns this, where do I send it, when are they around, and who covers it when they are not. Everything stays in your browser.

Entry 1

Entry 2

Entry 3

Entry 4

Gap check

Every entry says what it owns, where to send it, when it is covered and who backs it up. That is a directory people will trust.

A directory is a snapshot. People need an answer.

Even a good directory makes someone read a grid, guess which row applies, and hope it is current. What they actually wanted was one sentence: send it here, expect a reply by then, and if it stalls go to this person.

CRACTT is the live version of this page. You map your departments, worker levels, internal contacts and coverage hours once inside your own private instance. After that anyone in the business can ask in plain language — "where do I send a refund over $500?" — and get the accountable team, the contact to try first, a realistic reply window, the steps in order and the escalation path. No customer records, no personal data, and nothing you enter is used to train any AI.

Set up your instance Watch the walkthroughRACI matrix builder

What to put in each column

Role, not just a name
People move on. The seat and the work it carries usually stay.
What the seat owns
The trigger for using it. Without this, people guess and misroute.
Covered hours and reply window
Sets expectations and stops the second "any update?" message.
Backup
The single field most directories skip, and the one dead ends come from.

Four reasons directories stop getting used

  1. It lists titles, not work. Nobody knows which title handles their question.
  2. It goes stale quietly. One wrong row and people stop trusting the whole file.
  3. No hours. Across time zones, "who owns it" without "who is awake" is not an answer.
  4. No escalation. When the first contact is out, the request just sits.

Common questions

Should the directory list people or roles?

Roles first, with people attached. That way a departure changes one line instead of invalidating the file.

How big should it be?

Start with the seats that get asked about most — approvals, escalations, access requests, scheduling, invoices. Ten strong rows beat sixty vague ones.

Does this work across time zones?

Fill in covered hours and a backup for every seat. A global team needs to know who is on shift, not just who owns the work.

Is anything I type here saved?

No. It all runs in your browser and nothing is sent anywhere. Use the export button to keep a copy. Do not put personal employee data in it — internal role addresses are enough.