Skip to main content

Client Settings: Notes, Objective, Tax State, and Filing Status

Written by Taylor Stewart

Client settings are split between Profile → Household and Office → Notes. Use Household for client identity and planning defaults. Use Office Notes for advisor context, account notes, and Guide template fields.

Household Name

The Household Name is the display name used in the client list and client file. You enter it when creating the client and can correct it later in Household.

Changing the name does not merge households or change portal ownership. Confirm you are editing the correct client before renaming it.

State

State records the household's planning state and supplies the default used by applicable tax work. Choose the state relevant to the client's tax filing situation, not simply the advisor's office or a temporary mailing address.

Changing Household State can affect defaults and downstream analysis. Review existing tax scenarios before assuming they all changed in the same way; a saved scenario can contain scenario-specific assumptions.

Tax Filing Status

Choose the household filing status supported by the client facts:

  • Single;

  • Married Filing Jointly;

  • Married Filing Separately; or

  • Head of Household.

The Household value supplies the normal client-level assumption. Taxes can use scenario-specific values when comparing alternatives. If a tax result looks wrong, check both the Household setting and the selected scenario.

Financial Objective

Use the Objective field for the short, high-level outcome that should anchor the plan—for example, retiring at a target age while maintaining a supportable lifestyle.

Office Home displays the objective near the household header. Keep it concise enough to orient the advisor. Do not use it as a substitute for detailed Goal assumptions, Changes, or Tasks.

Review the objective before presenting it to a client. Client-facing presentation can include household objective context, so write it in language you are comfortable sharing.

Notes

General notes no longer belong only on Profile Household. Open Office → Notes for the full advisor notes experience.

Office Notes can include:

  • general meeting and relationship context;

  • account-specific notes;

  • template-field values used by Guides; and

  • template-field history.

Notes across Kerdora can have a visibility control. Review whether a note is Internal or Client visible. Do not assume that every note is advisor-only. A Guide note component can require a client-visible note before the content is available.

Use an internal note for advisor context that should not appear in client output. Use a client-visible note only when the wording and content are appropriate for the portal or Guide.

Giving

The Household Giving setting controls whether Giving is part of the Cash Flow experience. Enable it when the household's charitable contributions deserve separate planning and presentation.

Disabling Giving hides or removes Giving from some cash-flow presentation and planning behavior, but it does not delete the stored entries. Tax scenarios can still derive tax-deductible Giving from those saved records. Review and correct the entries themselves when they should no longer affect tax work; do not rely on the household toggle as a universal calculation switch.

Portal access

Household also manages adult portal access. Each adult receives a separate signup link and linked email. This permission is separate from the household's state, filing status, objective, and notes.

Where the settings flow

  • Household Name identifies the file.

  • State and Filing Status inform Taxes and related planning defaults.

  • Objective orients Office and client-facing plan context.

  • Notes support internal work or client-visible Guide content according to visibility.

  • Giving controls the charitable-cash-flow experience.

  • Portal access controls which adults can sign in.

After changing State, Filing Status, Objective, Giving, or note visibility, inspect the affected Taxes, Cash Flow, Office, Guide, or portal surface to confirm the intended result.

Did this answer your question?