The RankOps Dashboard is the answer to this scaling problem. It is a real-time operational headquarters for your agency that answers the five questions every SEO manager asks themselves every single morning: How is the current sprint tracking? Which clients need attention right now? What is my team working on today? Are our strategic goals on track? What is at risk of being missed this week? These questions used to require a morning standup meeting, four Slack channel scans, a spreadsheet review, and several individual messages to agents. The Dashboard answers all five in under 90 seconds, from a single screen, without asking anyone anything.

This guide is a complete, section-by-section reference to every element of the RankOps Dashboard — what each metric means, how it is calculated, how to read it accurately, and how to act on what it tells you. By the end of this guide, you will be able to open the Dashboard and make five or six concrete management decisions in under three minutes, before touching a single piece of client work.

Why a Dedicated Agency Dashboard Matters

The case for a purpose-built agency dashboard — rather than a combination of analytics tools, spreadsheets, and project management views — comes down to cognitive load. Every time a manager switches between tools to answer a single operational question, they absorb the context-switching cost: reopening the tool, navigating to the right view, interpreting data that was formatted for a different purpose, and mentally synthesising information from multiple sources into a coherent picture. Research on knowledge work consistently shows that these context switches are expensive — each one adding minutes to the cognitive overhead of forming a decision, and significantly increasing the probability of missing something important.

The RankOps Dashboard eliminates context switching for operational management. Every KPI, every client health signal, every sprint metric, every activity log, every upcoming deadline is in the same view, designed to be read together as a coherent operational picture. The manager who uses the Dashboard effectively thinks less about gathering information and more about acting on it — and that shift in cognitive focus is where the real productivity gain comes from.

The Architecture of the Dashboard: Three Zones

The Dashboard is organised into three horizontal zones that correspond to three different management time horizons. Understanding this architecture makes the Dashboard significantly easier to read and act on.

The top zone — the KPI strip — is your sprint-level view. It answers the question: "How is the current sprint performing right now?" The seven metrics in the KPI strip are all sprint-scoped: active tasks this sprint, overdue tasks this sprint, goals on track this sprint. This is your highest-level, most aggregated view — the numbers you look at first every morning to orient yourself.

The middle zone — the sprint ring, velocity chart, and activity feed — is your daily view. It answers the question: "What is happening right now today, and how does it compare to our historical pace?" The sprint ring shows today's completion percentage. The activity feed shows exactly what your team has done in the last few hours. The velocity chart shows whether today's pace is consistent with your historical sprint velocity.

The right zone — the client health panel and upcoming deadlines panel — is your client-level view. It answers the question: "Which individual clients or tasks need my attention today?" This is the most actionable zone: after scanning the top and middle zones for overall sprint and daily health, you use the right zone to prioritise which specific clients or tasks to address first.

The KPI strip is a row of seven metric tiles immediately below the navigation bar. These seven numbers are the first thing your eyes should go to every morning when you open RankOps. They are the pulse of your agency's sprint — aggregated, comparative, and instantly actionable. Each tile shows the metric name, the current value, and a directional indicator showing whether the metric is improving or worsening relative to the previous sprint. Learning to read these seven numbers fluently — to see the patterns they form together, not just the individual values — is one of the most valuable skills for an SEO agency manager.

Active Tasks

Active Tasks is the count of all tasks in your current sprint that are not yet in Done status — including Backlog, To Do, In Progress, and In Review tasks across all clients. This number gives you the scope of the current sprint at a glance. A sprint with 42 active tasks for a five-person team looks very different from one with 14. The Active Tasks count decreases each time a task is moved to Done, and increases each time a new task is created and assigned to the current sprint period. Watch this number's direction during the sprint: it should generally decrease as the sprint progresses. If it is increasing or flat mid-sprint, new tasks are being added faster than old ones are being completed — which is a sprint scope discipline problem that needs to be addressed before it cascades into overdue tasks.

In Progress

In Progress is the count of tasks currently in the In Progress status column — tasks that an agent has actively started working on. The healthy ratio is 50–70% of active tasks. When In Progress is very low relative to Active Tasks, it means the team is starting tasks slowly — a signal of unclear priorities, blocked tasks, or agents who are multitasking across too many clients. When In Progress is very high — above 85% of active tasks — it means tasks are piling up in In Progress without completing, which often indicates that the definition of "In Progress" is being used too loosely, or that blockers exist that are preventing completion.

