These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Manufacturing Analytics
- Features
- Review and follow-up
Review and follow-up
Connect reviewer decisions, supporting evidence and assigned actions.
OverviewReview decision inbox×
Manufacturing Analytics · Review and follow-up
New
Review decision inbox
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|
| PS-27469 | 60 | Pending | ER-951 | ||
| PS-47964 | 110 | Pending | ER-876 | ||
| PS-28639 | 300 | Pending | ER-482 | ||
| PS-67943 | 920 | Pending | ER-779 | ||
| PS-61525 | 90 | Pending | ER-891 |
6 of 6 records
ER-951Review decisions · RD-91909
PendingSourcePS-27469
Source revision60
What you can do
Keep a decision tied to its revision
A review decision names the source, source revision, reviewer, decision, time, reason and evidence reference. Pending, Approved, Returned and Rejected have different meanings in the handoff. An Independent Reviewer decides whether the analyzed result can be used. A later change to the source should not make an earlier approval appear to cover a new revision. The revision on the decision is the control that lets the team check this.
Evidence documents can hold a title, attachment, document date, external reference and verification state. A named person verifies the document. Follow-up actions have an assignee, due date, status, completion time and resolution. Those records let an operations manager distinguish the decision about a result from the corrective work opened because of it. The Manufacturing Analytics Overview includes the overdue follow-up exception queue for this reason.
How the work is organized
- Decision. The reviewer records a reason and evidence reference against the exact source revision.
- Evidence. Verification state and verifier show which supporting document was checked.
- Action. The manager assigns a due-dated task and closes it with a resolution.
What to agree during setup
Decide who may review a result and whether the preparer may serve as reviewer. Agree which evidence must be present before approval and how a Returned decision is handled. Define the rule for reopening review after any change to the source revision. For follow-up, agree how due dates are set, when in progress is used and what a satisfactory resolution contains. The manager should settle these decisions before the first production report is treated as released.
Check the handoff on an actual case
Take an analyzed source and inspect its run, measured inputs and evidence document. The reviewer records a decision for that revision. If an input is questioned, return the source with a reason and assign a follow-up action to a named person. The assignee records the resolution and completion date. Before publication, compare the current source revision with the reviewed revision; if they differ, route the current result through review again. This preserves the meaning of the earlier decision. When the action is completed, the manager checks the assignee, resolution and completion date before closing the discussion. The reviewer can still inspect the earlier decision and evidence when explaining why a later revision received a different outcome.
What your team sees
- Review decision inbox — Pending decisions with source revision, reviewer and evidence reference.
- Open follow-up actions — Due-dated work assigned to a person and source.
- Production results for review — Analyzed sources requiring a decision.
Follow the work through
Read result review and follow-up resolution. See roles for the access handoff.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Evidence documents
- Supporting source evidence documents and verification state.
- Follow up actions
- Assigned corrective and follow-up actions with due dates.
- Production snapshots
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
- State history
- Immutable lifecycle transition history for each source.
Who uses it
Permissions- Independent Reviewer
- , Operations Manager, Snapshot Owner, Production Analyst.
Set up Manufacturing Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.