Multi-Party Review Flow

How the Performer → Checker → Approver sequential workflow operates, with rules for each party.

Inspections follow a sequential multi-party review workflow. Each party reviews the previous party's work before passing it forward. Nothing gets signed off without proper review.

Party Roles

Performer (First Party)

The field inspector who physically checks each item:

Goes through each checklist item on-site
Records Pass, Fail, or N/A for each item
Adds notes for failures (mandatory) and observations
Attaches photo evidence with GPS coordinates
Toggles auto-create punch item for failures
Clicks Submit for Review when done

Checker (Middle Party)

The first-level reviewer who validates the Performer's work:

Sees all of the Performer's verdicts, notes, and evidence
Records their own verdicts — agreeing or disagreeing with each item
Can access the Performer's evidence photos for comparison
Clicks Approve & Forward to send to the Approver
If they fail any item, the inspection goes straight back to the Performer to fix — it does not move forward to the Approver

Approver (Final Party)

The final authority who accepts or rejects the inspection:

Reviews verdicts from all prior parties
Sees a comparison view of Performer and Checker verdicts
If satisfied → Approve Inspection — status becomes Completed with Pass verdict
If issues found → Reject — triggers reinspection, cycles back to Performer

Approver review view showing prior party verdicts alongside the approver's own verdict buttons — Approver view — reviewing all prior party verdicts before making the final decision

Rules

Sequential Enforcement

Only the current party can record verdicts — other parties see a read-only view
Parties advance in strict order — no skipping
Each party's verdicts are stored separately and never overwrite another party's data
Verdicts become read-only after submission

What Each Party Sees

Your Role	What You See
Active Performer	Verdict buttons on every item, evidence upload, notes field
Active Checker	Performer's verdicts visible + your own verdict buttons alongside
Active Approver	All prior parties' verdicts visible + your own verdict buttons
Not your turn	Read-only view — all existing verdicts visible, no action buttons

Two-Party Inspections

For simpler inspections with only two parties:

Party 1 is the Performer
Party 2 is the Checker / Approver (combined role)
The workflow has only two steps instead of three

Custom Party Count

Additional parties can be added between Performer and Approver as Checkers. The sequence always starts with a Performer and ends with an Approver, with any number of Checkers in between.

One person per party

Each party must be a different person. If a single person performs and signs off the whole inspection, create a single-party inspection instead of assigning the same user to multiple parties.

Completion Outcomes

Outcome	When	What Happens
All Pass	Approver approves with no failed items and no open punch items	Status → Completed, overallVerdict → Pass
Reviewer Rejects	Any reviewer (Checker or Approver) fails an item	Reinspection triggered — goes straight back to the Performer to fix

Multi-party verdict comparison table showing Performer, Checker, and Approver verdicts side by side — Comparison table — all party verdicts displayed side by side after completion

Policy Controls

These policies (Admin → Inspection Policies) affect the multi-party flow:

Policy	Effect
Reviewer Re-Sign-off	During reinspection, whether every reviewer re-signs each cycle (default) or reviewers with nothing to re-judge are auto-skipped
Approver Auto-Inherit	A dedicated Approver's verdicts are pre-filled with Pass for items where ALL prior parties passed or marked N/A. Applies only when there is a separate Approver after at least one Checker
Reinspection Verdict Rules	Per party (Performer / Checker / Approver), how much must be re-judged each cycle. Previous records are always kept and viewable
Max Reinspection Cycles	Limits how many times an inspection can cycle back

Rejections always return to the Performer

When any reviewer fails an item, the inspection always goes straight back to the Performer to fix it before any further review — this is built in and not configurable. The Approver can only approve when there are no failed items and no open punch items.

Next Steps

Verdicts & Evidence — How to record verdicts and manage evidence
Reinspection — What gets cleared when an inspection cycles back
Completed View — What the final comparison view looks like