Peak Automations / Handoffs
One person is done.The next one doesn't know.
Between two steps there is often the longest wait, because the next person doesn't learn it's their turn. In Peak Automations “task completed”, “deal won” or “project created” triggers the next task for the right person, with a due date and a note in the Inbox. A condition narrows it to one project or task title.
Put the goal into words. Add perspectives and timing right below.
Try it with a made-up handoff.
Sample task / fictional data
What happens after “done”.
- Trigger
- Task “draft done” completed.
- Condition
- Only in the project “website relaunch” (example).
- Next step
- Task “proofread” for the editor, due in two days.
Your handoff in three answers
Who is up next?
Fill in the example with a made-up handoff. You see which details Peak needs. Nothing is saved or created.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A handoff without a dead spot.
Draft · not yet put together
- The trigger
- Still open
- The next person
- Still open
- The deadline
- Still open
From “done” to “my turn”
Trigger. Narrow. Hand off.
The order makes sure only the right tasks are passed on and nothing is created twice.
- 01Trigger
Completing is the signal.
TriggerTask “draft done” completed.
The automation starts when a task in Peak Task is completed. Each event counts once.
Task completed → run - 02Narrow
A condition filters.
ConditionOnly in the project “website relaunch” (example).
Only tasks of one project or with a certain title trigger the handoff. Everything else stops there.
Condition → yes or no - 03Hand off
The next task is created.
Next stepTask “proofread” for the editor, due in two days.
With a person, a due date and a note in the Inbox. The history shows which handoff ran when.
Sample artifact → new task
The next proof is the product
Set up the next handoff.
In Peak Automations you describe the handoff in one sentence, and Peak builds the trigger, condition and task. After the test run you switch it on; every change becomes a new version.
Start with Peak AutomationsPeak Automations / Your next step
Every handoff has a recipient.
Try the example with the handoff where something last got stuck.
See the handoff example
No work falls through the cracks.
Task “proofread” for the editor, due in two days.
Frequently asked questions
Which events trigger a handoff?
For example task completed, task blocked, project created or deal won.
Can I narrow it to one project?
Yes, with a condition. Only matching events continue.
Is there a trigger for stalled tasks?
Not yet. Inactivity triggers are planned.