Resource planning without the spreadsheet
Most agencies plan capacity in a spreadsheet: one row per person, one column per week, numbers typed by whoever runs the planning meeting. It works until about ten people. CapacityKit keeps the same mental model — people × weeks — and takes over the parts a spreadsheet does badly.
Create a free workspace Download the CSV template
Where capacity spreadsheets break
- One number per cell hides who it's for. “32” in Ana's week doesn't say which projects make it up, so moving one project means editing a dozen cells by hand.
- Tentative work gets mixed in or left out. Either the pitch you might win inflates everyone's week, or it lives in someone's head until it's signed and suddenly clashes.
- Percentages need formulas per person. “Half of Dev's time” means something different for a four-day week, and the formula is copied — and broken — every quarter.
- Time off is a colour, not a number. Shading a cell doesn't reduce capacity, so overload stays invisible.
- Two people edit two copies. “Planning v3 FINAL (Grace)” is a version-conflict system without the conflict check.
The same plan, kept honest
| In the spreadsheet | In CapacityKit |
|---|---|
| A row per person with a weekly total | A person with working hours per weekday (e.g. 8, 8, 8, 8, 6) and skills |
| Typed hours per week | Allocations: person × project × date range, in hours per day or % of working hours, totalled for you |
| A “pipeline” tab | Tentative projects with a probability, shown in their own lens |
| Red cells via conditional formatting | ▲ overload markers with the number of hours and days over, in text |
| Shaded holiday cells | Unavailable blocks that reduce available hours (full day or part of a day) |
| “What if we win it?” copy of the file | One scenario with a compare view and a conflict-checked commit |
| Emailing the sheet to staff | Read-only staff links with “My next 4 weeks” and a CSV of their own rows |
Moving over takes one planning meeting
- Export your people. Put names, roles and each weekday's hours into the people template (or rename your columns to match) and save as CSV.
- Import and check the preview. CapacityKit shows every row before importing: new, skipped as a duplicate, or an error with the reason.
- Add this quarter's projects. Mark each as confirmed or tentative; import a projects CSV if you have a list.
- Re-enter the next 12 weeks as ranges. “Ana, Website rebuild, 50 % from 16 Nov to 11 Dec” is one allocation instead of four cells. Drag across the grid or use the form.
- Share staff links. Each person gets a private read-only link; nobody needs an account.
Keep your spreadsheet for the things CapacityKit doesn't do — budgets, actuals, invoicing. Export a CSV of planned person-day hours any time to feed it.
When to stay on the spreadsheet
If you schedule fewer than about ten people, change plans rarely, and one person owns the file, a spreadsheet is hard to beat. CapacityKit is for the point where several people need the same live plan and tentative work keeps colliding with confirmed work.
Plans are user-entered forecasts, not guaranteed availability.