Production II: problem-solving, reshoots and the mid-term review

No capstone goes exactly to plan. A site withdraws access, a key subject moves away, a drive fails, a week is lost to illness, or the images simply do not say what the proposal hoped they would. What distinguishes successful projects is not the absence of problems but how quickly they are noticed and how well they are handled. This lesson covers problem-solving during production, managing changes to the plan, the mid-term review in week 7, and planning reshoots. It builds on the critique methods of PHOT-401 lessons 7 and 8 and the scheduling and risk tools from lesson 3.

Noticing problems early

Problems are cheapest to solve when they are small. The weekly review from lesson 4 and the risk register from lesson 3 are your early warning system. Watch for signals: a site contact who stops replying, a coverage gap that does not close, shoots that take longer than planned, a budget line that is running ahead, images that look competent but do not move you, or a growing reluctance to go out and shoot. Each of these is information. Write it in the log, decide whether it needs action, and if it does, act within the week.

Some signals are about you rather than the project. Night shoots, demanding subjects and a heavy course load can wear people down. Fatigue leads to mistakes with files and safety, and to poor judgement in the edit. Build rest into the schedule, especially after late shoots, and treat a persistent loss of energy or motivation as a real problem to raise with your supervisor or the school's support services, not as a personal failing to hide.

A method for solving production problems

When a problem appears, work through four questions. What exactly has happened, and what is the evidence? What is the impact on the critical path, the budget, the coverage grid and the concept? What are the options, including doing nothing? Which option best protects the opening date and the integrity of the work at an acceptable cost? Write the answers in the log; if the decision changes the scope, outputs, budget by more than the contingency, or the ethical basis of the project, discuss it with your supervisor before acting.

Managing changes to the plan

The approved proposal and production plan are the baseline. Changes are normal, but they should be deliberate and recorded. A simple change log lists the date, what changed, why, the impact on schedule, budget and outputs, and who approved it. Minor changes, such as swapping the order of two shoots, need only a log entry. Major changes, such as replacing a site, switching from a book to a screen-based output, or changing the question, need supervisor approval and may need updated permissions.

When the hospital's communications office paused Amara's access in week 6 during a busy period, she logged the problem, checked the critical path (hospital shoots were on it), and chose between waiting, switching to the cleaning company that serviced several office towers, or dropping the hospital strand. She proposed switching to the office towers while keeping the two hospital portraits already cleared, which preserved the theme of cleaning work at night, cost two extra travel nights and needed new access agreements and releases. Her supervisor approved the change on condition that the new agreements were in place before shooting.

Checking progress against the plan

Progress is easier to judge with numbers. Compare the work you planned to have done by now with the work actually done, and the money you planned to spend with the money actually spent. A simple way, borrowed from project management, is to estimate the percentage complete of each stage, multiply by the stage's planned hours to get the earned hours, and compare earned hours with the planned hours to date and the actual hours spent. If earned is below planned, you are behind schedule; if actual is above earned, the work is taking longer than estimated.

plan = {'research': 14, 'preproduction': 18, 'shooting': 45, 'files': 10, 'editing': 16, 'post': 12,
        'writing': 10, 'output': 14, 'install': 8, 'portfolio': 8, 'presentation': 6}
done = {'research': 1.0, 'preproduction': 1.0, 'shooting': 0.75, 'files': 0.6, 'editing': 0.15}
actual, capacity_left = 82, 6 * 12 * 0.9
earned = sum(plan[k] * done.get(k, 0) for k in plan)
remaining_plan = sum(plan.values()) - earned
factor = actual / earned
forecast = remaining_plan * factor
print(f'earned {earned:.2f} h, effort factor {factor:.2f}')
print(f'remaining at plan {remaining_plan:.1f} h, at current factor {forecast:.1f} h')
print(f'capacity left {capacity_left:.1f} h, gap {forecast - capacity_left:+.1f} h')

earned 74.15 h, effort factor 1.11
remaining at plan 86.8 h, at current factor 96.0 h
capacity left 64.8 h, gap +31.2 h

The forecast compares remaining work, adjusted for the effort factor so far, with the hours left in the term. A positive gap means something must give. Work through the options in the same order every time: use float and spare nights, trim tasks that do not affect assessed outputs, simplify outputs, and only then reduce the body of work itself.

Budget variance

Track spending against the budget weekly. A forecast at completion adds money already spent to a fresh estimate of what remains; comparing it with the budget shows whether the contingency will cover the difference. Output costs are often fixed by quotes in week 9 or 10, so a budget that is running ahead in week 7 is the last moment to change output decisions cheaply.

Preparing for the mid-term review

The mid-term review is the third assessed deliverable and the single most useful meeting of the term. Its purpose is to test whether the body of work is cohering and whether the plan will deliver it, while there is still time to change course. Bring a rough edit of fifteen to twenty-five images, printed small (work prints) or laid out on screen in a draft order; the coverage grid; the schedule with progress marked; the budget with spending to date; the change log; the process log; and two or three questions you want answered.

Reviews often include peers as well as the supervisor. Use the critique methods from PHOT-401 lesson 7: present briefly, then listen; let reviewers describe what they see before you explain what you intended; ask open questions such as "Which images feel like they belong to a different project?" and "Where does the sequence lose you?"; and write everything down. Gaps between what reviewers see and what you intended are the most valuable information you will get all term.

Acting on mid-term feedback

After the review, sort the feedback into three groups: act on now, test before deciding, and set aside with reasons. Feedback that several reviewers give independently, or that matches what you already suspected, usually belongs in the first group. Suggestions that would change the concept substantially belong in the second or third, because there may not be time to develop them properly. Write a short response document within two days that lists the main points and what you will do about each, and agree it with your supervisor.

Amara's reviewers said that the portraits were strong but similar, that the interiors were the more surprising images, and that the taxi strand felt thin. She decided to act on the first point by asking some subjects to choose a different working position for a second portrait, to test the second point by building a draft sequence that led with interiors, and to set aside a suggestion to add archival night photographs of the city because it would change the project's form and could not be researched properly in the time.

Planning and making reshoots

A reshoot replaces or improves an image that is close to working but has a fixable problem: soft focus, a distracting background, an unflattering moment, a consent issue, or a gap in the sequence. Reshoots should be planned like any shoot: a list of target images, why each is needed, what will be different, and how it will match the images it sits beside. Matching matters; a reshoot made with different light or a different lens will stand out in the sequence. Bring prints or a tablet showing the original to the reshoot to match framing, height and light.

Knowing when to stop shooting

By the end of week 9 at the latest, production should stop except for a final reshoot or two that the edit specifically needs. Stopping is hard because there is always another picture to make. The edit, the writing and the output all need time and fresh eyes, and they are assessed with the same weight as the images. Treat the last shoot date as you would a client's delivery date: fixed unless something serious changes.