Museum staff scheduling software: four ways to do it, compared honestly

Scheduling a museum looks like scheduling any other workplace until you try to do it with a tool built for a coffee shop.

A coffee shop needs enough people on the floor. A museum needs the right people in the right places: a guard in every open gallery, a trained educator for each school group, a docent for the 2pm tour, two people on admissions when the timed-entry slots fill up, and somebody who knows how to close the building after the Thursday-evening lecture. Half of those people may be volunteers who give you four hours a month and don't want to download an app to do it.

This post compares the four ways small and mid-sized museums usually handle it: the spreadsheet, a general shift-scheduling app, a volunteer-management platform, and building a small scheduling app of your own. None of them is right for everyone. The goal is to help you figure out which one fits your building and your staff.

What makes museum scheduling different

Before you compare tools, write down which of these apply to you. They decide the answer more than any feature list does.

• Coverage is by place, not just headcount. Many museums need a person posted in specific galleries whenever they're open, especially rooms with loaned objects, where the loan agreement may set out security requirements. "Six people on shift" is meaningless if two of them are in the same room and Gallery 4 is empty.
• Roles need qualifications. Not everyone can lead a school group, open the building, run the AV for an evening event or handle cash at admissions. A scheduler has to know who is trained for what.
• Paid staff and volunteers mix on the same day. Front-of-house staff, security, educators and part-timers sit alongside volunteer docents and greeters. Volunteers usually choose their own shifts; staff usually get assigned.
• Demand moves with bookings. School visits come in waves in term time. Timed-entry ticket sales tell you a week ahead which Saturdays will be busy. Exhibition openings and private hires add evening shifts.
• Rules from outside the building. Some museum staff are unionized, with rules on shift length, breaks and how far ahead schedules are posted. Some cities have predictive scheduling laws. Government and university museums have their own HR rules.

If only the first two lines apply to you, almost any tool works. If all five do, the choice gets harder.

Option 1: The spreadsheet

Most museums start here, and some stay here for good reasons.

What works: It's free, everyone can read it, and it bends to anything. You can make a grid with galleries down the side and hours across the top, color-code qualifications and print it for the staff room. For a museum with eight staff and a handful of volunteers, that may honestly be enough.

What breaks: The spreadsheet doesn't know anything. It can't warn you that nobody trained in school groups is on for Tuesday's three classes, or that a guard is in two places at once. Swaps happen by email and only make it into the sheet if someone remembers. Volunteers can't sign up for shifts without editing the master file, so someone retypes their replies. And there's no history: when a question comes up about who was on the floor the day something was damaged, the answer is whatever the file says now.

Choose it if: you're small, coverage rarely changes, and one person owns the schedule and doesn't mind owning it.

Option 2: A general shift-scheduling app

Tools like When I Work, Homebase, Deputy, Sling and Connecteam were built for retail, hospitality and healthcare, and they're good at their core job.

What works: Staff get the schedule on their phones, request time off and swap shifts with manager approval, and many tools include time clocks, labor-cost views and payroll exports. Most let you define positions or roles and assign people to them. Setup takes an afternoon, not a project.

What breaks: Museum coverage rules usually don't fit the data model. You can create a "position" called Gallery 4, but then you're maintaining dozens of fake positions, and the tool still won't tell you that a gallery is uncovered during opening hours, because it thinks in shifts, not in rooms and hours. Volunteers are the other problem. Per-user pricing for people who work four hours a month adds up, and many volunteers won't install a work app at all. School bookings and timed-entry sales live in separate systems, so demand never shows up in the schedule.

Choose it if: most of your people are paid staff, coverage is mostly "enough people per shift", and you want time clocks and payroll exports more than gallery-level rules.

Option 3: A volunteer-management platform

Platforms such as VolunteerHub and Better Impact are built for organizations that run on volunteers, and many museums, historic sites and zoos use them.

What works: They're designed for people who choose their own shifts. Volunteers sign up for open slots from a web page, get reminders, log hours and keep their training records up to date. Coordinators can require a qualification before someone can take a given role, and hour reports are ready for grant applications and annual reports.

