Goal AI workflow template: A goal that closes when the work does.

The ConvOps Goal template makes your AI turn an objective into a measurable target with a timeline, hold it active while initiatives and tasks are linked under it, then review progress against the metric. You approve the target before tracking starts and approve the close. Reject the review and it returns to active.

4 steps · 2 approvals · 1 loop back · waits for child tasks

Goal · example runyour AI client
  1. 01Capturewaits for approval
  2. 02Activewaits on children
  3. 03Reviewwaits for approval
  4. 04Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Goal template do?

For founders and team leads who set quarterly objectives and want progress tied to the actual work, not to a status meeting.

Goal is stored in ConvOps as four steps, and your AI client receives them one at a time. A Goal run holds at Capture and Review until an explicit approval is given.

  • Set Q1 revenue targets and track progress to the milestone
  • Define a product-market-fit goal with explicit sign-off on the target
  • Run a quarterly objective from definition through verified completion
step by step

How does the Goal workflow run?

The 4 Goal steps in order, each with the instruction your AI receives there as Goal stores it.

Capturewaiting for you
Activewaits on children
Reviewapproval
Completeclosing note

An active goal with an approved metric and timeline, the work linked under it, and a progress review you approve before it closes.

  1. 01

    Capture

    waits for your approvalrole · planner

    Define the goal with a measurable outcome and timeline.

    Confirm:

    • What is the measurable outcome (the metric or deliverable)?
    • What is the timeline (quarterly, annual, multi-year)?
    • How will success be measured?

    Record the answers in the goal's description or metadata. Request operator approval before activating.

    no rejection path · the run moves on only when approved

  2. 02

    Active

    waits for child tasks

    Goal is now active. Create or link child work items that drive toward this goal: initiatives for committed bodies of work, or direct tasks/bugs for standalone items. Types are semantic; pick what matches the work.

    This step is the steady state: the goal stays here while work is in progress. Advance to review when ready for a progress check or when the timeline milestone arrives.

  3. 03

    Review

    waits for your approvalrole · reviewer

    Review progress toward the goal's measurable outcome.

    Report:

    • Current status of linked child work (initiatives, tasks, or bugs)
    • Progress toward the target metric or deliverable
    • Whether the timeline is still realistic

    If the goal is met, request operator approval to close it. If still in progress, reject to return to the active state and continue working.

    rejected → back to Active

  4. 04

    Complete

    closes with a note

    Goal achieved. Record the final outcome and close it out.

reach for it when

  • You have a target with a number and a date, and work that should move it.
  • Progress should be read from linked work, not from a status meeting.
  • The goal should stay open until its work is actually done.

something else fits when

  • There is no measurable outcome yet: frame it with a Decision Memo or a Research Report first.
  • It is a single deliverable, which a Feature or a Task covers.
  • It is a standing number to watch every week, which belongs in a metric.
example · telecom customer supportenterprise

First response in under 4 hours

A support director sets the target for Q2. Initiatives for routing and staffing sit under the goal, and the quarter review reports progress on the metric before the close is approved.

Capture and Review approvals

where approval is required

Where do you approve in Goal?

Goal holds at Capture and Review until an explicit approval is given, recorded with the account that gave it.

step 1

Capture

A goal without a measurable outcome and a timeline cannot be reviewed. You approve the target and how success is measured before the goal goes active.

what you review

  • What is the measurable outcome (the metric or deliverable)?
  • What is the timeline (quarterly, annual, multi-year)?
  • How will success be measured?

no rejection path · approve to continue

step 3

Review

Your AI reports the status of linked child work, progress on the metric and whether the timeline still holds. Approve to close, or reject to return to Active and keep going.

what you review

  • Current status of linked child work (initiatives, tasks, or bugs)
  • Progress toward the target metric or deliverable
  • Whether the timeline is still realistic

reject → back to Active

gates the engine checks without you

  • Active waits until every child task Goal created is completed or cancelled.
  • Complete closes Goal only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Goal?

make it yours

How do you customize Goal?

Once installed, Goal is a workflow in your workspace. Ask your AI to change Goal in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Review, also compare progress with the same point last quarter.
workflow_step_update · Goal
Done. Goal in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Review, also compare progress with the same point last quarter."
  • "Add a rule to Capture: every goal names one owner."
  • "Make Active list the linked initiatives and their status in the goal description."
the difference

Goal: without a workflow vs with it

  • A goal gets declared in a meeting, then drifts with no agreed target or owner
  • By quarter-end nobody can say what moved the metric or when
  • The goal closes even though its underlying work never finished
  • The Goal process lives in a prompt, and each run follows it a little differently
  • The AI drives through Capture, then pauses at an approval step so you sign off on the target before tracking begins
  • Every step (Capture, Active, Review) is logged automatically, so the audit trail of progress is already there
  • The AI cannot close the goal until its child work completes, so completion means the work is actually done
  • Your AI receives the 4 stored steps one at a time, and the run holds at Capture and Review until an explicit approval is given
questions

Goal template FAQ

What is the ConvOps Goal template?

The ConvOps Goal template makes your AI turn an objective into a measurable target with a timeline, hold it active while initiatives and tasks are linked under it, then review progress against the metric. You approve the target before tracking starts and approve the close. Reject the review and it returns to active.

Can a goal be active with no work under it yet?

Yes. In ConvOps, the Goal template's Active step waits for child work to finish but allows an empty start, so you can activate the target as soon as Capture is approved and link initiatives, tasks or bugs as they come. Active is the steady state: the goal stays there while the work under it is in progress.

How often does the goal get reviewed?

As often as you ask. ConvOps keeps the goal at Active, and your AI advances to Review when you want a progress check or when the timeline milestone arrives. Review reports the status of linked work, progress toward the target metric or deliverable, and whether the timeline is still realistic. Rejecting the review returns the goal to Active.

What work can sit under a goal?

In ConvOps, initiatives for committed bodies of work (the Feature template attaches to initiatives) or direct tasks and bugs for standalone items. Types are semantic, so you pick the one that matches the work. The catalog lists Feature as this template's dependency, and Goal ships with Feature, Plan and Phase in the Strategic Delivery kit.

What does Goal Capture record?

The ConvOps Capture step defines the goal before it activates: the measurable outcome (the metric or deliverable), the timeline (quarterly, annual or multi-year) and how success will be measured. Your AI records the answers in the goal's description or metadata, and the run holds at Capture until an explicit approval is given, recorded with the account that gave it.