Intro to PrePass — Content Tracker

Track 1 Module · Company Onboarding Framework · Adam Wick + Michael Danielson
Updated April 1, 2026 — Post-Meeting
8
Modules
~90m
Target Duration
4
Ready / Near-Ready
2
Partially Ready
2
Needs Input

Key Takeaways — April 1 Meeting

Below captures the updates from our discussion today. I've folded these into each module's green/red breakdown so you can see the current picture at a glance. Happy to adjust anything — these are suggestions based on our conversation.

DISCUSSED Duration expanded from 30 min to potentially ~90 min
NEW 8th module proposed: Departmental Training
PRIORITY Module 5 (Customers/Market/Product) identified as area for deepest content + confirmation of learning
IDEA CEO welcome video as two-parter — intro + closing bookend
IDEA Modular design to support future audience variations (leadership, external, dept-specific)
1

Mission, Vision & Values

Awareness Partially Ready
👤 Likely source: People Team / Executive 🎯 Framework format: President/CEO video + stories ⏱️ Est. 10–12 min

✓ What We Have

  • Mission statement confirmed: "We exist to make highways safer and more efficient through innovative, data-driven solutions."
  • Core Values confirmed (from official PrePass card): (1) Our mission drives us, (2) We invest in relationships, (3) We challenge ourselves to innovate and improve, (4) We win together
  • Photos of the physical PrePass card in project uploads

✕ Still Needed

  • Vision statement — Michael mentioned getting this from Patty
  • CEO video direction — we discussed a 2-part bookend approach: intro at the beginning + closing at the end of the full course. Open question: does Chris want to record on camera, use a scripted AI voice, or freelance the message? Michael coordinating with Patty.
  • Founding stories / narrative anecdotes that bring the mission to life
Articulate approach: Dedicated slide sequence — motion graphic or video opener with the mission statement, followed by Core Values with a reflection prompt. CEO video embed when available.
2

Foundational Principles / "Drivers"

Awareness Needs Input
👤 Likely source: Executive / Patty 🎯 Framework format: Scenario examples ⏱️ Est. 8–10 min

✓ What We Have

  • Core Values from the PrePass card (same 4 values as Module 1)
  • From our discussion: the idea of "Drivers" — operating beliefs beyond values that senior leaders reference (growth mindset, expansion, people development)

✕ Still Needed

  • Clarification: Michael mentioned possibly reframing as "Drivers" rather than "Foundational Principles" — are these the lexicon senior leaders are using?
  • Specific driver language — "growth-oriented," "develop our people," "expansion" were all mentioned; capturing the full list would shape this module
  • 2–3 real-world scenarios that illustrate these principles/drivers in action
Articulate approach: 2–3 scenario-based slides. Each scenario ties back to a principle/driver. Great fit for Articulate branching interactions.
3

Company History

Awareness Ready to Build
👤 Likely source: People Team / Nicole 🎯 Framework format: Visual timeline ⏱️ Est. 10–12 min

✓ What We Have

  • Full public timeline confirmed: Crescent Project (late 1980s) through AI Toll Insights (Feb 2026)
  • RFID selection (1991), HELP Inc. charter (1993), first CA sites (1995)
  • CVO spin-off (2018), rebrand to PrePass Safety Alliance (2019)
  • Alliance acquires CVO (2022), Chris Murray named President (2023)
  • FleetDrive 360 acquisition (Dec 2025)

✕ Still Needed

  • Headcount growth milestones — Michael mentioned the story from ~150 to nearly 500. Nicole may have this timeline.
  • Geographic expansion story — Phoenix → Utah → remote employees across 30+ states
  • "Sexy numbers" per our discussion — 4M vehicles on the road, employees in 30 states, site count growth
  • Verification that public-source history is OK for internal training use
Articulate approach: Interactive click-to-reveal timeline. Michael mentioned wanting these as "milestone events, not just dates" with the living history feel — interactive clicks that reveal the growth story.
4

PrePass Alliance Relationship

Awareness Ready to Build
👤 Likely source: Executive / Legal 🎯 Framework format: Executive explainer ⏱️ Est. 5–8 min

✓ What We Have

  • Full 3-entity governance structure:
  • PrePass Safety Alliance — 501(c)(3) nonprofit parent, equal public/private board representation
  • PrePass LLC — wholly-owned commercial subsidiary, Chris Murray reports to Alliance CEO Mark Doughty
  • Auxilium, Inc. — Type I supporting org for state-compensated services

✕ Still Needed

  • More safety focus — per our discussion, the safety mission could be emphasized more here
  • Alliance history context — Michael mentioned potentially including more about what the Alliance's history looks like
  • Verification: Confirm detail level is appropriate for new-hire audience
Articulate approach: Org relationship diagram with click-to-reveal detail on each entity. This is close to buildable now — I'll go ahead and assemble a draft using available content so you have something to react to.
5

Customers, Market & Product

Deep Dive Needs Input — Priority
👤 Likely source: Vedrana / Product Team / Marketing 🎯 Framework format: Customer journey + product knowledge ⏱️ Est. 15–20 min (deepest module per our discussion)

✓ What We Have

  • Scale data: 100,000+ motor carriers, 800,000+ commercial vehicles, 584+ bypass locations across 46 jurisdictions
  • Product basics from FG: Preclearance/bypass, INFORM Safety, 360 SmartView, Mobile App
  • Competitive differentiators: Only provider with both RFID + mobile app bypass; only system combining bypass + electronic toll on one device
  • FG Day 1, Day 4, Day 11 content covers product foundations

