Shawsheen Freight - Onboarding Plan
Documentfinal Shawsheen Freight · onboarding plan · final · 6 Apr 2026
BG-Demo's onboarding plan for a Growth tier account with 40 licensed users, covering the eight-week implementation for the term from 27 Mar 2026 to 26 Mar 2027. It sets phases, milestones and customer duties. It states no price or service levels.
What it says
What this says
As at Fri 9 Oct 2026BG-Demo's onboarding plan for a Growth tier account with 40 licensed users, covering the eight-week implementation for the term from 27 Mar 2026 to 26 Mar 2027. It sets phases, milestones and customer duties. It states no price or service levels.
What it is: an onboarding plan prepared by Laura Penhaligon, Implementation Consultant, for the customer service team. Its purpose is to get them "querying shipper loads, claims and calls together in B-Viz within the eight-week implementation."
Commits: BG-Demo to agree the connector list by the end of week one, have all connectors loading by the end of week five and go live for licensed users by the end of week eight. Amara Obi owns the quarterly review schedule and the renewal conversation ahead of 26 Mar 2027.
Customer duties: name administrators, give access to source systems and nominate a service lead for each team. The risks section says a connector "can stop loading" after a source change, and promises a handover to another named administrator before access is removed.
Not settled: price, availability, support response times and connector delivery dates in days are not stated. The plan refers to the order form for dashboards and reviews, so that executed paper decides terms. The stored status is final, but the plan is not a contract, and the evidence does not show whether the milestones were met.
As found in this document
As at Fri 9 Oct 2026- Date end26 Mar 2027Source: the AI read of this record
- Date start27 Mar 2026Source: the AI read of this record
- Connector list agreedEnd of week oneSource: the AI read of this record
- All connectors loadingEnd of week fiveSource: the AI read of this record
- Go-live for licensed usersEnd of week eightSource: the AI read of this record
- Quarterly review schedule setBefore go-liveSource: the AI read of this record
- Renewal conversation openedAhead of 26 Mar 2027Source: the AI read of this record
Body
Shawsheen Freight Onboarding Plan
Account: Shawsheen Freight, Growth tier, 40 licensed users
Term: 27 Mar 2026 to 26 Mar 2027
Prepared by: Laura Penhaligon, Implementation Consultant
Account owner: Jordan Pike, Account Executive, US
Customer success: Amara Obi
1. Purpose
This plan sets out how we will get your customer service team querying shipper loads, claims and calls together in B-Viz within the eight-week implementation.
2. Scope
- Growth tier: 40 licensed users
- Up to eight connectors to your core systems, agreed in week one
- Dashboards builder and quarterly reviews, as set out in the order form
3. Phases
| Phase | Timing | Lead | What happens |
|---|---|---|---|
| Set-up | Week one | Laura Penhaligon | Admin access set up, licensed users invited, connector list agreed |
| Connectors | Weeks two to five | Laura Penhaligon with your systems team | Each connector built, loaded and checked |
| Testing | Weeks six and seven | Laura Penhaligon with your service leads | Sample questions checked against source records |
| Go-live | Week eight | Laura Penhaligon and Amara Obi | Licensed users move onto B-Viz for daily use |
Read the whole document (2,179 characters)
4. Milestones
| Milestone | Timing | Owner |
|---|---|---|
| Term starts | 27 Mar 2026 | Jordan Pike |
| Connector list agreed | End of week one | Laura Penhaligon |
| All connectors loading | End of week five | Laura Penhaligon |
| Go-live for licensed users | End of week eight | Laura Penhaligon |
| Quarterly review schedule set | Before go-live | Amara Obi |
| Renewal conversation opened | Ahead of 26 Mar 2027 | Amara Obi |
5. Your responsibilities
- Name one or more administrators who can manage users and connectors.
- Give the implementation team access to the source systems for each connector.
- Nominate a service lead for each team that will use B-Viz.
6. Risks
- Source changes: if a system changes after a connector is built, the connector can stop loading. We will flag any connector that stops loading and agree the fix with your team.
- Key people: if an administrator leaves, we will hand over to another named administrator before access is removed.