Management review and objectives
Prepare immutable QMS inputs and metric snapshots, obtain QA completeness approval, record executive objectives and assigned actions, then independently verify results and close the review.
Screen orientation
management_review:read is site/clearance scoped. Preparation, QA approval, executive decision, action response, verification and closure use management_review:prepare, :approve, :decide, :act, :verify and :close. The input author submits their own version. QA excludes author/submitter; the executive also excludes the input approver. Assigned MANAGEMENT_REVIEW_ACTION_OWNER users must be active, scoped, cleared and different from all those input/decision actors. Only the specifically assigned owner can respond. Verification excludes the action owner, executive decider and input approver. Closure excludes the input author/submitter and approver, but does not require a different executive from the original decider.
Six summary cards count input review, meetings, action tracking, closure review, open actions and active objectives. New review opens an input editor. Searchable review cards contain metrics/history, executive outputs, objectives, assigned actions, response history and closure evidence. Action forms open below the register.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Search register / Filter register by status / Sort register | Search and two selects | Optional view controls. | Search review number, site, status or returned input title. Filter returned states and sort by creation time or review identity. Showing counts the filtered subset; summary cards still describe the authorized register. | Changes only the visible review list. |
| Site / Classification / Review title | Two selects and text | Required on creation; title at least 5 characters. | Choose the review scope within your assigned site and clearance. Revisions retain the site/classification and allow a replacement title. | Defines the governed review context. |
| Period start / Period end / Meeting date | Three dates | Required; end on/after start and meeting on/after period end. | Set the reporting interval and planned meeting. Most governed counts are current open-work snapshots; only FAI acceptance uses records created within the reporting period. | Freezes the reporting context without reconstructing historical open counts. |
| Review scope / Context changes / Customer feedback / Process and product performance | Four multiline text controls | Each required; at least 20 characters each. | Define the boundaries, changes affecting the QMS, customer signals and measured operational performance separately. | Creates the first four narrative sections of the immutable input. |
| Resource adequacy / Risks and opportunities / Prior action review / Improvement opportunities | Four multiline text controls | Each required; at least 20 characters each. | Explain resource sufficiency, current risks, prior action results and proposed improvements with attributable evidence. | Completes the management-review input package. |
| Metric code / Label / Value / Unit / Target / Trend / Controlled source reference | Optional manual-metric group | One manual metric can be entered on creation; its code activates the group. Label, value, unit and source become required when a code is present; Target remains optional. | Use an uppercase letter-led code with letters, digits or underscores that does not collide with a governed metric. Revision restores the first editable metric including Target and retains any additional existing manual metrics unchanged. | Adds an externally sourced indicator alongside system snapshots; leaving code blank omits the new group. |
| Input package evidence / Replacement input evidence | Controlled evidence select | Required for each input version. | Select one CLEAN immutable version from an active same-site document within review classification. Creation/revision snapshots governed metrics and prior objectives again; earlier inputs remain retained. | Pins the immutable review basis. |
| Input submission note | Multiline text | Required; at least 20 characters; current input author only. | Explain readiness for independent QA completeness review. | Moves DRAFT to INPUT_REVIEW. |
| QA decision / Independent completeness rationale / QA input decision evidence | Select, multiline text and controlled evidence select | APPROVE/REJECT, rationale at least 20 characters and CLEAN same-site evidence required. | Review completeness independently of the input author/submitter. | Approval enables MEETING_PENDING; rejection enables a new immutable input revision. |
| Decision date / chair Summary / qms Change Decision / resource Decision / improvement Decision / risk Decision / customer Focus Decision | Date and six multiline text controls | Date on/after approved meeting; each narrative at least 20 characters. | These are the generated executive-output labels. Record explicit decisions on QMS change, resources, improvement, risk and customer focus, even when a reasoned no-change decision applies. | Freezes the accountable-executive output. |
| Objective key / Title / Metric code / Direction / Baseline / Target / Unit | Repeatable texts, numbers and select | 1–20 objectives; unique letter-led uppercase keys; finite baseline/target numbers required. | For each measurable objective choose AT_LEAST, AT_MOST or EQUAL and consistent metric units. The UI creates exactly one linked QUALITY_OBJECTIVE action for each objective. | Defines how target achievement will be evaluated. |
| Due date / Assigned action owner / Owner | Date and named-user selects | Required for every objective/action; due date on/after decision date. | Assign an eligible MANAGEMENT_REVIEW_ACTION_OWNER. The objective and its linked action use the same owner. A visible response button does not authorize another person to submit it. | Makes each management output attributable. |
| Measurement method / Action description / Success criteria | Multiline text controls | At least 20 characters each; measurement method applies to objectives. | Specify the measurement method, work to perform and verifiable success criteria separately. Additional actions still require description and success criteria. | Provides the testable basis for later independent effectiveness review. |
| Action type | Select for additional output actions | Required for each additional action; at most 40 actions overall. | Choose PROCESS_IMPROVEMENT, QMS_CHANGE, RESOURCE_NEED, RISK_OPPORTUNITY, CUSTOMER_FOCUS, EXTERNAL_PROVIDER or OTHER. Add/remove additional actions; the final objective cannot be removed. | Records management outputs beyond objective-linked work. |
| Authoritative route / Expected authoritative reference | Select and conditional text | Reference at least 3 characters required when route is not NONE. | Choose NONE, QUALITY_NCR, QUALITY_AUDIT, PRODUCT_ESCAPE, SUPPLIER_QUALITY, PRODUCT_CONFIGURATION, PROCUREMENT, INVENTORY, DOCUMENTS or EXTERNAL. Route changes clear the expected reference. This assigns accountability rather than opening a downstream record. | Directs the owner to the module where work must actually occur. |
| Accountable-executive output evidence | Controlled evidence select | Required with the executive decision. | Select CLEAN same-site evidence of the meeting outputs, objectives and assigned actions. | Moves the review to ACTION_TRACKING. |
| Completed on / Completion summary / Observed result / Observed objective value / Authoritative record reference | Date, two multiline texts and conditional numeric/text controls | Completion cannot be future; texts at least 20 characters; objective value required only for objective-linked actions; reference required for routed actions. | The assigned owner reports completed work and measured results. Supply the actual value explicitly and cite the authoritative record for work performed elsewhere. | Creates an immutable response in PENDING_VERIFICATION, not a verified result. |
| Assigned action evidence | Controlled evidence select | Required for each response version. | Choose CLEAN same-site evidence that substantiates completion and the observed result. | Retains the owner's evidence for independent review. |
| Decision / Residual risk / Independent verification method / Observed effectiveness | Two selects and two multiline texts | EFFECTIVE, ACCEPTED_MISSED or REJECT; method/result at least 20 characters; risk required. | EFFECTIVE cannot retain UNACCEPTABLE risk. Objective-linked verification compares the reported value with the target; governed metric values must also match the current source count/rate. ACCEPTED_MISSED is only for an actually missed objective, not an ordinary action or a met target. | EFFECTIVE verifies success; ACCEPTED_MISSED finalizes a missed objective with follow-up; REJECT reopens the action for a new response. |
| Controlled follow-up reference / Effectiveness evidence | Conditional text and controlled evidence select | Follow-up reference required for ACCEPTED_MISSED; CLEAN same-site evidence required for every verification. | Cite a real controlled follow-up when accepting a missed objective. The reference does not automatically create follow-up work. | Retains the independent verification basis and accepted-miss accountability. |
| Closure summary / Output accountability / Residual risk / Accountable-executive closure evidence | Two multiline texts, select and controlled evidence select | Required at CLOSURE_REVIEW; texts at least 20 characters; risk ACCEPTABLE or MONITOR. | Confirm every action has a final verified result and every objective is final, then select CLEAN same-site closure evidence. | Closes this review without closing its source-domain records. |
Actions and effects
When to use: An authorized preparer supplies the complete input package.
What it does: Creates a DRAFT immutable input with governed metric and prior-objective snapshots.
When to use: The author submits and independent QA decides.
What it does: Approval enables executive outputs; rejection allows a replacement input with newly captured snapshots.
When to use: An independent executive defines at least one objective and eligible action owners.
What it does: Stores the decision and starts ACTION_TRACKING; adding rows does not execute work in another module.
When to use: Only the assigned owner responds; an eligible independent verifier decides.
What it does: Rejected responses remain in immutable history and the action reopens. All final actions move the review to CLOSURE_REVIEW.
When to use: The executive closure actor is independent of input authorship and approval, with every objective/action final.
What it does: Records final output accountability without changing source Quality, inventory or configuration records.
Lists and states
- Review cards show number, classification, period, meeting, current input version and metric/prior-objective counts. Input metrics and immutable history show metric code, source type, value, unit, trend, source reference and version authors/deciders. Snapshots are not live dashboards; open-work counts reflect capture time.
- Executive cards show objectives, baseline/target direction and final values. Action cards show owner, due date, route, status and immutable response/verification history. Closed reviews retain the named closer, summary and residual risk.
Authority boundary
Management review coordinates accountability; it does not close an NCR, alter an audit, release a baseline, move stock or send a customer/authority message. Expected and actual authority references are evidence fields, not automatic cross-module execution or proof that the referenced record is closed. ACCEPTED_MISSED is not target achievement.