A carrier PDF becomes a table in about half a minute.
The sheet is dropped on the screen. The model reads it twice and proposes rows. The operator reviews the table and presses Create — and only then does anything exist.
Two passes, because a skipped line does not look like an error.
A rate table missing one row is not broken: it quotes confidently, and it quotes the wrong number. The sheet is therefore read a second time for the one question that matters: whether anything was dropped. Fig. 1 follows both passes.
The screen states the cost before it is spent
Half a minute and a few cents. That figure is placed on the screen because a job that costs money and takes time should say so before it starts rather than after. The alternative is a spinner that a person cancels at twenty seconds because nothing indicated that twenty seconds was normal.
It also states what it read from
Every proposed row carries the page and the row it came off, so checking a line means looking at one place on the PDF instead of re-reading four pages.
Nothing here exists yet, not one row.
| Chosen | Lane and service | Basis | Buy | Valid | Read from |
|---|---|---|---|---|---|
| ☑ | LAX → PUS · LCL | W/M | 62.00 | 01–30 Sep | p.2 row 14 |
| ☑ | LAX → PUS · FCL 20GP | Per container | 1,180.00 | 01–30 Sep | p.2 row 15 |
| ☑ | LAX → PUS · FCL 40HC | Per container | 1,940.00 | 01–30 Sep | p.2 row 16 |
| ☐ | LAX → PUS · LCL minimum charge, figure not legible | Minimum | — | 01–30 Sep | p.2 footnote |
| ☐ | LAX → INC · LCL port code could be ICN or INC | W/M | 64.00 | 01–30 Sep | p.3 row 4 |
An unticked row is a question rather than a failure
A minimum charge printed over a fold, or a port code that could be one of two airports — the model can read those two ways and it will not choose one for the operator. The tick is off, the reason is on the row, and the sheet remains open beside the table.
The cost of a guess here is not a broken screen. It is a quotation that goes out at the wrong number and is accepted.
Rates → Read a rate sheet on the demo company, with PACIFIC-LAX-PUS-SEP26.pdf in a folder beside the window- Drag the PDF onto the drop area and let go.
- Let both passes run through to Done. Do not cut the half minute out.
- Stop on the proposed table: 14 rows ticked, 2 unticked with their reasons. Do not press Create.
The model proposes. A person creates.
There is no unattended import here, and none is planned. The basis those LCL rows carry — W/M — is the rule in Fig. 2.
A wrong rate is a silent failure
Twenty checks can stop a release at CBMGO, and one of them fails any build that draws a zero when a read failed — a screen showing a confident number for data it never received. The reading screen follows the same principle. A line the model is not certain of is not drawn as a fact, because a wrong rate does not announce itself. It prices, the customer accepts, and the loss appears at invoicing weeks later.
The pause is therefore part of the product
The gap between reading and saving is not a delay in automation. It is the one moment where a person who knows the lane looks at sixteen rows for fifteen seconds and catches the one that is wrong. Without that moment the sheet reader stops being a tool and becomes a source of silent errors with a machine’s authority behind them.
Four things it will not do.
The sheet nobody wants to retype is welcome.
The scanned one, the one with the footnote nobody reads, the one that arrives as four photographs. It is dropped on the screen during the call and the result is read together, including whatever comes back unticked.