Tracking Quality Issues with Audits
A Quality Audit verifies that your food products and service outputs actually meet the standards you’ve set. It catches defects, waste, and rework before they reach students or guests — and creates the documentation you need to investigate root causes and hold vendors accountable.
Quality audits work best when they’re run consistently, during production and service, not just when something looks off.
When to Use It
- At the point of production, to verify that a batch or menu item meets spec before it goes out
- During service, to check that food is holding correctly and meeting quality expectations
- After a complaint — to document what was happening at the time and trace the issue back to its source
- During receiving, to verify that incoming products meet quality requirements
- Periodically, to generate trend data on which products, vendors, or processes generate the most issues
Example Questions
| Example Question | Response Type | Why It Matters |
|---|---|---|
| Does the item meet expected appearance, color, texture, portion, and presentation standards? | Yes / No / N/A | Appearance is the first quality indicator guests see |
| Was the item prepared according to the approved recipe or production standard? | Yes / No / N/A | Recipe drift is a leading source of quality inconsistency |
| Is the product within the required hot or cold holding range? | Yes / No / N/A | Holding temperatures affect both safety and quality |
| Were any defects observed — undercooked, overcooked, off-spec, wrong portion, or damage? | Yes / No | Defects caught here don’t reach the guest |
| Was product waste generated due to spoilage, overproduction, or rejection? | Yes / No | Waste data supports forecasting and cost improvement |
| If an issue was found with received product, was the vendor or supplier documented? | Yes / No / N/A | Vendor documentation enables follow-up and claims |
| Was corrective action taken immediately and documented? | Yes / No | Immediate action protects the guest and the record |
What Good Looks Like
Signs of effective quality auditing Issues are caught before service, not reported by guests. Defects are traced back to a source (vendor, recipe, process, equipment). Corrective actions are assigned the same day. Over time, the same issues stop recurring because root causes are addressed. |
What Happens After
- Each defect, waste event, or rework situation is logged with its source, quantity, disposition, and follow-up owner
- Vendor-related issues are flagged for follow-up and tracked to resolution
- Trend data shows which products, vendors, or meal periods generate the most quality issues
- Over time, patterns surface that support menu changes, vendor decisions, or retraining
| Best frequency | Per batch, per meal period, or any time a quality concern is flagged |
| Who runs it | Kitchen lead, site manager, or QA auditor |
| Time to complete | 10–25 minutes depending on batch size and issue complexity |
| Key output | Defect and waste log, vendor flags, corrective actions, trend data |