Documents

What this screen is for

Documents turns reviewed work into a controlled record. The left panel is where you choose a type, a household or client, the accountable adviser and any featured strategies, then generate a draft. The right panel shows the draft for review and the history of every version. Draft, final, published and portal-visible are four distinct states, and this guide is mostly about the boundaries between them.

The five document types

Type	Described on the card as	Scope
Statement of Advice	Comprehensive advice covering goals, recommendations and projections	Household or individual
Record of Advice	Focused advice update for a specific change or recommendation	Household or individual
Annual Review	Annual review covering progress, updates and next steps	Household or individual
Pre-Meeting Summary	Pre-review summary prepared ahead of the next advice meeting	Household or individual
Outcome Receipt	Annual statement of the value your advice delivered	Individual only

A household with one member is always in individual scope; the Household choice does nothing there.

There is no fee disclosure statement generator. Fee consents are records kept on their own screen, and fee disclosure appears only as prose inside the Statement of Advice.

What each type contains

A Statement of Advice runs: cover, executive summary, objectives and situation, entity structure, financial position, risk profile, goals, scope of advice, a recommendations divider, one chapter per strategy, tax strategy summary, financial projections, assumptions and disclosures, product comparison, investment allocation, insurance, estate planning, fees, risks, implementation plan, authority to proceed, and two appendices listing strategies considered but not recommended and information limitations. Sections marked optional in the design are left out when there is nothing to say.

A Record of Advice is shorter: cover, summary of change, client details, financial position, the advice given, investment allocation, tax strategy summary, fees and costs, assumptions. An Annual Review adds goals progress, updated projections and action items. A Pre-Meeting Summary is cover, details, financial position, goals and a “where you’re tracking” projection.

Which strategies appear depends on the type. A Statement of Advice includes proposed, accepted and active strategies. A Record of Advice includes accepted ones only. A review includes accepted and active.

The cover, executive summary, recommendations divider and authority to proceed each start a fresh page, as does every strategy chapter. Everything else flows on from the section before it.

Before you can generate

• A supervising adviser must be chosen. The page refuses before it starts, and the server refuses again if one is missing or is not an active adviser in your firm.
• Featured strategies must be this client’s, and proposed or accepted. Up to three. Anything else is refused with “refresh the list and pick again”.
• The compliance gate must pass. The page runs it first and lists every blocker by code and member; the server runs the same checks and is the authority.

The compliance checks:

Always	For a Statement or Record of Advice
Scope defined for the client	At least one recommendation exists
No active strategy in an out-of-scope area	Each recommendation has an impact statement, a consequence of inaction, a rationale, and its three alternatives (do nothing, a cheaper option, a simpler option)
No active strategy in an unclassified area	Modelling scenarios exist (a warning, not a block: assumptions fall back to defaults)
An insurance recommendation that states a cover amount (the life, TPD and income protection gap family) has a needs analysis recorded; trauma, ownership, premium-structure and business expense recommendations generate without one

The three free-text notes (goals introduction, executive summary, adviser fee) are capped at 600 characters each and may not contain angle brackets. A household whose goals carry no free text has the goals introduction highlighted so you write one before generating rather than finding a bare section after.

The AI toggle

With AI on, the executive summary and strategy chapters are drafted from the compiled figures and then polished for flow. The polished text is kept only if every number in the template text survives it, counted as many times as it appeared; otherwise the template text is used and nothing is said in the document. If the firm has AI off or the key is unavailable, the document is generated without narratives and the response says the AI was requested but not delivered.

What the firm can customise

Per firm, three kinds of text can replace the coded defaults: a letter body per document type (up to 1,200 characters), an introduction for the goals section (600), and a description per strategy code (900). Nothing else in a document is editable as template text.

The projections chapter

The projections chapter reads the household’s latest published projection, never the working copy and never a fresh run. If no projection has been published, the chapter carries an info box saying so and telling you to publish one from the projections workspace and reissue the document. If the published run modelled nobody or has no household rows, it says that instead, and nothing is substituted.

The funding verdict (“funded to age N” or “shortfall from year Y”) is shown only when the publication was stamped by the publish run itself. A publication written before that stamp existed shows its series with the verdict marked as not checked. Republishing the projection produces a stamped one.

Fees, costs and remuneration

The fee section is built from four sources:

• Adviser fee from the household’s fee type and rate. A household with no fee type recorded reads as zero, never as the house rate. The funds-under-management base is the canonical household figure (super plus investment assets, deduplicated across owners) when the engine could compute it, otherwise the profile’s own super plus investments, and the document records which.
• Product and platform fees from the recorded indirect cost ratios on the scenario the document is built from.
• Insurance premiums, annualised.
• One-off transaction costs, listed separately and never added into the ongoing total.

The current-versus-proposed fee comparison is hidden, because nothing records the client’s current fees.

Draft, final, published

A generated document is a draft, and generating again for the same subject and type reuses the existing unlocked draft rather than adding a version. Marking it final is a status change you make from the history row.

Post to Vault is the publish step. It accepts only a final, unlocked document. In one transaction it marks the document published and locked, renders the PDF into the vault, records a receipt holding a fingerprint of the exact HTML and data that were published, and marks the previous version superseded. From that moment the document’s content cannot change: status edits, video-intro edits and deletion are all refused with “Published documents are immutable”.

Two consequences worth knowing:

• Anything that later improves how documents render does not reach a published one. The stored HTML is served as it was; only the PDF is re-rendered from that stored HTML when requested.
• Post new version on a published row does not touch it. It generates a fresh draft for the same subject and type, which supersedes the old one when it is posted.

One quirk of the history list: a published document’s status tag still reads “Draft”; the lock badge and the “Post new version” action are what tell you it is published.

The pre-vet review

The pre-vet findings you see on a document are derived every time from its evidence, not stored. A strategy chapter with no calculation trace is high severity; an unresolved adversarial-review challenge is high or medium by category; a recommendation whose validity is no longer fresh is medium; a rejected alternative with no reason is medium; a strategy with no client decision recorded is low. Signing off records your review. It does not block posting, and posting does not re-run the compliance gate.

The client portal

Publishing and sharing are two separate acts: posting to the vault leaves the document invisible to the portal; making it visible is a separate toggle, and superseding a document hides it again. The portal lists only documents that are published, visible and not superseded.

A client reading a shared document can record a decision on each strategy: accepted, declined, or discuss. The decision is bound to that document and to that strategy; a second decision on the same strategy is refused with “Strategy already decided”, and “discuss” leaves it open. Each decision is written as an acceptance event and a notification is queued to the adviser.

What does not stop a document

No document is refused for a stale projection or a stale recommendation. A stale projection produces the info box described above; a stale recommendation is a pre-vet finding. Both read as ordinary documents to a client, so check the projections chapter and the pre-vet panel before posting.