Giving Feedback to Second Shooters and Editors

Good feedback to a second shooter or editor is specific, kind and tied to the next job. Point to examples, say what worked, say what to change and agree one thing to try next time. A short scorecard keeps your reviews fair and consistent, so people know what you value.

Why feedback matters

Without feedback, people guess. A second shooter may not know you wanted more reaction shots, and an editor may not know the skin tones run too warm. Small differences become repeated habits.

Feedback also helps retention. People stay where they learn and feel valued. It saves you time too, since every round makes the next job easier. Our second shooter guide describes what shooters expect to hear from the lead.

Scorecard

A one page scorecard turns a feeling into something you can discuss. Score each item from 1 to 5, and add a note.

Use the same scorecard for editors, swapping items such as skin tones, white balance, consistency across a set and revision count. Share the scorecard before the first job so nothing is a surprise. Keep scores private and use them only for coaching.

Example notes

Useful notes are concrete. Here are examples to adapt.

Weak: "Your photos need to be better." Useful: "In the ceremony set, many frames show guests' heads in front of the couple. Next time, move to the left aisle after the processional for a clear view."

Weak: "You edited too dark." Useful: "The reception images run about half a stop darker than my reference. Please check against the sample set before exporting."

Positive: "Your candid shots of the grandparents were lovely. I want more of those at the next event."

Pattern: "I have noticed late deliveries on the last two jobs. Can we agree on a Thursday deadline and check in on Wednesday?"

A good structure for any note:

1. What worked.
2. One thing to change, with an example.
3. Why it matters.
4. What to try next.

Say it as you would like to hear it. Avoid sarcasm and comparisons with other people.

Frequency

Match the rhythm to the stage.

• First three jobs: a short note after each, within a few days.
• After that: a brief note when something stands out, good or bad.
• Every quarter or season: a 20 minute review with the scorecard.
• Year end: talk about growth, pay and goals.

Do not save everything for one big talk. People remember praise and correction better when it comes soon after the work. Our onboarding checklist suggests when to schedule the first check-in.

ClickBook lets you keep notes and comments on a job and its editing versions, so feedback stays with the work and approvals are in one place. Look at a demo to see the edit queue.

Dealing with problems

If something goes wrong, act early and calmly.

1. Describe what happened, using facts and dates.
2. Ask for their view. There may be a reason you do not know.
3. Agree on a fix and a date to review.
4. Write it down and send a short summary.
5. Follow up as promised.

If the same problem continues, or if conduct puts clients or the team at risk, you may need to change their role or stop working together. Follow what is in your agreement, and ask a local adviser if you are unsure. Do it privately and respectfully.

Receive feedback too. Ask your team what would make the job easier. You might hear about unclear briefs or late call sheets that you can fix. For wording ideas on tone in other messages, see inquiry email subject lines.

Feedback for editors

Editors need slightly different notes because their work is a set, not a moment. Review a whole gallery side by side, not a single image. Look at white balance and skin tone across scenes, then at consistency of contrast. Send notes with annotated screenshots and a plain request, such as "warm the skin tones in the reception set by a small amount." Keep a running list of style rules and add to it after each round. If one editor handles most of your work, hold a short monthly call rather than long email threads.

Making it a habit

Add a short feedback step to your job closing routine. After each event, spend five minutes writing one note for each person. Send the notes the next day, while the memory is fresh. Keep a file for each team member with dates and themes. When it is time for a quarterly chat, you will have specific examples at hand, not general impressions, and the conversation will be fairer and more useful.

Frequently asked questions

How do I give feedback to a second shooter without upsetting them?

Be specific, start with what worked, point to the images or moments you mean, and say what you would like next time. Keep it about the work, not the person.

How often should I review my team's work?

Give short notes after each of the first few jobs, then a brief review every quarter or after a busy season.

Should feedback be written or spoken?

Both help. A short call lets you listen, and a written note gives them something to refer back to.

What if the same problem keeps happening?

Name the pattern, agree a fix with a date, and check again. If nothing changes, it may be time to adjust their role or stop working together.