Many leadership meetings run on a planning spreadsheet that someone updates every week. Peak Command reads the same questions straight from the Peak products. Here both sides stand next to each other, including where a spreadsheet is the better choice.
What decides it for you?
Who keeps the numbers up to date?
Same questions. Two kinds of tool. No winner decided in advance.
01 / The basis for deciding
Pick a focus. Each row asks Peak Command and a typical planning spreadsheet the same question. The spreadsheet side is described in general; you check your own file yourself.
6 dimensions · Same standard for both options
Command reads goals, initiatives, tasks and capacity where they are maintained and shows how fresh each source is.
Who keeps the numbers up to date?
Typically someone copies or types in the values. The state is as fresh as the last update.
Who keeps the numbers up to date?
| The criterion | Peak Command | A spreadsheet |
|---|---|---|
| Current numbersWho keeps the numbers up to date? | Peak CommandRead from the source products Command reads goals, initiatives, tasks and capacity where they are maintained and shows how fresh each source is. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced Typically someone copies or types in the values. The state is as fresh as the last update. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Free modellingCan I build my own formulas and models? | Peak CommandNot what Command is for Command computes fixed, named rules and scenarios. It isn't a free formula builder. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced For your own models, formulas and experiments a spreadsheet is usually the better choice here. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Who sees whatDoes each person see only what they may see? | Peak CommandPermissions inherited from Peak One Members see in Command only what they may see in the source product. Writes go through the owning product. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced Whoever can open the file often sees everything in it. Finer permissions depend on the tool. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Decisions and reasonsCan you find later what was decided and why? | Peak CommandDecision memory in Peak Log Decisions, their reasons and their outcome are searchable. Reviews that are due show up on their own. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced Reasons sit in a column, a tab or a comment, as long as someone remembers. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Outside Peak OneWhat about numbers that aren't in Peak One? | Peak CommandReads Peak One only Areas not connected, such as Growth or Customer, show in Command as “not available”, never as zero. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced For data outside Peak One or a one-off calculation a spreadsheet is often the better choice. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Review rhythmWhat is on the table in the weekly, monthly and quarterly meeting? | Peak CommandAn agenda per rhythm Command puts together an agenda of goals, decisions and tensions for the week, month and quarter. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A spreadsheetNot yet evidenced A spreadsheet can hold any agenda, if someone fills it in before the meeting. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
Source code is evidence of implementation. It does not replace a current live test.
This page describes Peak Command only as it is built in Peak One today. It describes spreadsheets as a category, not a product, and says what a spreadsheet is better suited for.
Peak Command per its register. The tool category described in general only.
The same question, the same period, the same data for both tools.
For Peak Command only what the register lists as built counts. Planned features are not here.
For free modelling, your own formulas and one-off calculations a spreadsheet is usually the better choice. The table says so.
02 / From feature to moment
A check turns a list into a concrete trial. Pick the first test for both tools.
The same question in both tools. The protocol prepares the test; it doesn't run it.
Prepare the next weekly meeting once with your spreadsheet and once in Command, and time it.
You know how much upkeep each meeting needs.
Peak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace.
Source checked:
Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register)Task selected. No test run.
Open the interactive demo03 / Before the next step
A table doesn't replace a test, this one included. The interactive demo shows Peak Command at the fictional Nordwind Studio: goals, tensions, a scenario. None of it reaches Peak One.
Switching is a separate decision. Prepare it and keep the open evidence in view.
The demo runs locally in your browser and changes nothing.
For free calculations a spreadsheet often stays right. For the running state of goals, plan and decisions, try Peak Command in Peak One.
Sign in to Peak One and open CommandPeak Command statements per the PCMD register (as of 2026-10-27). The tool category is described in general, with no statement about a specific product.
Often the answer is both, for different jobs.
For free modelling, your own formulas and one-off calculations a spreadsheet often stays the better choice. Command provides the running state of goals, plan and decisions from the source products.
Permissions come from Peak One. Each person sees in Command only what they may see in the source product.
No. A scenario computes with Peak Finance and Peak Year and changes nothing until you apply it in the owning product.
No. The page describes spreadsheets as a category, with no statement about a specific product. Individual tools differ a lot; check your own yourself.