Overdue

Overdue is the single most important metric on the KPI strip. Any number greater than zero requires immediate attention. Overdue tasks are tasks whose due date has passed with any status except Done. Each overdue task reduces the affected client's health score, and high-priority overdue tasks reduce it significantly. Your goal for every sprint is to maintain a zero-overdue count from Day 1 to Day 10. In practice, this requires proactive deadline management: checking the Upcoming Deadlines panel every morning and intervening before tasks become overdue, not after.

Goals On Track

Goals On Track shows what percentage of all active strategic goals across all clients are classified as On Track or Completed. The classification is automatic: a goal is On Track when its KPI progress percentage is consistent with the time elapsed since the goal started (i.e., if 50% of the goal period has passed, at least 40% KPI progress is expected). A goal is At Risk when progress is significantly behind the expected rate. A goal is Overdue when the due date has passed and the target has not been achieved.

Team Score

Team Score is the average composite performance score across all active agents. Each agent's individual score is calculated from three components: their on-time task completion rate (what percentage of their assigned tasks were completed by or before their due dates), their task done-rate (what percentage of tasks they were assigned are now Done), and their time accuracy (how closely their logged hours match their estimated hours — consistently over or under is both a problem). The Team Score aggregates these individual scores into a single number on a 0–100 scale.

Monthly MRR and At-Risk MRR

Monthly MRR shows the total monthly retainer value across all active clients. This number should only increase over time as the agency grows. Below the MRR total, the At-Risk MRR indicator appears in amber or red when any client's health score drops below 70% — it shows how much monthly revenue is at risk if that client churns as a result of poor campaign delivery. A single at-risk client with a $5,000/month retainer makes a $5,000 at-risk MRR warning appear. This financial risk signal is one of the most powerful features in RankOps because it frames client health as a revenue protection issue, not just a delivery quality issue.

Utilisation

Utilisation is the ratio of hours logged by the team this sprint to the team's total available capacity. A utilisation of 75–85% is healthy: the team is working productively without being overloaded. Below 65% suggests underutilisation — either the sprint was under-planned, agents are working inefficiently, or time logging is being skipped. Above 90% raises a burnout-risk flag: the team is at or near full capacity, with no buffer for unexpected tasks, urgent client requests, or the natural variability in task completion times.

The sprint progress ring is the most visually prominent element on the Dashboard — a large circular progress indicator that fills lockwise as tasks are completed throughout the sprint. The percentage inside the ring is the simplest possible expression of sprint health: tasks done divided by total sprint tasks, multiplied by 100. It fills green during a healthy sprint, transitions to amber when you are meaningfully behind, and turns red when sprint completion is severely behind the elapsed time.

The ring does not just show percentage — it contextualises it. The colour is not based on the absolute percentage alone, but on the percentage relative to how far through the sprint you are. A sprint that is 40% complete on Day 4 of a 10-day sprint is exactly on pace — the ring stays green. A sprint that is 40% complete on Day 8 of a 10-day sprint is severely behind — only 20% of the sprint remains, but 60% of tasks are still open. The ring turns red, signalling that intervention is required today, not tomorrow.

The Three Supporting Counters

Three numbers sit immediately below the ring: Done, In Progress, and Overdue. These three numbers provide the breakdown behind the ring percentage, and they reveal patterns that the percentage alone obscures. The most important diagnostic: when the ring percentage looks acceptable but the Overdue number is greater than zero, the sprint has a timeline problem even if the overall completion rate seems fine. Conversely, when the ring is lower than expected but Overdue is zero and In Progress is high, the team is working hard and on schedule — they just have not yet moved tasks to Done.

Read these three numbers as a group, not individually. Done tells you what is finished. In Progress tells you what is actively being worked on. Overdue tells you what is already failing. Together, they tell you whether the sprint is healthy (high Done, moderate In Progress, zero Overdue), at risk (low Done, low In Progress, growing Overdue), or severely behind (low Done, low In Progress, high Overdue — meaning the team has stopped working on tasks without completing them, which is the most serious pattern).

