Research Report AI workflow template: A sourced answer to one question.

The Research Report template makes your AI answer one research question with a sourced report: state the question precisely, scope the sub-questions, gather findings with sources and reliability, then synthesize an answer that separates fact from inference. You approve the scope before gathering and the report before it is shared.

6 steps · 2 approvals · 1 loop back

Research Report · example runyour AI client
  1. 01Question
  2. 02Scopeyou approve
  3. 03Gather
  4. 04Synthesize
  5. 05Final Reviewyou approve
  6. 06Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Research Report template do?

For founders, analysts and marketers who research markets, competitors or options and need every claim tied to a source.

It is a stored workflow, not a prompt. Your AI client receives one step at a time from ConvOps over MCP, does the work, and advances. The engine holds the run at each of its two approvals until a person says yes.

  • Research a market and write up the findings with sources
  • Compare competitors and summarize what matters for a decision
  • Investigate an option and lay out the evidence both ways
step by step

How does the Research Report workflow run?

6 steps, in this order. Below each one is the instruction your AI receives at that step, exactly as the template stores it.

Question
Scopeapproval
Gather
Synthesize
Final Reviewapproval
Completeclosing note
  1. 01

    Question

    the agent works

    State the research question precisely before anything else.

    Capture:

    • The question: the specific thing this report must answer
    • Why it matters: the decision or need behind it
    • The audience for the report
    • Any constraints: depth, deadline, sources to use or avoid

    A fuzzy question produces a fuzzy report. If the operator's ask is broad, narrow it with them before advancing.

    Save the question and its context as a task note with task_notes_add. The next step (Scope) reads this note.

  2. 02

    Scope

    waits for your approval

    Read the task notes with task_notes_list: the note from the Question step contains the question and its context. Work from it.

    Scope the research. What good looks like:

    • The sub-questions that, answered, answer the main question
    • What is in scope and explicitly out of scope
    • The kinds of sources you will use
    • The shape of the final report: sections and depth

    Save the scope as a task note with task_notes_add. Then ask the operator to approve the scope before gathering begins. This is a checkpoint: scope drift wastes the most time in research, so the AI cannot advance until you approve.

    no rejection path · the run moves on only when approved

  3. 03

    Gather

    the agent works

    Read the task notes with task_notes_list: the note from the Scope step contains the sub-questions and boundaries. Work from it.

    Gather evidence against each sub-question. For every finding capture:

    • The finding itself, stated plainly
    • The source: a link or citation
    • How reliable the source is and any caveat
    • Which sub-question it answers

    Stay inside the approved scope. Note where evidence is thin or conflicting rather than papering over it.

    Save the gathered findings and sources as a task note with task_notes_add. If it exceeds 10,000 characters, split across notes or store where the operator keeps documents and record the location. The Synthesize step reads this note.

  4. 04

    Synthesize

    the agent works

    Read the task notes with task_notes_list: the Gather note holds the findings and sources, and the Scope note holds the sub-questions to answer. Work from them.

    Write the report:

    • A direct answer to the main question up front
    • Each sub-question answered with its evidence and sources cited
    • Conflicting evidence and uncertainty stated honestly
    • A short conclusion and, if asked for, a recommendation
    • Sources listed so claims can be checked

    Do not assert beyond the evidence. Distinguish fact from inference.

    Save the full report as a task note with task_notes_add. If it exceeds 10,000 characters, split across notes or store where the operator keeps documents and record the location. The Final Review step reads this note.

  5. 05

    Final Review

    waits for your approval

    Read the task notes with task_notes_list: the Synthesize note holds the report, the Gather note holds the sources, and the Question note holds what was asked. Work from them.

    Review the report:

    • It answers the original question directly
    • Every claim is backed by a recorded source
    • Uncertainty and conflicting evidence are surfaced, not hidden
    • It stays within the approved scope and matches the planned shape

    Ask the operator to approve the report. This is a checkpoint: once shared the report informs decisions, so the AI cannot advance until you approve. If you reject, the workflow returns to Synthesize.

    rejected → back to Synthesize

  6. 06

    Complete

    closes with a note

    The research report is approved and ready to share. Confirm the final report, with its sources, is saved as a task note, then close out the task. This note is the named input for a Decision Memo workflow if a decision follows.

where a person decides

Where do you approve in Research Report?

Two steps wait for a person. You answer in the chat; the engine records the verdict and the audit row records who gave it.

step 2

Scope

Scope drift wastes the most time in research. You approve the sub-questions, the boundaries and the shape of the report before gathering begins.

what you review

  • The sub-questions that, answered, answer the main question
  • What is in scope and explicitly out of scope
  • The kinds of sources you will use
  • The shape of the final report: sections and depth

no rejection path · approve to continue

step 5

Final Review

Once shared, the report informs decisions. The AI checks it answers the question and every claim has a recorded source. Reject it and the run returns to Synthesize.

what you review

  • It answers the original question directly
  • Every claim is backed by a recorded source
  • Uncertainty and conflicting evidence are surfaced, not hidden
  • It stays within the approved scope and matches the planned shape

reject → back to Synthesize

gates the engine checks without you

  • Complete closes only when your AI leaves a closing note. The note is saved to the task as context, so later work can find why it ended the way it did.
what you need

What do you need to run Research Report?

Read from the template's own steps: the tools they call, the files they write, and whether they touch code.

An AI client
Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode, or any MCP client. ConvOps does not run the model; your client does the work.
ConvOps
A workspace with Research Report installed. It attaches to the task task type, so new work of that type starts on it.
Tools your AI calls
workflow_advance to move between steps, plus task_notes_add and task_notes_list to save and read each step's output.
Where the work lands
Task notes in ConvOps. Each step saves its output with task_notes_add, and the next step reads it back.
A repository
No. A plain chat client is enough.
Roles named in steps
None. One AI runs every step.
make it yours

How do you customize Research Report?

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

ChatGPTexample

new chat

more example prompts

  • "In Gather, only use primary sources: official docs, filings and pricing pages."
  • "Add a one-page executive summary to Synthesize."
  • "After Complete, start a Decision Memo with this report as its input."
the difference

Research Report: without a workflow vs with it

  • The research wanders, balloons in scope, and answers a question nobody asked
  • The report states conclusions with no sources, and nobody can check the claims
  • You research for an hour, close the chat, and lose every source and note you collected
  • The process lives in a prompt, and each run follows it a little differently
questions

Research Report template FAQ

How does it handle weak or conflicting evidence?

Gather records each finding with its source, reliability and caveat, and notes where evidence is thin or conflicting. Synthesize states uncertainty honestly and does not assert beyond the evidence.

Does the AI browse the web?

ConvOps does not run models or browse. Your AI client does the research with whatever tools it has, and the workflow structures the question, scope, sources and review.

What happens after the report?

The Complete step saves the final report with sources as a task note, which is the named input for a Decision Memo workflow if a decision follows.

Which AI clients can run the Research Report template?

Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. It needs no repository, so a plain chat client works.