Skip to content
AloZen
English

The customer asks for a change.
What is agreed now?

Connect the new request to the agreed task, its implications and the current working version. This way, the team works from the right version instead of conflicting messages.

Download the change sheet
Illustrative scene: a floor plan with a marked change in a carpentry workshop. AI-generated concept image.
AI-generated concept image. Not a customer reference.

One small message changes the whole job.

“Can you do this as well?” sounds straightforward. It may mean only a permitted change to a detail. Or it may require additional time, materials or a new date. If that remains unclear, the office plans according to the original quote, the team follows a new message and the customer already expects more.

A cleaning business adds another room, a landscaping business an additional section, an agency a second format. The problem is not the change request itself. What is missing is a shared understanding of what has been agreed and what may be done next.

A request, a decision and what currently applies are different things.

A customer request is initially just information. It can be acted on directly under existing rules or may require a decision. Only the actual agreement establishes the applicable scope and date. The team then needs this current version, not a stack of old messages.

Project methods refer to this as scope and change control. In everyday work, a clear change note on the task is often enough. It is not meant to create more bureaucracy, but to prevent different people from working from different information. A routine change within agreed limits does not require new owner approval.

Four steps keep the job on track.

  1. Find the existing basis. Link the request to the right task and the most recently confirmed version. What was agreed on scope, timing and services? If the same change has already been received, continue with the existing record.
  2. Describe the change precisely. What is being added, removed or replaced? Record the impact on time, resources and existing commitments. Ask targeted questions to obtain missing information; have the responsible person clarify the practical implications.
  3. Act within existing authority. Coordinate permitted routine changes directly. Prepare additional commitments outside the rules as a concrete decision, including the consequences. Do not confuse the internal decision with any necessary agreement with the customer.
  4. Make sure the new version is shared. Once agreement has actually been reached, update the current version in the primary system and inform the people affected. Mark old versions as superseded. Pending approval or implementation remains visible.

You would also like to include the meeting room. We will check how much additional time is needed and get back to you to agree on a suitable scope and date. Until then, the previously agreed service remains the basis for our planning.

The note does not establish legal claims, additional fees or contractual terms. Whether and how a change is validly agreed depends on your specific task and the people responsible for it.

AloZen keeps the coordination and office work moving.

AloZen can capture the change request, bring together existing task information, ask for missing details and coordinate the team or suppliers. He handles permitted routine work independently and prepares a genuine exception with the necessary facts.

Where appropriate, this includes calendar, project or document actions in your work environment. Sending a message does not in itself change the authoritative plan. The supported action and its actual result must match; professional decisions remain with the qualified people responsible.

Coordinate changes as a complete office task

Example: An additional room in a cleaning job.

A fictional cleaning company currently cleans five rooms on Tuesday mornings. The customer emails to request an additional meeting room. The existing standing rule allows a schedule change for the same service, but not an increase in scope.

Current task
Five rooms, a confirmed service description and an existing work schedule. The email alone does not replace these arrangements.
Decision prepared
The operations manager checks the area and workload: the new room requires additional working time. The office and management prepare the scope and a suitable work schedule for discussion.
Actual agreement
After an internal decision, the company agrees the new scope and terms with the customer. Only the confirmed agreement forms the new basis for the work.
Work updated
The new version covers six rooms. The work schedule and instructions are actually updated, and the team receives the current version. A later question about the same change stays with the same case.

A simple schedule change that meets all existing conditions is different: it can be coordinated directly under the standing rule. The benefit is making the right distinction, not seeking as many approvals as possible.

Review how changes are handled in your business.

Source and context.

Asana: Project scope, July 9, 2026: A provider's perspective on scope and changes. The simple workflow described here is not an Asana integration or legal advice.

Sources checked on 30. September 2026. They explain the work context or features of other providers; they do not establish an AloZen integration, customer results or guaranteed effects.

Here for you around the clock

Three ways to reach us.
An answer right away.

Chat, WhatsApp or phone: AloZen responds on all three channels, day and night and in your language. Experience firsthand how reliably your office will work in the future.

Would you rather speak to a person? Lily will book a personal appointment with us for you directly.

Book an appointment