Agents and subcontractors send delivery evidence through email, spreadsheets, paper connotes and photos. Freight gets delivered — the carrier record does not.
A POD can exist and still be operationally missing. Most delays are interpretation delays.
— Operational notes, Gridline pilot review
- The update exists. Nobody can use it yet.
- The proof exists. Billing still waits.
- The answer exists. Customer service still chases it.
Where the carrier record breaks down 4 patterns · observed rates
| Pain point | What actually happens | Observed rate |
|---|---|---|
| Missing PODs | Freight on the ground; consignment stays open in the TMS. Billing and agent settlement wait on proof. | 14–22% of agent-handoff lanes |
| Fragmented evidence | Email, XLSX, CSV, PDF, JPG, scanned paper, handheld CSV. Every agent reports differently. | 7+ formats per active lane |
| Manual follow-up | Ops, customer service, finance and claims all chase the same delivery questions. | 20–40 min per dispute |
| Continuity risk | The workaround lives in the person who usually handles it. When they're on leave, the operation feels blind. | 1–3 staff per lane |
One reconciliation layer for messy delivery evidence. Five stages, manifest to export, with a human review queue where confidence is low.
Evidence chain by default
Every exported event traces to its source file, line and extracted field. The audit log is part of the product.
Human review where it matters
Low-confidence records route to an operator queue with a side-by-side compare and a one-click override.
Read-only by default
We read manifests and prepare files. No write-back to your ERP, TMS or carrier portal without an integration you authorise.
Full process — manifest to carrier-ready export 5 stages · click to expand
| Stage | Step | What it covers | Inputs / outputs |
|---|---|---|---|
| 01 | Carrier Manifest | Shipments, connotes, items, weights, assigned agents, expected delivery dates. | CSV / XLSX / API |
| 02 | Agent Evidence | POD emails, spreadsheets, delivery photos, scanned paper, failed-delivery notes. | Email / PDF / JPG / XLS |
| 03 | Extraction & Matching | Identify connote, status, recipient, timestamp, signature/photo, exception code. | OCR + rules + match |
| 04 | Review Queue | Uncertain records, duplicates, missing PODs — manual override with audit log. | Operator workbench |
| 05 | Carrier-Ready Export | CSV, SFTP, REST API, EDI 214 event file, structured email or ERP/TMS import. | CSV / SFTP / API / EDI |
No new file standards. We accept what your agents already send, and produce what your carrier systems already expect.
| Inputs accepted | Outputs prepared |
|---|---|
| CSV / XLSX manifest · agent spreadsheets · POD emails · scanned connotes (PDF) · delivery photos · handwritten notes · failed-delivery notes · multi-page POD PDFs · handheld depot CSV | Delivered events · failed-delivery events (reason coded) · damaged freight notes · missing POD reports · payment-ready lists · claims evidence packets · schema-matched CSV · SFTP / REST / EDI 214 · structured email |
Full input format reference 9 formats · intake method & notes
| Type | Format(s) | Notes |
|---|---|---|
| Carrier manifest | CSV, XLSX | Per-lane schema map |
| Agent POD spreadsheet | XLS, XLSX, ODS | Column order tolerant |
| POD email | EML, IMAP, forward | Body + attachments |
| Scanned connote | OCR + review queue | |
| Delivery photo | JPG, PNG, HEIC | EXIF timestamp used |
| Handwritten note | Scanned, typed | Routed for human read |
| Failed-delivery note | Email, PDF, photo | Reason code mapped |
| POD PDF (multi-page) | Carrier & agent forms | |
| Carrier handheld export | CSV | Per-depot |
Full output format reference 9 export formats & event types
| Event | Format(s) | Notes |
|---|---|---|
| Delivered status update | event_type=DEL | POD reference attached |
| Failed delivery event | event_type=FAIL | Reason: RFD / CLO / etc. |
| Damaged freight note | event_type=DMG | With photo reference |
| Missing POD report | CSV (per lane / agent) | Daily or weekly |
| Payment-ready list | CSV (settlement) | Verified POD only |
| Claims evidence packet | PDF + source links | Per consignment |
| Carrier-ready CSV | Schema-matched CSV | Per import contract |
| SFTP / API event file | SFTP, REST, EDI 214 | Scheduled drop |
| Structured email | Plain-text / HTML | For non-API receivers |
A reconciliation queue with form controls and a side review panel. The view your team actually works in. See full product tour »
Same evidence, same audit trail, six per-role views — no duplicate chasing across departments.
Operational outcomes by team 6 teams
| Team | What Gridline does for them | Tools used inside the workspace |
|---|---|---|
| Operations | Identify missing handoff events and unresolved deliveries. | Per-lane status board, missing POD report, daily close checklist. |
| Customer Service | Answer "where is my freight?" with better evidence than an inbox search. | Search by connote or recipient, evidence chain view, one-click POD bundle. |
| Finance | Release payment-ready jobs and reduce billing delays. | Payment-ready list, held-billing report, agent settlement export. |
| Claims / Disputes | Prepare POD and exception evidence for disputes — with audit trail. | Dispute evidence packet, audit log per consignment, confidence score. |
| Agent Network Mgmt | Monitor agent compliance, late PODs and per-agent SLA. | Per-agent scorecard, lane compliance trend, exception volume report. |
| IT / Systems | Feed clean files into existing carrier workflows. | CSV / SFTP drop, REST API, EDI 214 event file, schema mapping. |
No system migration. One carrier, one regional agent lane, a manifest, and a sample of POD evidence. We return a reconciled export, a missing-POD report, and a side-by-side against your current close.
Pilot checklist 6 items · ~4 weeks
- 1 carrier manifest (CSV or XLSX) for the chosen lane
- 2–4 weeks of historical POD evidence
- Agent emails, spreadsheets, scanned PODs, failed-delivery notes
- Required output format: CSV, SFTP, API, EDI, or structured email
- Success metrics agreed before processing
- Operations contact for the chosen lane
Request Pilot »
No integration commitment. No production access required.
Pilot metrics — sample lane week 4 vs baseline
POD match rate
94.2%
▲ from 71.4% baseline
Missing POD count
418
▼ 62% vs 1,107 baseline
Manual follow-up
−71%
customer-service touches
Avg time → clean event
38 min
baseline 2d 11h
Exceptions found
312
surfaced & reason coded
Export acceptance
100%
into client TMS schema
Source: pilot, NSW regional carrier lane · 4 weeks · 14,382 shipments
Not a replacement for your ERP, TMS, driver app or carrier portal. A reconciliation layer that cleans up the evidence already moving through your network.
Full system compatibility matrix 7 system categories
| System category | How Gridline integrates | Status |
|---|---|---|
| ERP / TMS | Export-ready files and integration support for the carrier's system of record. We feed it; we don't replace it. | Supported |
| Carrier portals | Structured upload packages matched to portal schemas, ready for daily or batch ingestion. | Supported |
| Existing spreadsheets | Import and normalise the spreadsheets agents already use, regardless of column order or status code conventions. | Supported |
| Agent emails | Parse forwarded mail or connect via IMAP / mailbox alias. Match attachments and body text to manifest lines. | Supported |
| Paper & scans | OCR scanned connotes and POD paperwork; route low-confidence records to the review queue rather than failing silently. | OCR + review |
| EDI / API / SFTP | Supported as output paths when available — EDI 214 events, REST event POSTs, or scheduled SFTP drops. | Supported |
| Driver app / carrier handhelds | Read-only ingestion of depot CSV exports. Gridline does not write back to handhelds. | Read-only |
Compatible with
SAPSAP TM
OTMOracle OTM
MAManhattan
MGMercuryGate
CWCargoWise
NSNetSuite
MYAMYOB Advanced
Click a question to expand the answer.
Does Gridline replace our TMS or ERP?
No. We read manifests, reconcile agent-side evidence, and prepare export files for the systems you already operate. No migration required to run a pilot.
Where does our data live during the pilot?
An isolated workspace per customer. Historical files only during pilot — no production access or write-back to your TMS. Full data-handling notes on request.
What if agent evidence is incomplete or ambiguous?
Low-confidence records do not auto-close. They route to the review queue with a side-by-side compare; an operator approves, edits or rejects. Decisions captured in the audit log.
Which export formats are supported?
CSV (schema-matched), SFTP drop, REST API event POSTs, EDI 214, and structured email for non-API receivers. Output is matched to the import contract the receiving system already expects.
How long does a pilot take?
Typically 4 weeks for a single carrier-agent lane — week 1 setup and schema map, weeks 2–3 reconciliation and review, week 4 measured comparison against your current close.
What does success look like?
Agreed in writing before processing. Common pilot KPIs: POD match rate, missing-POD count, manual follow-up reduction, time-to-clean-event, exception count, export acceptance into the client TMS schema.
Run a pilot on one of your messiest lanes.
Send us a manifest and a sample of agent POD evidence. We return a reconciled export, a missing-POD report, and a side-by-side comparison against your current close numbers.
Member of / aligned with
ARTAAustralian Road Transport Association
SCLSupply Chain & Logistics Assoc.
SOCSOC 2 Type II — in progress
GS1GS1 standards aware
ABNABN 00 000 000 000