Rework Flow
A freight exception should not become an office mystery. Rework Flow connects the arrival promise, dock work, evidence, and invoice through one load record.
The next person receives the work and the reason behind it.
The public sandbox uses fictional branding, synthetic records, and illustrated evidence. It resets on reload or after 30 minutes.
The problem
A shifted load arrives with urgency. Dispatch needs capacity, the dock needs an accurate scope, and billing needs proof of what happened. When each role keeps its own notes, the office must reconstruct the job after the driver leaves.
Built for dispatchers, dock operators, and office teams whose work crosses physical and administrative handoffs.
The observation
The useful unit is the load, not the screen. The inspected implementation already connected bay reservations, material counts, condition evidence, and billing. The public demo makes those connections—and the exceptions between them—deliberate and explainable.
Carry the context forward.
Driver → Dispatch
Before
A phone promise with a separate bay note.
After
A timed reservation carrying requested work and arrival context.
Dispatch → Dock
Before
The operator reconstructs the request at the trailer.
After
One job shows the requested quantity alongside the actual tally.
Dock → Office
Before
Photos, counts, and signatures need to be collected again.
After
Evidence and sign-off travel with the completed handoff.
Office → Invoice
Before
Charges are typed from scattered notes.
After
Itemized charges derive from the same material and labor record.
The solution
Keep the reservation, actual material counts, before-and-after evidence, driver acknowledgment, and calculated charges on a single job. Make unresolved handoffs visible before billing.
- Timed bay reservation
- Actual material and labor counts
- Before-and-after evidence
- Driver sign-off checkpoint
- Itemized demo invoice
- Resettable exception scenarios
The happy path is only the beginning.
6 deliberate scenarios show where a handoff succeeds, where it stops, and what the next person needs.
Normal job
Arrival, work, evidence, sign-off, invoice.
Quantity dispute
Four requested pallets; six handled. Review the adjustment.
Damaged material
Record two broken runners before work begins.
Late arrival
An expired hold triggers a fresh capacity decision.
Signature refusal
An unsigned job remains an unresolved office handoff.
Completed invoice
Trace the total back to the work and its supporting record.
Intended outcomes
Intended outcomes are a clearer arrival promise, visible differences between requested and actual work, and a billing handoff that carries its supporting record. The sandbox demonstrates these behaviors; time saved, dispute reduction, revenue recovery, and customer acceptance have not been measured.
This public prototype uses the fictional Juniper Freight Lab, synthetic people and loads, illustrated evidence, and simulated sign-off. It is a focused workflow simulation, not the complete client application. No live payments, accounting transmissions, camera capture, GPS evidence, or multi-user synchronization are connected.
A public demo with its own boundary.
Source logic preserved
The client application keeps its branding, routes, storage, and behavior. The demo uses a traceable snapshot of its pure pricing calculation and models its 45-minute bay hold and handoff concepts.
A separate public environment
Juniper Freight Lab runs in page-local memory at ops.yorkstead.com/rework. Reload, scenario selection, reset, or the 30-minute limit restores synthetic fixtures. No customer database or operational API is connected.
Clear teaching extensions
Quantity review and damage acknowledgment are explicit demo checkpoints. Signature refusal demonstrates a blocked handoff; it does not claim a new client approval policy.
Reusable demo structure
A product manifest supplies fictional branding and scenarios. Shared controls provide the banner, reset, guided entry, and explanations; a future 240 Union demo can supply its own workflow model.
Where does your team have to reconstruct the work?
Start with one handoff: the information arriving, the decision being made, and what the next person needs.
Discuss your handoffs