/projects//tasks/ ).
1. Connecting Tasks Directly to SEO Impact
Generic project management tools lack context. In SEO Runway, when an audit uncovers 40 broken canonical tags, you click 'Create Task' directly from the audit drawer. The resulting Kanban card links to the exact URLs, keeping developers and client stakeholders completely aligned.
LIVE PLATFORM SCREEN & TELEMETRY
SEO Runway Tasks Kanban Board & Client Approvals — Active Workspace
Below is the exact production screen with live parameters and dummy data illustrating the diagnostic findings and remediation buttons.
2. Managing Approvals in SEO Runway
In SEO Runway → Tasks, move completed content drafts or ad copy to Client Approval. The client receives an email notification with a secure review link to sign off digitally.
Target System: SEO Runway AGENCY Engine
Execution Frequency: Automated Background Queue (UTC Sync)
Tested across enterprise datasets with zero rate limiting or data loss.
3. Why Approvals Stall Agency Delivery
Agency work often waits on someone: a client approving a blog brief, a manager reviewing a technical fix, a designer waiting for copy. When approvals happen in email threads and chat messages, nobody can see where work is stuck. Deadlines slip, clients ask for updates the team cannot give, and completed work sits unpublished while results wait.
A Kanban board makes the flow of work visible. Every deliverable is a card, every stage is a column, and approval becomes an explicit step rather than an invisible delay. When the board is connected to the SEO goals each task supports, it also helps agencies prioritise work that moves results, not just work that is easy to finish.
4. Designing Columns for Agency Workflows
Columns should reflect how work really flows, including review and approval stages. A common agency board looks like this:
- Backlog: agreed work not yet scheduled.
- To do: scheduled for the current period.
- In progress: actively being worked on.
- Internal review: waiting for a senior team member to check quality.
- Client approval: waiting for the client to approve.
- Ready to publish: approved and waiting to go live.
- Done: published or delivered.
Keep columns to a manageable number. Too many stages make the board hard to read; too few hide where work waits.
5. What Every Card Should Contain
A card should give anyone, including the client, enough context to act without asking questions.
- Clear title: "Rewrite /services/boiler-repair page for 'boiler repair leeds'" is better than "Page update".
- Goal link: the SEO or business goal the task supports, such as "increase organic leads for boiler repair".
- Owner: one person responsible for moving the card forward.
- Due date and, for approval stages, an approval deadline.
- Deliverable: a link to the draft, design or document.
- Acceptance criteria: what "done" means, such as word count, target keyword and internal links.
- Comments: feedback and decisions recorded on the card, not in separate emails.
- Labels: channel, priority and client, for filtering.
6. Connecting Tasks to SEO Impact
Linking tasks to goals turns the board from a to-do list into a strategy tool.
- Tag tasks by goal or keyword cluster, so the team can see how much work supports each priority.
- Record expected impact: a simple high, medium or low estimate helps sequencing.
- Track outcomes after completion: note the publish date and review rankings, traffic or conversions for the affected page a few weeks later.
- Show impact in client reports: "Five service pages rewritten in March; organic leads to those pages up 24% in April" connects delivery to results.
- Prioritise by impact and effort: high-impact, low-effort tasks go first.
7. Running Client Approvals on the Board
- Move the card to "Client approval" when the deliverable is ready, with a link to the draft and a short summary of what needs approving.
- Notify the client automatically or with a short message pointing to the card.
- Set an approval deadline: for example, three business days, agreed during onboarding.
- Collect feedback on the card: the client comments directly, so every decision is recorded.
- Return or approve: changes requested move the card back to "In progress"; approval moves it to "Ready to publish".
- Remind before deadlines: send a reminder a day before the approval deadline.
- Escalate overdue approvals: if a card stays in client approval past the deadline, the account manager raises it in the next client call.
Give clients access only to the columns and cards relevant to them, so they see their approvals without internal discussion.
8. Limiting Work in Progress
Kanban's core principle is limiting work in progress. When too many cards sit in "In progress" or "Internal review", everything slows down.
- Set limits per column, such as no more than three cards in progress per specialist.
- Finish before starting: help move cards through review before starting new work.
- Watch bottlenecks: if "Internal review" is always full, the reviewer needs support or the review process needs simplifying.
- Measure cycle time: track how long cards take from "To do" to "Done", and which columns hold them longest.
9. Board Structure for Multiple Clients
- One board per client: keeps each client's work separate and simplifies client access.
- Agency overview: a combined view across clients helps managers see overall workload and overdue approvals.
- Templates: start each new client board from a template with standard columns, labels and recurring tasks.
- Recurring tasks: monthly reports, technical checks and content publishing can be created automatically each period.
- Consistent labels across clients, so filters and reports work agency-wide.
10. Weekly Board Review
A short weekly review keeps the board accurate and work moving.
- Review cards past their due date and agree new dates or actions.
- Check the client approval column for overdue approvals.
- Identify bottlenecks in internal review or other columns.
- Pull the next priority cards from the backlog into "To do".
- Archive completed cards after recording outcomes.
Fifteen to thirty minutes per week is usually enough for a team managing several clients.
11. Metrics That Show Delivery Health
- Cycle time: average days from start to done, by task type.
- Approval time: average days cards spend in client approval.
- On-time delivery rate: the share of cards completed by their due date.
- Revision rate: how often cards return from review or approval for changes.
- Throughput: cards completed per week or month.
- Work linked to goals: the share of completed tasks tagged to a client goal.
Share approval time with clients. When they see that their approval delays add a week to every deliverable, most become faster reviewers.
12. Common Mistakes
- Vague card titles that require opening the card to understand.
- No approval column, so waiting time is invisible.
- Feedback in email instead of on the card.
- Several owners per card, so nobody feels responsible.
- Boards nobody updates, which quickly become inaccurate and ignored.
- Too many columns, making the board hard to read.
- No link to goals, so busy work crowds out impactful work.
13. A Worked Example
An SEO agency managed content and technical work for 20 clients through spreadsheets and email. Approvals for blog briefs often took two to three weeks, and account managers spent hours chasing updates. The agency moved each client to a Kanban board with internal review and client approval columns, gave clients access to their approval column, and agreed a three-day approval window in each contract. Cards were tagged to keyword clusters and goals. Within two months, average approval time fell to under five days, the team stopped losing track of deliverables, and monthly reports began showing which completed tasks drove traffic gains.
14. Automations That Save Time
- Notifications: alert the client when a card enters client approval, and the owner when it returns with feedback.
- Due date reminders for owners and approvers.
- Recurring cards for monthly and quarterly tasks.
- Status-based assignment: moving a card to internal review automatically assigns the reviewer.
- Completion logging: moving a card to done records the completion date for impact tracking.
15. Integrating the Board with Reporting
Completed cards are evidence of work delivered. Pull them into monthly client reports as a "work completed" section, grouped by goal, with links to the published pages. Pair each group with the relevant results, so clients see a direct line from the agency's effort to their outcomes.
16. Getting Clients Comfortable with the Board
Clients used to email may resist a new tool. Ease the transition.
- Walk them through it: a ten-minute screen share during onboarding showing only the approval column and how to comment or approve.
- Keep their view simple: limit what clients see to the cards that need their attention and the progress of their work.
- Send direct links: notifications should link straight to the card that needs review, so clients never have to search.
- Accept email at first, then move it: if a client replies by email, copy the feedback onto the card and reply with the link, gently reinforcing the new habit.
- Show the benefit: point out that the board lets them see progress at any time without waiting for a status update.
Most clients adapt within a month, especially when they see that approvals on the board lead to faster delivery.
17. Handling Urgent and Unplanned Work
Agencies regularly face urgent requests: a ranking drop, a broken page, a launch brought forward. Add an "Expedite" label or swimlane at the top of the board for genuine emergencies, limited to one or two cards at a time. Define what qualifies, such as site outages or issues affecting revenue, so the expedite lane does not fill with ordinary requests. When urgent work arrives, make the trade-off visible: something else moves back, and the client sees which deliverable is delayed as a result. This keeps priorities honest and protects planned work from constant interruption.
18. Keeping the Board Trustworthy
A board is only useful if it reflects reality. Ask every team member to update their cards before the end of each day, and treat out-of-date cards as a process problem rather than an individual failing. When clients can trust that the board is accurate, status update emails become unnecessary.
19. Kanban Approval Checklist
- Create columns for backlog, to do, in progress, internal review, client approval, ready to publish and done.
- Give every card a clear title, one owner, a due date, a deliverable link and acceptance criteria.
- Tag cards to client goals or keyword clusters.
- Agree approval deadlines and give clients access to their approval column.
- Record all feedback on cards.
- Set work-in-progress limits and watch for bottlenecks.
- Review the board weekly.
- Track cycle time, approval time and outcomes of completed work.
20. Your Next Step
Pick one client and move their current deliverables onto a Kanban board this week, with a dedicated client approval column. Invite the client to review cards there instead of by email, and measure how long approvals take over the next month compared with the previous month.
Want the complete procedural runbook?
Visit our comprehensive step-by-step Knowledge Base for interactive screen maps, configuration parameters, and adjacent module workflows.
Open Knowledge Base Hub →

Bookmarked. We run this exact setup in SEO Runway across our agency client retainers. As a Search Intelligence Lead, this provides exactly the architectural depth we look for.