Frame the decision
Name the audience, requested decision and source pack. Review imported tables and extracted text; record gaps instead of allowing a polished narrative to conceal them.
A simple walkthrough for turning reports, notes, and source documents into a business brief you can review, improve, and share.

The briefs workflow combines source files, format selection, editing, and export so one workspace can take a document set to a finished brief.
A business brief is a short, structured document — built from your own reports, notes, and source files — that summarizes the key facts, figures, and recommendations a team needs to act on, without the reader having to read the underlying source material. Describe the business question and intended audience, add the sources you want to use, and review the proposed outline and missing evidence before generating. A repair stage compares figures in paragraphs, lists and table body cells with the uploaded text; it leaves table headings and the totals a table works out from its own figures as written, and can retain an original figure when repair fails. Review the sources and the editor’s Evidence findings before sharing.
Inspect an actual Business report. A readable decision brief needs the question, supplied evidence, options, assumptions and next decision—not just a shorter source document.
A decision, options compared on stated criteria, risks and a roadmap, with statements in the analysis labelled Fact, Inference or Assumption. The decision, lists and some summary sentences carry no label.
Business question: Which actions should a small business that stores customer personal information take first to protect it and to be ready if it is exposed? Decision maker: The owner of a small business. Timeframe: The next quarter. Context: A small business collects customer personal information and keeps it in paper files and on computers. It has no dedicated security staff. Refer to it as 'the business' throughout and do not give it a name. Options: Take stock of the personal information it keeps and where it is stored; Reduce what it keeps to what the business needs; Lock down the information it keeps with practical safeguards; Prepare a plan for responding to a data breach. Criteria: How much personal information at risk it removes or protects; How realistic it is for a small team without security specialists; How well it limits the harm if information is exposed. Constraints: No dedicated security staff; Limited time and budget.
Open the full export and compare its statements with the cited sources before reuse.
Name the audience, requested decision and source pack. Review imported tables and extracted text; record gaps instead of allowing a polished narrative to conceal them.
Separate supplied facts, calculated values, assumptions and recommendations. For variance work, reconcile the period, unit, baseline and actual value before interpreting the direction of a difference.
Use options, trade-offs, risks and named next actions. Review the final artifact and, when using Analyst calculations, inspect the calculation evidence separately from the narrative.
Select source documents, case context, working notes, assumptions, options and decision constraints before generation. Inspect claims, metrics, exact quotations, source tables and conflicting figures. Review decisions are scoped to the source or artifact and can become stale after evidence changes; unresolved evidence should stay visible.
Keep investment, recurring costs, benefits, delays, growth, discount assumptions and scenario probabilities explicit. Inspect deterministic cash flow and the available return, payback and sensitivity outputs. Compare scenarios before selection, and inspect the formula workbook or calculation receipt separately from the narrative recommendation.
Inspect the dossier's source tables, working rows and columns, calculation ledger and workbook handoff. Metric packs retain reviewable calculation and source context. Preview source replacements for a new period before accepting them. Execution records distinguish an action owner, baseline, target, measured value, data source and the reason for a status change.
A calculation can be replayable while the supplied inputs remain wrong. A generated report is decision support, not independent diligence, audit assurance or investment advice.
| Element | What it is | Where it appears on this page |
|---|---|---|
| Steps to produce a brief | 6 (upload sources, choose brief type, review draft, edit, team review, export) | Stats bar + step-by-step section |
| Question, sources and reviewed outline | Question, sources and reviewed outline | Stats bar |
| Number verification | Figures checked against the uploaded source files | Stats bar ("Checked" / "Numbers") + FAQ |
| Structuring format | "Semantic blocks" — pre-built section types (KPIs, steps, checklists, comparisons) | FAQ |
| Team review | Comments and named sharing require Business Professional or higher and an authorized current content role | Step 5 + stats bar |
| Reusability | Source documents stay attached to the workspace for reuse across multiple briefs | FAQ |
| Editability | Brief remains editable in the workspace after export | FAQ |
This is the easiest path if you already have documents and want a clear first draft instead of starting from a blank page.
Start with the reports, notes, transcripts, or research that should feed the brief.
State the question, audience and source scope, then review the proposed outline before generating.
Gixo turns the source material into a structured brief, checks the output, and gives you something concrete to review.
Tighten wording, change sections, and improve weak spots without rebuilding the entire brief.
On Business Professional or higher, use comments and named sharing where the current content role permits. Review the saved version and resolve save conflicts before distribution.
Once the brief looks right, export it in a shareable format and send it where it needs to go.
Updated