PDF changes need exact pages, locations, actions and review points. A vague request can mean removing pages, replacing text, changing order or preparing a new version.
State page, section, desired change, target state and expected output before running the action.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Change this PDF only according to these instructions: page, location, change, target state, output format and review points.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to files, sources, responsibilities and expected output format. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not bundle several unclear edits into one sentence.
The file action becomes traceable and easier to check.