One inspection
Request, invite, inspect, close. Each party in its own login.
- RequestContractor or vendor
- InviteQA/QC picks the parties
- InspectAttendance and result on the day
- CloseResult feeds the ITP; NCR if failedgate
Modules / Joint Inspection
Joint Inspection
Vendor, contractor and client inspections on one schedule; results flow into the ITP.
Used by QA/QC, vendors, client inspectors, third-party inspectors, authorities
What it does
When more than one company has to witness the same test, the schedule is the hard part. We put the request, the invitation, the attendance and the result in one place, and the result closes the ITP item.
What the dashboard reads from it
- Inspections this week
- Pass / fail
- Pending client witness
How the work flows
1 flow · 4 steps · 1 gate
Gate: cannot pass until recordedPortal: the outside party does this stepAutomatic: the system does it
Screens
Screens to follow. Ask us for a live walkthrough in the meantime.
What is inside
6 capabilities in 2 groups
Schedule
- Inspection requests against an ITP item or a vendor milestone
- Participants: client, vendor, third party, authority
- One schedule across companies
Results
- Attendance recorded per party
- Result and evidence on the day
- Result closes the ITP itemautomatic
How it connects
RecordsStay in this module. Entered once, with an owner and a date.
DashboardsL1 to L3 read a snapshot of this module on a schedule and print where the number came from.
RolesOne identity across modules. Vendors and the client see only their own packages.
Source per projectManual register in PMT, or the module feed, chosen in Config per project.
See Joint Inspection on your project.
A short walkthrough on your own project structure. Send us your WBS and we load it in before the call.