Scheduling a Photography Team Across Several Shoots
How to handle photography team scheduling with availability, skills matching, travel time and conflicts, including a worked example week.
In this article
Photography team scheduling works when you keep three things in one place: who is available, who can do which job and how long it takes to get from one to the next. Collect availability early, match people to shoots by skill and travel time, check for clashes before confirming anyone and send every team member a clear call sheet.
Below is the process, with a worked example week.
Availability
You cannot schedule people without knowing when they can work.
- Ask for availability on a regular rhythm. Monthly for part-timers, weekly in busy seasons. A shared form or sheet is enough.
- Record fixed blocks. Days off, other jobs, school runs and holidays.
- Ask for soft limits. "I can do evenings but not two weekends in a row."
- Confirm in writing. An assignment is not confirmed until the person replies "yes".
- Hold dates for peak season. Wedding season fills quickly. Ask people to keep specified Saturdays free.
- Set notice rules. How much notice a team member must give to cancel, and what happens if they do.
A shared calendar helps, but a calendar entry is not a booking. Pair it with a message that says what the job is.
Freelancers often work for more than one studio. Don't assume availability because they worked last month. Our post on paying freelancers explains how to agree terms and dates up front.
Matching skills
Not everyone does everything. Match the job to the person.
Things to consider:
- Type of shoot. Weddings, portraits, products, events and corporate work call for different strengths.
- Experience level. A first-time second shooter should not photograph the ceremony alone.
- Equipment. Do they have the lenses and lighting the job needs?
- Style. For clients who booked your look, a lead shooter's style matters. Our post on edit style consistency covers keeping the look steady.
- People skills. Some shooters are better with children, some with large groups.
- Languages. For certain communities and events, language matters.
- Reliability. Someone with a record of arriving early and delivering on time.
Keep a simple skills table.
| Person | Role | Strengths | Gear | Notes |
|---|---|---|---|---|
| A | Lead | Weddings, family | Two bodies, 35mm, 85mm | Prefers weekends |
| B | Second | Candids, events | One body, 24-70 | Evenings only |
| C | Assistant | Lighting, setup | None needed | Weekdays |
For roles in detail, see the assistant role and hiring editors.
Travel
Travel is where schedules break.
- Count real travel time, not map time on a quiet Sunday. Allow for traffic, parking and loading gear.
- Add buffers. At least 30 minutes between two locations, more on event days.
- Group jobs by area where possible.
- Plan gear. Who carries what, and how do batteries and cards get checked?
- Decide who pays. Mileage, parking and tickets. State the rule before the day.
- Time zones and distance matter for destination work. Add rest time.
- Return time. A person who finishes a long wedding at midnight should not start an early shoot the next morning.
Share the route and the times in the call sheet. Include the venue contact and a backup phone number.
Conflicts
Clashes happen. How you handle them decides whether a team trusts you.
Common conflicts:
- Double-booked person
- Two jobs close to each other in time or distance
- A job with too few people
- A person who cancels late
- Equipment needed in two places
Method:
- Check before confirming. When you add a job, view the person's other jobs that day.
- Set a priority rule. For example, signed contracts first, then by date booked.
- Offer alternatives early. Another person, another time or a shorter commitment.
- Tell the client only if their job changes, and do it directly.
- Keep a backup list. Two or three trusted people, briefed on your style.
- Write down what happened and update the process.
Example week
These are examples. Change them for your business.
| Day | Job | Lead | Second | Assistant | Notes |
|---|---|---|---|---|---|
| Mon | Headshots, office | A | 2 hours, 20 min away | ||
| Wed | Product shoot | B | C | Studio, 4 hours | |
| Fri | Rehearsal dinner | B | Evening, 1 hour | ||
| Sat | Wedding, 9 am to 9 pm | A | B | C | Venue 45 min from studio |
| Sun | Editing | A, B | No shoots |
Check this week:
- A has Monday and Saturday, not back to back.
- B has a Friday evening shoot and a Saturday wedding. Is there rest? Is a morning start realistic after a late night? Consider moving B to shorter hours on Saturday morning.
- C helps on two jobs but not Friday.
- Sunday is blocked for editing, which stops delivery slipping. If delivery dates are at risk, see our post on late delivery.
Send each person a one-page schedule showing only their jobs, times, contacts and notes.
Shoots and crew view
If you use ClickBook, a won deal becomes a client and project in one step, with crew, call sheets and deliverable deadlines. Editors and freelancers see only their own work, never prices or income. That makes it easier to hand out schedules without exposing the rest. The demo shows the shoots and crew view.
Keep schedules simple: ask early, check clashes, confirm in writing.
Frequently asked questions
How far ahead should I schedule my team?
Weddings and large events need to be locked months out, and smaller shoots a few weeks ahead. Confirm everything again a week before and the day before.
What if two shoots overlap?
Decide which job has priority from the contract and the date. Offer the other client another photographer from your team or a different time, never a silent substitution.
How do I handle last-minute sickness?
Keep a short list of backup photographers you trust and brief them in advance. Put a replacement clause in your contracts.
Should everyone see the full schedule?
Each person needs their own jobs, times and contacts. They do not need pricing or other people's pay.