Run the crew, not the crew spreadsheet

The build-week shifts, crew meals, the programme and department budgets — one crew list underneath, instead of nine sheets with edit access for everybody.

No sign-up, no email. Free for your crew.

Organising something else?
How it works

Set up in an evening

Step 1
Start your crew

The festival template speaks build week, derig and departments.

Step 2
Send the joining link

Crew add their own skills, arrival dates and diets.

Step 3
Watch coverage fill

Shifts claimed, catering counted, budgets adding up per department.

The trick

Say it once. It shows up everywhere.

Ana joins the build crew
Certified rigger
On site from Monday
Vegan

Filled in once, by them.

She claims build-day slots — coverage fills

Crew catering counts her from Monday

Her certs are on file before the safety check

Who it's for

Built for crews like yours

Production & build crews

The people who put the site up and take it down. Shifts, arrivals, spend.

Stages & areas

One stage or dome inside a bigger festival — your own programme, crew and budget.

Co-created festivals

Where the participants are the programme. Proposals in, a timetable out.

The production sheet has forty editors, six tabs only one person understands, and a version from last year nobody dares delete.

Four documents describing the same forty people — and keeping them agreeing is somebody's whole job.

Today Six production tabs, Submission forms, The crew chat, The budget sheet, Last year's version all route through one person. With Burnbase, everyone reads and updates the same shared base.

What's inside

The modules a production crew actually uses

Switch the rest off. It calls things what your festival calls them.

Crew & teams

Skills, certifications, arrivals, contacts. Departments are teams with their own leads.

Build shifts

Slots across build, show and derig — claimed by the crew, coverage visible.

Programme

Proposals in, curated, scheduled by space. Or curation off entirely.

Line-up

Sets on the same timetable, with links to listen.

Crew catering

Meals scaled to the real crew count, a cooking schedule, one shopping list.

Department budgets

Projected vs actual per department, plus pots anyone can chip into.

Forms

Arrival times, gear, sizes — one link, answers attached to the person.

Crew applications

Your application form, one queue, joining links.

One overview

Build week and the festival on one calendar.

Arrivals & transport
Coming soon

Who lands when, and spare seats matched.

Creating and collaborating is the point.

The admin shouldn't be what people remember.

Why it's different

One set of records — and it isn't the production sheet

The whole production in one place

Crew, shifts, programme, catering and budgets — one set of records that agree, across every department.

And it isn't the production sheet

Forty editors and six tabs make one person the keeper. Here each department holds its own piece, on the same crew list.

1
It speaks your festival's language

Build week, derig, crew, programme — every word is configurable, and a template sets them for you.

2
Money legible while it matters

Actuals come from the ledger as it's written. A department going over shows during build, not in the post-mortem.

3
One area can start alone

You don't need main production to adopt anything. One stage can run on this and the rest can follow.

What it costs

One number, no tiers

Free

The whole platform

Every module, everyone in your group. No tiers, no seat counts, no trial that runs out.

1%

When money moves through it

Added on top of what you asked for, shown before anyone pays. Your number stays your number.

0%

When it doesn't

Bank transfer, payment link, cash in a tin — record them for free and the books still balance.

Paying through Burnbase is optional. It's also the only thing that funds building it — so if it makes your crew's life easier, using it is how you and your members support the platform.

Details on the pricing page.

Why now

Nobody learns a new tool during build.

The weeks before are the only ones with slack — and the crew list resets anyway.

Where it's at

Usable today, honest about the rest

Every module above is built and running in the demo. Payments are the exception: the whole flow is there — fees, destinations, receipts — but no money moves yet. Next up includes importing your existing spreadsheet, so a group that runs on one today can switch in minutes rather than evenings.

Here now
Crew roster & teams
Build shifts & coverage
Programme & curation
Line-up
Crew catering & shopping list
Department budgets
Funding pots
Forms
Applications & joining links
Spreadsheet views
Overview calendar
Configurable vocabulary
Next up
Real payments (Stripe)
Cost splitting
Packing lists
Spreadsheet import & export
Rideshare & arrivals
Art grants
WhatsApp nudges
Multilingual
Offline on site
Stay in touch

Planning to use it? Let's talk.

Using it for your next crew?

Tell me what you're organising and when. I'd be glad to help you set it up, meet your crew, and stay reachable while you run it — so it actually goes smoothly.

Just want to follow along?

One list, rarely used — for when real payments land and the big pieces ship.

Occasional updates about Burnbase. No spam, unsubscribe any time.

Look at it with a real crew in it

The demo is seeded: a programme, a week of shifts, a budget with actuals. See what a lead, an organizer and a new arrival each get.

Open the demo

Burnbase

AboutPricingContactPrivacy

Shared infrastructure for camps and crews · burnbase.org

Photos by Yoav Aziz, Jeremy Bishop, Kenji Katahira, Maria Isabella Anastasia Stål, Conner Baker and Max Langelott on Unsplash.