<img height="1" width="1" src="https://www.facebook.com/tr?id=737313050390762&amp;ev=PageView &amp;noscript=1">
Skip to content
Submit a ticket
  • There are no suggestions because the search field is empty.

The Bus Network (TBN) Integration

Keep driver eligibility in lockstep between DriverHub and your dispatch system.

The TBN integration connects DriverHub, your driver compliance platform, with The Bus Network (TBN), your dispatch system. It syncs your driver roster and the compliance data that drives TBN's Do Not Dispatch status, so an ineligible driver never gets assigned to a route.

Overview

Bus companies typically run compliance and dispatch as two separate systems that don't talk to each other. DriverHub decides whether a driver is legally eligible to be on the road; TBN assigns drivers to routes. Without a connection between them, a compliance change in DriverHub — an expired medical card, a lapsed CDL — never reaches the dispatcher, and routes can still be assigned to non-compliant drivers.

This integration closes that gap. DriverHub becomes the single system of record for driver compliance, and TBN acts on it in near real time. The result: one roster, one source of truth, and no driver on the road who shouldn't be.

Key Benefits
  • Close the compliance-to-dispatch loop — Do Not Dispatch status (driven by license number, license expiration date, and medical card expiration date) syncs automatically, so dispatchers never assign a route to an ineligible driver.
  • Eliminate double data entry — New hires are created in TBN straight from the DriverHub hire flow, ending the manual re-keying of every roster and profile change.
  • Controlled, configurable rollout — Job filters lists let each customer scope exactly who syncs, turning the integration on safely one job or account at a time.
How It Works

Once configured, the integration keeps your two systems aligned through a mix of on-demand and scheduled actions:

  1. Configuration — Set up the integration in DriverHub Settings under the dedicated TBN screen: enter your TBN credentials (username, password, tenant ID), choose which jobs to sync, add any exclusions, and map your TBN statuses to DriverHub statuses.
  2. Preview Sync — Use Preview Roster Sync to see exactly who will be created in TBN before anything is committed.
  3. Create on Hire — In the DriverHub Hire Candidate flow, toggle Create Person in TBN to push the driver to TBN immediately at the point of hire.
  4. Create on Profile — Create a driver in TBN on demand directly from their DriverHub profile page.
  5. Daily Sync (4 AM) — A nightly sync updates existing TBN records with the latest email, driver license number, license state, license expiration date, and medical card expiration date from DriverHub.
Setting Up the Integration1. Enter your TBN credentials

Go to Settings → TBN. Under TBN Credential, enter your TBN username, password, and tenant ID. If you need help locating these, see the setup guide linked on the configuration screen.

2. Turn on Sync TBN Roster

Enable the Sync TBN Roster toggle to activate the daily sync between DriverHub and TBN.

3. Scope who syncs
  • Which jobs would you like to sync with TBN? — Select the jobs that should be included in the sync.
4. Preview and save

Click Preview Roster Sync to review who will be created in TBN, then Save Changes to apply your configuration.

Creating a Driver in TBN

You can push a driver into TBN three ways:

Method

When to use it

How

At hire

You want the driver in TBN the moment they're hired..

In the Hire Candidate flow, turn on the Create Person in TBN toggle before saving.

From a profile

You need to add or re-create a single existing driver in TBN on demand.

Open the driver's DriverHub profile and use the create-in-TBN action.

Daily sync

You want existing drivers kept current automatically.

No action needed — the 4 AM sync updates all matched records.
What Data Syncs

Do Not Dispatch in TBN is determined by three values, all of which are kept current by this integration:

  • Driver license number
  • Driver license expiration date
  • Driver medical card expiration date

In addition to these, the integration maps a broader set of driver fields from DriverHub to TBN on creation and, where applicable, keeps them updated during sync:

TBN Field

Sent on Creation

Updated in Sync

Driver Reference ID

Yes

—

First / Last Name

Yes

—

Mobile Phone

Yes

—

Email

Yes

Yes

Address (street, city, state, zip)

Yes

—

Date of Birth

Yes

—

Employment Status

Yes (mapped to TBN status)

Yes

Employment Start / End Date

Yes

End date: Yes

Primary Location / Yard

Yes

—

License Number

Yes

Yes

License State

Yes

Yes

License Issue Date

Yes

Yes

License Expiration Date

Yes

Yes

Medical Card Expiration Date

Yes

Yes

Before You Begin: Initek Requirement

This integration is powered by Initek, which manages the APIs and client credentials that connect DriverHub with TBN. Your setup path depends on your current status with Initek:

  • Existing Initek customers — Enjoy a turnkey configuration process using your active credentials.
  • New customers — Must complete onboarding and account setup with Initek before configuring the TBN sync in DriverHub. You can reach out to Initek via this email address: support@initekconsulting.com

If you're unsure of your status, contact your Customer Success representative before starting configuration.

Who This Is For

Motorcoach and bus operators running both DriverHub and TBN who want to eliminate manual reconciliation and close the compliance gap between hiring and dispatch.