← All field notes

A WordPress agency task board that does not hide the real work

A card in Done looks reassuring. It means little if nobody checked the client page after the change.

An agency’s task board should explain what needs attention and who is responsible. The site operation record should explain what ran and what was verified. Mixing those jobs makes both harder to trust.

Keep tasks, requests and operations distinct

A request describes what someone wants. A task tracks responsibility and the next action. An operation records work attempted against a site. One request can create several tasks, and one task can need more than one operation.

For example, “fix the mobile calendar” might include reviewing the reference, agreeing on an accordion behavior, implementing the change and checking the published page. Do not mark the whole task complete because the first code edit finished.

Link the request and the operation evidence where the workflow supports it. The teammate reviewing the task should not need to search several chats to discover what was actually deployed.

Make the next action visible

Give each active task an owner, client or site context and a concrete next step. Add a due date only when it means something. Filling every card with an arbitrary deadline makes genuine overdue work harder to spot.

Use a title that names the outcome: “Check the contact form delivery on the client’s site” is better than “website issue.” Include the affected URL and the accepted result. Keep secrets and personal customer data out of task descriptions.

Waiting for approval should be visible. It is not the same as a teammate forgetting the task. State who must decide and what the decision will authorize.

Choose list or Kanban for the job in front of you

A compact list is useful when you need to scan owners, deadlines and client names together. A Kanban board is useful when the important question is where work is waiting. Neither view should change the underlying task or trigger a new site action.

IrmaWP’s task interface offers list and board views and retains the last choice. Filter the work to the relevant client rather than treating every workspace task as your own queue. Look at due-today and overdue indicators before rearranging cards for appearance.

Limit the number of items someone has actively in progress. If a task is blocked, say why. Moving it into a different column without explaining the blocker does not make the work clearer.

Define Done before work starts

  • The requested change is present on the intended site.
  • The agreed desktop or mobile checks passed.
  • Any required approval and operation outcomes are recorded.
  • Remaining issues have an owner or an explicit deferral.
  • The client has the information needed to use the result.

For a content edit, acceptance might be checking the published text and links. For a plugin change, it may require a separate smoke test. For a report, the client needs the correct reporting period and delivered output. Choose the test for the task rather than imposing one meaningless checkbox on everything.

Keep client visibility narrower than workspace access

A client portal is not an invitation to the agency’s entire operating workspace. Decide which site information and requests the client should see. Internal investigation notes can contain details that are neither useful nor appropriate for that audience.

In IrmaWP, client portals start at Starter. Agency adds white-label controls. Appearance and access are separate concerns: a branded portal still needs the correct client scope and permissions.

Use team approvals for decisions that need them, and inspect the operation history when the task involves a site change. A task status is an organizing signal, not a technical receipt.

Start with one client’s queue. Close tasks only when their agreed evidence exists, then review what repeatedly waits for the same person. That tells you where the process needs attention more clearly than adding another column.


Have a correction or a workflow we should cover? Tell the IrmaWP team.