Change Request

What this is about

Briefs mature during a project, so changes are normal and refusing them is rarely the answer. The instrument that keeps them harmless has three lines: what changes, what it costs, what it moves in the schedule. Approval comes from whoever holds budget authority, and work starts after that, not before. Handled this way, a change is a business decision the client makes with open eyes. Handled informally, the same change becomes scope creep — the difference between the two is not the size of the request but whether it was ever priced and signed off.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

• Three lines are enough: what changes, what it costs, what it moves — sent before the work begins
• Zero-cost changes still deserve a note, because they set the precedent for the next one
• The approver has to be someone with budget authority, not whoever happened to send the email

With TillyGen

TillyGen shows what an extra scene or setup does to days and budget, so a change request carries a number from the start.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.