An archived illustration should be reopened before you promise a quick revision because the source may depend on missing links, old software, or fonts no longer installed. The requested visual change may be small while recovery takes substantial effort. Inspect the actual starting material and delivery context first, then estimate the revision from evidence rather than the apparent simplicity of the client's sentence.
Verify the archive's usable starting point
Locate the approved source and exact prior delivery, using revision records rather than the most recently modified file. Open a copy of the source and check for missing resources or conversion warnings. Compare its appearance with the archived export. If the image changes in current software, resolve whether the difference affects the requested work before making an effort estimate based on a misleading preview.
Inspect the layer or object structure around the requested change. A label may remain editable, be outlined, or be painted into a flattened group. A character may have movable parts or require reconstruction from a composite. These differences determine the real work. Do not assume a native file contains every original editing boundary simply because it has the application's familiar extension.
Check fonts, linked images, third-party permissions, and application version requirements relevant to the revision. A new campaign or usage context may need a separate rights review even if the artwork looks unchanged. Keep the question tied to the actual resource and proposed use. A past delivery's validity does not automatically establish every later distribution or source-sharing permission.
Assess the change in its new context
Confirm current wording, dimensions, formats, audience, and delivery date. A request described as the same image with a new date may also involve a different poster size or language. Compare those requirements with the archived composition. New text can require spacing changes, and a different crop may reveal unfinished areas that were never part of the original delivery.
Make a small exploratory edit in a duplicate if that helps establish feasibility. Try replacing the wording or isolating the object and inspect the dependencies. Keep the archive intact. The purpose is to understand the work, not to complete an unagreed redesign while investigating. Note what can be reused and what requires reconstruction or new approval.
Estimate recovery, revision, adaptation, review, and export checks separately where the distinction is meaningful. Explain any uncertainty caused by missing material. If the source cannot be restored reasonably, offer a reconstruction or new-artwork option with its actual implications rather than describing the work as a quick tweak. Clear evidence helps the requester choose a realistic path.
Save the new project under a fresh revision identity and retain the original delivered package. Record any repaired dependencies so the next reopening is easier. Reopening before promising protects the schedule and the quality of the result, allowing a genuinely small edit to remain small while exposing the archive and compatibility work that a brief request might otherwise conceal until the deadline is already committed.