A revision becomes a scope change when it alters the agreed work rather than refining it within the approved direction. Replace the character with a crowd or add a tall poster version may be phrased casually, yet each can introduce substantial production. Identify the new requirement, explain its visible consequences, and update the project agreement before treating it as an ordinary local correction.
Compare the request with the approved baseline
Keep the working brief, selected concept, required formats, and agreed review rounds accessible. When a new comment arrives, compare it with those records. A request to clarify the existing character's gesture may fit the current direction; a request to depict a different event may reopen the concept. The distinction depends on the actual agreement and effect, not a universal rule about how many pixels change.
Restate the request concretely. Add more energy might mean a stronger pose within the same scene, or it might mean several new figures and a different viewpoint. Clarify before estimating. A vague phrase can hide either a modest adjustment or a new illustration, and responding to the most expansive interpretation immediately can create work no one knowingly authorized or scheduled.
Trace the dependencies of the proposed change. A crowd affects composition, anatomy, overlaps, lighting, and possibly audience representation. A new format affects framing, text space, and exports. Show these relationships through a rough sketch or concise explanation so the requester can understand why a short sentence may require more than a quick edit to a finished layer.
Agree on the practical consequence before production
Offer feasible options when they preserve the underlying need. A stronger gesture or a few background silhouettes might supply energy without a complete scene redesign, if that meets the communication goal. Do not present a shortcut as equivalent when it sacrifices a required meaning. Explain what each option achieves and where its limits remain, allowing the decision owner to choose deliberately.
Estimate the effect on effort, review, cost, and delivery timing through the project's normal agreement process. Include adaptations and checks that must be repeated after the change. Avoid absorbing the new requirement silently and then rushing quality control to maintain an obsolete schedule. A scope discussion is most useful before substantial new work has already been done.
Record the chosen option and what earlier approval it replaces. If the team decides to keep the original scope, preserve the deferred request as a possible later task rather than leaving it ambiguously half accepted. If the change proceeds, update the brief and revision list so future comments are judged against the new agreed baseline, not competing memories of the earlier project.
Continue with a saved checkpoint and a clear production plan. Scope recognition need not turn every comment into a dispute; it makes consequences visible when a request changes the work's foundation. The project remains easier to manage when refinements and new requirements receive the appropriate decision, resources, and review time before the illustration accumulates effort based on an uncertain agreement.