Skip to main content
Use Console’s Planning section to state an intended outcome, organize delivery work, and expose impediments. Planning records and workflow execution answer different questions: a completed run records execution, while a goal records the business result you intended to achieve.

What you can do

Choose the right planning surface

These pages are under Planning, rather than the older Workforce navigation. Use the linked guides for their current controls and access requirements.

Establish a plan

  1. Define the intended result and its measure in Goals. Use a concrete metric and target rather than treating activity volume as success.
  2. Create or choose the roadmap and workstreams that organize the delivery theme and milestones.
  3. Create a project for the bounded body of work. Set its customer attribution deliberately; attribution does not grant access.
  4. Assign tasks to people or agents with clear ownership and supported status transitions.
  5. Record blockers with enough context for the responsible worker to resolve them.
  6. Review Critical Path alongside the actual project and task state before changing commitments.
For example, a team improving ticket response can measure response time as the goal, organize integration and knowledge work as workstreams, and use project tasks to deliver each change. This is an illustrative planning structure, not a preconfigured workflow.

Review progress using the right evidence

Inspect the planning record, then the execution and business evidence behind it:
  • A task marked complete describes that task’s lifecycle.
  • A workflow’s terminal status describes its execution.
  • An execution outcome explains handled exceptions or unresolved work.
  • A goal or domain outcome measures the intended business result.
Do not advance one automatically from another without a declared integration. A completed automation can still leave a business exception or a human review task.

Recover from an apparent gap

Key state to watch

  • A completed task or run — it records that work’s lifecycle or execution, not the business result a goal measures.
  • A blocker — the impediment and its owner; a planning badge does not cancel a run.
  • Two surfaces that disagree — check their filters, time windows, scope and last recorded state before changing the plan.
For decisions waiting on a person, use My Work and Approvals. For technical failures, follow Runs and Events.
  • My Work: the tasks assigned to you.
  • Approvals: decisions planned work is waiting on.
  • Runs: the workflow runs that carry out planned work.