Sprint Velocity: Your Planning Truth Machine

Below the ring and the three counters, the Sprint Velocity chart shows a nine-sprint history of task completions as a bar chart. The current sprint's bar is highlighted in green; the eight preceding sprints are shown in violet. This chart is not just an interesting historical record — it is the single most reliable planning tool in RankOps.

Sprint velocity is the number of tasks your team actually completes in a sprint, measured consistently over time. If your team has completed 11, 13, 10, 12, 11, 14, 10, 11 tasks in the last eight sprints, their realistic, evidence-based capacity for the next sprint is 10–13 tasks. If you are planning 20 tasks for the next sprint, the velocity chart is telling you — before the sprint even begins — that you are planning a failure. You will not complete 20 tasks. You will complete 11–13 and carry 7–9 tasks forward as overdue or deferred work. The team will feel like they failed even though they performed exactly as their historical velocity predicted. The sprint was simply planned at twice their actual capacity.

Use the velocity chart to set evidence-based sprint backlogs. Plan to a number at or slightly below your rolling average velocity, leaving a 10–15% buffer for unexpected tasks and urgent client requests. A team with an average velocity of 12 tasks should plan 10–11 tasks for the next sprint, not 15 or 20. This approach results in consistently completed sprints, zero or near-zero overdue tasks, and a team that feels competent and effective rather than perpetually behind.

Sprint Velocity Trends to Watch

The real-time Activity Feed occupies the centre panel of the Dashboard and is, in many ways, its most transformative feature. It is a chronological, timestamped log of every action taken by every team member across every client — task status changes, task completions, comments added, KPI goal values updated, subtask checkboxes ticked — presented as a live feed that updates automatically as your team works, without any page refresh required.

The Activity Feed changes the fundamental relationship between a manager and their team's work. Before tools like this existed, management visibility into team activity required either disruptive interruptions (status update questions in Slack, which pull agents out of deep work), periodic standup meetings (which are expensive in terms of everyone's time and attention), or end-of-day reports (which are always retrospective and often incomplete). All of these approaches share a common failure mode: information is gathered through human intermediaries, which means it is subject to selection bias, memory lapses, and the social dynamics that cause people to report the positive and underreport the negative.

The Activity Feed has none of these failure modes. It is a direct, unmediated record of what actually happened, when it happened, and who did it. A manager who spends two minutes reviewing the Activity Feed every morning gets a more complete picture of their team's previous day than a 20-minute standup meeting would provide — and they get it without consuming anyone else's time.

How to Read the Activity Feed: Four Activity Types

Task status changes appear with an arrow icon (→) and show the task name, the agent who made the change, the old status, and the new status. The most meaningful status changes to watch for are moves to In Review (work completed — is a reviewer assigned?) and moves from In Review to Done (work approved — did it happen within a reasonable time?) or back to In Progress (work needs revision — is the feedback clear?).

Task completions appear with a checkmark icon (✓) and show the task name, the agent who completed it, the client it belongs to, and the total time logged on the task. Compare the logged time to the estimated time mentally — consistently over-estimated tasks signal that the team is under-delivering on time budgets, which may mean estimates need revisiting or the work is more complex than anticipated.

KPI updates appear with a chart icon (📈) and show the goal name, the client, the agent who made the update, the previous value, and the new value. These are the most strategically important entries in the Activity Feed — they tell you whether your KPI metrics are actually moving in the right direction. When you see a KPI update entry showing "Crawl errors: 47 → 31," the campaign is working. When you see "Organic sessions: 2,840 → 2,710" for a client where traffic growth is the primary goal, that is a warning that needs investigation today.

Comments appear with a speech bubble icon (💬) and show the task, the commenter, and the first line of the comment. When multiple comment entries appear in sequence on the same task — back-and-forth discussion — it almost always signals a blocker or an ambiguity in the task brief. Click through to the task to understand what the conversation is about and whether you need to make a decision or clarify direction.

Using the Activity Feed as a Coaching Tool

