Product architecture
How CheckPilot works under the hood
A multi-tenant platform built around three actors — Super Admins, Company Admins, and Employees — with a rules engine that turns simple checklists into compliance-grade workflows.
System layers
L1
Client
- • Mobile web
- • Tablet PWA
- • Admin desktop
L2
API Gateway
- • Auth & rate limit
- • Localization
- • Multi-tenant routing
L3
Services
- • Checklists
- • Assignments
- • Reports
- • Billing
L4
Data
- • Postgres
- • Object storage
- • Search index
Core flow: from field to report
1
Field capture
Employee opens an assignment on mobile and completes the checklist.
2
Rules engine
Required items, conditional branches, and incident triggers evaluate in real time.
3
API ingestion
Submission posts to the assignments service with offline-safe retries.
4
Persistence
Results stored with audit trail; events emitted to the analytics pipeline.
5
Notifications
Admins notified of overdue items, failed checks, and incident reports.
6
PDF rendering
On-demand PDF generation with company branding and signatures.
Rules engine
When
→
Then
Required item is unchecked
→
Block submission and highlight the item.
Item flagged as 'incident'
→
Auto-create an incident report and notify Company Admin.
Assignment past due date
→
Mark as overdue and escalate after 24h.
Photo item missing in safety checklist
→
Warn user but allow submit with reason.
Weekly completion volume
Checklist mix by category
Tenant isolation
Row-level scoping across every service.
Audit trail
Every state change is logged and replayable.
Localization
EN/ES today; pluggable locale packs.