Data location
Confirmed in scopeThe proposed storage region, service provider processing locations and contractual position are confirmed for the engagement.
Review material: Processing boundary and subprocessor reviewSecurity and procurement
The proposed storage region, service provider processing locations and contractual position are confirmed for the engagement.
Review material: Processing boundary and subprocessor reviewThe access model and organisation scoping can be reviewed against supporting application and database evidence.
Review material: Architecture and data flow summaryTransport and hosting controls are reviewed with the evidence available for the proposed customer scope.
Review material: Architecture and data flow summaryCustomer roles, access pathways and onboarding controls are confirmed for the pilot and reconsidered for any wider rollout.
Review material: Pilot onboarding and access planThe agreed device, connectivity pattern and workflow are validated before site use.
Review material: Device, connectivity and support planRequired export formats are confirmed for the pilot. Integration work remains a separate design and approval decision.
Review material: System boundary and required output scheduleCustomer review material
Start with the public documents, then request the evidence that depends on the proposed customer, site and workflow. Contractual documents remain controlled by FaultPilot's legal team.
Public website privacy and usage terms remain available without a diligence request.
Open public legal documentsArchitecture, processing boundary, access, device and contractual material is assembled for the proposed engagement.
Questions, available evidence, accountable owners and unresolved gaps are kept explicit before site use.