Restaurant Cell Phone Write-Up

Restaurant cell-phone write-up (phone use on the line)

A restaurant cell-phone write-up is the dated record that a scheduled employee used a personal device at a working station against a published policy—plus the observation times, station, guest or ticket impact, policy citation, and next progressive step. It is not a group-chat vent about "always on their phone," and it is not a Friday memo that bundles three dinner services after the unemployment letter arrives.

Use this page when you manage FOH, BOH, or a bar and someone was on a personal device while on the clock. This is conduct, not attendance: a late clock-in still belongs on the restaurant tardiness write-up, and a ghosted shift belongs on the restaurant no-call/no-show write-up. For the full floor file (hire packet, guest complaints, alcohol, cash), use the restaurant employee documentation checklist. For write-up language that is not this incident type, see how to write up an employee and employee write-up examples. A guest-facing service miss belongs on the restaurant rude-to-guest write-up. A uniform or appearance miss belongs on the restaurant dress-code write-up. An unapproved early-out or unauthorized/extended break belongs on the restaurant leaving-early write-up. A refused lawful work order belongs on the restaurant insubordination write-up. A published guest photo, public complaint, or private workplace post belongs on the restaurant social media write-up—this page is the device at the station, not the caption. An observed product walkout, unpaid comp, or tip-jar/till taking belongs on the restaurant employee theft write-up. A withheld tip-out or tip-pool skim belongs on the restaurant tip-theft write-up.

What phone use is—and is not

Phone use means the person was on the posted schedule, on the clock, and had a personal device out at a working station your handbook restricts. Your handbook should define the clock: on-duty vs. clocked-out break, guest-facing vs. BOH, and whether photographing a ticket or stepping out for a family call is allowed.

Treat these as different records, even when they happen the same week:

Event	What to log	Typical next step
Personal phone at a working station	Station, observation times, what was on screen if visible without grabbing the phone	Occurrence; coaching or write-up per ladder
Guest-facing phone (dining room, host, bar well)	Table or stand, whether a guest commented, who covered	Often a first write-up if policy is guest-facing
Phone over uncovered food	Station, product on the board, whether hands returned to food	Pair with the food safety write-up if a holding or handwashing standard was also missed
Allowed ticket photo / expo pic	Whether the kitchen already allows it; who asked	Not a write-up if the posted rule allowed it
Clocked-out break in the office	Clock-out time, location	Not on-duty phone use
Refusal to put the phone away	The request, the exact reply, witnesses	Insubordination documentation, not only this form

One 40-second scroll at expo is an occurrence. Three dated observations with coaching between them is a pattern. Unemployment boards treat "they are always on their phone" as a story until the times match a named station.

What to document the same day

Capture this before the shift ends—voice note on the floor is fine if it hits the official file the same day.

1. Identity — Employee, role (server, host, line, dish, bartender), home store if borrowed.
2. Station — Expo, sauté, host stand, section 2, bar well. Not "on the floor."
3. Observation times — Clock times you saw the device, not "during rush." Two times beat "again."
4. What you observed — Phone in hand, earbuds, filming, texting. Do not unlock or confiscate the phone to "see who they were texting."
5. On-duty status — Clocked in; not on a published break; not stepped out to the office.
6. Impact — Missed expo call, tickets +N minutes, guest comment, host stand uncovered. Numbers beat adjectives.
7. Policy — Handbook phone, device, or phone-use section the employee already acknowledged.
8. Employee explanation — Their words, or "declined to comment."
9. Next step — Coaching, written warning, final warning, or separation per the published ladder.

Skip: "addicted to their phone," "doesn't care about the pass," "third time this month" with no prior dates. Those sentences are what hearing officers discard.

If you are scoring the whole file—not just this observation—walk the personnel file checklist for handbook and I-9 storage, then the restaurant checklist for floor extras.

Progressive discipline for restaurant phone use

Write the step you are on, and list the prior dated phone observations. Do not invent a "final warning" on the day you terminate unless the file already shows the earlier paper.

Step	What belongs in the file	Restaurant miss
Same-day occurrence	Station, observation times, on-duty status, impact, MOD	"I told them in the walk-in"
Coaching	Facts from the occurrence, policy cited, follow-up date	"I talked to him by the dish pit"
Written warning	FACT write-up, prior phone dates listed, employee response	First paper appears on termination day
Final warning	Same issue or published phone-use threshold	New issue stacked without dates
Separation summary	Who, when, which phone dates, property/keys, final pay	Termination text with no observation history

