One extra request can affect materials, staff time and the delivery promise. Use a simple decision record to agree the change before the team starts.
Agree the requested change before updating the delivery plan.
The café counter is nearly ready when the owner asks for one more display shelf. It sounds straightforward. But the carpenter is booked elsewhere, the extra board has not been purchased and nobody has agreed whether the shelf is included in the original price.
For a small service business, that is how a friendly “yes” can become an unclear deadline and an uncomfortable payment conversation.
A customer change request needs a short, visible decision before it becomes delivery work. You do not need a large approval committee. You need to know what changed, what it affects, who can agree it and which plan the team should now follow.
The café fit-out example below is hypothetical. It shows a practical routine for Nepal’s contractors, agencies and other businesses that deliver work against an agreed scope.
A customer discussion can reveal details that still need agreement.
Check what the customer originally agreed
Keep the accepted quotation, drawing or scope description where the person reviewing the request can find it. Include the relevant version and approval date. “The customer asked for a shelf” is hard to evaluate without knowing what shelving was already included.
First decide whether the request changes the agreement or simply clarifies it. If the team delivered the wrong shelf size against an approved drawing, investigate that as a correction. Do not automatically turn it into a paid addition. If the customer wants a second shelf that was never included, assess it as a proposed scope change.
Where the agreement is unclear, record the uncertainty and discuss it before promising a price or date. This is an operational review, not a substitute for reviewing the actual contract.
The Association for Project Management’s change-control guidance describes recording and evaluating proposed changes, deciding whether to approve, reject or defer them, and updating the plan after approval. A small business can apply that logic with a simple change register.
Classify the request against the accepted scope first.
Give each request a reference and link it to the existing project. Capture the requested result rather than a vague instruction such as “make the display better.”
For our hypothetical café, the request could read: “Add one wall-mounted display shelf above the counter, with dimensions and finish to be confirmed before purchase.” That wording exposes the missing decisions.
| Record field |
Useful entry for the hypothetical request |
| Reference and project |
CR-004, Café Fit-out P-018 |
| Requested addition |
One extra display shelf above the counter |
| Specification needed |
Dimensions, finish and fixing requirements |
| Original scope reference |
Accepted drawing and quotation version |
| Review owner |
Named coordinator responsible for the assessment |
| Decision evidence |
Agreed scope, price, timing and customer confirmation |
Keep the request attached to the same project. If it arrives in a phone call or chat, summarise it in the register and ask the customer to confirm the important details. A message saying “looks good” should not silently stand for approval of an unspecified price and delivery date.
Check materials and available time before confirming the addition.
Review materials, labour, access, supplier lead time and any work that must be repeated. Confirm whether a component is already available and allocated to this project before ordering another one.
Assume the extra shelf requires the following incremental inputs:
| Input |
Hypothetical assumption |
Estimated direct cost |
| Board, finish and fixings |
Materials only, excluding installation labour |
NPR 6,000 |
| Fabrication and installation |
10 hours at an internal planning rate of NPR 800/hour |
NPR 8,000 |
| Total incremental direct cost |
NPR 6,000 + NPR 8,000 |
NPR 14,000 |
The ten hours include both fabrication and installation. Do not add another installation charge to this cost estimate for the same work. The material figure excludes that labour.
NPR 14,000 is an illustrative direct-cost estimate, not the customer’s selling price or a profit calculation. Review overheads, uncertainty, commercial terms and any applicable tax treatment separately before issuing a quotation. No tax rate is assumed here.
ERPNext’s Project Costing documentation illustrates linking task time to projects and distinguishing costing rates from billing rates. The practical lesson is to keep internal effort estimates separate from the amount offered to the customer.
Hypothetical cost and capacity calculations use separate measures.
Check capacity before giving a revised date
An estimate of ten hours does not mean the team can finish tomorrow. Suppose the carpenter has six uncommitted project hours available before the currently agreed handover. The additional ten-hour task leaves a four-hour capacity gap.
10 additional hours − 6 available hours = 4 hours that still need a plan
The coordinator can propose a later shelf installation, review another booking with its owner or assess an alternative design. Check skills, access and material availability before treating any option as confirmed. Do not move another customer’s work without reviewing that commitment too.
Give the customer a realistic proposal with the dependencies stated. For example: “We can confirm the installation slot after you approve the dimensions and finish and the material availability is checked.” Replace that with a firm date once the necessary checks are complete.
Get the decision and update the working plan
The customer should be able to see the addition, agreed price and effect on timing in one place. Record who approved it and when. Keep proposed, approved, deferred and declined requests visibly distinct.
For an approved request, update the project tasks, purchasing requirements and relevant commercial records. Keep the earlier accepted scope available as history; label the revised working version clearly.
When planning connected WorkSphere workflows, evaluate these links:
- CRM keeps the customer conversation and confirmation reference.
- Project/Task Management records the approved work, owner and dependencies.
- Inventory checks relevant materials and purchasing needs.
- Accounting receives the approved commercial details for review.
- HRM can provide relevant employee availability without exposing private information.
These are suggested integration requirements, not a claim that particular WorkSphere connections are currently live.
Carry the approved decision into the working records.
Close the request against the agreed result
Before marking the addition complete, check it against the approved dimensions, finish and other acceptance points. Record any remaining action with an owner. Compare actual material use and time with the estimate so the next similar request starts with better information.
Keep customer acceptance, invoicing and payment as separate checks. An installed shelf does not by itself show that an invoice was issued or paid.