A deviation memo is a written record of an event in which an actual activity, result, or condition differed from an approved plan, procedure, specification, or expectation. Use the template below to capture what happened, when and where it happened, its known impact, the response, and any review or follow-up needed; adapt it to your organization’s procedures rather than treating it as a universal form.
What a Deviation Memo Is
A deviation memo explains a departure from an expected or approved state. Depending on the workplace, the event might involve a missed process step, an unexpected test result, an equipment issue, a document that was not current, or a deadline that was not met. The memo creates a concise, traceable account so the people responsible for reviewing the event can understand the facts and decide what should happen next.
The term does not have one universal definition or mandatory format. Some organizations use a deviation memo as an initial notification; others use it as the main record for a low-risk event or as a supporting document linked to a formal incident, nonconformance, or corrective-action record. Internal procedures may specify who reports deviations, how quickly they must be reported, what approval is required, and which records must be retained. Check those requirements before using a general template.
A useful memo separates observed facts from interpretation. It can identify a possible cause, but it should not present an unverified theory as established fact. It also records uncertainty honestly: if the impact has not yet been assessed, say that the assessment is pending and identify who will complete it.
When to Use One
A deviation memo is appropriate when a meaningful difference from an approved or expected process needs to be documented and reviewed. It is generally more useful than an informal message when other people must assess impact, approve a response, or refer back to the record later. Examples include:
- A required review or sign-off was missed, delayed, or completed in the wrong sequence.
- An activity was performed using a version of an instruction that may not have been current.
- A process result, measurement, or output fell outside an established acceptance criterion.
- Equipment was unavailable, behaved unexpectedly, or was found in a condition that could affect work.
- A planned activity changed, and the change was not covered by the approved plan or change process.
Not every minor variation requires a deviation memo. A planned, reviewed change may belong in a change-control record instead, while a customer complaint, safety incident, or product defect may require a separate process. When uncertain, report the event through the designated channel and ask the responsible supervisor or quality contact how it should be classified. Prompt reporting is especially important if work is continuing or the potential impact is not yet known.
Deviation Memo Template
| Field | Entry |
|---|---|
| Memo or record number | |
| Date prepared | |
| Person reporting and role | |
| Department, site, or work area | |
| Date and time of event | |
| Process, activity, or item affected | |
| Applicable procedure, plan, or requirement | |
| Expected condition or step | |
| Actual condition or event | |
| Immediate action taken | |
| Known or potential impact | |
| Evidence or related record references | |
| Cause assessment or status | |
| Corrective or follow-up action, owner, and due date | |
| Reviewer, decision, and date | |
| Closure status and date |
How to Complete the Memo
Start with identifiers: the record number, preparation date, reporter, work area, and event date or time. If the event continued over a period, give the start and end times when known. Identify the affected process, batch, project, document, or item using the identifiers your organization normally uses. Avoid putting sensitive personal details into a memo unless they are necessary and permitted by local procedures.
Next, state the expected condition and the actual condition separately. The expected condition should point to the specific instruction, requirement, or approved plan, including its version or section when available. Describe what was observed in neutral, concrete language. For instance, write that a required second-person review was not recorded before a task proceeded, rather than calling the event carelessness. A reviewer can evaluate evidence; labels and blame do not establish what happened.
Record the immediate response and the impact assessment as distinct items. Immediate actions may include pausing work, isolating an affected item, notifying a responsible person, or preserving relevant records, but only describe actions that were actually taken and authorized. Then state what is known about the impact. If the review is incomplete, identify what remains to be checked, who owns that check, and when an update is expected. Do not claim that there was no impact merely because none is apparent at first glance.
Finally, reference supporting evidence and route the memo for review. Useful references can include a log entry, a measurement record, a work order, a version-controlled document, or a linked incident number. Follow internal rules for attaching or linking records; avoid copying material unnecessarily. Include a responsible owner and due date for each follow-up action. A memo is not complete just because it has been written: the required review, decisions, and closure steps still need to be documented.
Short Filled-In Sample
Fictional sample: This example is illustrative only. The people, site, record number, and event are invented.
Record: DEV-204, prepared 14 May 2026 by Jordan Lee, operations coordinator, North Workshop. Event: On 13 May at approximately 10:20 a.m., the team used checklist version 3 for a routine inspection. The current work instruction listed checklist version 4. Expected condition: The inspection should use the current approved checklist. Actual condition: Version 3 was completed before the version mismatch was noticed during a document check. Immediate action: The coordinator notified the area supervisor and paused use of the completed checklist for release decisions. Impact: The supervisor assigned a review to compare the completed entries with version 4; the outcome is pending. Follow-up: Casey Morgan will complete and document the comparison by 16 May. Review status: Supervisor review pending.
The sample does not assume the older checklist caused harm or that repeating the inspection is automatically the right response. Those decisions depend on the requirements, evidence, and authorized review in the actual setting. The memo records the known facts and leaves unresolved conclusions open until they are assessed.
Impact, Cause, and Follow-Up
Impact assessment asks what the deviation could have affected, not only what was immediately visible. Depending on the work, relevant considerations may include the validity of a result, the status of an item, a later decision made using the result, a delivery commitment, or the reliability of a record. The person completing the assessment should identify the evidence considered and any limits on the conclusion. If several items or activities may be involved, define the scope clearly instead of relying on phrases such as possibly everything.
Cause assessment may require a separate investigation. A first report can record a suspected contributing factor, but it should label it as preliminary unless it has been confirmed. A useful review looks beyond the person closest to the event and considers whether instructions, training, workload, access, equipment, handoffs, or controls played a role. The goal is to understand the conditions that allowed the departure, not to force a single explanation before evidence is available.
Follow-up should be specific enough to verify. Compare “improve awareness” with an action such as “update the point-of-use checklist display and verify the current revision during the next scheduled area review.” Assign an owner, a due date, and, where appropriate, a way to confirm that the action was completed and effective. Whether an action requires formal effectiveness monitoring depends on the organization’s process and the significance of the event.
Review, Approval, and Recordkeeping
Reviewers typically check whether the description is understandable, the applicable requirement is identified, immediate containment is adequate, and the impact assessment is supported. They may request clarification, assign additional investigation, approve a proposed action, or route the event into another system. The memo should show the decision and its date, not just a name typed into an approval field. If the review leads to a change in the record, retain a clear history according to the organization’s document-control rules.
Keep the memo factual, legible, and linked to related records. Use the approved storage location and access controls; a local copy saved without context can become difficult to find or may be mistaken for the official record. Retention periods, signatures, electronic approvals, and escalation thresholds are organization-specific. Follow the applicable procedure rather than assuming that a generic template establishes those rules.
Common Problems to Avoid
- Vague descriptions: “The process went wrong” does not tell a reviewer what differed. Name the step, requirement, date, and observed condition.
- Blending facts and assumptions: Mark a proposed cause as unconfirmed and explain what evidence is still needed.
- Leaving impact blank: State the assessment, or document that it is pending with an owner and target date.
- Writing conclusions too early: Avoid declaring an event harmless or fully resolved before the relevant checks are complete.
- Unclear actions: Give each follow-up an owner, due date, and observable completion criterion when appropriate.
- Using the memo for every record type: A deviation may overlap with a complaint, safety report, nonconformance, or change request, but the required system depends on local rules.
A practical quality check is to ask whether a colleague who was not present could understand what happened, what requirement applied, what has been done so far, and what remains undecided. If not, add the missing facts or clearly identify the open questions.
Frequently Asked Questions
What should a deviation memo include?
A basic memo identifies the reporter and event, the requirement or expected condition, what actually happened, immediate actions, known or potential impact, supporting evidence, follow-up ownership, and review status. Add fields required by your organization’s procedure.
Is a deviation memo the same as a nonconformance report?
Not necessarily. Organizations use these terms differently. A deviation memo may document a departure, while a nonconformance report may be a separate formal record for a requirement not met. Check local definitions and routing rules before choosing a form.
Can I write that there was no impact?
Only when the available evidence supports that conclusion and the assessment is within your role. Otherwise, state what has been checked, what remains uncertain, and who will complete the assessment. Do not use absence of an obvious problem as proof of no impact.
Who should approve a deviation memo?
The responsible reviewer depends on the process, the risk, and organizational policy. A supervisor, process owner, quality reviewer, or another designated role may be involved. The template cannot determine the required approval chain.
Can this template be used in a regulated workplace?
It can be a starting point for organizing information, but it is not a substitute for required procedures, controlled forms, records, or reporting timelines. Use the organization’s approved system and ask the designated compliance or quality contact if requirements are unclear.