Reinspection
What happens when an inspection is rejected — clearing rules, cycle tracking, and issue resolution gates.
When any reviewer (Checker or Approver) rejects an inspection, it cycles back to the Performer for reinspection. How much each party must re-judge depends on the reinspection mode configured in your project's Inspection Policies. Previous verdicts, notes, and evidence are always kept for the audit trail and stay viewable in the comparison column — reinspection only decides what must be re-judged, it never deletes records.
When Reinspection Triggers
| Trigger | What Happens |
|---|---|
| Any reviewer fails an item | The inspection goes straight back to the Performer to fix — a Checker's rejection does not move forward to the Approver |
| The final Approver fails an item | Same — cycles back to the Performer |
| Reinspect on a completed inspection | Every completed inspection, passed or failed, shows Reinspect. The project owner or anyone assigned to a party can use it to reopen the inspection for the Performer |
The reinspection counter increments each time the inspection cycles back.
Re-Judging Modes
Each party role has a configurable mode that determines how much they must re-judge on reinspection. Nothing is deleted — items that must be re-judged are simply shown as pending until the party records a fresh verdict; previous records stay viewable in the comparison column.
| Mode | Effect | When to Use |
|---|---|---|
| Re-do everything | The party re-judges every item from scratch (shown as pending). Previous records kept. | When you want the performer to re-evaluate everything without bias from prior results |
| Re-do failed only | The party only re-judges items they previously failed. Passed/N/A items carry forward. | When you only need the failed items re-checked — saves time on large checklists |
| Carry everything forward | Nothing needs re-judging — previous verdicts carry forward. The party can still update any item. | When you want to keep prior results and selectively update — useful for minor corrections |
Default Configuration
| Party | Default Mode |
|---|---|
| Performer (first party) | Re-do everything |
| Checker (middle parties) | Re-do failed only |
| Approver (final party) | Re-do failed only |
Configure Per Role
Reinspection modes are set in Inspection Policies (Admin → Inspections → Policies) and can be configured at the organization level (defaults) with project-level overrides. Each party role has its own setting.
Reinspection Limits
| Policy | Default | Effect |
|---|---|---|
| Max Reinspection Cycles | Unlimited | When set, the reviewer's submission is refused once the limit is reached, with a message naming the limit and telling them to ask a project admin to adjust the policy. |
If the limit is reached, the inspection stays in its current state and cannot be cycled back. This prevents endless inspection loops on problematic items.
Issue Resolution Gate
Open Issues Block Reinspection
The Performer cannot submit their reinspection until ALL linked issues are resolved (Fixed or Closed) — this always applies. The "Require Issue Resolution Before Reinspection" policy adds a second gate: Reinspect on a completed inspection is refused while any linked issue is still open.
The flow with issue resolution:
- Inspection fails → quality issues created for failed items
- Assignee fixes the defects → marks issues as Fixed
- ALL sibling issues must be Fixed
- Only then can the Performer submit the reinspection
- On successful reinspection advancement → Fixed issues auto-close
A passing submission also closes every linked issue marked Fixed, even when the inspection was never sent back — for example a single-party inspection where you raised an issue during the run, had it fixed, and then passed the item.
Issue Rules During Reinspection
- The Performer can only FIX issues — they cannot close them directly
- ALL sibling issues (from the same inspection) must be Fixed before any single issue can close
- Auto-close fires when the Performer advances during reinspection AND all issues are Fixed
The Reinspection Cycle
Next Steps
- Issue Lifecycle — How issues move through their status workflow
- Multi-Party Flow — The sequential review process
- Completed View — What the final outcome looks like
Questions
What do I do when the reinspection limit is reached?
The reviewer's fail can't be submitted, and the inspection stays where it is. Someone who can edit Inspection Policies can raise Max Reinspection Cycles, or clear it for no limit. The reviewer can then submit again.
Why were issues created when nobody switched on Auto-create issue?
Your project has Auto-Create Issues on Fail turned on in Inspection Policies. When an inspection is sent back, an issue is raised for every failed item, whatever the switch in the item said.
Do Fixed issues stop my reinspection from being submitted?
No. Only a linked issue that's still Open or In Progress blocks the submit. When the inspection passes, every linked issue marked Fixed closes on its own, even on a single-party inspection that was never sent back.