Hiring Plan Timing Analysis in Confluence

Your hiring plan doc explains the “why.” The numbers behind it live somewhere else entirely.

A hiring plan is two documents pretending to be one: the narrative (why this role, why now, what it unblocks) and the math, salary run-rate and how it changes depending on when the role actually starts. The narrative usually lives in Confluence, where the rest of the team’s planning happens. The math usually doesn’t, because seeing how run-rate impact shifts across twelve possible start months needs real calculation, and that’s not something a Confluence page can do on its own.

So the run-rate math ends up in a spreadsheet the Team Lead maintains separately, testing a month or two by hand and hoping those are the ones anyone actually asks about. Every time Finance or the Head of PMO wants a different month, that means going back to the spreadsheet, recalculating, and pasting a new screenshot into the doc it was supposed to live next to in the first place.

Excel-like Tables for Confluence lets the full picture live in the same page as the narrative.

What this looks like in practice

A Design Lead is planning to add a Senior Product Designer role and needs to know how the run-rate impact changes depending on when the role starts. January costs more this year than October does, and the Lead wants the full picture before recommending a date, not just one or two months checked by hand.

The hiring narrative: why this role, what it unblocks, is already written up in a Confluence planning page. The run-rate math lives in a separate spreadsheet, where the Lead tests a couple of likely-looking months manually. When the Head of PMO asks about a month that wasn’t tested, the Lead has to reopen the spreadsheet, recalculate, and send a new screenshot.

What breaks without a way to see every option at once

• Testing a specific start month means manually recalculating in a spreadsheet, one month at a time.
• Seeing the full-year picture across all twelve possible start months means building twelve separate calculations by hand, most Leads just pick two or three to show instead.
• Finance or the Head of PMO can’t check the live model themselves; they only see whichever months happened to get tested.
• When someone asks “what’s the latest we can start and still stay under budget,” there’s no direct way to answer, just more manual testing.
• The reasoning behind the plan and the numbers behind it live in two different places, so reviewing it means jumping between a doc and a file that may not even be shared with them.

Every additional stakeholder who wants to see a different month adds another round of manual recalculation.

How Excel-like Tables for Confluence fixes this

Excel-like Tables puts a Data Table directly next to the hiring narrative: one row per possible start month, one column for the run-rate impact, generated in a single step instead of tested by hand one month at a time. The full picture (all twelve months) is there at once, not just the two someone had time to check.

When the question flips, what’s the latest month that still keeps this year’s impact under $100,000, Goal Seek solves for that start month directly, instead of scanning the table for the closest row.

Key capabilities for this scenario:

• Data Table → generate the run-rate impact across every possible start month in one step, not just the two or three someone had time to test by hand
• Goal Seek → solve backward for the latest start month that keeps this year’s impact under a set budget ceiling
• Excel-like editing interface → build the run-rate formula directly in the page, with the formulas and shortcuts already familiar from Excel
• Templates and reusable sheets → reuse a standard hiring-plan layout each quarter instead of rebuilding it from scratch
• Rich formatting and styling → color-code roles by status (approved, pending, hypothetical) so the plan is readable at a glance
• Version-free real-time collaboration → the Team Lead, Finance, and HR view and edit the same live plan; no spreadsheet to request access to

What changes for your team

Before, a budget check-in meant testing two or three specific months by hand and hoping the one someone asked about was among them. Now the Data Table already has every month’s impact calculated, and Goal Seek answers “what’s the latest we can start” directly instead of more manual testing.

When someone asks about a month that wasn’t already checked, the Team Lead points to a row instead of reopening a spreadsheet.

Built for the people running this

Team Lead / Department Head — You’re the one who has to defend both the reasoning and the math behind a hiring plan, often in the same conversation. Excel-like Tables keeps them on the same page, literally, and gives you every month’s impact at once instead of whichever two you had time to check.

HR / People Ops — You need visibility into hiring timing and headcount plans across teams without chasing down each Lead’s personal spreadsheet. A shared, formatted plan inside Confluence gives you that without extra file requests.

Head of PMO / Director of Operations — You’re accountable for how hiring plans roll up into overall budget and headcount visibility. Cross-page dashboards let you see live numbers from multiple departments’ plans in one place, instead of collecting screenshots.

Want to see it built step by step?

Watch the What-If Analysis walkthrough video for a live look at using Goal Seek and Data Table like this.