Quality
Quality manages punch lists or defect findings from reporting, assignment, work, completion, through separate verification. Each finding can have a code, area, priority, due date, project, person in charge, free reference, private photo evidence, reporter, verifier, and audit history.
Done status and Verification are two different controls. The person doing the work can declare a fix done, then an authorized person verifies the result. Vasco saves the time and person who verified, plus the change history when the audit feature is available, so close-out doesn't depend on a single status mark.
Before you start
Have this ready
- Agree on the definitions of High, Medium, and Low priority.
- Decide who does the work and who may verify it.
- Prepare the project, area, due date, and relevant photo evidence.
- Don't use delete to close a finding that really happened.
Done when
- The finding has an actionable description and a unique code.
- Person in charge, project, priority, and due date are filled in where relevant.
- Done and Verified are used as separate stages.
- Corrections and deletions are made with an understanding of the audit trail and evidence.
Understand the data and the finding cycle
| Field/action | Purpose | Rule |
|---|---|---|
| Code | Punch list identity | Can be left empty when creating; Vasco generates PL-#### |
| Description | Explains the defect and the expected result | Required |
| Area | Physical location of the finding | Use consistent terms |
| Priority | High, Medium, Low | Affects focus, not status |
| Status | Open, In progress, Done | Done is not the same as Verified |
| Assigned to | Person in charge of the fix | Only active staff appear |
| Related reference | Report ID, zone, note, or free link | Not an automatic relation |
| Photo evidence | One private photo path | A new upload replaces the form value |
| Verification | Timestamp and verifier account | Can be undone separately from the status |
Don't verify just because the status is Done
Check the fix and the evidence first. Verifying adds the verifier's stamp; the Done status on its own only says the work is considered finished.
Manage findings through close-out
- 1
Add finding
Fill in the required description; add a code or leave it automatic, plus area, priority, initial status Open, due date, person in charge, project, and reference if any.
Result: The finding appears in the list and the audit history records Created when the feature is available.To cancel / undo: Choose Cancel before Save. No text data is created.If something goes wrong: If an extra field isn't supported by the database version, the core data may still be saved without that field. - 2
Upload photo evidence
Choose the file and wait for the upload to finish before Save. The photo is stored privately and the screen uses a temporary link.
Result: The photo path is linked to the finding.To cancel / undo: Clear the photo from the form before Save. A file that was already uploaded may stay in storage even if the dialog is canceled. - 3
Assign and set a due date
Choose an active staff member and a realistic due date. Use the High priority or Overdue filter for review.
Result: The person in charge and the risk of delay can be monitored.To cancel / undo: Edit again and clear the person in charge/due date if wrong. - 4
Change to In progress
Edit the finding when the fix starts. Add the latest reference or evidence if it helps.
Result: The status history records the change when the audit is available.To cancel / undo: Edit back to Open if the change was a mistake; the change history may remain. - 5
Mark as Done
Change the status after the person doing the work finishes the fix and the evidence is sufficient.
Result: The finding is no longer counted as open/overdue.To cancel / undo: Edit the status back to In progress/Open if it isn't really finished. - 6
Verify separately
Open the Verify action after the inspector accepts the result. Vasco saves the time and the verifier account.
Result: The finding gets the Verified display status.To cancel / undo: Use Undo verification to clear the stamp; the Done status doesn't change automatically. - 7
Open details and audit
Check the reporter, verifier, reference, photo, and action timeline before the close-out meeting.
Result: Decisions can be traced to the person and time.If something goes wrong: An empty timeline may mean the audit table isn't available yet; the core details can still be used. - 8
Delete only test/duplicate data
Read the name/code on the confirmation. Delete only if the finding should never have existed.
Result: The row is permanently deleted; the delete event is recorded in the audit when possible.To cancel / undo: Choose Cancel. After Delete, there is no restore on the screen.
Status, priority, and verification
| Value | Meaning | Reversible? |
|---|---|---|
| Open | Not started/waiting for follow-up | Yes, edit the status |
| In progress | The fix is underway | Yes |
| Completed | The person doing the work says the fix is done | Yes; not Verified |
| Verified | The inspector has stamped the verification | Yes, Undo verification |
| Overdue | Due date before today and not done/verified | Correct the status/due date to match the facts |
| High priority | Needs top attention | Yes, edit the priority |
Undo, correct, or delete safely
| Situation | The right action | What still happens |
|---|---|---|
| Form not saved | Choose Cancel | The finding doesn't change |
| Wrong status | Edit it to the correct status | The change history may remain recorded |
| Wrong verification | Choose Undo verification | The work status stays as it was |
| Wrong photo | Edit, clear or replace the photo, then Save | The old file in storage may not be deleted automatically |
| Finding deleted | No undo | The row is permanently gone; the delete audit may remain |
Don't invent an undo
If the screen doesn't offer an undo, edit, or delete button after a transaction is saved, this documentation does not assume the action can be reversed. Note the reference, stop any follow-up actions, then ask for a correction through the main admin or Vasco support.
Troubleshooting
| Symptom | Possible causes | What to do |
|---|---|---|
| Duplicate/odd automatic code | The sequence is based on the count at creation time | Use a unique explicit code and report the conflict to your Admin |
| Person in charge doesn't appear | The staff member is archived/inactive | Activate them or choose the right active staff member |
| Verification isn't available | The verification column/migration isn't active yet | Ask your Admin to update the database |
| Photo doesn't show | The signed URL failed/expired | Reload the details or upload again from the source |
| A finding was treated as done when it wasn't | Wrong status/verified | Undo the verification and restore the status before continuing the fix |
Questions and answers
What's the difference between Done and Verified?
Done is the work status; Verified is a separate inspection stamp with the time and verifier account.
Do I have to type the code?
Not when creating. If it's empty, Vasco tries to generate a PL-#### code automatically.
Can a verification be undone?
Yes, through Undo verification. The Done status isn't changed automatically.
Does the related reference open an automatic relation?
No. That field is free text for an ID, zone, note, or URL.
When may I delete a finding?
Only for test/duplicate data that should never have existed. Real findings are better closed through status and verification.