These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Penetration Test Management
- Features
- Disposition and corrective actions
Disposition and corrective actions
Review failed inspection scope and verify corrective work before closure.
OverviewInspections awaiting review×
Penetration Test Management · Disposition and corrective actions
New
Inspections awaiting review
Approval conditions
| Inspection number | Subject reference | Inspection type | Assigned to | Status | |
|---|---|---|---|---|---|
| INS-86213 | Review ins-280 | Incoming | Review | ||
| INS-60587 | Review ins-906 | In process | Review | ||
| INS-81488 | Review ins-360 | Final | Review | ||
| INS-59213 | Review ins-822 | Service | Review | ||
| INS-18631 | Review ins-339 | Incoming | Review |
6 of 6 records
Review ins-280Inspections · INS-86213
IncomingStatusReview
What you can do
Disposition and corrective actions in daily work
An inspection in Review reaches a human disposition decision. The reviewer looks at its requirement results and decides whether the scope is accepted or rejected. Failed check evidence remains with the inspection. A linked nonconformance records the issue, severity and progress through containment, investigation and disposition. The corrective action records the root cause, response, owner and due date.
How the work is organized
- Decide from checks. Inspection Reviewer opens the required results before accepting or rejecting an inspection.
- Track the issue. A rejected inspection stays linked to its nonconformance and any corrective actions.
- Verify independently. Effectiveness Reviewer assesses the completed action before the issue can close.
What to agree during setup
Decide who may review an inspection and who independently assesses corrective effectiveness. The owner should know what completion evidence to provide before a review. If the reviewer finds the response ineffective, work returns to implementation rather than being closed. Closure of the linked issue depends on acceptance of its corrective actions.
Use the inspection reference on the nonconformance to trace the failed check. Corrective Action Owner should make the root cause and action specific enough for someone else to assess after completion. Effectiveness Reviewer should open the linked issue and confirm which actions are still awaiting review. Keep the owner’s completion separate from the review decision.
Check the handoff on an actual case
Use an inspection with a failed check. Have the reviewer reject it, preserve its failed result, and create a linked nonconformance. Assign a corrective owner, record the root cause and action, and move it to effectiveness review after completion. A different reviewer checks the outcome. Rehearse a failed verification first, then a successful one, and confirm that the issue closes only after the linked actions are accepted.
Ask the person receiving the work to open the record without extra explanation. They should be able to tell what the current state means, which evidence supports it, and what decision they are expected to make. If they cannot, revise the entry and repeat the handoff with the same case.
A corrective action has an owner, due date, completion date, root cause and action text. The owner can describe the completed work there before handing it to Effectiveness Reviewer. That reviewer should compare the response with the original failed check through the linked issue and return ineffective work to implementation for another attempt.
What your team sees
- Inspections awaiting review — Reviewers can inspect checks before accepting or rejecting the inspection.
- Nonconformance queue — Open the related evidence and working context when making the next decision.
Follow the work through
See the related process for the handoff, decision and rehearsal. Review roles before granting access and the data model when preparing records.
What it keeps track of
Data model- Inspections
- Scheduled and completed inspections with type, assignee and lifecycle status.
- Inspection checks
- Individual requirement checks captured against an inspection, with observation, result and evidence.
- Nonconformances
- Nonconformances raised from failed inspection checks, with severity and disposition status.
- Corrective actions
- Root cause and corrective action plans owned by a person, tracked through effectiveness review.
- People
- Team members who perform inspections, own corrective actions, audit and acknowledge controlled documents.
Who uses it
Permissions- Inspection Reviewer
- , Corrective Action Owner, Effectiveness Reviewer, Admin.
Set up Penetration Test Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.