Client disagreements rarely start with bad intent. They start with a gap: the client thought something was included and you did not, or they could not tell what was happening and assumed nothing was. A shared board closes many of those gaps, because it makes the work, the status and the agreement visible to both sides.
Where conflict usually comes from
- Unclear scope. “A new homepage” means different things to each person.
- Silence. No updates feels like no progress, even when work is happening.
- Moving targets. New requests arrive and nothing is traded off.
- Lost decisions. Approval given in a call is later disputed.
- Surprise delays. Waiting on the client is not visible, so it looks like you are late.
Give the client a view, not the keys
KanbanWP has a client role on a board. Clients can view and comment, but cannot move or rearrange cards. You decide which boards and tasks they see. Tasks and comments marked internal stay hidden from them, so your private notes remain private. See permissions and roles and the client portal.
That gives you a transparent space for agreed work and a private space for your own thinking.
A board layout that prevents arguments
Use a Client board (there is a Client template) and adapt the stages. A useful set:
- Requested
- Agreed scope
- In progress
- Waiting on client
- Ready for approval
- Approved
Two stages do most of the heavy lifting. “Waiting on client” shows whose turn it is, so delays are not silently blamed on you. “Ready for approval” gives the client a clear moment to say yes, and their comment on the card becomes the record.
Practices that reduce friction
Write the scope on the card
Describe each deliverable in the description, including what is not included. Use a checklist for acceptance criteria, such as “Works on mobile” or “Three revision rounds included.”
Handle new requests deliberately
When the client adds something, put it in Requested, not Agreed scope. Then discuss it: what does it cost, and what does it replace? The board makes the trade-off visible instead of absorbing the request quietly.
Capture decisions in comments
When a decision is made on a call, post it as a comment on the card: “Agreed on call: logo stays as is, footer links change.” Client comments sit alongside it. See task comments.
Use due dates honestly
Set dates on cards and update them if they change, with a comment saying why. Late is forgivable. Late without explanation is not.
Keep internal work internal
Mark your own planning tasks and frank notes as internal. Clients see a clean board focused on deliverables.
A checklist for starting a client project
- Board created from the Client template
- Client added with the client role
- Deliverables written as cards with acceptance criteria
- Out-of-scope items listed
- Ground rules agreed: where requests go, how often you update, who approves
- First review date set
When conflict still happens
Sometimes it does. Having a record helps you stay factual: you can point to the card, the date it was agreed, and the comments since. Start from what was written, acknowledge anything that was unclear, and propose a fix such as a new card with a new date. Moving from argument to adjusting the board usually lowers the temperature.
You can set up a client board in minutes. Follow your first board, then add the client from the board’s members. For a broader look at agency workflows, see what isn’t on the board on agreeing rules before you begin.