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
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
example · the steps are this template's real steps
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.
The 4 Goal steps in order, each with the instruction your AI receives there as Goal stores it.
An active goal with an approved metric and timeline, the work linked under it, and a progress review you approve before it closes.
Define the goal with a measurable outcome and timeline.
Confirm:
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
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.
Review progress toward the goal's measurable outcome.
Report:
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
Goal achieved. Record the final outcome and close it out.
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
Goal holds at Capture and Review until an explicit approval is given, recorded with the account that gave it.
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
no rejection path · approve to continue
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
reject → back to Active
gates the engine checks without you
Goal runs in a ConvOps workspace and attaches to the goal type, so new work of that type starts on it. Install Feature with it, since Goal creates child work that runs on that workflow. Goal ends with a closing note on the task. Goal needs no repository, so a chat client such as ChatGPT or Claude can run it. The Goal steps name the planner and reviewer roles, a hint for clients with subagents. Connect a client , then install Goal from the catalog .
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.
new chat
workflow_step_update · Goalmore example prompts
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.
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.
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.
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.
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.