Building Our Financial Doctrine

Our Financial Doctrine turns a household's Blueprint into a document they can read: what they are working toward, what financial freedom means to them, what they are protecting, and the principles they want to use when making decisions. It is written in the household's own first-person voice.

A doctrine is not a financial plan, a recommendation, a projection, an illustration, or a suitability determination. It records what the household told you.

Generate a Draft

1. Open Practice -> Clients and select the client.
2. Open Discovery and scroll to Our Financial Doctrine.
3. Select Generate Doctrine.

The panel shows which source it is working from and when that source was last updated. What the button reads depends on the source:

• Complete Blueprint — Generate Doctrine.
• Incomplete Blueprint — Generate Draft, and the result includes an Open Questions section naming what was missing or contradictory.
• No Blueprint — request a Household Check-In first.

Generating twice does not overwrite work in progress. If a draft already exists, the panel shows that draft rather than replacing it.

What Reaches the Draft

Only the household's own Blueprint answers and Smart Paste updates you explicitly accepted. Advisor-private notes never reach a doctrine. Fields are allowed in one at a time by an explicit ruling, so a new Blueprint question does not silently start appearing in client-facing documents.

Where the source is ambiguous, the draft preserves the ambiguity instead of inventing a fact.

Edit the Draft

Each of the ten sections is editable in place. Prose sections are free text; Our Guiding Principles holds a title, statement, and explanation per principle; Our Priorities separates near-term from longer-term.

Use Client preview to read the document as the household will see it. Select Save Draft to keep your edits.

If two people in your practice have the same draft open, the second save is refused rather than overwriting the first. Reload to pick up the newer text.

Approve a Version

Approve Version runs a compliance review of the text as it stands right now, not as it was generated. Two outcomes:

• Wording that needs a change — approval is held, and each phrase is marked on the field it appears in. This catches instruction-style language ("we should…") that does not belong in a document describing what a household values.
• Wording from the household's own answers — adjusted automatically when you approve. You cannot edit a word out of the household's own history, so these are corrected rather than held. The panel tells you which sections changed so you can read the result.

Approving keeps the doctrine advisor-only. The household sees nothing until you send it to their account, which is a separate action.