Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Glossary: projects

What Is Change Request? Meaning, a Worked Example and How to Approve One

For project managers, agency owners and delivery heads: what a change request is and how to handle one so extra work is agreed, priced and planned.

A site manager and a client looking at a floor sheet on a trestle table

What is change request? It is the written, assessed and approved way to change a project that is already under way. It turns a casual ask into a decision with a price and a date.

In many Indian agencies, contractors and IT service firms, changes arrive on calls and chat. The team says yes to keep the client happy, the work grows, and the invoice or the deadline becomes a fight at the end.

This page explains the term, gives an illustrative example and shows how Apragya records change requests on the project.

Change request meaning and what it should contain

A change request is a formal proposal to change something already agreed in a project: its scope, timeline, budget or quality standard. It is written down, assessed for impact and approved or rejected before anyone acts on it.

A good change request answers five things: what is changing, why, and the impact on scope, schedule, cost and quality. Only then can the sponsor or client decide with open eyes.

A worked example: a client asks to add a Hindi version of a website two weeks before launch. The request estimates 60 extra hours at 1,500 an hour, so 90,000 more cost, and a 10-day delay. The client approves the cost but asks for launch in English first, with Hindi ten days later.

Without the request, the same change would have slipped in informally and turned up later as a late launch and a billing dispute.

  1. Write the change: what, why and who asked.
  2. Assess the impact on scope, schedule, cost and quality.
  3. Submit it to the person who can approve.
  4. Approve, reject or ask for changes, and record the decision.
  5. Update the plan, budget and tasks only after approval, then mark it implemented.

What skipping the change request process costs

Unbilled work

Extra effort is delivered but never priced.

Silent delays

Deadlines slip without anyone agreeing to the new date.

Client disputes

Nobody can show what was agreed and when.

Team fatigue

People absorb extra work with no change to the plan.

An example: a Bengaluru interiors contractor

Take an illustrative interiors firm fitting out an office. Three weeks in, the client asks for a glass meeting room in place of an open area.

The change request, as approved

Change request, meeting room

  1. Raised after a site visit.

  2. Partitions, door and wiring added.

  3. Glass lead time from the supplier.

  4. Materials and labour, before GST.

  5. Same specification as the other rooms.

  6. Signed off by the client before work began.

Every impact was on the record before a single panel was ordered.

The glass was ordered the day the request was approved. The client paid the extra amount with the next milestone, and the eight-day shift was already in the plan, so nobody was surprised at handover.

Glass panels with a sealed sheet taped on top, ready to fit
The glass arrived on the date the approved request had already built into the plan.

How Apragya handles change requests in project management

Step 1 of 5

Request on the project

Title, description, reason and who asked, on the project itself.

  1. Request on the project: Title, description, reason and who asked, on the project itself.
  2. Four impacts: Scope, schedule, cost and quality, with a number for the cost impact.
  3. Lifecycle: Draft, submitted, approved or rejected, then implemented.
  4. Triggers on submit: A submitted request can trigger an automation, such as alerting the approver.
  5. Project financials: Approved changes sit next to the budget and billing.

Why scope change approval belongs on the project

A change request kept in email cannot be read next to the plan. When it lives on the project, the manager sees every approved change beside the tasks, budget and milestones it affects.

Changes by email, against Apragya

FeatureEmail and chatApragya
RecordScattered threadsOne request on the project
ImpactOften missingScope, schedule, cost and quality
DecisionA reply that says okApproved or rejected status
Total effectAdded up by handCost impacts on one project
Follow-throughAssumedMarked implemented

Checked against public information on 16 September 2026.

What sets Apragya apart for project teams

Critical path and Gantt

See how a delay moves the finish date.

Milestones

Tie approved changes to the milestones they shift.

Time logs

Track the hours the change actually took.

AI you can put to work

An agent can draft the impact summary from the request.

Access by role

Clients and staff see only what they should.

Audit log

Who approved, and when, is logged.

See change requests, risks and project financials. Related terms: critical path and burndown chart.

Getting started

  1. Agree with your client that changes go through a request.
  2. Record the next ask as a change request.
  3. Fill in all four impacts, with a cost figure.
  4. Get a decision before any work starts.
  5. Review approved changes at each milestone.

The first request usually settles the habit for the whole project.

What it costs to start

INR 7,999
Pro, a month
Up to 25 users, with Project Management and every enterprise app
5,000
AI Credits a month
Included on Pro
Free
Up to 3 users
CRM and HR, to try the platform first

Change request process, answered

Does every small change need a request?
Agree a threshold with the client. Tiny fixes can be logged together; anything that moves cost or dates should be a request.
Who approves a change request?
Usually the project sponsor or the client's representative, as agreed at the start.
What if a request is rejected?
Record the decision and the reason. The project continues on the original plan.
Is a change request the same as an issue?
No. An issue is a problem that has happened. A change request proposes changing the agreed plan.
What does it cost to start?
Project Management comes with the Pro plan, INR 7,999 a month for up to 25 users, which includes every enterprise app, 5,000 AI Credits a month, single sign-on and audit logs. The free plan covers up to 3 users with CRM, HR and Vendor Onboarding if you want to try the platform first.

Price every change before you do it

Log your next client ask as a change request and get a decision on the record.