Corrective Actions & Follow-Up¶
Overview¶
Once a deviation has been classified, record what will be done — and later, what was actually done — to prevent it from recurring, and conclude the case once it's resolved.
Corrective Measures¶
| Field | Description |
|---|---|
| Proposed Corrective Action | The suggested corrective action. This field can be hidden entirely by an administrator — see Setup & Permissions. |
| Corrective Action | The corrective action actually taken. |
| Responsible for Corrective Action | The person responsible for carrying it out. |
| Corrective Action Deadline | When the corrective action should be completed by. |
| Corrective Action Date | When it was actually completed. |
Follow-Up & Conclusion¶
| Field | Description |
|---|---|
| Follow-Up | Free-text notes on the outcome and any further observations. |
| Responsible for Quality Assurance | The person responsible for QA sign-off. |
| Date Assigned | Marks the deviation as processed/completed — this is the completion date shown on role center cues. |
Tracking open deviations
The "Assigned to Me" cue on several role centers counts deviation reports assigned to the current user that don't yet have a Date Assigned — use it to see outstanding work at a glance. See Setup & Permissions.
Long text fields¶
Description, Cause Details, Proposed/Corrective Action, and Follow-Up are long free-text fields. If an administrator has enabled Use Larger Text Areas in the module setup, these fields open in a larger, easier-to-use text editor.
Change history¶
If Business Central's Change Log feature is activated, changes to the Deviation Report, its Technical Drawings, and its Related Documents are tracked and can be reviewed via the standard Change Log Entries page.