Document intake
One bag, one driver, one upload. Everything on the page is read by the software.
STEP 1
Whose bag is this
STEP 2
Add the documents
STEP 3
Check before indexing
STEP 4
Index
The driver is not printed on the POD. It is a property of the bag, not the page:
each driver returns a bag, a folder is created and named for that driver, and the scan happens inside it.
This is the only field entered by hand.
Defaults to today, the upload date. Delivery date is derived from the invoice
index date downstream and is never read off the POD.
Drop documents or a driver folder here
PDF, TIF or TIFF · single or batch · up to 25 MB each
Document
Dispatch
Status
Result
Review queue
Documents the software was not sure about. Each one needs a person to look at the original.
Needs review
Dispatch
Customer
Driver
Issues
Confidence
Upload sessions
One session per bag. Every document carries the session it arrived in.
The session is what makes an upload traceable. Months later, “where did this driver come from”
has an answer: upload_metadata, from this session, entered by this person, on this date.
Sessions
Session
Driver
Detail
Docs
Indexed
Status
All documents
Every proof of delivery held in the system.
Documents
Dispatch
Customer
Driver
Index date
Lines
Document
Extracted fields — correct anything the software got wrong
Stock lines
| Code | Stock | Qty | Unit | Flag |
|---|
Notes read from the page
Drivers
The list behind the intake dropdown.
The driver is never extracted from the document, because it is not printed there. It is captured once,
at upload, from the physical sorting. Every document created from an upload carries
driver_id_source = upload_metadata. If a pipeline ever starts inferring a driver
from the page, that value is what makes it visible.
Active drivers
Add a driver
In this build the list lives in the browser for the session.
Wire it to the drivers table and this screen becomes its maintenance UI.
Audit log
Every change made by hand, and who made it.
The point of this platform is that a delivery can be evidenced. That argument fails if the record can be
edited without trace.
Activity
When
Who
Record
What changed