RaisedashOrientation is day one—not the whole journey.
Raisedash is building a structured follow-up workflow for the months when a driver is learning your equipment, routes, customers, and expectations.
Planned driver program
J. Okafor · started Jun 30
Day 1 · Orientation wrap-up
Facility walkthrough · 3 short lessons
The problem
The structure often disappears after day one
A driver can finish orientation and still need help learning your equipment, routes, customers, and expectations. But once the driver is on the road, check-ins often depend on someone remembering to make them happen.
The gap is usually not a lack of care. It is the lack of a repeatable workflow. We are designing a simple way to give follow-up a steady rhythm and keep the work connected to the driver's training record.
Where the gap shows up
- No shared plan for the first months
- Check-ins that depend on memory
- Small concerns that go quiet until they become bigger
- Follow-up work separated from the driver's training record
How it works
A steady rhythm through the first 90 days
This product preview shows the repeatable workflow we are building for follow-up after orientation.
- 1
Start with a clear plan
Build a day-1-through-90 program around the milestones that matter to your fleet.
- 2
Set a steady rhythm
Choose when check-ins and refresher lessons should be assigned during the first 90 days.
- 3
Follow up where needed
Choose a targeted refresher when a check-in or quiz shows that a driver needs more help.
- 4
Keep the follow-up record
Completed follow-up training will stay with the driver's other Raisedash activity.
In development · corrective action
When something happens, make the response consistent.
The workflow will connect an event recorded by your carrier with the follow-up training your team chooses.
Planned corrective action — S. Patel
Concept preview with sample data
Event recorded
Roadside inspection issue · Tue 2:14 PM
Refresher assigned
Targeted lesson texted to driver
Completed · quiz passed
Done on the driver's phone
Planned: follow-up completion appears with the driver's training activity
What we're building
A simple structure for meaningful follow-up
A starting program
Start with a day 1, week 1, day 30, day 60, and day 90 structure that your fleet can adjust.
Regular check-ins
Give follow-up work a clear place in the driver's first months with the fleet.
Follow-up lessons
Send short refresher lessons after orientation instead of waiting for a problem.
Help where it is needed
Choose follow-up training when a check-in shows that a driver needs more help with a topic.
A consistent response
Connect a carrier-recorded event with the follow-up training your team chooses.
Progress through 90 days
See where a driver stands in your fleet's day-1-to-90 program.
One connected record
Keep completed follow-up training with the driver's other Raisedash training activity.
Programs that fit the driver
Adjust the program around a driver's role, terminal, equipment, or start date.
FAQ
Questions, answered
What's in a first-90-days program?
This workflow is still in development. We are designing milestones for day 1, week 1, day 30, day 60, and day 90, with check-ins and refresher lessons your fleet can adjust.
What is the corrective-action loop?
We are designing it to connect a carrier-recorded event with a refresher chosen by your team. This workflow is still in development.
Can we change the programs, or are they fixed?
That is the plan. Fleets will start from a template and adjust it to their own policies and needs.
Does the corrective loop decide fault or predict risk?
No. The planned workflow does not decide fault or legal responsibility. Your team records the event and chooses any follow-up training.
How does this connect to the evidence record?
The planned workflow will connect completed follow-up training with the driver's other Raisedash training activity.
Explore the platform