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.
The festival template knows build week, derig and departments.
Crew add their own skills, arrival dates and diets.
Shifts claimed, catering counted, budgets adding up per department.
Filled in once, by them.
She claims build-day slots, and coverage fills
Crew catering counts her from Monday
Her certificates are recorded before the safety check
The people who put the site up and take it down. Shifts, arrivals, spending.
One stage or dome inside a bigger festival, your own programme, crew and budget.
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.
Switch the rest off. It calls things what your festival calls them.
Skills, certifications, arrivals, contacts. Departments are teams with their own leads.
See it in the demoSlots across build, show and derig, claimed by the crew, coverage visible.
See it in the demoProposals in, curated, scheduled by space. Or curation off entirely.
See it in the demoSets on the same timetable, with links to listen.
See it in the demoMeals scaled to the real crew count, a cooking schedule, one shopping list.
See it in the demoProjected vs actual per department, plus shared funds anyone can add to.
See it in the demoArrival times, gear, sizes: one link, answers attached to the person.
See it in the demoYour application form, one queue, joining links.
See it in the demoBuild week and the festival on one calendar.
See it in the demoWhat each department fronted, and who settles with whom.
See it in the demoWho's driving which trip, and how many seats are left.
See it in the demoEvery module above is running. Payments stop short of moving money: members record what they paid and leads confirm it, and nothing is charged through Burnbase yet.
Creating and collaborating is the point.
The admin shouldn't be what people remember.
Crew, shifts, programme, catering and budgets: one set of records that agree, across every department.
Forty editors and six tabs make one person the owner. Here each department holds its own piece, on the same crew list.
Build week, derig, crew, programme: every word is configurable, and a template sets them for you.
Actuals come from the ledger as it's written. A department overspending shows during build, not in the review afterwards.
You don't need main production to adopt anything. One stage can run on this and the rest can follow.
Free
Sign in, set it up and invite everyone. Nothing to pay until money is collected.
Free
Shifts, food, program, payments, budget and the rest. No tiers, no seat counts, no trial that expires.
1%
That is the whole price. On a €200 camp fee it comes to €2 a person.
One percent is the only thing that funds building it. For every module your crew uses, that is a small price, and it is the same however your members pay.
Details on the pricing page.
Nobody learns a new tool during build.
The weeks before are the only ones with spare time, and the crew list resets anyway.
Set shifts across build, show and derig with how many people each needs. Crew claim their own slots, and you see coverage fill.
Yes. Use your own application form with one review queue, or send a joining link to people you have already said yes to.
Crew enter their diet and arrival once. Meals are scaled to the real crew count, with a cooking schedule and one shopping list.
Creating your crew and every module is free. The one charge is 1% of crew fees or contributions.
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.
One list, rarely used: for when real payments and the big pieces arrive.
Sign in, name it, invite the crew. Or look first: the demo is seeded with a programme, a week of shifts and a budget with actuals.