01 / Brokerage
The daily operating problem
In ProgressA broker coordinates a customer commitment with a carrier's execution. Coverage changes, pickup windows, rate confirmations and delivery proof often live across separate conversations. The critical operational problem is not simply seeing a truck on a map; it is retaining the relationship between the customer's shipment, the assigned carrier and the evidence supporting that movement.
Kaporeal's core load, customer, carrier, event and document targets are intended to preserve that context. In an illustrative workflow, a broker records the requested movement, assigns a carrier and tracks reported pickup and delivery milestones against the same reference. If coverage changes, the previous assignment and its documents remain explainable instead of disappearing into a new email thread.
Rates, quotes, accessorials, customer / carrier prices and margin visibility are planned extensions. Compliance verification, EDI tendering, carrier portals and accounting settlement are not operational today. A stored MC / DOT identifier is not a qualification outcome. The near-term design question is how dispatch, commercial context and document review stay coherent; automated pricing and settlement should follow verified core workflows rather than be presented as already available.
Illustrative workflow
A workflow story
A shipper emails a request for a dry-van move from a distribution center to a regional retailer. In the illustrated workflow, the broker creates a load with stops and appointment windows, tenders it to a vetted carrier, and records the agreed rate confirmation against the same reference. When the carrier reports a late pickup, the event lands on the load timeline with its source and time rather than in a private inbox.
After delivery, the POD is attached to the load. The broker can see whether the customer packet is complete before anyone builds an invoice. Nothing in this story describes a real transaction; it describes the record continuity Kaporeal is designed to keep.
Relevant modules and their status
These are the parts of the conceptual module map that matter most for this scenario. Status labels describe development state, not availability for production use.
- Load & shipment model (In Progress)
- Carrier records with compliance notes (In Progress)
- Document workflows: rate confirmation, BOL, POD (In Progress)
- Quotes, lanes and margin visibility (Planned)
What is not built, and may never be core
PlannedBeing clear about scope is part of being useful. The following are either not built yet or are deliberately left to neighboring systems.
- Automated carrier vetting against FMCSA or insurance data
- Load board posting
- Customer invoicing and carrier settlement