Beyond daily operational awareness, the Activity Feed is a powerful coaching tool. When you review the feed with an agent during a 1:1 meeting and work through the events chronologically — "I see you moved this task back to In Progress from In Review, what feedback came back?", "I notice you logged 5 hours on a task estimated at 1.5 hours — what made it more complex than expected?" — you build the kind of specific, evidence-based coaching conversations that actually improve performance, as opposed to vague performance reviews based on impressions rather than data.

The client health panel occupies the right side of the Dashboard and shows every active client project as a compact row with a colour-coded health bar. This is your portfolio health view — a ranked, visual representation of how every client is performing in the current sprint, from best health to worst. It is the most client-action-oriented element on the Dashboard: it does not just tell you the aggregate state of your agency, it tells you exactly which specific clients need your attention today.

The health panel is ordered automatically by health score from highest to lowest. This means the clients who need your attention most appear at the bottom of the panel — scroll to the bottom first when you are doing your morning review, not the top. The clients at the top are performing well; the ones at the bottom are the reason you need to take action before the day begins.

Understanding the Health Score Calculation

Each client's health score is a composite of three signals weighted in a specific proportion. Task completion rate contributes approximately half the score — the percentage of the client's current sprint tasks that are Done. A client with 20 sprint tasks and 16 Done has a strong task completion signal; a client with 20 tasks and 4 Done, mid-sprint, does not. Overdue task penalties contribute approximately 30% — each overdue task deducts points from the score, with the deduction weighted by task priority. A high-priority overdue task deducts significantly more than a low-priority one, because high-priority overdue tasks have a proportionally larger impact on campaign outcomes. Goal health contributes approximately 20% — goals classified as At Risk or Overdue significantly reduce the client's overall score, reflecting the fact that a client whose strategic KPI goals are failing is a fundamentally different risk level than one whose goals are on track.

Reading the Health Bar: Beyond the Number

The health bar shows both the visual fill and the percentage number, with the fill colour changing based on the score: green above 85%, amber between 60–84%, red below 60%. But the number alone is not the complete picture. The campaign stage badge next to the client name provides critical context: a health score of 74% (amber) for a client in Active Sprint is a genuine concern requiring action. The same score of 74% for a client in Onboarding is expected — they have just started, not all tasks are created yet, and the first sprint is typically lighter than subsequent ones. Always read the health score in the context of the campaign stage.

The At-Risk MRR Alert

When a client's health score drops below 70%, their MRR value appears in the KPI strip's At-Risk MRR indicator, highlighted in amber or red depending on the severity. This connects the operational health signal — a health score dropping — to a financial consequence signal — revenue potentially at risk. This connection is intentional and important. Framing client health purely as a delivery quality metric makes it easy to deprioritise. Framing it as a revenue protection metric forces the correct prioritisation: a client with a $6,000/month retainer whose health score drops to 65% represents $6,000/month of at-risk revenue, and the cost of addressing it today (an hour of management attention, a quick client call, a sprint restructure) is trivially small compared to the cost of losing the retainer.

Weekly Client Health Review Checklist

The Upcoming Deadlines panel sits at the bottom of the Dashboard and shows the next five to seven tasks ordered by urgency — tasks due today first, then tomorrow, then later this week. Each entry shows the task title, the client name, the current status, the assigned agent, the priority badge, and how many days until (or since) the due date.

The Upcoming Deadlines panel is the most action-oriented element on the Dashboard. While the KPI strip, the sprint ring, and the client health panel are all diagnostic — they tell you about the state of your agency — the Upcoming Deadlines panel is prescriptive. It tells you specifically what to do today. Every task in the panel with a today-due date should be either In Review or Done by end of day. Any today-due task that is still In Progress or To Do at 9:00 AM needs immediate attention — either the agent needs to be focused exclusively on it, or the due date needs to be extended (with the client informed if it affects a committed deliverable).

The Five-Minute Morning Deadline Review

The most effective way to use the Upcoming Deadlines panel is as the first five minutes of your management day, before opening email, Slack, or any other tool. Work through the panel top-to-bottom and ask one question about every task: is this task in the right status for where it is in the timeline?

