> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.netnet.app/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Plan vs Actual Dashboard Preview: Estimate Accuracy ||| **Coming at the end of August 2026.** Performance Dashboards are not in Net Net yet. This article previews how the Plan vs Actual tab will work so you know what to expect when it arrives. Nothing described below is clickable in your workspace today. **In brief:** Coming August 2026, the Plan vs Actual tab will compare first plan against logged time on closed Deliverables, grouped by service type. **Applies to:** Owners and Admins, the only roles that see the Performance section. **See also:** Baselines: Why Net Net Never Rewrites the Plan explains the two plan numbers this tab reads, and Jobs Report: Look Up Any Job's Plan vs Actual History is the same comparison one Job at a time. **Plan vs Actual will answer one question: when Deliverables closed, how close were the planned service type hours to the time actually logged? It measures at the moment a Deliverable closes, and it speaks in four plain words: first plan, approved changes, updated plan, and logged time. The signal that matters most is first plan against logged time, because that is what tells you whether your original estimate was any good. It is strictly work-level: service types and closed Deliverables, never people.** This is the learning tab. Every other Dashboard is about work in flight. This one is about what finished work has to teach you about the next estimate. It is one of the five tabs previewed in [Performance Dashboards: Five Tabs Coming August 2026](https://help.netnet.app/en-us/article/performance-dashboards-five-tabs-coming-august-2026-1qrsbq9/). # The four words The tab avoids jargon on purpose, so you can read the numbers without a glossary. **First plan.** What was planned originally, frozen when the Job activated. **Approved changes.** Scope added since, through applied Change Orders. **Updated plan.** First plan plus approved changes. **Logged time.** What was actually logged against the work. These are the same two baselines described in [Baselines: Why Net Net Never Rewrites the Plan](https://help.netnet.app/en-us/article/baselines-why-net-net-never-rewrites-the-plan-1ep4h4s/), stated in the plainest possible language. First plan is Original Plan. Updated plan is Current Plan. # Why first plan versus logged time is the primary signal Because it is the only comparison a Change Order cannot rescue. If Plan vs Actual led with updated plan against logged time, a Job that was badly underestimated and then rescued with a large Change Order would read as perfectly accurate. The estimate would look good precisely because it was wrong enough to require fixing. So the tab keeps them separate. First plan against logged time is the estimating signal, shown first. Approved changes are shown alongside as scope growth in their own right, never folded in silently. Updated plan against logged time is a secondary read on delivery: how the team did against what they were actually asked to deliver in the end. || A large gap between first plan and updated plan is not automatically a problem. It means scope grew, which is a normal part of client work. What matters is whether that growth was recorded as a [Change Order](https://help.netnet.app/en-us/article/change-orders-how-to-add-scope-to-a-locked-job-plan-1gplwsw/) or quietly absorbed. Net Net can only show you the growth it was told about. # It measures when a Deliverable closes Not while work is in flight, and not at the Job level. The measurement moment is the point a Deliverable closes. At that moment Net Net compares the planned hours for each service type against the time logged against it. That is why an in-progress Job contributes nothing here: there is no final number to compare against yet. Everything on this tab is grouped by [service type](https://help.netnet.app/en-us/article/service-types-and-service-groups-what-each-one-does-y89pui/), because that is where estimating patterns actually live. Discovery consistently running over is a useful thing to know. "This Job ran over" much less so. # The one tab with a trend Plan vs Actual will be the only Dashboard in the first release allowed to show direction over time. It compares the last three months against the three before, weighted by planned hours, and shows both how far off you were and which way it moved. The other tabs go without trend arrows because direction on live work needs a nightly health snapshot that Net Net does not store yet. This tab is the exception because closed work already carries everything the calculation needs: each closed Deliverable has its plan, its logged time, and its close date. Weighting by planned hours matters. Without it, a two-hour Deliverable that ran 100% over would move the trend as much as an eighty-hour one that landed on plan. # Closed Deliverables to review Below the trend will be a list of the closed Deliverables where planned and logged were farthest apart, in either direction. It will be read-only. This is a learning surface, not a correction surface. Nothing on this tab rewrites a plan, and nothing here can change a closed Deliverable's history, which is the same principle that governs Baselines everywhere in Net Net. | Both directions are worth reading. Consistently running well under plan on a service type is not a win; it usually means that work is being overestimated, which quietly costs you capacity you could have sold or scheduled elsewhere. # What Plan vs Actual will not do **Never people.** It reports service types and closed Deliverables. It will not attribute an overrun to whoever did the work, because planned hours are usually set by whoever planned the Job. **Never task-level.** The unit is the closed Deliverable. **No money.** Plan and actual are both in hours. **Not an estimate builder.** This tab was previously called Estimates and was renamed so it would never be mistaken for one. It does not create an estimate, quote a client, or price anything. It reports on estimates you already made, after the work is done. Deliverable Type trends are noted as a later addition, once Deliverables are labeled consistently enough across workspaces for the comparison to be fair. # Frequently Asked Questions ###### Are Performance Dashboards available today? **No. They are scheduled to arrive at the end of August 2026.** Until then, [Jobs Report](https://help.netnet.app/en-us/article/jobs-report-look-up-any-jobs-plan-vs-actual-history-ip3kjc/) is where you can see Original Plan and Current Plan side by side for every Job you have run, which is the same underlying comparison one Job at a time. ###### Why does it lead with first plan instead of updated plan? **Because a Change Order can make a bad estimate look good.** If the tab compared logged time against the updated plan, a Job that was underestimated and then corrected with a large Change Order would read as accurate. First plan against logged time is the only comparison that cannot be rescued after the fact. ###### When exactly does a Deliverable get measured? **When it closes.** At that moment Net Net compares the planned hours for each service type against the time logged. Work still in flight does not appear on this tab at all. ###### Why is this the only Dashboard with a trend? **Because closed work already contains everything the trend needs.** Every closed Deliverable carries its plan, its logged time, and its close date. Trends on live work would require a nightly snapshot of workspace health, which Net Net does not store yet. ###### Will I be able to see which person runs over on estimates? **No, and that is deliberate.** Planned hours are usually set by whoever planned the Job rather than by the person doing the work, so attributing an overrun to an individual would measure the wrong thing. This tab reports service types and closed Deliverables only. ###### Can I fix a closed Deliverable from this screen? **No. The review list is read-only.** Net Net never rewrites history on closed work. The value of keeping the original number next to what actually happened is exactly that it cannot be quietly corrected later. # Related articles The comparison this tab will make in bulk is already available one Job at a time. [Reading the Job Performance Tab: Plan, Actual, Drift](https://help.netnet.app/en-us/article/reading-the-job-performance-tab-plan-actual-drift-1hi6cta/) shows planned against logged inside a single Job, and [Baselines: Why Net Net Never Rewrites the Plan](https://help.netnet.app/en-us/article/baselines-why-net-net-never-rewrites-the-plan-1ep4h4s/) explains why the first plan is preserved rather than overwritten. [Activating a Job: What Happens When the Plan Locks](https://help.netnet.app/en-us/article/activating-a-job-what-happens-when-the-plan-locks-15b8p4o/) covers the moment that first plan gets frozen. For the measurement underneath all of it, [How Performance Works: Effort, Timeline, and Drift](https://help.netnet.app/en-us/article/how-performance-works-effort-timeline-and-drift-ikzayn/) is the place to start.