Document review

Apply tracking from the inbox with Express review

Express review is the delivery-order queue a freight-forwarder workspace gets in Document Review. One row per forwarded delivery order, an inspector on the right, and a single Apply tracking button that turns a parsed document into a tracked container without opening a full review screen.

7 minute read · Updated July 27, 2026

What Express review is

Open Document Review in a freight-forwarder workspace and you do not get the standard needs-review table. You get a two-pane Express layout: a list of forwarded delivery orders on the left, and an inspector on the right for whichever row is selected. Selecting a row on a phone swaps the inspector in full-screen, with a Back to Express Review button at the top.

The list has five columns — Receiver, Container, B/L, Trucker, and Date — and each cell carries a second line. Under the receiver is the pickup terminal (or No pickup terminal). Under the container is the vessel (or No vessel). Under the B/L is the house bill, prefixed H:. Empty cells read No container, No B/L, and No trucker rather than going blank.

Small badges tell you why a row is still here. Conterminal tracks five fields per row and marks each one:

Missing: An orange badge. The field is empty — nothing was parsed and nothing has been typed. In a list cell it shrinks to an exclamation mark.
Not matched: An amber badge. Something was parsed, but it has not been matched to a record Conterminal can track against. In a list cell it shrinks to a question mark.
Warning: An amber pill next to the receiver name. The document or its sender tripped a check, and the row is held out of the ready path until an admin resolves it.
No badge: The field is confirmed. When all five are confirmed and there is no warning, the row can be applied.

Applying a row is what enrolls the container with LongShorty, the worker that signs in to terminal, rail, and steamship-line systems on your behalf and keeps the container updated. Nothing polls on a row that is still sitting in this queue.

Choosing Express vs Traditional

The review mode is a single organization-wide value, not a per-user preference. It lives in Settings under the Delivery-order review panel, described as “Choose the default review surface for delivery-order tracking intake.” The control is a Review Mode select with two options — Express review and Traditional review — and a Save Review Mode button.

The panel appears only in freight-forwarder workspaces. Trucker and importer workspaces resolve to traditional review regardless of what is stored.
Only a tenant_admin gets the form. Everyone else sees the current value as read-only text.
A forwarder workspace with nothing configured defaults to Express review.

If the save is rejected you get Could not save document review with one of two reasons: “Only logistics-provider tenant admins can change this setting.” or “Choose Express or traditional review.”

Traditional does not remove the Express queue.

Switching to Traditional does not change Document Review. The inbox picks the Express layout from the workspace type alone and never reads this setting, so the Express table, its inspector, and its Apply tracking button all keep working. What the setting actually controls is the delivery-order confirm screen: with Express review on, that screen opens in its compact Express panel and offers Back to Express when you switch to full review; with Traditional set, the Express confirmation is refused with “This workspace is configured for traditional delivery-order review.”

The three rail buckets

A forwarder workspace gets three review buckets in the status rail, plus Recently Confirmed and Archived underneath.

All Pending: Intended as every forwarded delivery order awaiting Express review.
Missing Fields: Rows where at least one of container, B/L or booking, tracked vessel, pickup terminal, or local carrier is missing or unmatched. This is where you will spend your time.
Warnings: Rows held back because the document or its sender tripped a check. Only a tenant admin can clear these.

All Pending will not stay selected.

The rail entries are filter links. All Pending writes an empty action into the URL, and a forwarder inbox with an empty action is rewritten to the review action before it renders — so selecting All Pending lands you on Missing Fields. Work Missing Fields and Warnings in sequence instead. The same rewrite behaviour is covered in the Document Review queue article.

There is no search box and no column filter in the Express layout. The keyword search that trucker and importer workspaces get above the table is not rendered here, and the Express column headers are plain labels rather than filter controls. Your only navigation is the rail and the pagination bar.

Repairing fields inline

The inspector is where the work happens. It is headed by the container number and an Open delivery order button that opens the source PDF in a new tab. Below that are the editable fields, in order.

