Verdicts & Evidence
How to record Pass/Fail/NA verdicts, attach photo evidence with GPS, and manage notes on checklist items.
Each checklist item in an inspection needs a verdict. This guide covers how to record verdicts, what's required, and how to attach evidence.
Verdict Options
| Verdict | Symbol | Color | Notes | Evidence |
|---|---|---|---|---|
| Pass | ✓ | Green | Optional | Optional (required if the item itself requires evidence) |
| Fail | ✗ | Red | Mandatory | Required if policy enabled, or if the item requires evidence |
| N/A | — | Gray | Optional | Required if the item itself requires evidence |
Click the verdict button on the item row. To change, click a different button — the previous selection is replaced immediately. Verdicts are stored locally until you submit.
Recording a Verdict
From the table (desktop):
- Find the checklist item row
- Click Pass, Fail, or N/A button
- For failures — the notes field highlights as required
Then, in the item detail sheet:
- Click the item label to open the side drawer — it shows the verdict you recorded on the row; the sheet itself has no verdict buttons
- Add notes (a required Remark on a failure), any measurement the item asks for, and evidence
- Click Save Details (Confirm Failure on a failed item) — the details are held on the page until you submit
Notes
Notes provide context for your verdict:
- Mandatory on Fail — explain what's wrong. Be specific: "Rebar spacing 180mm, drawing specifies 150mm" not just "Failed".
- Optional on Pass — add observations: "Within tolerance, 148mm measured"
- Optional on N/A — explain why not applicable: "Section not yet poured"
- Multi-line — supports detailed descriptions
- Notes are visible to all subsequent parties during review
Use specific, measurable descriptions in failure notes. Reference drawing numbers, specifications, and measured values. These notes become part of the permanent record and may be reviewed by clients or auditors.
Photo Evidence
Attach photos to document the condition of each item:
- Open the item's detail sheet — click the item, or its Remarks button (Edit once the item has a verdict) — and go to Evidence
- Take a photo or select from your device gallery
- GPS coordinates are captured from your device when you record the verdict, and shown in the item detail drawer
- Up to five photos can be attached per item
- The item row shows a camera icon with the number of photos attached
What Gets Captured
| Data | Source | Stored |
|---|---|---|
| Photo | Camera or gallery | Uploaded to project storage |
| GPS coordinates | Device location at the time of the verdict | Recorded on the verdict, covering every photo attached to it |
| Timestamp | Device clock | Recorded on the verdict |
| Captured by | Logged-in user | Attributed to the submitting party |
The coordinate belongs to the verdict, not the photo
PleoStack records one location per verdict — read from your device when you record it — rather than reading location data out of each image file. Photos attached to the same verdict therefore share its coordinate, and a photo chosen from your gallery is stamped with where you were when you recorded the verdict, not where the photo was originally taken.
Evidence Policies
Require Evidence on Fail
When this policy is enabled (Admin → Inspections → Policies), at least one photo must be attached for every failed item. The evidence field becomes required — you cannot submit the inspection without it.
Item-level evidence overrides the policy
Checklist items configured to require evidence always require a photo on any verdict (pass or fail), even when the "Require Evidence on Fail" policy is off. An item can name Document or Measurement as its evidence type, but the only capture control is the camera / gallery photo picker. The item detail drawer marks the field as required and blocks submission until evidence is attached.
Best Practices
- Capture photos at the point of inspection — don't wait until later
- Include reference markers (ruler, level, tape measure) in photos for clarity
- Location and timestamp are recorded with the verdict automatically — no manual entry needed
- Evidence is immutable after submission — it becomes part of the audit trail
Auto-Create Issues
For failed items, you can toggle automatic issue creation:
- Toggle ON → a quality issue is created in the Issues register, linked to this inspection item
- Toggle OFF → no issue created (you can still create one manually later)
- The toggle's default state follows the project's inspection policy setting
- Performers always default to OFF (they don't raise issues against themselves)
Auto-created issues inherit the checklist item label as the title and maintain a link back to the source inspection. This enables automatic closure during reinspection when all issues are resolved.
Submission Validation
Before you can submit, all requirements must be met:
| Check | Requirement |
|---|---|
| All items have verdicts | Every item needs Pass, Fail, or N/A |
| Notes on failures | Every failed item needs explanatory notes |
| Evidence on failures | Every failed item needs at least one photo (when policy enabled) |
Items missing required data show validation warnings. The Submit button shows a count of outstanding items.
Next Steps
- Multi-Party Flow — How your verdicts flow through the review chain
- Reinspection — What happens to your verdicts when an inspection is rejected
Questions
Can I attach a PDF or document instead of a photo?
No. Evidence is photos only, from the camera or your gallery, up to five per item. That's true even when an item names Document or Measurement as its evidence type.
Can I change a verdict after I've submitted?
No. Once you submit, your verdicts are read-only. If a reviewer fails an item, the inspection comes back to the Performer and you judge it again.
Does the issue get created as soon as I switch on Auto-create issue?
No. It's created when you submit, and it goes to the Performer at High priority. That person gets a notification, unless they raised it themselves.