How to track change requests and scope creep in monday.com

By Kayabyte

Short answer: monday.com can hold a change request log. Create a board where each item is one change request, add columns for the project, a status, the amount, the reason and the requester, and use automations to notify whoever decides. That covers the log. It does not number the requests for you, get the client’s decision on record, or keep a running total per project. For those parts you need manual routines or an app such as Change Requests & Change Orders.

Scope creep rarely arrives as one big request. It arrives as “can you also…”, in a call or a chat, and it gets done because it is quick. A change request log makes each of those visible: what was asked, who asked, what it costs and whether anyone agreed. This guide shows how to build one on a monday.com board, step by step, and where it stops. Menu names and plan limits change over time, so check your own account when a step looks different.

What monday.com gives you

Items and groups: one item per change request, with groups such as Open, Decided and Closed.
Board relation (Connect boards) column: links a request to the project it belongs to on your project board.
Status column: a manual label such as Draft, Sent, Approved or Rejected.
Numbers columns: amount, hours and extra days.
Dropdown column: the reason, such as client request or unforeseen condition.
People column: who asked and who decides.
Automations: rules such as “when status changes to something, notify someone”.
Filters, views and dashboards: show only pending requests, or totals per project.

Step by step: a change request log

Create the board. Start a new board and name it Change requests. Rename the first column to Title and put a short description of the change in the item’s updates or a Long text column.
Add the columns. Add a Board relation (Connect boards) column to your project board, a Status column, Numbers columns for Amount, Hours and Days added, a Dropdown column for Reason, a People column for Requested by and Decider, and a Date column for Decided on.
Set the status labels. Use Draft, Sent, Approved, Rejected and Withdrawn. Add Invoiced if you also want to see what has been billed.
Number the requests. monday.com has an Item ID column that gives each item a unique number. Use it, or type a reference such as CR-0007 in a Text column, so people can refer to a request in emails and invoices.
Record every request. Add an item as soon as someone asks, even if you plan to do it for free. A free change is still a change, and the log shows how much you gave away.
Add the notification rules. Open Automations on the board and add a rule such as “when status changes to Sent, notify someone”, with the People column as the recipient. Add a second one for Approved so the delivery team knows it can start.
Make working views. Filter by status to see what is waiting. Group by project to see how many changes each project has. Add a dashboard with a chart of requests by reason, or the sum of the Amount column by status.

Where it stops

Numbering is loose. An Item ID column is unique but not formatted as CR-0007, and a typed reference is only as reliable as the person typing it.
The decision is not recorded properly. A status set to Approved says nothing about who approved, when and what they saw. If the client agreed by email, the proof lives in a mailbox.
Status is manual. Nothing stops someone from setting Approved on an item that was edited after the client agreed.
Reminders for stale requests need rules. A request that has been sent and not answered for a week does not nag by itself. You can build an automation for it, but each rule is yours to maintain.
Totals per project need extra setup. To see the original value, the approved changes and the revised value of a project, you need connected boards, mirror columns and formulas, which have limits. The third guide in this series, How to track a revised contract value in monday.com, goes through them.
Clients and the board. Asking a client to log or approve requests on the board means guest access and permissions. See How to get client approval for a change order in monday.com.

Habits that keep a change request log honest

Log the request the day it is asked, not when it is priced.
Write the change in one or two sentences a client would recognise, and the price next to it.
Keep Reason filled in. After a few months it tells you whether the changes come from the client, from unclear scope or from your own mistakes.
Do not start paid-for work before the status is Approved, and do not edit an approved request. Create a new one instead.
Review pending requests in your weekly meeting, and close or withdraw what is dead.
Put the reference number on the invoice line, so billing can match it.

Change Requests & Change Orders

Change Requests & Change Orders is the app we make for the parts above that stop. It works on a monday board, so your automations, filters, dashboards and exports keep working.

Setup can create a register board with the columns for you, or map the board you already have. Requests get a sequential reference such as CR-0007.
Each request has a project link, status (Draft, Sent, Approved, Rejected, Withdrawn, Invoiced), amount or hours times a rate, schedule impact in days, reason, requester and client contact.
Editing a sent request voids the open approval link and sets it back to Draft, so the client never approves something that has since changed.
The requester and watchers get a reminder when a request has been Sent for 3 and 7 days without a decision.
The board view has filters, totals for pending, approved, invoiced and approved but not invoiced, a per-project summary and a CSV export.
The app does not send email, generate PDFs or sync with invoicing systems.

There is a Free plan with a small number of requests sent per month. See the Change Requests & Change Orders page for current plans.

FAQ

What is a change request log? A list of every request that changes the agreed scope, with who asked, what it costs in money, hours and time, and what was decided. Its job is to turn “quick favours” into visible, decided changes.

Can monday.com track scope creep? It can record it. A board with a status column, an amount and a reason for each request, plus a dashboard, shows how much extra work was asked for and how much was approved. It does not detect scope creep by itself, so someone has to log each request.

Should I log changes I do for free? Yes. Mark them Approved with an amount of zero, or use a reason such as goodwill. The log then shows what the free changes added up to.

How do I connect change requests to a project? Add a board relation (Connect boards) column from the change request board to your project board. Each request then points at its project, and you can filter or group by it.

Is this contract or legal advice? No. It shows how to organize the requests. Your contract decides what counts as a change and how it must be agreed.

monday.com is a trademark of monday.com Ltd. Kayabyte is an independent developer and is not affiliated with or endorsed by monday.com.