Project reports and outputs

Open Project → Outputs → Reports to prepare the standard reporting set for a deal. Each output has its own draft, source snapshot, and version history.

Choose the output

Output	Use it for
Deal overview	A current deal summary, commercial context, financial snapshot, and next steps
Decision memo	The recommendation, rationale, blockers, and unresolved questions
Threshold issues	Deal breakers and critical issues requiring senior attention
Negotiation points	Proposed price adjustments, protections, and closing conditions
Integration handoff	Day-one readiness and actions to carry into integration
Appendix / evidence pack	The source index supporting the review
Contract diligence	Material contract issues, transfer constraints, open questions, and next steps
QoE pack	Earnings quality, working capital, value mechanics, and open finance issues

Choose the output by the decision and audience. Its sections provide a starting structure; the evidence and your review determine what the final document can support.

Generate and review a draft

1. Check that the relevant evidence has finished processing and that the project context is correct.
2. Open the output and choose Generate draft.
3. Review the narrative, tables, and source links once generation completes.
4. Edit the draft where your team’s judgement differs from the initial analysis.
5. Resolve material evidence gaps or state them explicitly before filing.

The QoE output uses financial context and schedules from the project. Confirm the applicable periods, currency, entity scope, and modelling assumptions before relying on its comparisons.

Understand the state

State	What to do
Undrafted	Generate the first draft when enough evidence is available
Draft	Review and edit the working version; generation progress is shown while work runs
Stale	Review the changes since the output’s source snapshot and refresh affected content
Filed	Use the filed version as the reviewed record; check for subsequent evidence changes
History only	Inspect available earlier versions when no current version is available

A stale output is not automatically rewritten. Review the reported changes and decide whether to refresh sections or regenerate the output.

Refresh sections and retain history

Use section refresh when a change affects a specific part of the document. Use Regenerate all when the whole output needs a new pass. Read the refreshed content again: an earlier editorial or factual review does not automatically apply to new text.

The version selector lets you inspect earlier output versions. Confirm which version you are reviewing before making changes or circulating a copy.

File the reviewed version

Change the output to Filed once the wording, evidence, and conclusions have been reviewed. Filed content is locked for editing. If further work is needed, use the available draft action and preserve the earlier filed version in the history.

Filing records the team’s workflow decision. It does not prove that all evidence is complete or that every conclusion is correct.

Reports, AI deliverables, and exports

Need	Use
Standard project reporting with version history	Outputs → Reports
A custom memo, model, workbook, or presentation	Colabra AI
Structured project records in Excel	Outputs → Export → Project data export
Original project files in a ZIP	Outputs → Export → Download all files, with bulk-download permission

Before distribution, check the source support for material conclusions, unresolved issues, the selected version, and the intended recipients.