The workbench is the operator's daily surface. Five tabs cover the full path from manifest in to carrier-ready export. Every record carries its evidence chain — source file, line, extracted field, confidence.
| Tab | Primary use | Who works in it |
|---|---|---|
| Manifest | The shipments your carrier expects to close in the lane window. | Operations · IT |
| Evidence | Inbox of agent-side PODs, spreadsheets, photos, scans and notes. | Operations · agent network |
| Reconciliation | The merged view: every manifest row with its matched evidence and status. | Operations · customer service |
| Review | Queue of ambiguous, conflicting or low-confidence records for human override. | Operations · claims |
| Export | Carrier-ready event file in your TMS / ERP / portal schema. | IT · finance |
Upload by CSV / XLSX, pull from the TMS API, or set a scheduled SFTP. The manifest is the source of truth — everything else reconciles against it.
Schema map per lane
Bring your existing column names. Map once, reuse forever. Column order tolerant.
Validation on intake
Duplicate connotes, missing agents, malformed dates and unknown lanes are flagged before reconciliation runs.
Window controls
Process per shift, per day, per week, or for a specific date range. Re-runs are non-destructive.
Agents do not change. Gridline accepts what they already send and normalises it for matching.
| Channel | Intake method | Typical agents |
|---|---|---|
| Forwarded email | Forward to a per-lane alias, or connect via IMAP / OAuth. | Most subcontractors |
| Mailbox monitoring | Direct IMAP poll of an agent-specific mailbox. | Regional agents |
| SFTP drop | Scheduled pull of CSV / XLSX / PDF batches. | Larger franchisees |
| Web upload | Agents upload PODs through a per-agent portal page. | Smaller agents |
| API push | Agents POST events directly; rare but supported. | Tech-mature agents |
Every manifest row, side by side with its matched evidence, confidence score and current status. Filter by lane, agent, status or confidence. Bulk close, bulk export, or open a record into the side review panel.
Columns in the reconciliation table
| Column | Description |
|---|---|
| Shipment | Internal carrier shipment ID, from the manifest. |
| Connote | The customer-facing consignment number. |
| Carrier | The carrier moving the freight on this leg. |
| Agent | The agent or subcontractor responsible for the handoff. |
| Event | Delivered, failed, refused, damaged, missing — with timestamp. |
| Evidence | Stacked icons: IMG, SIG, EML, PDF, NOTE, CSV. Click any to open source. |
| Confidence | Score 0–100. Below threshold routes to review. |
| Status | Ready to close · Needs review · Exception · Missing POD. |
Low-confidence records do not silently fail. They route here with a side-by-side compare; an operator approves, edits or rejects. The decision is captured in the audit log.
| Routed when… | Operator action |
|---|---|
| OCR ambiguity | Compare extracted text against source image; accept the suggested correction or edit. |
| Timestamp out of window | Confirm against agent note or photo EXIF; approve with override and reason code. |
| Recipient mismatch | Match to known alias, accept as new alias, or reject and request reshoot. |
| Duplicate evidence | Choose canonical record; collapse duplicates into evidence chain. |
| Missing POD past SLA | Trigger chase email to agent, or mark as confirmed missing for claims handling. |
Output is matched to the import contract the receiving system already expects. No schema changes inside your TMS or ERP.
CSV / SFTP
Schema-matched event files, dropped on a scheduled cadence to your SFTP target.
REST API
Per-event POST to your TMS or ERP endpoint, with retry & idempotency keys.
EDI 214 & email
EDI 214 shipment status events, or structured email for receivers without an API.
Every exported event traces back to its source file, line, extracted field, confidence score and any operator decisions. Audit log is part of the product — not an add-on.
| Captured per event | Why it matters |
|---|---|
| Source file & line | Reproducible — the original POD email, spreadsheet row, or PDF page is one click away. |
| Extraction confidence | Disputes can reference the score and the field that triggered it. |
| Operator decisions | Who approved, edited or rejected; with timestamp and reason code if applicable. |
| Export destination | Which TMS / ERP / portal received the event, in what format, at what time. |
| Re-runs & corrections | Non-destructive history; superseded events are preserved alongside the current record. |
See it on one of your lanes.
Pilot scope is a single carrier-agent corridor. Four weeks, no integration commitment.