Hammertech + Teletrack — one login, one source of truth, zero duplicate admin.

Real SSO. SAML 2.0 between Hammertech and Teletrack — the operator authenticates against Hammertech once, and Teletrack honours the session. We don't share or store Hammertech passwords; the standard SAML assertion flow handles it. Your Hammertech admin provisions Teletrack as a service provider inside the Hammertech IdP configuration.

Configurable. Default behaviour is 'fail closed' on a Tier 1 site — if Teletrack can't reach Hammertech to verify competency, the pre-start can't run and the machine stays immobilised. Operator sees a clear error and can escalate to site supervisor. Some customers prefer a short cached-state window (e.g. last-known-good for up to 4 hours) where the operator can proceed if their cached competency was current. Configurable per site at setup.

No — that's the point of the integration. Operators exist in Hammertech as the master record. The first time an operator authenticates into Teletrack via SSO, their Teletrack identity is created automatically from the Hammertech data. New operators added to Hammertech appear in Teletrack on next sync without manual import.

Pre-start completion records (pass / fail / override, operator ID, machine ID, GPS, timestamp), photo evidence captured during the pre-start, immobilisation override events with reason, and tagged incidents. Engine hours and machine telemetry don't flow back unless you specifically want them to — those typically live in Teletrack and aren't part of Hammertech's data model.

The head contractor sees what your Hammertech account exposes — Hammertech's own permissions model governs that. Teletrack writes data into Hammertech; what Hammertech does with it from there is Hammertech's configuration. In practice, head contractors set the visibility level they need at project start and Hammertech enforces it.

No. The integration runs through the PROSTART® pre-start workflow — that's the trigger that fires the Hammertech competency lookup and writes the pre-start record back. You need PROSTART® deployed on at least one site to activate the integration. The Track + PROSTART® tier ($31.90 / asset / month) includes it plus the 6-stage rollout.

The Teletrack ↔ Hammertech integration only covers operators and machines on your Teletrack subscription. Other sub-contractors keep their own records in Hammertech. You can use Portal Sharing Mode 2 to give head contractors a unified view of teletrack-managed assets across multiple sub-contractor accounts — that's a separate, complementary capability.

Competency lookups are real-time at pre-start. Pre-start records write back to Hammertech within seconds of completion. Bulk reconciliation jobs run every 15 minutes to catch any retries or queued events. There's no overnight batch — everything is near-real-time.

Month-to-month contract on the Teletrack side, 30 days notice. If you cancel Teletrack, the data already written into Hammertech stays in Hammertech — it's Hammertech's record now. The teletrack-side data is fully exportable through the platform UI or API before cancellation.

Yes — anywhere Hammertech is deployed. We see it most on Tier 1 / Tier 2 construction because that's Hammertech's strongest segment, but customers in resources, infrastructure, and large facilities operations also run it. The integration logic is the same; the value just lands hardest where the regulatory and tender pressure is highest.

Yes. We run a sandbox against a Hammertech test instance during the 6-stage rollout. You see the data flow end-to-end before going live on a real site. Hammertech-side sandboxes are arranged through Hammertech directly — we'll help coordinate.

No. Teletrack doesn't pursue NHVR Electronic Work Diary approval — that's a separate compliance stream. The Hammertech integration covers site safety, operator competency, and pre-start workflow. For HV fatigue compliance you'd use an NHVR-approved EWD product separately.