> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan and track work

> Use goals, roadmaps, projects, tasks, and blockers to connect delivery work with observable outcomes.

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 planning surface that fits the question. See [Choose the right planning surface](#choose-the-right-planning-surface).
* Set up a goal, roadmap, workstreams, project and tasks in order. See [Establish a plan](#establish-a-plan).
* Check progress against the right evidence. See [Review progress using the right evidence](#review-progress-using-the-right-evidence).

## Choose the right planning surface

| Need | Surface |
| - | - |
| State a measurable target and track key results | [Goals](https://docs.gloo.com/forge/console/planning/goals.md). |
| Arrange milestones and delivery themes over time | [Roadmaps](https://docs.gloo.com/forge/console/planning/roadmaps.md) and [Workstreams](https://docs.gloo.com/forge/console/planning/workstreams.md). |
| Organize a specific body of work, customer attribution, and staffing | [Projects](https://docs.gloo.com/forge/console/planning/projects.md). |
| Assign and advance individual work items | [Tasks](https://docs.gloo.com/forge/console/planning/tasks.md). |
| Record an impediment and its owner | [Blockers](https://docs.gloo.com/forge/console/planning/blockers.md). |
| Inspect dependency risk and what work is constrained | [Critical Path](https://docs.gloo.com/forge/console/planning/critical-path.md). |
| Review recorded domain outcomes | [Outcomes](https://docs.gloo.com/forge/console/planning/outcomes.md). |

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

| Symptom | Check |
| - | - |
| A record is missing | Clear filters, inspect its status or archived group, and confirm your readable scope. |
| A worker cannot be assigned | Check directory access separately from authority over the task. |
| Work is blocked | Inspect the named blocker and dependency evidence; a planning badge is not itself a runtime cancellation command. |
| The run succeeded but the target did not improve | Review the business measure and selected output, not just the completion count. |
| Two surfaces disagree | Check their filters, time windows, scope, and last recorded state before changing the plan. |

## 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](https://docs.gloo.com/forge/console/my-work.md) and [Approvals](https://docs.gloo.com/forge/console/production/approvals.md). For technical failures, follow [Runs](https://docs.gloo.com/forge/console/production/runs.md) and [Events](https://docs.gloo.com/forge/console/observe/events).

## Related surfaces

* [My Work](https://docs.gloo.com/forge/console/my-work.md): the tasks assigned to you.
* [Approvals](https://docs.gloo.com/forge/console/production/approvals.md): decisions planned work is waiting on.
* [Runs](https://docs.gloo.com/forge/console/production/runs.md): the workflow runs that carry out planned work.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.