A high-priority task due today that is In Review is healthy — the agent has completed the work and it is waiting for your approval. You can approve it in the next hour and close the loop immediately. A medium-priority task due today that is In Progress is borderline — the agent is working on it, and may complete it on time, but it is worth a quick check-in to confirm there are no blockers. A high-priority task due today that is still in To Do status at 9:00 AM is a serious problem — the agent either has not started, has a different priority, or does not realise the due date is today. Intervene immediately: assign it to an available agent, move the due date with a client notification, or clear the agent's other tasks so they can focus exclusively on this one.

Tasks due tomorrow that are still in To Do are not yet urgent, but they deserve a mental note — they should be In Progress by end of today. Tasks due this week in Backlog status should be moved to To Do if they are in the current sprint scope, or explicitly deferred to the next sprint if they are not.

Setting Due Dates That Make the Deadline Panel Work

The Upcoming Deadlines panel is only as useful as the due dates in your task data. The most common reason the panel gives misleading signals is inaccurate due dates: tasks assigned arbitrary due dates at the end of the sprint regardless of their actual complexity or timeline, or tasks with no due date at all (which never appear in the panel). Both patterns render the panel ineffective as a management tool.

Best practice: every task should have a due date that reflects the actual date by which that task must be completed, not a default "end of sprint" buffer date. A task that needs to be done by Tuesday so that a dependent task can start Wednesday should have a Tuesday due date — not a Friday one. Tasks with accurate due dates turn the Upcoming Deadlines panel into a genuine early-warning system. Tasks with arbitrary end-of-sprint due dates turn it into a Friday fire alarm — you discover everything is due at once too late to intervene effectively.

Knowing how to read the Dashboard is one thing. Knowing how to act on what you read — quickly, systematically, and with the right priorities — is what separates an agency that runs well from one that is perpetually reactive. This section provides practical, step-by-step workflows for the three most common management scenarios you will face using the Dashboard: the morning portfolio review, the mid-sprint intervention, and the end-of-sprint retrospective. Follow these workflows consistently and the Dashboard will become not just a monitoring tool but a management methodology.

The Daily Morning Dashboard Routine (5–10 minutes)

Mid-Sprint Intervention: When the Sprint Is Off Track

A sprint goes off track when the sprint ring falls significantly behind its expected completion percentage relative to the elapsed sprint days. If you are on Day 6 of a 10-day sprint and the ring shows 30% completion, you need to intervene today — not on Day 9 when it is too late. The mid-sprint intervention starts with a diagnosis: why is the sprint behind?

The most common causes, and their Dashboard signatures: Agent overload — check the Workload view. If one or two agents are at 110%+ load, they cannot complete their tasks at the expected rate. Solution: immediate task redistribution. Task complexity underestimated — the Activity Feed shows many tasks with high logged hours relative to estimates. Solution: extend due dates for the most overdue tasks and flag the scope issue to the client if it affects deliverables. Sprint over-planned — more tasks were planned than the velocity chart suggested the team could complete. Solution: move non-critical tasks to the next sprint backlog immediately, focusing the team on the highest-priority items. Blockers — the Activity Feed shows back-and-forth comments on multiple tasks, or multiple tasks have been stuck in To Do or In Progress for days without movement. Solution: identify and remove the specific blockers — a missing client deliverable, a tool access issue, an unclear brief — today.

End-of-Sprint Dashboard Retrospective

At the end of every sprint, before starting the next sprint's planning, spend 10 minutes on the Dashboard reviewing the sprint's performance data. The sprint ring should show 100% (or close) — if not, the unfinished tasks become your first retrospective question. The velocity chart now includes this sprint's bar — compare it to the previous eight sprints. Did you match your historical velocity? Exceed it? Fall short? The answer informs your next sprint's task count.

Review the Activity Feed for the full sprint period to identify patterns: which clients generated the most task activity? Which agents were most active? Were there any weeks where activity dropped significantly — suggesting a bottleneck or capacity issue? These patterns, reviewed consistently at the end of every sprint, build the institutional knowledge that makes future sprint planning progressively more accurate and realistic.

Finally, review the Goals tab in the Reports view — did any goals move significantly this sprint? Were any goals updated at all? Goals that received no KPI updates for a full sprint either had no work done toward them (a planning failure) or had work done but no KPI measurement taken (a data hygiene failure). Both need to be corrected before the next sprint begins.