Product

Every hand-off on the show, on one record

RunSheets covers the whole set-decoration loop — the purchase request, the run, the hand-off, the return, and the wrap — so the answer to “where is it and what condition was it in?” is a record instead of a group chat. Here’s what each part does today.

Purchase requests and approvals

Web · iPhone · iPad · Android

A buyer photographs what they’ve found, adds quantity and cost, and sends the request straight to the show’s approver — there’s no draft step to forget about. Object capture on the phone is camera-first: the shutter comes up immediately and the details get filled in after the shot.

The decorator approves line by line, so one rejected chair doesn’t hold up the other eleven items. Buyer and approver talk in a comment thread attached to the request rather than in a text chain, and cost codes and PO numbers ride along for accounting.

  • Estimated total auto-sums from the line items until you type your own
  • Approved items convert to a run sheet in one click, carrying the number (PR-1042 → RS-1042)
  • Receipts attach to a purchased request, and Claude reads each one — vendor, date, tax, total and line items are filled in for you

Dispatch

Web · iPhone · iPad

Build a run from an approved request or from scratch, pick a driver and a pickup date, and the sheet is on their phone. No printing, no handwriting, no carbon copy to lose. A run with no driver yet waits in an Unassigned lane instead of vanishing into someone’s inbox.

The week board is the office’s planning surface: a Monday-to-Sunday grid with a lane per driver, every run placed on its day and colour-coded by action. Drag a run to another driver or another day to reassign and reschedule in one gesture, or hit Auto-assign to spread the week’s unassigned runs across your available drivers by workday and daily cap. A day tints red when one driver is carrying too much.

Auto-assign balances by date, availability and load — it is not route optimization. Drive-time route ordering is an iPhone feature (below).

The driver’s view

iPhone · iPad · Android · Web

Drivers get a cockpit, not a spreadsheet. Their runs are grouped into Happening now, Upcoming and Completed, and a run that isn’t until Thursday stays a heads-up until Thursday. A live run is an action card: the verb and the vendor, the address, a take-a-cheque flag, and one tap to start the pickup.

The hand-off is a single screen — directions and call-vendor tiles at the top, the pre-checked item list with condition grading below, confirm pinned at the bottom. A pickup is three taps end to end. On iPhone, two or more live stops chain into a drive-time route that accounts for pickup windows and re-chains from wherever the driver actually is after each stop.

  • Signature capture at pickup and return
  • Addresses open straight into Maps
  • Share a printable run-sheet PDF from the iPhone — print it, mail it, or AirDrop it to a vendor

Custody and condition

Web · iPhone · iPad · Android

Every item is a tracked object with a status, not a line of text. Each hand-off is stamped with who, when, and — where the device allows it — where. Condition is graded good / fair / damaged at pickup, at delivery and at return, with up to eight photos per object.

That’s what turns a damage argument into a document. If something is graded damaged later that wasn’t damaged at pickup, a loss & damage case opens by itself with the before-and-after photos already attached, and the office gets a push notification.

The items catalog

Web · iPhone · iPad

Every object on the show in one place, searchable and groupable by set, status or vendor, with photos, condition history and which run sheets carried it.

Item photos are read on upload, so the catalog knows a piece is a green mid-century floor lamp without anyone typing that in. On the web you can search it in plain English — “green mid-century lamp” — and get a ranked list back with the filters it understood shown as chips. Items that were never tagged still match on plain text, so a sparse catalog degrades gracefully.

Rentals and returns

Web · iPhone · iPad · Android

Mark a run as a rental and a return date is mandatory. When the pickup dispatches, RunSheets schedules the return leg for you — a future-dated run against the same vendor, set and objects, sitting in the Unassigned lane on its due day until someone takes it. Cancel the pickup and the return cancels with it.

Overdue rentals chase themselves: a daily digest goes to the buyers and decorators on the show listing everything past its return date.

Wrap and disposition

Web · iPhone · iPad

The wrap dashboard is the “what’s still out” board: items needing a decision, rentals still out, deposits at risk, damaged items. Disposition objects one at a time or in bulk — return, hold on the truck, store in the warehouse, dispose.

The wrap pack exports a per-vendor return manifest with run-sheet numbers, cost codes, values and deposits, as a CSV. Closing out a season runs a readiness check first, then stops the billing while every record stays readable. On a returning series, items held for next season carry forward with their photos, condition history, cost and deposit intact.

Spend, budget and insights

Web · iPhone · iPad

Spend by set, vendor and buyer, with deposits at risk, out-now liability and overdue rentals, exportable as a CSV your production accountant can code straight to the show. Set a season budget and per-set targets and you get a consumption meter, a budget-vs-actual bullet by set, and a burn-up projecting current spend to your wrap date.

Across a slate, Insights scores your vendors — run sheets, units, spend, and an on-time-return grade — so the vendor conversation next season starts from data.

The budget is a planning target. It never blocks a dispatch.

Built for the field

Web · iPhone · iPad · Android

Photos taken in a dead zone queue on the device and upload when coverage comes back. Purchase-request edits and hand-offs commit locally and sync in the background, so nothing hangs on set Wi-Fi. There’s an offline indicator, so a driver knows what state they’re in.

Push notifications cover the moments that actually matter: a run sheet assigned to you, a request submitted for your approval, your request approved, a comment on your thread, and damage recorded on your show.

Where it runs

Web · iPhone · iPad · Android

The apps are role-aware — everyone gets the view their job needs. Coordinators, decorators and buyers work the full office on the web or an iPad; drivers get the truck view on their phone. The same person can be a buyer on one show and a driver on another, and their profile and your vendor file follow them from show to show.

The web app is an installable PWA. The iPhone and iPad app is in TestFlight while we’re in limited testing, and the Android app is built with store distribution in progress. Plan management lives on the web.

New to the paperwork itself? Start with what a run sheet is and what goes on one. Wondering what a show costs? Pricing is per production, and the FAQ covers the rest.

Put it on a real show

RunSheets is in limited testing with a small group of set-decoration departments. Tell us what you’re working on — if it’s a fit, we’ll set your show up personally.

Request early access