Evidence stays attached
Source packs remain connected to the brief, recommendation, decision, or framework (standalone decision and framework artifacts are made in Gixo Prism) instead of disappearing into a chat transcript.
A confident answer is not the same as a defensible decision.
Business is designed to make evidence strength, uncertainty, assumptions, and human review visible before an executive artifact is treated as ready.
Gaps are surfaced early
Business identifies missing inputs and source concerns before drafting so thin evidence is not mistaken for certainty.
Review is explicit
Verification gates carry required checks, warnings, and human-review conditions with the output, and the gate runs again on a finished brief. For a brief written from sources you upload or from the search results web research drew on, the Evidence tab under Checks in the brief editor lists up to five sentences or table cells whose wording or figures it could not match to those sources, for you to check. It matches wording and exact figures, not meaning: a faithful paraphrase, or $8.1M where the source says 8,100,000, can fail to match while being true, so an unmatched sentence is a place to look, not an error, and a matched one is not confirmed either, because this is a comparison with your own sources, not a fact-check. It reads only part of a long source (24 passages of up to 1,600 characters) and at most 12 sources, files first. Of web research it reads the title and snippet of each search result, not the page, so a figure taken from the page alone does not match, and if it could not read every result the list is advisory. It reads a table cell with its row and column, and a total the table works out from its own cells passes when the arithmetic holds. It checks the draft as generated, not your later edits.
Structure is inspectable
Options, criteria, confidence, assumptions, and reversal conditions remain visible for the people accountable for the decision.
Keep review decisions tied to current evidence
The evidence owner records a decision against the current source item and wording. Unchanged identified items can retain their decisions; changed or removed items can leave earlier decisions orphaned and need another review. A recorded rejection or stale decision still counts as a decision. These item decisions are separate from the formal Business Case readiness and approval requirements.
Export the approved case revision
Approval attempts to retain a snapshot of that case revision. The governed memo renders only from an available approved snapshot after checking the revision, state hash, audit receipt and supported financial results. A missing or unverifiable snapshot prevents export, and PDF also needs configured rendering. The checks establish consistency of the retained record, not independent accuracy of the original assumptions.
Recalculated and attested figures are labelled apart
Where a financial case is built from scenario inputs, the server re-runs those inputs and compares them to the stored result. Where the figures were entered by hand with a reference instead, the export says so rather than presenting them as checked. The source forecast and verification gate are review aids, not independent fact-checking. Reviewers must confirm important claims, figures, assumptions, and recommendations against authoritative sources.
Business workflow principles
- Do not hide uncertainty behind polished prose.
- Do not treat an incomplete source pack as a complete answer.
- Keep the business question visible from intake through delivery.
- Make the final human approval step clear.
See the evidence-to-artifact journey in a real Business example.
View Business examplesUpdated
More from Gixo