Use Profile → Household for people and ownership entities in a client's plan. Client, Other adult, Child, Business, and Trust records have different planning effects; choose the type based on those effects as well as the person or entity you're recording.
Household-wide defaults are covered in Client Settings: Notes, Objective, Tax State, and Filing Status.
What changes when I add a Client to Household?
In Profile → Household, a Client is a person whose financial plan you're building. A household can have at most 2 Clients; use Other adult for another adult whose retirement isn't part of that plan.
Clients set retirement timing and the default planning horizon. Kerdora uses the earliest configured Client retirement year and the latest expected death year among Clients. Clients also supply person-specific tax inputs, insurance needs, estate questions, age reminders, and new portal invitations.
Other adults can remain account owners and income owners. Their income still counts in household cash flow, but their wages and business income stay off the tax return for that household's Clients in Taxes.
Changing a person's type doesn't delete that person's records or automatically exclude their accounts from household totals. Existing life or disability policies can still appear even when their insured person is an Other adult.
Older Adult records load as Client. If Household shows more than 2 Clients, review who the plan is for and change any additional adults to Other adult.
Why is a grown child in Household affecting Retirement?
In Profile → Household, a grown child saved as Client affects retirement timing and the default planning horizon. An advisor can change that person to Other adult without deleting and recreating their record.
Open the grown child's member record in Profile → Household.
Under Member type, select Other adult.
Read the confirmation and select Change.
That change removes the person from Client-specific retirement timing, insurance needs, estate questions, age reminders, and tax inputs. It keeps their underlying records. Review account inclusion and income separately.
Kerdora won't change the last Client to Other adult. Changing an Other adult back to Client requires an available Client slot. Child records still can't be converted through this selector, and birthdays don't automatically change member types.
For an incorrectly saved Child, review relationships before replacing that record.
Does a blank retirement age exclude a Household Client from Retirement?
No. In Profile → Household, clearing a Client's retirement age removes that person's retirement date from the earliest-retirement calculation, but their birthday and life expectancy can still extend the default planning horizon.
Clearing a Client's retirement age also changes income and insurance calculations. Income set to end at that person's retirement uses their household plan's retirement year instead.
In Planning → Insurance, the Human Life Value Method uses 0 work years for that person, even though its "How many more years do you plan to work?" field shows years until 65. Its coverage need becomes $0 unless you enter work years in that field.
A new Client starts with retirement age 65. A new Other adult starts without a retirement age. When an advisor changes a Client to Other adult, Kerdora clears retirement age unless that person owns income, in which case it preserves the age for income tied to their retirement.
Changing an Other adult with no retirement age to Client gives them retirement age 65, which can change their household's retirement year.
Use Member type to represent whether retirement planning is for that person. Don't enter an artificial birthday or life expectancy to neutralize a household member. Which household structure fits depends on your planning approach; review retirement timing and tax results after changing it.
Does every Child in Household count as a tax dependent?
Yes. A household's Child records in Profile → Household feed its derived dependent count in Taxes. Kerdora uses birthdays to determine under-17 and under-13 counts for a tax scenario's year; children outside the under-17 count contribute to other dependents.
A Child can have a birthday making them older than 18, but that doesn't make the record tax-neutral. There isn't a general per-child dependent checkbox or a field allocating dependency to one adult versus both.
A tax scenario can override derived counts, but that is a scenario-specific adjustment. It doesn't change a Child's saved member type.
Use Office notes for relationship context when adding a planning person would misstate your client's household. Appropriate dependent treatment remains an advisor judgment.
Can I record relationships, special needs, or separate dependency in Household?
No. Profile Household has no separate family-relationship, special-needs, or dependency-allocation field; its person types are Client, Other adult, and Child.
To record a special needs trust, use Planning → Estate, add a Trust document, and choose Special Needs Trust. Saving that document creates a Trust household entity.
Member fields capture name parts, preferred name, birthday, sex, and a photo. Advisors can record contact details for any person, and employment for a Client or Other adult. Clients have retirement age and life expectancy fields; an Other adult shows Retirement age only while an age is saved.
Estate planning has its own roles and designations, which serve different purposes from tax dependency.
Keep additional context in notes or supporting documents, and enter specific ownership and estate roles in their own controls. A note saying "dependent of one parent" doesn't change a derived tax count.
Neither a relationship description nor the choice of Child establishes legal dependency or a special-needs planning result. Review your client's planning and tax assumptions separately.
How do I add a Household member or entity?
In an advisor's Profile → Household view, Add member offers people and ownership entities.
Select Add member, then choose Client, Other adult, Child, Business, or Trust.
Enter a first name for a person, or a name for a Business or Trust. Add applicable person details and an optional photo.
For a person, select Add email or Add phone under Contact details if you have them now. You can also add them later in that member's record, which is also where Employment is entered. Business and Trust records have no Contact details.
Turn Create education goal on or off for a person; it starts on for a Child and off for a Client or Other adult.
Select the button matching your chosen type, such as Add client, Add other adult, or Add trust.
Adding an email here doesn't send a portal invitation; invitations stay a separate step. Kerdora matches CurrentClient texts and calls to phone numbers saved for household members.
With Create education goal on, saving the person creates a named Education Goal with default assumptions: 100% funding, $40,000 current cost, and ages 18–22. It has no linked accounts, contributions, or lump sums. Review it in Goals.
Plan Setup's people-entry steps use the same underlying records. Check Household before creating someone again just to complete an initial setup step. Review the saved type and birthday before continuing.
Why doesn't Household life expectancy change after I correct a birthday?
In Profile → Household, a Client's Life expectancy can be fixed even when its original number was calculated from that person's birthday. When an advisor adds a Client with a valid birthday and the life-expectancy field is shown, Kerdora saves that displayed number as a fixed value. A later birthday or sex edit won't recalculate it.
To resume calculation, open that Client's details drawer and select the circular-arrow icon beside Life expectancy. The field then follows the current birthday and sex. Review the resulting planning horizon before relying on Retirement.
A new Client without a valid birthday stays calculated unless a number was entered. Client-created members keep calculated life expectancy because the client form doesn't show that planning field.
How do I add a Household member photo or family photo?
In Profile → Household, advisors can add a member photo in a person's Photo field, or a household picture in Family Photo under Household Details. Clients have these photo fields on their Household page too.
Open the member's record, or find Family Photo in Household Details.
Select Upload, choose a picture (or drag one onto the photo area), adjust its crop, then select Upload in the crop dialog.
For an existing picture, use Change photo → Upload new to replace it, Adjust to change its crop, or Remove to clear it. After adjusting a crop, select Save.
Advisor member drawers and Family Photo save immediately. A client editing a member confirms with Save changes; when adding a person, finish the member's add action. Uploading a photo doesn't add a separate person or change a member's planning type.
How do I remove a household member?
An advisor in Profile Household, or a client on the portal's Household page, opens a person's record and selects Delete member. Kerdora blocks deleting the last Client.
Open the intended member and choose Delete member.
Review the dependency list if one appears.
Select the correct replacement for every listed relationship, then confirm Delete.
Check affected accounts, liabilities, income, insurance, Education Goals, and Tasks afterward.
The dependency dialog's Delete button stays enabled even with missing replacements. Any item left unassigned keeps pointing to the deleted member.
Select a replacement for every listed item. If no valid replacement exists, cancel and correct that item first.
Removing a planning member and managing portal access are separate checks. Use Inviting a Client to the Portal for access changes, and contact Support before proceeding when relationships are unclear.
What is the difference between a Household Business entity and a Business asset?
In Profile Household, a Business entity is an ownership identity that can own eligible accounts. It doesn't by itself add business value to a household's balance sheet.
In Profile Accounts, a Business asset holds ownership value. The Business planning module holds detailed operating, valuation, and exit assumptions and can link to that asset.
These records can describe the same business for different purposes. Don't enter the same ownership value in 2 included assets merely because you also created a Household entity.
See The Business Owner Module: Valuation, Cash Flow, and Exit Planning for valuation and exit mechanics. Use Account Types in Kerdora for owner eligibility.
When should I add a Trust to Household?
In Profile Household, add a Trust when an eligible account needs a trust owner and you aren't also about to add its Trust document in Estate. The Trust investment subtype requires a Trust entity.
If you will record the document, start in Planning → Estate → Add Document. Saving a new Trust document creates a new household Trust; that form has no existing-Trust selector.
Use the Trust it creates as the account owner. Adding a Household Trust first and the Estate document afterward creates 2 entities.
Estate captures trust type, trustees, and funding status; the Household Trust drawer edits its name. These records don't transfer assets or complete legal documents.
For duplicates, identify the Trust linked to the document and review every ownership and estate reference before removing another Trust. The deletion dialog handles only its listed dependencies, so contact Support if you can't confirm the remaining links.
What can clients change in Household?
On the portal's Household page, clients can add an Adult or Child, edit a person's name parts, preferred name, birthday, sex, or photo, and delete people.
In Household Details, clients can also change Household Name, State, and Filing, and add or replace Family Photo. These fields save as soon as they change. These changes affect the same planning records advisors use.
To add a person, clients select Add member, choose Adult or Child under Relationship, enter the details, and select Add member. Existing-person edits use Save changes; Delete member opens the shared deletion flow. Neither role can delete the last Client through that flow.
A client-added Adult becomes a Client while fewer than 2 Clients exist, otherwise an Other adult. Only a new Client starts with retirement age 65.
Client-created Children don't automatically create Education Goals. Clients can't add Business or Trust entities, edit retirement age or life expectancy, or manage invitations from this editor. Advisors should review planning effects after clients add or remove people.
Which Household members can use the portal?
Profile → Household offers new personal portal invitations for Clients. Other adult, Child, Business, and Trust records don't qualify for new personal invitations.
An Other adult who already has portal access keeps an access row so an advisor can revoke it. Changing Client to Other adult doesn't revoke existing access. An Other adult can also still use an invitation link received while saved as Client.
Revoke removes that person's access to this household. If that person must never sign in again, contact Kerdora Support right after revoking.
Advisors manage invitations and household access. A client adding an Adult on Household doesn't itself send an invitation. Review member type separately from portal access; Inviting a Client to the Portal explains invitation choices.
How do I edit a Household member's name, contact details, and employment?
An advisor can edit a person from Profile → Household; member details save as they change, without a separate Save button.
Open a person's member record in Profile → Household.
Fill in First name, Middle name, Last name, and Suffix as needed. Preferred name is what Kerdora calls that person in phrases; it isn't part of their full name.
In Contact details, select Add email or Add phone, or edit an existing entry. Contact entries save when you leave their fields. Use a row's menu to choose Make primary or Remove; Undo restores a removed entry.
For a Client or Other adult, enter Employer, Job title, and Started under Employment as needed.
Contact details and employment are advisor fields. Editing a contact email doesn't change an existing portal login. Clients can edit name parts and preferred name from their Household page, then select Save changes.
What does Check for changes do for a CRM-linked Household?
In an advisor's Profile → Household view, Check for changes compares a linked CRM household with Kerdora and lets the advisor choose which person and household details to take. Linked to Slant or Linked to Wealthbox identifies that connection; Open in Slant or Open in Wealthbox opens its source record.
Wealthbox in Kerdora is in a pilot for selected practices. If Wealthbox isn't listed in Advisor Settings → Integrations, contact Kerdora Support to ask for access.
Open a linked household's Profile → Household and select Check for changes.
Review CRM updates, conflicts, and new people. Choose the values and people to bring into Kerdora.
Select the action showing your chosen counts, such as Update 1 field. With nothing selected, Keep Kerdora's, stop asking keeps Kerdora's values and marks those differences reviewed.
Checking alone doesn't overwrite planning data. A CRM household or person disappearing doesn't delete Kerdora records through this review. A Slant-linked household's Stage, under Household Details, follows its type in Slant without this review. Clients don't see CRM notes or CRM connection controls.
How do I keep a Household's business and personal finances apart?
Adding a Business in Profile → Household lets an advisor name that business as an eligible account's owner. It doesn't create a second dashboard or automatically separate business money from household totals.
In Profile → Household, select Add member → Business, enter a name, and select Add business.
In Profile → Accounts, use a business checking account's Owner column to choose that Business.
Review whether the account should count toward household planning. Turn on Exclude From Plan? only when that account should be left out of planning totals.
An included business-owned account still contributes to household totals. Avoid counting the same value in both a Business asset and another included account.
Exclude From Plan doesn't remove linked transactions from Spending. Currently it also removes an account from Spending's account filter and rule account choices, which can make an account-specific hide rule impossible to select.
Use transaction-level hiding for identified business transactions, or contact Support if you can't identify them safely. Which balances and spending belong in a client's plan depends on your planning approach.