What breaks: They're not built for paid staff, so most museums that use one also run a second system for employees, and the two calendars never quite agree. Gallery coverage across both groups ends up checked by eye. They also tend to have opinions about how volunteer programs should run, which is great if you agree and frustrating if you don't.

Choose it if: volunteers are the hard part of your schedule and paid staff are few or scheduled elsewhere already.

Option 4: Build a small scheduling app for your museum

The fourth option used to mean hiring a developer, which put it out of reach. With AI app builders it now means describing your rules in plain English and getting a working app with a database behind it, often in an afternoon. I work on one of these, Mythex, so take this section with that in mind. I'll be specific about where it fits and where it doesn't.

What works: The app models your museum the way it actually works. Galleries are records with opening hours and a minimum number of people. Roles have qualifications. Paid staff and volunteers live in the same system with different permissions. The home screen shows the thing you actually worry about. Here's a first prompt along those lines:

Build a staff scheduling app for a museum. Locations are galleries and desks (admissions, coat check, shop), each with opening hours and the minimum number of people needed while open. People are paid staff or volunteers, with the roles they're qualified for (gallery attendant, admissions, educator, docent, building opener, AV). Managers create shifts on a week calendar: date, location, role, start and end time, and the person assigned. Volunteers can sign up for open volunteer shifts from their phone; paid staff see their assigned shifts and can request swaps that a manager approves. The manager's home page shows, for each day this week, any gallery or desk that's below its minimum during opening hours, and any shift assigned to someone who isn't qualified for its role.

From there you iterate in the same chat: "add school visits with a date, time, class size and the number of educators needed, and flag days where booked visits need more educators than are scheduled" or "keep a history of every change to a shift, with who made it and when." That last one matters if you ever need to show who was on the floor on a given day.

What breaks: You own it. Someone has to decide when the rules change and ask for the change, even if they ask in plain language. It won't come with a time clock connected to your payroll provider, so if that's a must, a general shift-scheduling app may still be the better choice. And because your schedule includes people's phone numbers and availability, the app has to require staff to sign in. Make that one of your first requests, and test it with a volunteer account before anyone else gets the link.

Choose it if: your coverage rules are the hard part, you run paid staff and volunteers together, and you've already tried a general tool and found yourself maintaining workarounds.

The comparison at a glance

	Spreadsheet	Shift-scheduling app	Volunteer platform	Build your own
Gallery-by-gallery coverage	By eye	Workarounds	By eye	Built in, your rules
Qualifications per role	Color codes	Usually	Usually	Built in
Paid staff and volunteers together	Yes, manually	Paid staff first	Volunteers first	Yes
Swaps with approval	Email	Yes	Partly	Yes, as you define it
Time clock / payroll export	No	Often	No	Only if you build it
Setup effort	Minutes	An afternoon	A few days	An afternoon, then iteration
Who maintains it	One person	The vendor	The vendor	You

A quick way to decide

Look at last month's schedule and ask what actually went wrong. If it was swaps, no-shows or time-off requests, a general scheduling app solves that. If it was volunteers not showing up or not signing up, a volunteer platform solves that. If it was "Gallery 4 was empty for an hour" or "no educator for the 10am school group", your problem is coverage rules, and that's where building your own pays off.

Whatever you choose, run it in parallel with your current schedule for two weeks before you switch. It's the cheapest way to find the rule nobody wrote down, and every museum has at least one.

For teams

If several people build and manage the schedule, put the app in a shared team workspace rather than one person's account, so it doesn't disappear when that person moves on. On Mythex you can publish it under your museum's own domain (on Pro and above), and the staff area stays behind a sign-in. The museum staff scheduling page has a starting prompt you can adapt, and current plans are on the pricing page. The free plan is enough to build the first version and see whether it fits.

If your museum has a scheduling rule that none of these options handle well, describe it in the comments. I'm curious which ones come up most.