Changing the scope of a service project: estimate the impact before it disappears into conversation
Assess a project scope change through its result, dependencies, cost, timing and acceptance. Compare options before a small request becomes an unclear obligation.
Article language: English

In this article
“Let us add just one field.” The sentence is small, as is the visible change on screen. Only later does it become clear that the field needs translations, new validation, changes to messages and instructions for the team handling enquiries. Assess a scope change by following it through the whole project. The number of new pixels is a poor measure of its dependencies.
First record what is to change, against which agreed version and what result the recipient should receive. Then assess the effect on work, timing, cost, acceptance and maintenance. Only then can you choose to carry it out, exchange part of the scope, postpone it or decline it. Receiving a request should not be confused with approving its implementation.
Find a shared baseline
Imagine a fictional multilingual website for a service company. A form with a specified set of fields, a way of delivering messages and responsibility for the reply have been approved. After seeing a preview, the client asks to attach additional material. To assess the change, both sides need to know what result was previously agreed.
The baseline may consist of the current scope description, design, acceptance criteria and confirmed decisions. A guide to preparing a website brief (in Polish) can help organise that starting point. If the scope changed later, do not rely on one sentence in the first message: the current agreement should also include accepted modifications.
If the baseline is unclear, reconstruct it together first. A discrepancy may be an implementation error, a new requirement or an incomplete earlier description. These should not automatically be placed in one category of paid changes. This guide organises the practical assessment; the actual agreements govern the detailed obligations of the relationship.
Turn the request into a description of the result
“An attachment in the form” leaves questions. What should the client send? Who receives it? Is it needed to respond? How will the sender know it arrived? Different answers may lead to different solutions and amounts of work. Do not price an interface while the need is still undefined.
Record the ordinary path and an important exception. In our example, the user selects a file, sends the enquiry and receives confirmation; an authorised person can access the material with the case. The exception is an invalid file or one that was not delivered. Details should fit the actual need and be assessed by the appropriate people before implementation. For attachments, distinguish selection, transfer and confirmation of availability, as explained in the article on attachments in forms (in Polish). This makes the result clearer before the team assesses implementation and acceptance.
Follow the complete contact-form journey to handling the enquiry. At the first stage, a description of the material and a later conversation may suffice; file transfer may not be needed yet. Considering alternatives is not a refusal to help. It allows the company to choose an outcome it can maintain. For the path to the recipient, the guide to the B2B contact form journey (in Polish) offers further context.
Separate the request, assessment and approval
APM describes change control as recording and assessing proposals to change an approved project baseline, followed by acceptance, rejection or deferral. Assessment includes scope, time, resources, cost and risk. This project method helps distinguish receiving a request from deciding to implement it.
A simple project does not need a multi-page form for every detail. A record of the question, impact and decision in a place both sides can access may be enough. Documentation should match the consequences. Even a short note must show which version was approved for implementation.
Decide who can approve the assessment and who approves implementation itself. If developing alternatives is separate work, name its scope and conditions before starting. Do not later present a lengthy investigation as an obvious addition to a request the other party understood as a question about feasibility.
Assess effects beyond implementation
For the form, check content, design, behaviour, error handling, message delivery, language versions and instructions for recipients. Also assess what must be checked again after the modification. One field can affect several existing paths. A small interface change need not be a small process change.
For content publication, consider roles and approval using the article on publishing content in a CMS (in Polish). For several languages, check implementation and acceptance using the guide to implementing and checking language versions (in Polish). Copying a field alone does not confirm that each recipient will see the right explanation and receive a reply in the appropriate language.
Also check dependencies on suppliers, accounts, materials and client decisions. If an unknown could materially change the work, describe the pricing condition or separate out discovery. Do not replace the unknown with an arbitrary allowance hidden in one number. The recipient should understand what has been assessed and what still needs confirmation.
Prepare comparable decision options
For the fictional website, consider four options: add full material handling now, prepare a limited stage, replace another task or defer the feature. Each option should state the outcome, inputs required, effect on timing, scope of checks and subsequent operation. Compare the same categories so a simpler option does not conceal a missing part of the process.
If you propose exchanging scope, specify exactly what is removed. “We can fit it into the project” is incomplete without the effect on remaining work. The choice may be sensible, but it must be visible. Otherwise both sides will remember the added task and neither will remember the agreed reduction.
For several providers or a larger change, a guide to a B2B service-provider selection brief (in Polish) can help establish a common description of the result and compare offers for the same work. Comparing price requires the same outcome scope. A cheaper proposal may suffice if its limitations were consciously chosen; an omitted stage must not be treated as already included.
Estimate the work by stages and assumptions
List analysis, preparation, implementation, checking, corrections within the agreed scope and handover. For each stage identify the skill needed and the way effort is estimated. Use your own rates and work data; there is no universal price for a field, a language or an integration. The same visible result may arise in very different conditions.