Wait a beat after selecting the row. A quarter of a second after you select a row, Conterminal runs a background reference pass and shows Preparing references... above the buttons. If it resolves the vessel against the registry, the Tracked vessel field flips to confirmed on its own and the originally parsed name drops to a Parsed sub-line. A row that looked incomplete can become applicable while you are reading it.
Container and B/L. Both are free-text monospace inputs, tinted orange while the field is missing. If the document carried a booking number, it shows under the B/L field as Booking followed by the number, and that booking satisfies the requirement on its own — you do not have to invent a B/L.
Tracked vessel. A search box labelled Search vessel. If your workspace has no matching vessel, use the registry action — Search vessel registry, or Search vessel registry for plus the name in quotes. It opens a Verified vessel lookup panel reading “Validate a vessel match for” and your query. Pick a candidate to create the verified reference, or Dismiss the panel.
Pickup terminal. A search box labelled Search terminal. A parsed-but-unmatched terminal name stays visible as a sub-line so you can see what the document said.
Marine terminal, on rail-ramp pickups only. When the pickup terminal resolves to a rail ramp, an extra Marine terminal field appears with Add terminal / Search marine terminal. A note underneath reads Rail-only tracking until you set one, and Marine + rail tracking once you do. Adding the marine terminal is what lets LongShorty follow the container on the ocean leg as well as the ramp.
Local carrier (trucker). A search box labelled Search local carrier. If nobody matches, use Add local carrier to create one from what you have typed; it becomes Adding local carrier... while it runs. Once a carrier is set, a badge shows how it is known to you — Connected carrier, Existing local carrier, or New local carrier. Until one is set, the parsed name shows as Parsed: plus the name, which is not the same as having selected it.

A collapsed Details block below the fields shows receiver, source file name, sender address, vessel ID, carrier or steamship line, the parsed vessel name, and any notes on the row. Open it before you guess at a mismatch — the sender address is often the fastest explanation.

The HAWB / House B/L box does not save.

The inspector has a third text field labelled HAWB / House B/L, and the Express action route drops it before it reaches the server. The house bill you type there is discarded; container and B/L repairs are kept. Until this is fixed, set a house bill from Open full review instead of from the inspector.

Applying tracking, single and batched

Apply tracking is the blue button at the bottom of the inspector. It stays disabled until the container has a value, the B/L has a value or the row carried a booking number, and every field that was missing or unmatched now has a record selected. Typing a vessel or terminal name without picking a match from the list does not count.

While the action runs, the whole pane is covered by Applying tracking for plus the container number. When it succeeds the row disappears from the list, the selection moves to the next row down (or the previous one if you were on the last), and a small green notice appears in the lower-left reading Now Tracking and the container number as a link through to the new shipment. That notice clears itself after fifteen seconds, or immediately with its dismiss button.

A second line under that notice reading “Tracking was applied, but LongShorty enrollment needs retry” means the shipment exists but LongShorty did not pick it up. The row is gone from your queue and will not come back — open the shipment from the link and confirm tracking actually started.

There is no multi-select today

The Express list has no row checkboxes and no bulk bar. Conterminal does carry a batch apply entry point on the server, capped at 50 attachments per call, but nothing in the interface calls it — so “batched” in practice means the queue is built to be worked quickly one row at a time: applying never reloads the page, the applied row is removed locally, the selection advances on its own, and the rail counts update in place. Fifty rows fit on a page, so a full page is a full sitting.

Trusting a sender

Rows in the Warnings bucket are quarantined, usually because the sending address is not yet authorized to send delivery orders into your workspace. Trusting the sender is a tenant_admin action, and only an admin sees the buttons in the Express inspector.

Trust sender & apply tracking: The primary button, shown only when the row is a warning, every tracking field is already complete, and you are a tenant admin. It authorizes the sender, releases the document, and applies tracking in one pass. The notice reads Trusted sender and applied.
Trust sender for future documents: The secondary button, shown on any warning row for an admin. It authorizes the sender and releases this document without applying it. The notice reads Trusted sender for, and a second line says Row moved to Missing Fields.

Trusting is durable and forward-looking: the address is recorded as an authorized sender for the workspace, so the next document from it skips the warning entirely. It is not a one-off release. Treat it as an access decision, not a queue-clearing shortcut.

