Documents & onboarding
Onboard a season from the documents you already have.
Every touring company owns the same pile: a schedule named FINAL(2), a rooming list with merged cells, a scanned contract. The pile is where this product starts.
Best forDirectors moving a season off nine spreadsheets- Free for up to 5 events
- Your originals stay yours
- Nothing saves without your review
New workspace · Season 2027
ImportingDay one — built from the documents you already have
Season
26 events on the calendar
Roster
43 people, roles assigned
Hotels
12 blocks linked to weekends
Venues
14 directory records
Every import lands in a review first — nothing saves without your OK.
- Every import is confirm-before-save
- Files land in private storage, yours only
- Built by people whose season lived in nine spreadsheets
The season exists. It's just trapped in files.
Drop them exactly as they are — FINAL(2) filenames and all.
How it works
From a pile of files to a working season.
Drop everything
One dropzone, any file, no sorting, no labels.
Each file gets read
“Looks like a schedule” routes onward; “might be” asks you.
Routed to the right importer
Schedules build the season; rosters import staff; packing lists go to inventory.
You keep what's right
Every field editable, every row uncheckable. Only your review commits.
Built in the open
Trust is a design decision, not a testimonial.
0
records written without review
Extraction and scraping are read-only. The only write is your commit.
11
document types recognized
Each with its own route — and an honest “we couldn't tell” for the rest.
0.6
confidence bar for “looks like”
Below it, the product hedges to “might be” and asks.
Facts about the pipeline's design — verify them in an afternoon with your own files.
Fair questions
Asked by everyone who's been burned by an importer.
- What if it reads my documents wrong?
- You'll see it before it matters. Every extraction lands in a review where each field is editable — and the extractor leaves a field blank rather than invent a value.
- Our documents are a mess. Genuinely.
- Merged cells, FINAL(2) filenames, schedules in forwarded emails — that's the expected input. CSV, Excel, PDF, plain text, and pasted text all parse.
- Can it read scanned paper?
- Not yet — an image-only PDF gets an honest error suggesting CSV or Excel instead. We'd rather tell you here than mid-migration.
- Do we have to do this all at once?
- No. The intake stays open while you find files, sources merge additively, and the hub tracks real progress across weeks. Onboarding is a pile you chip at.
In development: more import types are actively being built — each one means less typing between you and a running season.
Also in this module
The rest of the paperwork story.
- Eleven document types recognized
- One inbox per onboarding
- Errors that name the file
- Paste instead of upload
- Scrape your own website
- Sources merge additively
- Date-clash warnings
- Venues become directory records
- Honest manual mode when AI is off
Bring the pile
Drop one document and watch what happens.
Start with the messiest schedule you own. If the review table gets it right, that's your onboarding.
- Free for up to 5 events
- No card required
- Cancel any time