Separate one-off work from ongoing maintenance costs. In the material-upload example, questions arise about handling, availability and response to problems. The article on website maintenance responsibilities (in Polish) helps identify which responsibilities begin after launch. An implementation estimate should not masquerade as a complete description of the later relationship.
If you provide an estimate range, explain what determines its bounds and when it will be narrowed. If the price is fixed for stated assumptions, record them. The recipient needs grounds for a decision. One precise number without a scope may look more certain than a sound estimate while knowing much less about the project.
Example calculation: work cost and offer scope
Prepare items that correspond to real stages. For each, multiply expected effort by the adopted cost of the relevant skill, then add identified external costs. Describe estimate risks and assumptions separately. This is a working internal model, not a universal way to set a client price. The company must still decide deliberately what scope and conditions to offer.
In our example, analysis establishes who receives the material and how it is linked to the enquiry. Implementation covers the selected solution, while checking covers agreed cases in the languages and conditions used. Handover includes updated instructions for recipients. If the first estimate covered only adding an element, comparison will reveal the specific missing work. There is no need to explain the difference with a generic claim that the project became harder.
For a limited option, remove only tasks that truly cease to be necessary. If the simpler interface still needs the same handling path, the backstage cost remains. Deferring a feature may reduce the burden now but require a return to a closed stage later. Show such dependencies without automatically assuming every later step will cost more.
Present options with their different outcomes and conditions. The recipient need not see each role's internal costs to understand an estimate. They should know what work the proposal includes, what it excludes and what could change it. Transparency here means comparable outcomes, not pouring an entire spreadsheet into a message.
Check team availability and sequence
An effort estimate is not yet a schedule estimate. The required person may have other commitments, and a change may require re-entering a closed stage. Check when materials, providers and the recipient will be available. For shared resources, use priority planning for a limited team. The guide to priorities with a limited team (in Polish) considers availability and dependencies.
Name waiting for client materials or a decision separately. For the effect of a wait on the plan, consult the article on work waiting for client material (in Polish). Check what remains feasible during the pause and what condition triggers a new plan assessment. Receipt of a missing file does not itself restore the team's former availability.
Do not automatically divide work among several people to preserve a date. First check which tasks are independent and who will combine and assess them. More contributors can help, but need coordination and available reviewers. The date should follow from the actual arrangement of work, not just division of the number of hours.
If the change affects publication, show a phased option. Sometimes the agreed baseline can be published and the new scope added later. Check whether the initial version remains coherent and useful. Not every project can be split sensibly at the point most convenient for the schedule.
Update scope, decisions and materials together
The NASA configuration management chapter covers identification of the current baseline, tracking proposed changes and preserving current and historical documentation. It concerns complex engineering systems. In a service project a simpler principle is useful: the result of the change and the description of the active solution must match.
After approval, update the scope description, plan, acceptance criteria and dependent materials. Record the result in the project decision register. Saving a message saying “yes, please proceed” is not enough if no one knows which option it approved and which effects were included. The guide to project decision records (in Polish) discusses preserving the reasons for a choice.
Also check the offer and recipient instructions. If a feature changes the stated handling method, return to evidence for promises in an offer. A change on the website should not automatically create a broader promise than the company can fulfil operationally. The article on evidence for B2B offer claims (in Polish) examines claims, their evidence and conditions.
Accept the change with appropriate rechecking
Acceptance criteria should cover the new feature and the places it affects. In our example, check ordinary submission, behaviour with invalid input and the company's ability to handle the case. Choose test conditions that do not disrupt real work. The outcome should confirm the whole agreed journey, not merely the appearance of an element on screen.
Use a website acceptance process, narrowing or expanding the test to the change's actual impact. There is no reason to retest everything without cause. Nor may you assume the earlier result covers behaviour just modified. The chosen test scope needs a rationale. For choosing a test scope, the guide to website acceptance (in Polish) provides a broader framework.
Hand over the new operation using the principles of project handover between teams. The person receiving enquiries needs to know what changed, where to find material and how to report a problem. Technical readiness does not replace the readiness of the team using the result. The guide to project handover between teams (in Polish) addresses what the receiving team needs to know.
Work through one small request before the next commission
Take a change recently considered small. Reconstruct the original scope, new result, dependencies and actual work performed after the request. Compare them with the first estimate. The purpose is not to blame someone for extra hours, but to find the stage worth retaining next time.
Agree on a simple way to request, assess and approve changes. It should be proportionate to their effect and understandable to the client. A good procedure helps explain what implementation needs. It need not turn every correction request into a ceremony with its own opening protocol.
If you are planning a website and want a clear scope and acceptance, see Aeneia Design. Start with the current brief and an example of a change whose impact was hard to assess. That grounds the conversation in a real task and its dependencies.








