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
- Open Practice -> Clients and select the client.
- Open Discovery and scroll to Our Financial Doctrine.
- 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. Approving and sending are two separate actions — approving on its own delivers nothing to the household.
Send It to Your Client
Send to Client emails the approved version as a branded PDF attachment. The email comes from Policy Stack, and replies go to you.
- On an approved version, select Send to Client.
- Select Preview the PDF to read the exact document your client receives.
- Add an optional note. It goes in the email body, never in the PDF.
- Select Send.
A doctrine belongs to the contact, not to a Policy Stack account, so a prospect who has never signed up can receive one.
The doctrine travels as an email attachment. It does not appear inside the client's Policy Stack account — there is no dashboard card, no Documents entry, and no acknowledgment to wait for.
Sending Is Permanent
An attachment already in someone's inbox cannot be recalled, so the version you sent becomes permanently read-only and is labelled Sent. Its wording cannot be edited afterward.
Change Something After Sending
Select Create New Version. The text you sent is copied forward as an editable draft, and the sent version stays exactly as your client received it. This is a copy rather than a regeneration — nothing is rewritten.
How the PDF Is Branded
Branding follows the practice that owns the doctrine, not whoever opens or sends it, so the same document reads the same way to everyone.
- Practice 10 and above — the practice logo and brand color on the cover.
- Practice Solo — the advisor and practice name as text, plus a "Prepared with Policy Stack" line.
Branded exports change the document's appearance only. Every paid Practice tier can send.
The PDF's embedded fonts cover Latin scripts. If the doctrine text or your practice profile holds characters outside that range, sending is refused with a message naming which fields to edit, rather than producing a document with missing text.