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 walkthrough uses a made-up company name, example records, and illustrative photos.
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 walkthrough follows those connections from a driver's reservation to a signed completion packet.
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 steps follow one job from reservation to a signed packet.
Reserve a bay
A driver gets a fixed price range and a bay before arriving.
Dock intake
The operator confirms trailer, carrier, driver and bay.
Before photos
Record the condition the freight arrived in.
Supplies and labor
Count materials and time while the invoice updates.
Driver sign-off
An after photo and a signature on the glass.
Completion packet
Photos, itemized invoice and signature in one 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 application is built around these behaviors; time saved, dispute reduction, revenue recovery, and customer acceptance have not been measured.
The walkthrough shows screens from the working application with a made-up company name, example people and loads, and illustrative photos. The software is a prototype still in development and is not yet running in a live operation. Available as a purchased system for $7,500. Included configuration, implementation, integrations, and handoff are defined in the proposal. Continued use of the purchased system does not require a Yorkstead support subscription. Hosting and third-party services are identified separately. Account ownership, billing, and ongoing responsibilities are agreed before implementation.
A public demo with its own boundary.
A working application
Rework Flow is a Next.js application with a driver reservation page, a dock terminal for phones and tablets, and an office board that updates as the dock works.
Real screens, example data
The walkthrough uses screens captured from the running application with a made-up company name, example carriers and illustrative photos. Nothing on the page is connected to a customer system.
Evidence travels with the job
Photos, counts, the driver's signature and an append-only audit record stay attached to one load, so the office bills from the same record the dock created.
Still in development
Dispute rate and turnaround figures in the demo are placeholders. No measured business outcomes are claimed.
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.
Prototype interface
Screens from the broader concept application. The public walkthrough above is a focused, fictional simulation.
