How to know when a new employee can really work alone

A new employee is ready to work alone when they have handled every critical situation of their role by themselves, in front of a witness, and it has been written down. Tenure, the manager's impression and the fact that they no longer ask questions are not enough. Readiness is confirmed one situation at a time: opening, prepping, serving, handling an incident.

The Thursday someone said "she's good"

A commis starts on a Monday at the group's second site. She shadows the morning cook for three days. On Thursday he asks her to start prep on her own because the chef is running late. She handles it. That evening the chef concludes: "She's good, we can leave her on her own."

On Saturday, opening is hers. The walk-in shows a temperature she does not know how to read, the delivery arrives one case short, and nobody has shown her who to call. She did not get it wrong through carelessness: she had simply never seen either situation. Thursday had proved one thing only, prep on a quiet day.

Why we get readiness wrong

Four mechanisms show up almost everywhere.

• The good first week effect. A new hire who is attentive, polite and quick gives an impression of mastery. We confuse behavior with competence.
• Rare situations do not show up during onboarding. A cooling failure, a guest with an allergy, a supplier who does not show: if none of them happen in the first few days, nobody knows how the new hire would react.
• Each trainer watches for something different. The morning cook judges speed, the sous chef judges cleanliness, the chef judges discretion. There is no shared reference for what "ready" means.
• Nobody keeps a record of what was seen. After ten days, the manager remembers an impression, not dated facts.

A grid of situations, not a date

The method takes six steps.

1. List the critical situations of the role. Four to six, no more: opening, running the station at peak, receiving a delivery, taking temperature readings, closing, reacting to an incident. The manager and the most experienced person in that role write them together, in an hour.
2. Describe what "done alone" means for each one. One observable sentence: "Checks the delivery against the purchase order and rejects an out-of-temperature product without asking."
3. Assign four statuses. Not seen, seen with a colleague, done alone and observed, done alone and checked afterward (proof: a log entry, a photo, a signed task).
4. Schedule the missing situations. If the new hire has never seen a delivery, arrange for them to be present at the next one, or simulate it with a real purchase order.
5. Have a named witness sign off. The manager or a trained colleague observes, notes the date, signs. The new hire does not declare themselves ready.
6. Decide the scope of solo work. "Can open the dining room alone," "cannot yet close alone": readiness is granted in pieces and can be withdrawn without drama if a situation has not been seen.

Fictional example of a grid for a commis role

Situation	Status	Observed by	Proof
Morning prep	Done alone and observed	Chef de partie	Signed task
Receiving a delivery	Seen with a colleague	Sous chef	To schedule
Temperature readings	Done alone and checked	Manager	Dated log entry
Closing the kitchen	Not seen	None	To schedule
Handling a rejected product	Not seen	None	To simulate

This table reads in ten seconds and answers the Saturday morning question: who can open, and who cannot yet.

Mistakes that skew the verdict

• Signing off on time served. "Three weeks, so they're ready" says nothing about the situations they have not met.
• Asking the new hire to self-assess. A beginner underestimates what they do not know yet, or is afraid to admit it.
• Signing off with a single observer and no written criteria. The next trainer will redo the assessment their own way.
• Turning the grid into a grade. It exists to allocate work, not to rank a person. As soon as it becomes a score, teams dread it.

What to look at after a few weeks

• The number of critical situations still "not seen" per role, site by site. It shows where your onboarding path has gaps.
• The time between arrival and the first situation done alone and checked, compared from one site to another.
• The number of identical questions asked by several new hires: that is an instruction that was poorly passed on, not a flaw in those people.

Where Tsuno comes in

For each role, Tsuno keeps the expected skills, the related training modules and what has been observed, with the date and source of each fact (declared, observed, proven). A manager can ask in their own words: "Who can open the site tomorrow without backup?" and get an answer based on validated situations, or an admission that the data is missing. Tsuno does not decide that a person is ready and does not grade them: it recalls what is written, and people validate. The detail of the modules is on the features page.

Further reading

This topic touches the whole onboarding process: see how to reduce onboarding time without cutting corners, how to build a useful skills matrix and why new hires say "nobody told me". For the overall logic on the manager side, read managers do not need another dashboard.

Key takeaway

Readiness is not a date, it is a list of situations seen, done alone and checked. Write four to six situations per role, give each one a status and have a witness sign. You will know who can work alone, and you will also know what to show the new hire next week.