Restaurant Disciplinary Action Form

The form, not the conversation

A restaurant disciplinary action form is the standard document your managers complete when they take a formal corrective step — and its real job is consistency. The point is not that the paper exists. The point is that a Tuesday-morning MOD and a Saturday-night MOD, at two different stores, document the same behavior the same way and apply the same level.

This page is about the form's structure and its action levels. For the language that goes in the narrative field and how to deliver the document, use restaurant employee write-up. For tracking completed forms and spotting variance, restaurant disciplinary action tracking.

What belongs on the blank form

Required — the form should not be fileable without them:

• Employee name, role, store, and hire date
• Date and time of the behavior, and date of the document
• Action level, selected from a defined list
• Narrative: observable behavior in facts, with times and quotes
• Policy or standard cited by handbook section
• Business impact: guest, service, product, property, or safety
• Prior documented steps, each with its own date and level
• Expectation going forward, stated concretely
• Consequence if the behavior recurs, and the review window
• Follow-up date
• Manager name and MOD, plus witness where required by level
• Employee response field, and acknowledgment or refusal block

Optional but useful in a restaurant: shift and station, whether a guest was involved, whether camera footage exists, whether training or retraining was delivered, and the scheduling or POS record referenced.

Leave off anything you cannot defend: character assessments, references to undocumented history, medical speculation, and any field inviting the manager to summarize the employee rather than the behavior.

Define the action levels or they define themselves

An action level list without definitions is where consistency dies. Write these down and put them in the manager handbook.

Level	Use it when	Requires
Documented verbal coaching	First occurrence of a correctable behavior	Facts, expectation, follow-up date
Written warning	Recurrence after coaching, or a first offense your policy treats as written-level	Facts, policy cited, prior coaching listed, consequence stated
Final written warning	Recurrence after a written warning, or a published threshold reached	All of the above plus a defined review window
Suspension pending investigation	Serious allegation needing facts before a decision	Reason, expected duration, pay status per policy, and an investigation file
Separation	Policy-permitted endpoint, or a serious single incident	Prior steps listed with dates, or the policy basis for skipping them

A performance improvement plan is a parallel track, not a rung. Conduct goes up the ladder; capability goes into a restaurant performance improvement plan with measurable targets. Putting a slow new line cook on a final warning for being slow is the most common misuse of this form.

Serious conduct and skipped steps

Most restaurant policies allow immediate written-level or separation-level action for a defined set: theft, violence or threats, intoxication on shift, harassment, deliberate food safety violation, walking off mid-service, or falsifying records. Two rules:

1. The category has to be published before you use it. If the handbook does not list it, you are improvising, and it will read that way next to the file of an employee you coached three times for the same thing.
2. Write the basis on the form. "Immediate final written warning per Handbook §6.1 (food safety — willful)" is a complete thought. A blank prior-steps section with a final warning selected is not.

Consistency across MODs and stores

Variance shows up in three predictable places, and all three are form problems as much as training problems.

Same behavior, different level. One MOD coaches a no-show; another issues a final warning. Fix: define the level for common restaurant behaviors in the policy, and reference the definition on the form.

Same level, different depth. One manager writes three factual sentences; another writes "spoke to employee about attitude." Fix: make the narrative field require time, behavior, and impact, and reject forms that do not have them.

Steps that only exist verbally. Coaching happened but was never documented, so the written warning has nothing behind it. Fix: treat documented verbal coaching as a real level with its own form, not a conversation you remember.

At the district level, a monthly pass over completed forms — grouped by behavior rather than by store — surfaces variance before an employee's representative does. Run it against the restaurant employee documentation checklist.

The acknowledgment block

Three lines, and the distinction between them matters:

• Employee acknowledgment of receipt — "I have received a copy of this document." Not agreement.
• Employee comments — their account, in their words, with space to actually use.
• Refusal to sign — date, manager, witness name, and a note that a copy was still provided.

Give the copy. Note that you gave it. "Nobody ever showed me anything" is one of the easiest disputes to prevent and one of the hardest to argue about after the fact.

Retention and access

Completed forms live in the employee's official record, and the next manager needs to be able to find them without asking a predecessor. Investigation material stays in a restricted file. Medical information is stored separately per your counsel's guidance. Retention schedules vary by state and record type — confirm yours and apply one policy across locations rather than letting each store decide.

Conclusion

A disciplinary action form is a consistency instrument. Defined levels, required fields, a narrative that has to contain facts, prior steps that were already documented, and an acknowledgment block that distinguishes receipt from agreement.

Fill one out with the write-up generator, which enforces the fields above and flags labels as you type. See where the form sits among the other records in a restaurant file in the pillar guide, and build the ladder itself with the progressive discipline policy guide.

Docu-Coach™ standardizes the fields and the storage so records look the same across shifts and stores — better documentation and more consistent records, not legal advice. See it at /demo.