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
- Inspections and checks
Inspections and checks
Record assigned inspection work and requirement results with evidence.
OverviewMy inspections×
Penetration Test Management · Inspections and checks
New
My inspections
Inspections
| Inspection number | Subject reference | Inspection type | Scheduled at | Status | Assigned to | |
|---|---|---|---|---|---|---|
| INS-54294 | Planned ins-438 | Incoming | 10 Oct | Planned | ||
| INS-96416 | In progress ins-118 | In process | 16 Oct | In progress | ||
| INS-49905 | Review ins-410 | Final | 17 Oct | Review | ||
| INS-24151 | Accepted ins-638 | Service | 15 Oct | Accepted | ||
| INS-92944 | Rejected ins-556 | Incoming | 23 Oct | Planned |
6 of 6 records
Planned ins-438Inspections · INS-54294
IncomingScheduled at10 Oct
StatusPlanned
What you can do
Inspections and checks in daily work
The inspection record identifies the subject, inspection type, scheduled date and assigned person. Individual checks sit under that inspection. Each check names the requirement and holds an observation, result and any evidence. Pending, Pass, Fail and not applicable mean different things; a failed result should remain recognizable when the inspection moves to review.
How the work is organized
- Assign the inspection. Inspection Reviewer records the subject, type, scheduled date and assignee.
- Work each requirement. Tester records an observation, result and any attachment on the check under that inspection.
- Submit complete checks. Tester clears required Pending results before the inspection reaches Review; Fail remains visible.
What to agree during setup
Before the first inspection, agree which requirements apply to each type and what evidence is expected for a passing or failed check. The assignee should know when not applicable is a justified result. The reviewer should have a clear way to distinguish unfinished work from an intentionally excluded requirement when deciding the inspection’s disposition.
Give the assignee a recognizable subject and a scheduled date. For every required check, decide what observation is needed when the result is Fail and when not applicable is justified. Inspection Reviewer should be able to open the same inspection and explain why each result supports or blocks the disposition. Keep failed attachments with their original check.
Check the handoff on an actual case
Plan a Service inspection for one subject and assign it to a named person. Add requirement checks, mark one Pass and another Fail, and attach evidence to the failed check. Confirm that the reviewer can see both the result and its observation. Leave one required check Pending and rehearse the review handoff; it should remain unfinished until the assignee completes it.
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.
The check result belongs to the inspection, while the inspection’s status describes the overall handoff. Inspection Reviewer should open the checks before changing the overall status. A completed Pass check does not erase another required check still marked Pending, and a not applicable result should keep its reason in the observation.
What your team sees
- My inspections — Assignees can see planned work and check results for each subject.
- Check results — Tester can find Pending, Fail and not applicable results for review.
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.
- People
- Team members who perform inspections, own corrective actions, audit and acknowledge controlled documents.
Who uses it
Permissions- Tester
- , Inspection 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.