Apply tracking never appears on a warning row, even when every field is green. If you are not an admin, a warning row offers you nothing but Open full review — and the trust buttons on that screen will fail for you with “Only tenant admins can trust warning senders.” Route warnings to an admin rather than working around them.

Opening full review instead

Open full review sits at the bottom of every inspector. It is the secondary button on a row you can apply, and the primary blue button on a row you cannot — a warning row you are not allowed to clear, or a row with no usable attachment behind it.

A ready row opens the full tracking review screen, with the document preview beside the complete field set and the parser's evidence for each value. A warning row opens the warning screen instead: the preview, a Details list of warning reasons, a Receipt block showing received time, sender, and subject, the parsed tracking fields, and a Sender approval block with Trust sender & apply and Trust sender. Both screens carry Archive, Next Inbox Item, and < Back to Inbox.

Repairs you typed in the Express inspector are not carried into full review. The inspector holds them in the page only, and the button is an ordinary link. Either finish the row in the inspector, or open full review first and do the editing there.

Limits

50 rows per page: The forwarder review queue pages at fifty. Use the pagination bar under the table; there is no infinite scroll.
Five required fields: Container, B/L or booking, tracked vessel, pickup terminal, and local carrier. A forwarder workspace always requires the local carrier — this is stricter than other workspace types.
Delivery orders only: The Express queue is a delivery-order surface. Proofs of delivery, interchange receipts, and unclassified documents do not appear in it.
One action at a time: While an apply or a trust is running, the whole pane is blocked and rows cannot be selected. This is deliberate — it prevents a second click landing on a row that is about to move.
No filters, no search: The rail is the only filter. Unrecognized query parameters are stripped from the URL, and container, document type, and document date are single-value filters everywhere in Document Review.
Tenant admin for warnings: Trusting a sender requires the tenant_admin role. There is no per-document override for other roles.

Troubleshooting

Selecting All Pending sends you to Missing Fields

Expected, and not a bug you can work around from the rail. A forwarder inbox arriving with no action filter is rewritten to the review action before it renders, and All Pending is exactly that URL. To see warning rows, select Warnings directly.

The filters and search box you use elsewhere are gone

The Express layout does not render the keyword search or the Receiver, Container, and Document date column filters — those belong to the trucker and importer table. Nothing is broken and nothing is hidden by a saved preference. If you need to find one specific container, open it from the container dashboard rather than hunting the queue.

“Only tenant admins can trust warning senders.”

You are not a tenant_admin in this workspace. The trust buttons render on the full-review warning screen for everyone, so the refusal arrives after you click rather than before. Ask an admin to clear the warning; nothing you can do on the row will release it.

A quarantined document has no “Retry parsing” button

Correct — forwarder workspaces do not get one. The retry control exists only on the trucker and importer warning screen. On a forwarder warning your options are to trust the sender, archive the document, or ask the sender to resend it. Contact support if a document needs to be re-parsed.

Apply tracking stays greyed out

One of the five required fields is not confirmed. Typing into a search box is not selecting from it — the field only counts once you pick a record, and a Parsed: line means nothing has been picked. Check the badges: Missing means empty, Not matched means parsed but unresolved.

“Missing required fields: …”

The server re-checked the row and disagreed with the button. The message names the fields exactly as Container, B/L or booking, Tracked vessel, Pickup terminal, and Local carrier. This usually means a reference you selected no longer resolves; re-pick it and apply again.

“That attachment is no longer ready to apply.”

Someone else already worked the row, or it moved out of the ready state while your page was open. Reload Document Review; the row will be gone or in a different bucket.

“That attachment has already been archived.”

The document was archived from another screen. Look for it under Archived in the rail rather than reapplying.

“That staged email attachment is no longer available.”

The row no longer points at a delivery-order attachment your workspace owns — usually because the document was reclassified as something other than a delivery order. Open it from the rail bucket that now holds it.

“That Express review action could not be applied.” / “That repaired row could not be applied.”

The request itself failed rather than being rejected on its merits. Reload the page and try the row once more. If it repeats on the same row, send support the container number and the sender address from the Details block.

The house bill you typed did not stick

The HAWB / House B/L field in the Express inspector is discarded before the row is applied. Set the house bill from Open full review instead.