✕ Still Needed

  • Product team perspective — Michael mentioned scheduling meetings with Vedrana and all product people on "what they want everyone to know"
  • Clearly differentiated product knowledge — we discussed going deeper than other modules here, with confirmation of learning built in
  • Mobile app bypass emphasis — Michael specifically called out wanting people to articulate how amazing the bypass capability is
  • Day-in-the-life journey — animated, friendly, "something people could show their kids and smile at"
  • Customer personas: Owner-operator vs. small fleet vs. large fleet
Note: This is the longest lead-time item since it depends on product team conversations. The existing FG content gives us a foundation to start structuring the module, and we can layer in the deeper product content as it comes in.
Articulate approach: Interactive customer journey + product deep-dives with knowledge checks. The animated day-in-the-life concept is a great fit for Articulate — friendly truck and trucker following the PrePass journey from weigh station approach through bypass and tolling.
6

Revenue Model

Working Knowledge Partially Ready
👤 Likely source: Finance / Carol 🎯 Framework format: Flow diagram ⏱️ Est. 8–10 min

✓ What We Have

  • Self-funded model: $0 in charitable contributions — entirely revenue-driven
  • Revenue streams: Monthly per-truck subscriptions (~$17.65/vehicle, tiered), toll processing fees, gov contracts, compliance services, data analytics
  • FY2024 financials: $193.2M revenue, $162.2M expenses, $30.9M net income

✕ Still Needed

  • EBITDA definition — Michael noted this is a term Carol references frequently; defining it here would help people understand the bonus connection
  • Bonus / commission info — we discussed being specific about revenue terminology so employees understand how company performance connects to them
  • Finance sign-off on what level of detail is appropriate for training
Articulate approach: Animated flow diagram showing how revenue moves through the system. This is the only "Working Knowledge" section — deeper treatment with a sequencing activity. The EBITDA/bonus tie-in could make this feel personally relevant to every employee. I'll put together a draft using the available numbers so you can tell me what's appropriate to keep vs. adjust.
7

Market Goals

Awareness Ready to Build
👤 Likely source: Executive 🎯 Framework format: Strategy snapshot ⏱️ Est. 5–8 min

✓ What We Have

  • Platform expansion strategy: From single-product bypass to comprehensive fleet operations platform
  • Key moves: FleetDrive 360 acquisition (Dec 2025), NECS partnership (May 2025), AI Toll Insights launch (Feb 2026)
  • Geographic expansion: Maine (Nov 2025), Vermont (2026), Motive Marketplace integration
  • Competitive context: Fleetworthy consolidation (Drivewyze + Bestpass, Aug 2024)

✕ Still Needed

  • Verification: Which strategic details are appropriate for new-hire training?
  • Any internal priorities not in the public record?
  • Content refresh cadence — we discussed quarterly or semi-annual reviews to keep this current
Articulate approach: Strategy snapshot — 3–4 priorities with brief context, plus a matching activity. This section would benefit most from a regular refresh cycle since strategy evolves.
8

Departmental Training

Awareness New — Apr 1
👤 Likely source: Michael + Department Heads 🎯 Framework format: Dept intros / awareness ⏱️ Est. 15–20 min

✓ What We Have

  • Framework structure: Michael's original Orgs tab defines 9 dept profiles with columns for: what they do, systems they own, how they interact, when to engage them, common misconceptions
  • 9 departments defined: Sales & Revenue, Marketing, Product, Engineering/Technology, Business Intelligence, Operations/Customer Success, Finance, People Team (HR), Legal & Compliance
  • Org chart tools exist: ADP org chart, Teams org view, Outlook directory

✕ Still Needed

  • Department intros from each team — what they own, how they collaborate, when to engage, misconceptions about what they do/don't own
  • SLT / leadership video intros — Brennan and other leaders introducing their teams
  • Org chart tool walkthrough — how to find people via ADP, Teams, Outlook
  • Michael's idea of starting with HR + Operations as a proof of concept could be a great way to develop the template before scaling to all 9
Note: This is a new module from our April 1 conversation. It has the broadest stakeholder footprint since it touches every department. Michael's POC approach (start with 2 depts, then expand) seems like a practical way to get moving.
Articulate approach: Department cards with click-to-explore detail. Could include a "who do I contact for..." matching activity. The framework structure Michael already built gives us the content template — I'll put together an outline based on your original Orgs tab so you have a starting point to react to and share with dept heads.

Suggested Next Steps

Based on our April 1 discussion — happy to adjust priorities however makes sense for your schedule, Michael.

Future State — Ideas from April 1

Leadership Version Deeper systems + strategy content tailored for managers and above
External / Customer-Facing Shorter version for partners, prospects, website — modular blocks reskinned for the audience
Department-Specific Skins Same base content with audience-specific wrappers (HR, Finance, Call Center, etc.)
Copilot Integration Content structured for Microsoft Copilot so employees can self-serve company info
Content Refresh Cadence Quarterly or semi-annual review with SMEs to keep content current

What Happens Next

Modules 3, 4, and 7 are closest to buildable — they have strong content foundations and primarily need verification. Modules 1 and 6 can be started with placeholders for the remaining pieces. Modules 2, 5, and 8 are waiting on input that Michael is working to gather.

On my end, I'll get started this week on drafts for Module 4 (Alliance Relationship), Module 6 (Revenue Model), and an outline for Module 8 (Departmental Training) so you have something concrete to react to. Happy to adjust the order based on what makes sense for your schedule.

Intro to PrePass — Content Tracker · Updated April 1, 2026 · Adam Wick + Michael Danielson