PREPARATION — Customer change and current working version Do not transfer any real customer, contract or project data here. In your own approved system, on the correct task: Current confirmed version | existing scope/deadline | new request | receipt | what is being added/replaced/removed? Impacts: Required information | time/resources | existing commitments | specialist review | within the existing standing rule? Combine the same change from multiple messages; do not trigger it more than once. Next steps: Coordinate permitted routine work directly. New commitment outside the agreed limits: prepare a specific decision, including its impacts. An internal decision is not automatically an agreement with the customer. Updated status: Actual coordination with the customer | current version | authoritative source updated? | team informed? | old version marked as replaced? Keep pending approval or incomplete implementation visible. A message alone does not update a calendar or work schedule. Adaptable response: You would like [specific change]. We will clarify [impact] and agree [scope/deadline] with you. Until then, [confirmed status] remains the basis for our planning. Do not introduce new fees, contract terms or legal claims with this list. Specialist decisions remain with the responsible specialists. Check actual system actions separately.