Guides
Ghost kitchen hiring: a thirty-day reliability review
Ghost kitchen staff reliability is read from logs, not impressions: what to bring to a thirty-day review and how to confirm, coach or end a new hire.
What to take away
- The review at thirty days is the last step of hiring, not the first step of managing.
- Bring the scorecard, the refund log and the shift logs. Reliability is now evidence: bags out on time, logs complete, shifts covered.
- The outcome is one of threeconfirm, coach or end it, and it goes in writing.
- Before blaming the person, rule out the ways the kitchen itself loses reliable people.
A hire who passed the practical still has to prove reliability on real shifts. The thirty-day review reads that proof from records instead of memory, against the scorecard set out in the hiring guide.
What to put on the table at thirty days
Bring the same short pile for every new hire. Each item answers one question that the interview could not, and none of them depends on how likeable the person is or how well they talked about a night that went wrong.
| Record | Question it answers | Where it comes from |
|---|---|---|
| Scorecard | Does the person do what the role says? | The written scorecard for the role |
| Refund log | Did errors trace to a checklist failure? | The log kept at the pass |
| Shift logs | Are they complete, shift after shift? | The station and closing logs |
| Order history | Did the bags go out on time? | Each platform's order record |
| Timekeeping | Were the agreed shifts covered? | The kitchen's time records |
Add one more check: confirm that any food handler credential the health authority requires is on file, with the date it was verified.
Reading the evidence without guessing
Read the record first and the person second. A missing entry is a fact, and the reason for it is a question. Ask that question in the review with the page open, so the answer is about one named shift and not a general impression.
Separate the person from the conditions. A late bag on a night when the schedule changed without notice is a scheduling problem. The same bag on a night when the stated hours held is a coaching problem. The log shows the lateness; only the question shows the cause.
Check the new hire against what they were actually taught. If training was skipped because the person was experienced, the first refund is a checklist failure, and the cause sits with the kitchen. The training checklist is the record to compare against.
Confirm, coach or end it
Pick one outcome and write it down. Confirm when bags went out on time, logs were complete and shifts were covered. Coach when one of the three is weak and the cause can be fixed. End it when the evidence is weak and the conditions were fair.
The meeting itself can follow five steps:
- Lay the scorecard, refund log, shift logs and time records on the table.
- Ask the new hire to walk through one shift that went well and one that did not.
- Compare their account with the records, entry by entry.
- Name the outcomeconfirm, coach or end it.
- Write it down the same day and give the person a copy.
A coaching outcome needs a named gap and a date for the next look. "Be more reliable" is not a gap. "Logs completed on every shift" is one, and the next review can check it against the same records.
Keeping the records that back the decision
The hours a person worked are part of the evidence, and they are also a legal record. The U.S. Department of Labor's fact sheet on recordkeeping says the Fair Labor Standards Act requires no particular form, but the records must include data about the hours worked and the wages earned.
So the question "were the agreed shifts covered?" is answered from timekeeping records, not memory. Whatever method the kitchen uses, the review needs a sheet that shows each shift the person worked, so a coaching or ending decision rests on dates and not on recollection.
Where reliability is lost after hiring
Four things wear down a reliable hire, and the review should rule each of them out before it blames the person.
- The schedule changes without notice, and the person who was reliable for the stated hours cannot do the new ones.
- The site cannot be reached safely after the late close, which a site choice made without the night shift in mind can cause.
- Training was skipped because the person was experienced.
- Pay was set from instinct and turns out to be below the radius's current postings.
The U.S. Bureau of Labor Statistics notes that food service managers often work evenings, weekends, and holidays. In a delivery kitchen the manager's reliability sets the crew's, so the manager's own scheduling belongs in the review as well.
When demand outgrows the crew
Hire the next operator before the next platform is added. A promotion or a new platform that fills the peak beyond what the crew can pack on time turns reliable people into a late-order problem.
The marketing and growth guide covers matching promotion to capacity. For the review, the point is narrower: a late-bag pattern that appears right after a launch points to the peak, not to the new hire.
Common questions
What if the logs are thin after thirty days?
Incomplete logs are an answer too, because willingness to keep records is one of the things the hiring sequence tests. Name the missing entries in the review and make complete logs the coaching gap.
Should the review wait until there is a problem?
No. Hold it at thirty days for every hire, using the same records and the same three outcomes, so nobody is singled out and every decision can be explained.
What if every shift was covered but the bags were late?
Then shifts covered is met and on-time bags is the gap. That is a coaching outcome with the gap named, unless the schedule or the training the kitchen gave explains the lateness.
