Offline capture with delayed sync
Field devices can queue work when connectivity drops, then sync when the corridor is back. Sync state is visible so crews know what is still local.
Security
Built for poor signal, clear ownership, and hard questions later.
TrackForm’s security story follows the product: keep field work moving offline, keep roles separated, and keep an auditable trail.
Role-based access
Field users, managers, organisation admins, and platform superadmins get different surfaces. Invite-based onboarding keeps workspace membership intentional.
Audit-oriented history
Operational actions carry user, time, and activity context so teams can answer who changed what during reviews and investigations.
Attachment handling
Evidence attachments are stored with the operational record rather than living only in email threads or personal device folders.
Tenant boundaries
Organisation workspaces are scoped. Platform administration is separated from day-to-day field and manager workflows.
Responsible disclosure
Report vulnerabilities privately through GitHub security reporting where enabled, or email alex@trackform.co.uk.
What we do not claim
No theatre. No invented certifications.
TrackForm does not publish fake SOC/ISO badges. Ask us directly for the controls relevant to your procurement.
Live train feeds and optional external services are supporting context, not the core trust model.
Customer admins remain responsible for inviting the right people and reviewing access in their organisation.