Skip to content
Reports & Output · 5 min read

Refining Reports With Chat

Ask the chat to regenerate reports with different criteria — then compare versions side by side.

Your first report is rarely your final report. Maybe the structure does not match what your audience needs. Maybe you want more emphasis on financial implications and less on technical details. Maybe you ran the research with one question in mind and now realize the findings support a different angle entirely.

LumaVista lets you regenerate reports through the project chat. Describe what you want changed, and the system rebuilds the report from the same research graph — the same underlying evidence — but with different criteria, structure, or emphasis. You can then compare versions side by side and choose the one that works best.

How report regeneration works

When you ask LumaVista to regenerate a report, it does not start the research over. All the data gathering — the searches, the source evaluation, the reasoning — has already been done. Regeneration works with the completed research graph, re-reading the findings and synthesizing a new report based on your updated instructions.

This means regeneration is fast. You are not waiting for agents to search the web again. You are asking the report writer to take another pass at the same evidence with different guidance.

What you can change

Here are some examples of regeneration requests that work well:

  • “Rewrite this report for a non-technical audience.” Strips jargon, expands explanations, focuses on implications rather than mechanisms.
  • “Focus the report on cost implications.” Restructures the report to lead with financial data, downplays sections that do not have cost relevance.
  • “Make this an executive summary — no more than 500 words.” Compresses the full report into a concise brief.
  • “Add a section comparing the top three options.” Restructures findings into a comparison format.
  • “Rewrite with more emphasis on risks and limitations.” Shifts the tone from neutral reporting to critical analysis.

You can also combine criteria: “Rewrite this for a non-technical audience, focus on the competitive landscape, and keep it under 1,000 words.”

Using the chat to regenerate

  1. Open the project chat for the project whose report you want to refine.
  2. Describe what you want. Be specific about the changes — tone, structure, length, emphasis, audience. The more detail you give, the better the result.
  3. Wait for regeneration. LumaVista rebuilds the report from the research graph using your new criteria. This typically takes 30 seconds to a couple of minutes, depending on the report length.
  4. View the new version. The regenerated report appears in the report view. You will see a notification in real time as it is generated.

The chat understands natural language, so you do not need to use specific commands. Phrases like “can you redo the report,” “generate a new version that focuses on,” or “rewrite the report to be more concise” all work.

Version management

Every regenerated report is saved as a new version linked to the original. LumaVista does not overwrite your previous reports — each version is preserved.

The version switcher

Above the report content, a version dropdown lets you switch between all versions of the report. Each version is labeled with its generation timestamp. Select any version to view it.

Comparing versions

To compare two versions:

  1. Open the version you want to review.
  2. Switch to another version using the dropdown.
  3. Read through both, noting differences in structure, emphasis, and coverage.

The version system makes it safe to experiment freely. You can generate five different versions with different audiences in mind, compare them, and settle on the one that works — without losing any of the others.

What regeneration preserves

Since regeneration works from the same research graph, certain things are always preserved:

  • Source evidence. The underlying research findings do not change. Every claim in the regenerated report is still backed by the same source nodes.
  • Source links. The new report includes anchor links back to the same source evidence, following the same link format as the original.
  • Research depth. Regeneration does not add new research. If your original project searched 20 sources, the regenerated report draws from the same 20 sources.

What regeneration can change

  • Structure and organization. Sections can be reordered, merged, split, or restructured entirely.
  • Emphasis and tone. The same facts can be presented with different weight, from neutral reporting to critical analysis.
  • Length. A 3,000-word report can be compressed to a 500-word executive summary or expanded with more detail.
  • Audience targeting. Technical depth, jargon level, and assumed background knowledge can all shift.

How regeneration uses your research graph

When the report writer regenerates, it does not simply rephrase the original report. It goes back to the research graph — the full set of completed nodes from your project — and re-reads the underlying findings. This means:

  • Underemphasized findings can surface. If your original report briefly mentioned a finding that is now the focus of your regeneration request, the writer pulls more detail from the source nodes.
  • Context from chat and keywords. The regeneration pipeline also draws context from your project chat history and keyword search results, enriching the rebuilt report with additional nuance.
  • Source links are rebuilt. Each regenerated report gets its own set of source anchor links, accurately pointing to the nodes that informed the new version. The links are validated just like the original export — invalid references are stripped and missed sources are appended.

This architecture means regeneration is not just cosmetic rewriting. It is a genuine re-synthesis of your research evidence through a different lens.

Common regeneration workflows

The multi-audience approach

Run one research project, then generate three versions of the report:

  1. A detailed technical report for your engineering team.
  2. A concise executive summary for leadership.
  3. A client-facing overview that emphasizes business impact.

Each version draws from the same evidence but presents it differently. Export each one and distribute to the appropriate audience.

The iterative refinement loop

Start with a broad regeneration request, review the result, and refine:

  1. “Rewrite this report to focus on competitive positioning.”
  2. Review the result. “Good, but add more detail on pricing comparison and reduce the section on company history.”
  3. Review again. “Perfect. Now add a recommendation section at the end.”

Each iteration produces a new version. You can compare any two versions to see how the report evolved.

The format transformation

Transform your research findings into different document types:

  • “Rewrite this as a FAQ document with questions and answers.”
  • “Turn this into a bullet-point brief with no prose paragraphs.”
  • “Restructure this as a SWOT analysis.”

The research stays the same; the presentation changes to match the format your situation requires.

Tips for effective regeneration

  • Be specific about your audience. “Rewrite for executives” is good. “Rewrite for a CFO who needs to approve a $500K budget decision” is better.
  • Specify structure when you care about it. If you need a specific format — bullet points, numbered recommendations, comparison tables — say so explicitly.
  • Iterate. If the first regeneration is close but not quite right, refine your request. “That is good, but make the risk section more prominent and add a timeline” builds on what the system already produced.
  • Use versions as alternatives, not corrections. Sometimes you need the same research presented three different ways for three different stakeholders. Generate all three and export each one.
  • Export the version you like best. Once you have settled on a version, export it as Markdown or HTML. The version switcher makes it easy to go back and export a different one later if your needs change.