Skip to content
Kyle Rivelli.

Work

Web tools for teams · Live · since September 2026

The pick tracking board.

The shipper's daily tracking sheet lives in the platform now, mirrored against the TMS every 15 minutes and fed by the portal pull.

Livepositional parsercloud cronundoable bulk edits
sweepstatus

The problem

The owner tracked the day's pickups in a spreadsheet whose format the shipper dictated, re-keyed from two systems by hand, with notes nowhere anyone else could see.

How it works

  • The sheet's format is parsed positionally so the owner's layout stays the owner's. The board shows the TMS's answer beside every human note, so a disagreement is visible on the row.
  • A cloud cron mirrors the TMS every 15 minutes and checks the sheet's loads first, so the rows the desk is actually watching are never the ones that time out. The freshness stamp on the page is true of every row, not just the first.
  • Bulk status changes are guarded and undoable. A rate override typed on the board flows through the same chokepoint as everywhere else.

// the sheet's own loads are swept first; the freshness stamp never claims more than it checked

The result

The shipper's sheet and the TMS stopped being two sources of truth, and a sweep that used to time out now covers all 36 sheet loads inside its 240 second budget.

In practice

Schedule of the unattended systems, Central time.

Syncing the Central clock.

Your version of this exists.

Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.