Skip to content
Peak Atlas

Planned This capability is specified but not built yet. The page shows the plan with fictional examples. Available today: Today brief, Top 3, decisions with memory, goals, roadmap and scenarios.

Peak Command · business autopilot · planned

Routine, prepared.
Only what a person approves is carried out.

Planned: the autopilot is meant to prepare recurring leadership work, such as reminders for reviews due or drafts of tasks. Nothing is meant to run without a person. Today Peak Command carries out nothing on its own.

See permissions and approvals

Planned feature · example mapping · nothing runs

Peak CommandThe signal
Peak Work (draft, planned)The draft for approval
Peak Work (draft, planned) · Example mapping
One mapping in detail
01 / Peak CommandReview due
02 / Fictional test valueExample: check the pricing decision
03 / Peak Work (draft, planned)Task draft

A readable path as an example. No transfer.

View all 5 mappings
Example mapping with fictional values.
Peak CommandPlace in Peak Work (draft, planned)
Review dueTask draft
ReasonDescription
SourceReference
OwnerAssignee
ApprovalStatus
Example mapping
No transfer
This connection is planned. Nothing is connected or transferred on this page.
One concrete target

How it is meant to work.

Peak Work (draft, planned)Place in Peak CommandPlanned

The mapping shows a planned connection. It is an example, not a live connection.

02 / How it is meant to work

Detect. Prepare. Approve.

Every step with an effect outside or on data is meant to need approval by a person with the right permissions.

  1. 01 / The signal

    Detect

    Planned: a signal, such as a decision review that has been due for two weeks.

    Something is due.ReviewBlockerCheck-in
  2. 02 / The draft

    Prepare

    Planned: a draft, for example a task in Peak Work, with reason and source.

    Prepared, not done.ReasonSourceTarget product
  3. 03 / The approval

    Approve

    A person with the needed permissions checks it and approves or discards it. Without approval nothing happens.

    A person decides.CheckApproveDiscard

Trust needs clarity

Planned means: not here yet.

01 / The existing evidence

This connection is planned

The autopilot is planned. Today Peak Command prepares nothing on its own and carries out nothing.

Source / Peak CommandEXAMPLE
Peak CommandMappingPeak Work (draft, planned)
Mapping
Example
Arrival
Planned

02 / Your check

Built today

Today Peak Command writes only when you trigger it, and always through the owning product: a decision in Peak Log, an initiative in Peak Year, a task in Peak Work.

Account
Not connected here
Status
Not available yet

03 / The clear limit

No date promised

We do not say here when it arrives. We name it once it is provably available.

  • Adapter
  • Webhook
  • Embed
  • Planned

The next step

See how permissions work today.

The page on permissions and approvals shows how Peak Command takes over the permissions of Peak One.

See permissions and approvals
Your mappingPLANNED
Peak Command→Peak Work (draft, planned)
Review due → Task draft

Until then you use what Peak Command already reads today.

Frequently asked questions

Can I use the autopilot yet?

No. It is planned and no date is promised. Today Peak Command shows the daily brief, top 3, decisions, goals, initiatives and scenarios from the Peak products.

Is the autopilot meant to do anything without me?

No. The plan is that it prepares drafts. Every action is meant to need approval by a person with the right permissions.

What does Peak Command carry out itself today?

Nothing on its own. It writes only when you trigger it, and always through the owning product.