The due-date control loop
- Set the intervalUse the approved procedure, manufacturer guidance, history, and risk to support the interval decision.
- Record the next due dateKeep the date traceable to the last completed calibration and the chosen interval.
- Review upcoming workUse lead times that give the team enough time to schedule internal or outside-provider work.
- Escalate overdue workKeep overdue instruments visible and follow the organization's procedure for the exception.
- Close the loopRecord the calibration result, certificate, and next due date so the cycle starts again.
Use status to prioritize the next action
| Status | Meaning | Next action |
|---|---|---|
| Current | The next due date is more than 30 days away. | Continue normal control. |
| Due soon | The next due date is within 30 days. | Schedule or confirm the work plan. |
| Overdue | The next due date has passed. | Follow the approved overdue procedure and keep the exception visible. |
| Out of service | A failed result or manual decision makes the instrument unavailable. | Prevent use and follow evaluation, repair, recall, or disposition steps. |
Make reminders actionable
- Choose lead times such as 30, 14, 7, and 1 day when the work requires planning.
- Send summaries on weekdays when the team can act.
- Include workspace members, instrument assignees, or additional recipients who own the response.
- Keep overdue work in the summary until the record is updated.
- Review recipients and ownership when people or responsibilities change.
The date is a control point, not the whole decision
A date can tell the team that a review is due. It cannot determine whether an extension, risk assessment, interval change, repair, or recall is acceptable. Document those decisions through the approved quality procedure and keep the register aligned with the result.
GagePilot connects the due date to status, reminders, records, and evidence so the team has a clear place to act.