$100 Website Offer

Get your personal website + domain for just $100.

Limited Time Offer!

Claim Your Website Now

How to Keep a Done List for a CMS Website Build

Few website projects collapse from a single big error. Most simply wander off course. A page gets rebuilt because nobody remembers it was approved, a plugin is configured twice by two people, a redirect is tested on Monday and untested again on Thursday. The cure is dull and effective: keep a done list for the build. This tutorial shows how to set one up for a CMS project, step by step, so that every finished item is visible and nothing is redone.

Step 1: Pick a single place to store it

Settle on the storage spot before any task begins. A shared spreadsheet works. So does a page in your project tool or a plain document stored in the project folder. The principle is plain: one place, editable by the whole team, reachable in two clicks. If the list is split between a chat thread and someone’s notes, it will be wrong within a week.

Step 2: Define what “done” means for a web task

Agree a short, written definition. For a content management build, a reasonable standard has four parts: the work is complete in the staging site, it has been checked on a phone and a desktop browser, the person who requested it has accepted it, and any settings changed are noted. An item missing any of those four stays off the list. This keeps the record honest and prevents the familiar situation where something is “basically done” for three weeks.

Step 3: Set up the columns

Keep the structure lean. Five columns are enough for most projects:

  1. Date completed.
  2. Item. A clear object and verb, such as “Contact form connected to mailbox”.
  3. Area. Content, design, plugin, hosting, search visibility, security.
  4. Checked by. A role, not a person’s name.
  5. Where to find it. A staging link, a settings screen or a document reference.

Step 4: Seed it with work already finished

Do not start with a blank sheet if the project is already underway. Spend half an hour listing what exists: the theme installed, the domain pointed, the SSL certificate active, the main menu built, the first pages drafted. A seeded list immediately shows real progress and often reveals unfinished corners. If you are earlier in the process, our earlier step-by-step on scoping a business site ahead of the first line of code will help you decide which items deserve a line from the very start.

Step 5: Group entries by site area

After a few weeks the list gets long. Add a simple filter or a set of headings: structure, content, technical, search, launch. Grouping by area lets you answer practical questions quickly. Are the technical foundations all finished? Which pages are complete and which remain? Does anything in the search area need a second look before launch? When a stakeholder asks for a status update, you can answer in a minute without chasing anyone.

For the structure group in particular, it helps to check against a standard page inventory. A reference list of the pages most company sites carry is a handy cross-check: each page you have finished gets its own line, and each page not yet on the list is a visible gap.

Step 6: Record settings changes as they happen

CMS projects accumulate small configuration decisions: a permalink structure, a caching option, a role permission, an image size. These are the items people forget and later argue about. Log each one the day it changes, with the old and new value where possible. When something breaks after an update, the list becomes your first diagnostic tool.

Step 6b: Capture content work separately from technical work

Writers, editors and developers finish things at different speeds, and a single stream of entries hides that. Tag each line as content or technical. When the launch date approaches, a quick count of finished lines in each tag shows where effort is still needed. A site with a polished theme and half-written pages looks very different on the list from one with finished copy and an unconfigured contact form, and the difference tells you where to send people next.

Step 7: Add a weekly review

Once a week, read the list from top to bottom with the team for ten minutes. Confirm that every entry still meets the definition of done. Move anything that regressed back to the pending list. Note any area with few entries, since that usually points to work nobody has started. Use the same session to prune duplicates and sharpen any fuzzy wording.

Step 8: Use the list at handover and launch

When the project nears launch, the done list turns into a checklist for sign-off. The client or manager can see exactly what has been built, what has been checked and where it lives. After launch, the same document becomes the starting point for maintenance, because the next person inherits a clear history instead of guesses.

One practical tip for the launch stage: print or export the list and walk through it with the person approving the site. Reading entries aloud exposes anything that was logged too early, and the approver gains confidence from seeing evidence rather than hearing reassurance. Keep a copy with the project files so a future administrator can see why each setting looks the way it does.

A note on keeping non-web tasks in the same list

Real projects include tasks that never touch the CMS: a photo shoot, a legal review of text, a trip to a client’s premises. If a site visit requires rented transport, you can note the arrangement as finished once it is settled. In one example, a small team planning travel across Indonesia might read about MotoShare, a vehicle rental portal written in Bahasa Indonesia that talks about local rental partners, then log the final booking as a done item. The entry matters, not the research that led to it.

Common pitfalls

  • Logging items before acceptance. Wait until the requester signs off.
  • Letting entries go vague. “Fixed header” says nothing; “Header logo link now points to the home page” does.
  • Skipping content tasks. Copy and images are part of the build and belong on the list.
  • Relying on one person. Anyone who finishes a task should log it.

Putting it together

To recap the process: pick one location, define done, set up five columns, seed it with existing work, group by area, record configuration changes, review weekly, and reuse it at launch and afterwards. None of these steps is complicated. Together they give a CMS project a clear memory, which is exactly what most web builds lack. Begin with step one today; a week from now the sheet will already be worth opening.

Related Posts

Website Teardown Checklist: Audit a Finished Business Site First

A practical five-part checklist for taking apart a finished business website, structure, content, navigation and technical clues, before you plan your own CMS build.

Read More

Eight Plain-Word Fixes for Clearer Website Copy and CMS Labels

Menus, buttons, error messages and admin fields often use insider words. Eight practical fixes, each with a before and after, to make your site easier to read.

Read More

Page Cap, Plugin Cap or Palette Cap: Which Site Limit Fits?

A friendly comparison of three self-imposed limits for CMS builds, covering pages, plugins and palettes, with when each one helps and where it hurts.

Read More

Near Misses as a Career Skill for Web Developers

Why handling a caught mistake well is a learnable skill for CMS and web developers, and how to show it in a portfolio or interview.

Read More

Five Website Clean-Up Myths That Keep Your CMS Cluttered

Five comfortable beliefs about website housekeeping, and the simpler habit that replaces them: trim drafts, plugins and media files as you work.

Read More

Why Web Projects Slip: Diagnosing the Unchosen Trade-Off

Late, over budget and still rough? A diagnosis-first look at web projects that never decided whether speed, cost or quality would give, plus the written fix.

Read More
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x