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.
- Aerospace and Defense QMS
- Features
- Inspection execution
Inspection execution
Assign an inspection, record characteristic results and submit a complete evidence set for review.
OverviewMy inspections×
Aerospace and Defense QMS · Inspection execution
New
My inspections
Inspections
| Inspection number | Subject reference | Inspection type | Scheduled at | Status | Assigned to | |
|---|---|---|---|---|---|---|
| INS-84277 | Planned ins-679 | Incoming | 26 Oct | Planned | ||
| INS-71574 | In progress ins-282 | In process | 21 Oct | In progress | ||
| INS-73223 | Review ins-889 | Final | 15 Oct | Review | ||
| INS-46848 | Accepted ins-589 | Service | 19 Oct | Accepted | ||
| INS-29231 | Rejected ins-782 | Incoming | 10 Oct | Planned |
6 of 6 records
Planned ins-679Inspections · INS-84277
IncomingScheduled at26 Oct
StatusPlanned
What you can do
Start with the inspection scope
Quality Manager creates an inspection for the part or assembly under review, chooses incoming, in-process, final or service work, sets the planned date and assigns an Inspector. The subject reference gives the team a common case to discuss. The inspection stays planned until the assigned work begins. Inspectors then record each characteristic as a linked check, so a result can be read with its own requirement, observation and attachment.
A final inspection of a revised assembly is a useful pilot case. Quality Manager identifies the assembly in the subject reference and assigns the person who will examine it. Inspector opens the inspection, checks the requirement for each characteristic, records what was observed and marks the result. A photograph or document can be attached to the relevant check. The evidence stays with that check when the inspection moves to review.
How the work is organized
- Assignment. The inspection carries its type, planned date, subject and responsible person.
- Characteristic evidence. Each linked check keeps the requirement, observation, result and attachment together.
- Submission. The inspection reaches review after linked checks have recorded requirements and results.
What to agree during setup
Agree how the team identifies a subject in the inspection number and subject reference. Define when inspectors use incoming, in-process, final and service types. Choose what evidence belongs on each characteristic and which observations need an attachment. These choices make it easier for a reviewer to find the exact result behind an overall decision.
Agree who creates inspections and who is responsible for recording linked checks. Quality Manager can use the open inspection list to see planned and active work. Inspector can use the assigned list to keep daily work separate from the review queue. Keep the same naming convention for the first pilot cases so a check can be found from its inspection.
Check the handoff on an actual case
Run the revised assembly through a characteristic that passes and one that fails. Inspect the recorded requirement and result on both checks before submitting. Leave a result pending on a test copy and confirm that the case stays out of review. Then complete the missing result and send the inspection to the reviewer. The reviewer should be able to open the same subject, see the linked checks and reach the evidence without asking the inspector to reconstruct the test.
The handoff is the moment when the Inspector has finished recording, not an acceptance decision. The reviewer decides that outcome in Inspection disposition.
What your team sees
- My inspections — Assigned work with subject, type, scheduled date and current status.
- Open inspections — Planned, active and review cases for the quality team’s daily queue.
- Inspections in review — Cases whose linked results are ready for a reviewer decision.
Follow the work through
Inspection to disposition follows a case from assignment to the reviewer decision. Start with a pilot lists the setup decisions to settle first.
What it keeps track of
Data model- Inspections
- Quality inspections for aerospace and defense programs: incoming, in-process, final and service verification of parts and assemblies.
- Inspection checks
- Characteristic-level inspection checks recorded against an inspection, with requirement, observation, result and evidence.
- People
- QMS people directory: quality managers, inspectors, auditors and approvers, each linked to their platform user.
Who uses it
Permissions- Quality Manager
- Plans and assigns.
- Inspector
- Records characteristic results.
- Quality Approver
- Reviews the submitted evidence.
Set up Aerospace and Defense QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.