A first on-duty phone is often coaching even if expo was slammed. A second observation inside the handbook window is often a written warning. A documented pattern with the first steps dated and acknowledged is the unemployment-defense version of "we gave fair notice."

If your handbook is zero-tolerance for guest-facing phones or phones over uncovered product, say so in the write-up and attach the signed acknowledgment. Inconsistent enforcement—night MOD writes it up, day MOD waves it—hurts more than a missing adjective.

A first conversation that states the next step is still a verbal warning if you said a further occurrence becomes a write-up. For the ladder itself, use the progressive discipline policy guide.

Build the document with the write-up generator if you want the fields held in one place. The field definitions live on the restaurant employee write-up page.

Unemployment-defense angle

States differ on misconduct, but the questions are boring and predictable:

• Did the employee know the device / phone-use rule?
• Can you show they were on the clock at a restricted station?
• Did you document the observation the same day—or after the claim?
• Were prior phone steps dated, coached, and delivered?
• Did you apply the same rule to other employees on the same station type?

A charged claim is a tax event, not a morality play. Price it with the unemployment claim cost calculator. Build the hearing pack with how to defend an unemployment claim. Restaurants that fail with a "complete" hire packet usually have no same-day phone notes; that failure mode is spelled out in how restaurants lose unemployment claims.

If two of these boxes are empty, coach and document before you separate—unless the published guest-facing or food-contact rule and a same-day investigation support immediate action.

Example cell-phone write-up structure

Copy the headings. Replace the brackets. Do not add personality.

Employee: [Name], [line / server / host], [store]
Date of incident: [Saturday, date]
Station: [Expo / sauté / host stand / section 2]
On duty: Clocked in [4:02 p.m.]; not on a published break.
Observed: Personal phone in hand at [6:40 p.m.] and [7:15 p.m.] while [tickets were on the board / guests were at the stand].
Notification / redirect: Asked to put the phone away at [6:41 p.m.]; [complied / phone returned at 7:15].
Impact: Missed expo call; [3] tickets +[8] minutes 6:40–6:52 (expo). / Guest at table [12] commented that the server was on a phone.
Policy: Handbook §[Phone Use / Personal Devices], acknowledged [date].
Prior steps: Coaching [date] for phone at prep; verbal warning [date] for phone at the pass.
Action: [Coaching / written warning / final warning].
Employee response: [Quote or "declined to comment"].
Follow-up: Next on-duty phone use in [window] results in [next step]. Follow-up date [date].
MOD: [Name]. Witnesses still employed: [names].

That is a write-up. "Employee is addicted to their phone and ruined Saturday" is not. Pull FACT replacements from employee write-up examples if you catch yourself reaching for a label.

Common phone-use mistakes

• Logging Friday because Saturday was too busy
• Bundling three dinners into one "phone problem" memo
• Writing "always on their phone" with no observation times
• Grabbing or unlocking the phone to read messages
• Treating a clocked-out office call as on-duty phone use
• Skipping the handbook exception for ticket photos or approved step-outs
• Writing the first formal note on the day of termination
• Letting a transferred MOD take the coaching history with them
• Filing the write-up in camera roll or Slack, not the official record
• Calling a late clock-in phone use instead of using the tardiness write-up
• Calling a refusal to put the phone away "attitude" instead of using insubordination documentation

How to run this the next time someone is on a phone at the station

1. Confirm they are clocked in and not on a published break before you assume a violation.
2. Log the observation within two hours: station, times, on-duty status, impact, MOD.
3. File it to the official record the same day.
4. Draft the write-up from that note using the structure above—not from memory on Tuesday.
5. If this is occurrence two or three, pull the prior dated phone notes before you talk termination.
6. If they refused a direct order to put the phone away, add the insubordination record—do not merge the two.
7. If a claim is already filed, export the pack and follow how to defend an unemployment claim.

Conclusion

Restaurant cell-phone documentation is a same-day habit: station, observation times, on-duty status, guest or ticket impact, and a progressive step the employee already knew. This page is the write-up for one on-duty phone. The restaurant employee documentation checklist is the rest of the floor file. The personnel file checklist still covers hire packets and I-9 storage. Docu-Coach™ timestamps the capture so the write-up is a review, not a reconstruction.

Book a demo or start a 30-day trial at /demo.