Help Centre

Learn Tracfast

Step-by-step guides, video walkthroughs and answers to common questions — for drivers, operators and fleet owners.

Coming soon · for now, browse the categories below

Browse by role

Pick the path that fits how you use Tracfast.

🚀

Getting started

Logging in, setting up your tenant, inviting colleagues, configuring regional settings.

🚗

For drivers

Daily checklists, recording video inspections, picking up & returning vehicles.

👔

For operators

Managing hire records, reviewing PCNs, handling damage reports, contact admin.

📊

For fleet owners

Reporting, performance dashboards, regional units & currency, white-label setup.

🎞

Video walkthroughs

Three-minute tours of every major workflow.

💬

Glossary & jargon

Plain-English explanations of platform terms — VRM, PCN, GPS imei, Off-board, etc.

Frequently asked

If you can't find what you're after, ping help@tracfast.io.

What is the difference between a Driver, Contact and Operator?

A Contact is anyone the tenant has on file (drivers, leads, debtors, archived). A Driver is a Contact who's been activated and assigned to vehicles. An Operator is a Tracfast user who manages the platform from inside (account managers, admins).

How does Tracfast detect a missing or returned vehicle?

Telematics positions feed into a tracker pool every few seconds. Returns are recorded against the hire record by the operator (or the driver via the mobile capture flow). The vehicle profile shows the last-known telemetry alongside the active hire.

Can I integrate my own systems with Tracfast?

Yes — see the Developer portal for the API reference and webhook configuration. Common integrations include accounting (Xero/QuickBooks), telematics partners, and PCN providers.

What happens to a contact when they leave?

The contact moves to Archive status. They stay in the contacts list (and on hire/PCN/inspection history) but are hidden from the default view. You can re-include them via the Status filter.

How are personal details kept secure?

Phone, email, address, DOB and DL details are encrypted at rest using a per-platform key. Only authenticated users with a permission-checked session can read decrypted values.