Free Website Change Request Board Template
A website change request board tracks incoming site edits through intake, triage, scheduling, delivery, and deployment so nothing gets lost or shipped blind.
Share template
A site change lands as “quick tweak”, but the risk sits underneath: a form stops sending, tracking drops off, or the layout breaks on phones right before a busy week. A Website Change Request Board holds every request in one place and moves it through a visible workflow, so updates ship without guesswork and nobody has to wonder what’s happening next.
The board runs left to right from Onboarding through Staging and deployed, so a request gets checked, queued, worked, and pushed live in an order everyone can read. The layout uses inspection-purple and a status-light teal under Space Grotesk headings, which keeps the board feeling like release control instead of a chat thread... and makes “what could break” hard to ignore.
- Onboarding Use this column to capture access, context, and any release rules before a request moves into the queue.
- Intake Log each change request as it comes in, including what needs changing and any links or references you’ll need later.
- Triage Sort what’s straightforward versus risky work, so scheduling and estimates start from the real impact on the live site.
- Scheduled Place approved requests into a delivery order and add your own dates, since the board doesn’t run on a calendar.
- Staging and deployed Track what’s been verified and pushed live so nobody has to ask whether a change is still waiting or already shipped.
In Plutio, the template runs under projects so each request can sit in the right column and you can add your own dates, since the board carries the order of the work rather than a calendar. The same workflow fits frontend development handoffs, cms & wordpress updates, and e-commerce builds where a “small” change can still touch a live checkout.
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 setup steps that need to be true before any change request moves forward. |
Intake | The Intake column is where new requests land so the work doesn’t live across email threads and DMs. |
Triage | The Triage column is where each request gets checked for impact and risk before anyone books time for it. |
Scheduled | The Scheduled column holds the delivery order, with your own dates added where you need them. |
In progress | The In progress column shows what’s actively being worked on so status questions have a single answer. |
Staging and deployed | The Staging and deployed column tracks what’s been tested and released, so live-site changes don’t vanish into “done somewhere.” |
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
Web developers, agencies, and site owners handling ongoing website edits who need a single change log that survives handoffs and release days.
Questions about this project template
What should go in a website change request?
A website change request usually includes what needs changing, where it lives on the site, and any links, screenshots, or references that explain the current and expected state. The board gives you a place to log that request and keep it moving through the workflow.
How do you track website changes without email threads?
A change-request board keeps each edit as its own item, with a visible status that moves from intake to deployment. That way the latest answer sits on the board, not across a chain of replies.
How do you stop website updates from breaking the live site?
A workflow that separates triage, scheduled work, and staging or deployment makes risky requests visible before anything ships. The board’s columns make that separation explicit so checks happen before release.
Is a change request board the same as a bug tracker?
A change request board can track bugs, but it also covers content edits, layout tweaks, tracking changes, and small feature requests. The same intake and triage steps still apply because each item can affect a live site.
How do you manage lots of small website edits at once?
A board helps by turning each “small edit” into a separate tracked item, then ordering the work in a scheduled column. The workflow keeps the queue readable even when the request count grows.
Does a change request board include dates and a calendar?
A board like this carries the order and status of work rather than a calendar schedule. Add your own dates where you need them, but the columns stay focused on what stage each change is in.
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
