Free Website Change Request Board Template
A website change request board tracks incoming site edits, triage notes, scheduling, in-progress work, and deployment status in one workflow.
Share template
A set of website tweaks comes in, but the scary part is what happens around them: a “small change” can break forms, knock out tracking, or blow up a mobile layout right before a busy week. This Website Change Request Board keeps every request moving through one pipeline, so nobody’s guessing what’s queued, what’s risky, and what’s already shipped.
The columns read like the way change requests actually unfold, from Onboarding and Intake through Triage, Scheduled, In progress, and Staging and deployed. The work stays visible at a glance in deep plum with Space Grotesk headings, so updates look like status, not a chat thread... and the last column makes it clear what reached staging and what went live.
- Onboarding Holds the first setup work that needs to happen before edits start, so access and context don’t get buried in messages.
- Intake Captures each change request as it arrives, so the backlog stays in one place before any prioritising happens.
- Triage Separates straightforward edits from changes that could affect layout, forms, tracking, or other dependencies before anything moves onto the schedule.
- Scheduled Carries the requests you’ve committed to next, leaving you to add your own dates since the board tracks order, not a calendar.
- Staging and deployed Tracks what reached staging and what shipped to production, so finished work doesn’t vanish into “done somewhere”.
The board runs as a project workflow, so you add your own dates as you schedule work and break larger requests into tasks when you need an owner and a next step.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What is on this board
6 columns, ready for your own cards. Adding it builds the board as a project in your workspace, with every column in place. The cards in the preview are examples of how the board is used, and are not added.
| Column | What is in it |
|---|---|
Onboarding | The Onboarding column holds the initial setup work that needs finishing before change requests move forward. |
Intake | The Intake column collects incoming edits and questions, so the backlog stays together instead of spreading across email threads. |
Triage | The Triage column is where requests get sorted by risk and complexity before anything gets scheduled. |
Scheduled | The Scheduled column marks what’s up next; you add your own dates because the board keeps an ordered workflow, not a calendar. |
In progress | The In progress column holds the work currently being applied, so it’s obvious what’s active and what’s still waiting. |
Staging and deployed | The Staging and deployed column shows what reached staging and what went live, so release status stays explicit. |
What happens when you install it
- A project is created with its board and 6 columns, empty and ready for your own cards.
- Every card you add opens as a task with its own description, assignee, dates, subtasks and files, and columns are renamed, reordered or deleted like any other.
Who it is for
Frontend developers, full-stack developers, and CMS and WordPress teams handling ongoing site edits for clients who want clear status and safe releases.
Questions about this project template
What should a website change request board include?
A website change request board usually includes columns for intake, triage, scheduling, active work, and deployment status. The workflow makes it clear what’s waiting, what’s underway, and what already shipped.
How do you keep website changes from breaking the live site?
A change request workflow helps by forcing a triage step before work gets scheduled, so risky edits get spotted early. A final staging and deployment step also makes release status explicit instead of assumed.
Can a client log website changes without emailing?
A board gives you one place to capture each request as it comes in, so nothing gets lost in threads. The intake column becomes the single backlog you work from.
How do you manage lots of small website edits at once?
A board queues requests in one intake column, then moves them through triage and scheduling in order. The visible pipeline keeps priority and status clear even when the list is long.
What’s the difference between a change request board and a bug tracker?
A bug tracker focuses on defects and reproduction steps, while a change request board covers edits, tweaks, and planned updates as well as issues. The workflow emphasises triage and release status, not just bug resolution.
Do website change requests need dates on the board?
Dates help, but a board can still work without them because the columns show the order work moves through. This template keeps the workflow, and you add your own dates as you schedule.
Start free today
Your entire business, one login away
No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.
No credit card required
