Harborline LogisticsRollout deal room with RelayWorks
More
Theme
Ask a question
Evan BrooksService Operations Manager, Harborline
Mutual plan 3 of 9Executive decision Oct 9

Rollout plan

Three waves from Nov 2 to Jan 11, reusing the pilot's script. Drafted now so the decision includes the plan.

Kickoff plan, updated Sep 24, 2026

What we are trying to achieve

The shared plan for Harborline's company-wide rollout: every wave, who owns it and what needs a decision before each go-live. Prepared by Omar Lewis for Evan Brooks and updated weekly after kickoff.

Customer
Harborline Logistics
Vendor
RelayWorks
Implementation manager
Omar Lewis
Customer project lead
Evan Brooks
Target
All regions live by Jan 15, 2027
Plan
Business, 180 seats

Every service team works the way the pilot team does now: one shared record per handoff, an explicit owner and an acknowledgment, with the dispatch system unchanged.

Live from the Dashboards app: stages the pilot completedOpen the full report

Milestones at a glance

MilestoneWorkstreamStatusOwnerTarget
SSO and SCIM detailsIdentityCustomer actionNadia OrtizSep 30, 2026
Rollout kickoffGovernancePlannedOmar LewisNov 2, 2026
Northeast import and routingDataPlannedOmar LewisNov 13, 2026
Wave 1: Northeast liveGo-livePlannedEvan BrooksNov 16, 2026
Wave 2: Southeast and Midwest liveGo-livePlannedEvan BrooksDec 7, 2026
Wave 3: West and after hours liveGo-livePlannedEvan BrooksJan 11, 2027

Phases

  1. PilotDone Sep 21
  2. Decision and contractOct 9 and 16
  3. SetupNov 2 to 13
  4. Waves 1 to 3Nov 16 to Jan 11
  5. HandoverJan 15
Live from the Dashboards app: pilot handoffs by receiving team and dayOpen the full report

Who owns what

  • Evan BrooksService operations manager, Harborline

    Project lead. Approves configuration and each wave.

  • Nadia OrtizIT security and procurement, Harborline

    SSO, SCIM groups and the security sign-off.

  • Omar LewisImplementation specialist, RelayWorks

    Configuration, imports, testing and training.

  • Rachel KimCustomer success lead, RelayWorks

    Adoption reviews, coaching and escalations.

What could block us

  • SCIM group names per region. Without them, teams are created by hand and drift from the directory.
  • Regional exports. Each region's open handoffs are needed one week before its wave.
  • Waiting reasons. Two pilot users still skip them. Coaching continues and the job aid goes to every supervisor.
Live from the Dashboards app: agreed next actionsOpen the full report

Kickoff checklist

  • Pilot results reviewed with the sponsordone
  • Security pack shareddone
  • SSO and SCIM details confirmedopen
  • Wave dates agreed with regional leadsopen
  • Supervisors named for each teamopen
  • Job aid updated for all regionsopen

Confidence in the Jan 15 target

Moderate to high. The process is proven in the pilot and the waves reuse its script. The main risk is identity setup timing, which is why SSO details are due Sep 30, well before kickoff.

The live page in FuseBase

This document as a FuseBase page, read-only from the RelayWorks workspace. Changes made there appear here.
Open the page