Fleet, compliance, tracker, and training questions
Clear answers for buyers comparing software subscription, driver workflows, hardware-backed tracking, and regulatory telematics needs.
- Support
- AU
- Training
- Academy
- Content
- Static + DB
Australian heavy vehicle operators
DB-backed course catalogue
Static pages, dynamic blog/training
Frequently asked questions
Does Trackify cover both EWD/fatigue and TCA/TMA/RIM telematics?
Yes, the public product story includes both. EWD/fatigue is part of the compliance platform, while TCA/TMA/RIM is positioned as an optional regulatory telematics workflow where vehicles and schemes require it.
Do customers need Trackify-supplied trackers?
Not always. Some fleets can use mobile GPS or existing compatible telemetry, but FMC650 packages are positioned for hardware-backed GPS and regulatory evidence needs.
Which TMA scheme families are represented?
The v2 positioning includes HML, PBS, OSOM, TPAA, and Road Train monitoring workflow language. Final accreditation wording must be confirmed before public claims are hardened.
What remains static and what is content-managed?
The main public website pages are static in Next.js for design control. Blog and training/course content are Mongo-backed and can be managed through backend APIs and MCP.
Build a fleet compliance rollout that matches your operation
Talk through software, drivers, training, FMC650 trackers, TCA/TMA/RIM needs, and enterprise onboarding.
Pricing assumptions are visible on the pricing page and should be confirmed before rollout.