A tour operator can schedule freelance guides by collecting availability in one place, tagging each guide with languages and tour types, applying written assignment rules, and sending confirmations from the same tool. Software handles the collecting and messaging well, and AI can draft a proposed rota from those inputs. A person should approve it.
Roundups of "tour guide scheduling software" list products. A small operator needs something narrower: a way to stop chasing eleven freelancers by text each week. The deciding test is rarely price, since rota apps cost a few dollars per guide; it is whether the tool can match a free guide to the tour's language, and how much of that matching stays with you.
Why freelance guides break ordinary rota software
Staff rota tools assume employees: fixed contracts, regular shifts, everyone on the payroll. Freelance guides differ in four ways, and each one is a thing to check.
- They work for several operators. Availability changes without warning and you compete for their days. A tool should make replying one tap, or guides will ignore it.
- Few shifts each. Someone who guides five days a month is awkward under per-user pricing, so work out the cost per guide who actually works.
- Skills decide who can work. An Italian-speaking walk needs an Italian speaker, and a boat trip may need a particular licence. The assignment rule is not "who is free" but "who is free and qualified".
- Fairness and relationships matter. Freelancers notice who gets the best tours. A rota that always picks the nearest or newest guide loses your best people.
These four points turn into the checklist below. They also explain why a spreadsheet and a group chat feel fine at four guides and collapse at twelve.
Three setups, compared by the job they do
| Job | Rota app (When I Work, Deputy) | Booking system's resource features | Spreadsheet, form and AI |
|---|---|---|---|
| Collect availability | Built in; guides reply in an app | Usually limited | A shared form or a table guides fill in |
| Match language and tour type | Check whether you can tag by skill or position | Resource assignment per tour | A column per guide, checked by you or by AI |
| Apply assignment rules | Rules and auto-scheduling, plan-dependent | Per-departure rules | Rules in the prompt; a person approves |
| Send confirmations | In-app messages and reminders | Mostly customer-facing messages | Copy and paste or a simple email tool |
| Cost | Per user per month | Part of the booking subscription | Near zero, plus your time |
No single column wins on all five rows, which is why the choice depends on how many guides you have and how complicated your rules are. At four to six guides, the spreadsheet column is workable and nearly free. From about eight, the time spent chasing replies usually justifies an app.
Rota tool plans and prices, from the vendors' own pages
These are October 2026 snapshots. Confirm figures on the day you buy.
When I Work lists three plans billed per user per month: Essentials at $2.50, Pro at $5 and Premium at $8, with a 14-day trial. The Essentials plan includes unlimited users, auto scheduling, schedule templates, in-app messaging and shift swapping. Scheduling rules and role permissions sit on Pro. The page also gives $2.50 for single-location teams and $5 for multi-location ones, which does not map cleanly onto the three tiers, so ask which applies to you.
Deputy lists Lite at $5, Core at $6.50 and Pro at $9 per user per month, with auto-scheduling on Core and Pro. It says Deputy AI is included in every plan, labelled as introductory free, with a note that price and availability may change. There is a minimum invoice of $30 a month on monthly plans, and billing currency depends on your country. The page I read did not mention skills or qualifications tracking, so ask how it handles language or licence tags.
Rezdy, a booking system, describes resource management that covers assigning and tracking staff and equipment, and guest manifests that guides can use for check-ins, no-shows and cancellations. The page does not mention notifying guides, so test whether a guide gets a message when assigned.
The vendors' pages describe features in general terms. None of what I read described matching by spoken language, so treat that as the most important item to test. For a broader comparison of rota apps by cost, six AI rota tools compared by cost covers more of them, though it is written for restaurants.
Worked example: 14 freelance guides, 40 departures a week
An illustrative operator runs 40 departures a week across walking tours, a food trail and a day trip. It has 14 freelance guides, of whom nine work most weeks and five work occasionally. Languages: English (all guides), Spanish (4), Italian (3), Portuguese (2). Each week, the operator spends about five hours building the rota, gathering replies and fixing gaps.
Cost of a rota app, illustrative: 14 guides on When I Work Essentials at $2.50 is $35 a month. On Deputy Core at $6.50, 14 users is $91 a month, above the $30 minimum. Compared with the five hours a week, say about 22 hours a month, the app costs about $1.60 to $4.15 per saved hour if it halves the time, which is an easy trade. If the five occasional guides are paid for as users but work three days a month, the per-user cost is still small. The cost difference between the options hardly matters. What matters is whether the app can do the language match, and if not, how much of that job stays with you.
A realistic week of work looks like this: Thursday, the app asks all guides for availability for the next fortnight. By Monday, ten have replied. The operator filters available guides by language for the Spanish and Italian departures, assigns, publishes the rota, and the app notifies each guide. The remaining four are chased once, with a reminder the app sends on its own. The five hours become about two.
Selection checklist for freelance-guide scheduling
Use this when comparing tools. Each point is something you can verify in a trial.
- Availability in one tap. Can a guide mark days available or unavailable from a phone in under a minute, without a password reset or a long form?
- Recurring availability. Can a guide say "never Mondays" once, rather than every week?
- Tags for language and tour type. Can you label guides with languages, licences and tours they can lead, and filter by them when assigning?
- Assignment rules. Can you set a minimum rest gap, a cap of days per week, or a rule that a day trip needs two guides over ten guests?
- Conflict warnings. Does it warn when you assign a guide to two overlapping tours?
- Confirmation messages. Does the guide get a notification they can accept or decline, and do you see the answer?
- Swaps and cancellations. Can guides offer a departure to others, with your approval?
- Pay records. Can you export days or tours worked per guide for payment, so you can pay freelancers from the same data?
- Pricing for part-time users. What does a guide who works three days a month cost you?
- Export. Can you take the rota and guide list with you if you leave?
Run two or three of your hardest weeks through the trial, not an easy one. Include a week with a language gap, a guide who cancels, and a departure added at the last minute.
Collecting availability so people reply
The software matters less than the habit. Freelancers reply when the process is predictable, short and fair. A working pattern:
- Ask on the same day each cycle, for example every second Thursday.
- Ask for the next fortnight, no further, since longer horizons produce guesses.
- Give a deadline and say what happens if there is no reply (they are not scheduled, and the first pick goes to those who answered).
- Publish the rota by a fixed day so guides can plan their other work.
An illustrative request message for guides:
Hi [first name],
Availability for 5 to 18 March is open until Monday 6 pm. Please
mark the days you can guide and any you can't. If you don't reply,
we'll assume you're unavailable for those two weeks.
The rota will be published on Wednesday. Spanish and Italian
departures are filling first, so let us know if you can take extra.
Thanks,
[your name]Notice it states the cycle, the deadline, the default and the publish day, which is everything a guide needs to know. Use your tool's message feature to send it, or paste into your own channel.
Asking AI to draft the rota, and checking what it gives back
If your tool has no good auto-scheduler, an AI assistant can propose a draft from a table you paste in. Use a plan that does not train on your content, and keep surnames and phone numbers out of the table, using first names or codes.
I run guided tours. Draft a rota for the week below.
Rules:
1. A guide must speak the tour's language.
2. No guide works more than 4 days in the week.
3. A guide must not have two tours overlapping, and needs at
least 1 hour between tours.
4. The day trip needs 2 guides if more than 10 guests booked.
5. Spread tours fairly: nobody gets more than one extra tour
than anyone else if others are available.
If a departure cannot be staffed, say so and list who is
closest to qualifying. Do not invent availability.
Guides: A (EN, ES), B (EN, IT), C (EN, PT), D (EN, ES)
Availability: [table]
Departures: [table with day, time, language, guests]An illustrative response might assign every English departure, then flag: "Friday 2 pm Italian tour: only guide B speaks Italian, but B is already on the 12 noon tour and the gap is 30 minutes, which breaks rule 3. Options: move B to the 3 pm slot, or cancel the Italian departure." That is a useful catch. What you would fix: the AI sometimes counts a guide as available when the table shows a blank, and it can miss the overlap between a 10 am tour that runs two and a half hours and an 11 am start. Check every line of the draft against the table before publishing. The AI is a faster first pass, and you are the checker. For other uses in this business, how small tour operators use AI for bookings and itineraries sets out the wider picture.
Assignment rules written down
Write your rules before you pick any tool, because a rule you cannot state is a rule software cannot apply. An illustrative set:
- Language match is mandatory. No exceptions without a note to guests.
- Each guide gets at least two tours a week if they asked for them, before anyone gets a fifth.
- The most experienced guide leads private and VIP bookings.
- A new guide shadows once before leading a tour.
- If a guide cancels within 24 hours, the backup list for that language is called in order.
Put these in the guide handbook and in the AI prompt. When guides see the rule, they accept the outcome more readily. Unwritten favouritism is what drives freelancers to rival operators.
Confirmations and last-minute changes
The confirmation should include the tour, date, time, meeting point, expected group size, language, and who to call. It should ask for a yes or no. Draft the template once with AI, give it the facts, and ask it to leave placeholders in brackets. Then keep it in the tool.
For last-minute changes, such as weather, a sickness or a late booking, have two saved messages: one to the backup list ("Can you cover the 2 pm Spanish tour today? First yes gets it") and one to the cancelled guide. The weather case is covered in weather cancellations for tours with AI, and the same messages work for guides.
A realistic mistake: a guide confirms by replying to a text on a personal phone, and the operator forgets to update the sheet. Two days later a second guide is told they have the same tour. Having one place where acceptance is recorded, and treating anything else as unconfirmed, prevents this. Pick a tool in which the guide's answer updates the rota itself.
Fairness you can show: a quick count
Freelancers compare notes. A simple tally, kept per guide and per month, lets you answer "why did she get the food trail?" with numbers. An illustrative four-week tally for four guides:
| Guide | Asked for | Tours given | Premium tours | Declined by guide |
|---|---|---|---|---|
| A | 10 | 9 | 3 | 1 |
| B | 8 | 8 | 1 | 0 |
| C | 6 | 4 | 0 | 2 |
| D | 10 | 6 | 1 | 0 |
Guide D asked for ten tours and got six without declining any, so D is owed a better share next cycle. Guide A has three of the four premium tours, so the next premium departure should go elsewhere unless a rule such as "most experienced leads VIP" applies. You can paste a table like this into an AI assistant and ask it to flag who is under-served, then use that to adjust the draft. Keep first names or codes only, and read the answer against the table.
Paying freelancers from the same data
If the rota records which guide led which tour, you have the basis for pay without a second spreadsheet. A month-end export with date, tour, guide and hours lets you multiply by the agreed rate and send a statement. Illustrative sum: a guide led nine tours of three hours at $30 an hour, which is $810 for the month, and led one two-guide day trip at a flat $180, so $990 in total. Ask the vendor whether the export includes the tour name and times, and whether you can lock a month once paid, so late edits do not change what you already settled. If the tool cannot do this, a simple spreadsheet that copies the published rota will, as long as the rota is the single source of truth and nobody edits pay lines by hand.
A backup list that works on the day
The worst moment in this business is a guide cancelling at 8 pm for a 9 am start. A ranked backup list per language, kept in the same place as the rota, turns panic into a routine. An illustrative layout:
SPANISH BACKUPS (call in this order)
1. Guide A - usually free weekday mornings, prefers walking tours
2. Guide D - free weekends only
3. Guide F - can do short notice if before 11 am; day trip needs 24 h
ITALIAN BACKUPS
1. Guide B - only Italian speaker, weekdays
2. (none: if B cancels, offer guests a move or refund)The Italian list exposes a gap. A single guide for a language is a risk, and the list shows it at a glance, which a rota alone does not. The fix is a recruiting job for next month, plus a rule that Italian departures need 48 hours' notice to cancel. Spotting a language with one guide is among the best reasons to keep tags in the system at all, so test whether your tool can report "guides per language".
Before and after for a Sunday-night rota
Before: the operator sends a group message on Sunday night asking who can work the coming week. Replies trickle in until Tuesday, some by text, some by email, one by voice note. The operator copies answers into a sheet, notices on Wednesday that no Spanish speaker is free for Thursday, and spends an hour phoning. Two guides learn their days on Wednesday evening.
After: availability closes on a fixed Monday. The tool shows who replied and who did not, and sends a single reminder to the latter. The operator filters by Spanish, spots the Thursday gap on Monday evening, and offers the departure to the backup list while there is still time. The rota publishes on Tuesday, and each guide gets a notification they must accept. The change is less about the software and more about the fixed rhythm that the software enforces.
Who should stay on a spreadsheet
Under about six guides, with one or two languages and a stable timetable, a shared spreadsheet and a short form take little time. Add an AI draft only in the busy weeks. Move to an app when you notice you are spending more than two hours a week chasing replies, or when a missed message has already cost you a tour. If you pick a booking system, what small operators should check in tour booking software shows how to test its resource features.
If you would like help mapping this to your own guides and tours, that is what my AI implementation consultation covers; see the contact page.
Questions tour operators ask about scheduling freelance guides
Can I use a restaurant rota app for tour guides?
Often, yes, for availability, shift swaps and messaging, but test two things first: whether you can tag guides by language or tour type, and whether per-user pricing suits freelancers who work only a few days a month. Booking systems may do assignment better but messaging worse.
Should AI assign guides to tours automatically?
Let it propose, not decide. Give it availability, languages and your rules, ask for a draft rota with reasons, and have a person approve. Fairness between freelancers and relationships with guides are judgement calls that a model cannot see from a table.
How far ahead should freelance guides be scheduled?
Set a fixed cycle, such as publishing a fortnight's rota every second Thursday, and ask for availability a week before that. A predictable rhythm gets you more honest replies than ad hoc requests, and guides can plan their other work around it.
What if a guide cancels the night before?
Keep a ranked backup list per language and a standing message template. Software helps by showing who is free and qualified, but the real protection is a short written cancellation rule agreed with each guide in advance.
Further reads
- AI for Tour Guides: Multilingual Enquiry Replies and Review Responses — Covers multilingual enquiry replies from the guide's side.
- Tour Descriptions in Several Languages: An AI Workflow — Helps when each language tour needs its own description.
- AI Shift Scheduling vs a Rota Spreadsheet for Small Teams — Weighs an AI scheduler against a rota spreadsheet in general.
- How to Price Tour Packages: Per-Person and Group Rates With AI — Sets the group sizes that decide when two guides are needed.
- 8 Examples of AI in Tourism From Guided Tours to Group Bookings — Other places AI fits around a small tour business.
- How to Start a Bike Tour Business: Routes, Pricing and Bookings With AI — A staged plan for a first guided bike tour: ride-test the route, price per rider from real costs, check insurance and waivers, choose a booking tool.
- Walking Tour Software: Ticketing, Guide Rotas and AI Enquiries — How a small walking-tour company sets group caps, guide rotas, weather rules and private-group quotes, and which writing jobs AI can take on.
- AI in Travel and Transport: Jobs a Small Coach Hire Firm Can Hand Over — Follow one coach booking from enquiry to return journey to see which admin jobs AI can draft, and which checks stay with people.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: When I Work and Deputy pricing pages and Rezdy's features page checked in October 2026; no vendor page I read described language-skill matching, so that point is framed as a test to run.