Most new-client problems come from a source record, assignment, or visibility decision that was skipped. Use this list before relying on the analysis or inviting the client.

Extraction proposes structured information from documents and context. It can misread an owner, amount, frequency, tax treatment, or record type.

Fix: Compare each proposal with the source. Resolve duplicates and apply only the records you want saved.

A monthly income entered as Annual, or an annual amount entered as Monthly, can distort cash flow, Goals, and Financials.

Fix: Confirm that amount and frequency describe the same number. Check dates and ownership at the same time.

A second manual record can double-count assets, holdings, income, or savings.

Fix: Search the existing Profile and linked records before adding a manual account. Refresh or correct the existing record when it represents the same asset.

Missing adults or children can affect taxes, education Goals, retirement timing, portal access, and ownership-based analysis.

Fix: Complete Profile Household first. Add each relevant person and assign account, income, liability, policy, and portal records to the correct owner.

An account can exist in Profile without being assigned to a Goal. Kerdora does not assume that every retirement account belongs entirely to Retirement or every savings account belongs to Liquidity.

Fix: Use Assigned Accounts or Goal Mapping → Assignments. Avoid over-assignment and remember that a remaining assignment can change when fixed assignments change.

The household savings comparison in Goals and Gap Analysis can include monthly savings and employer contributions across available bank and investment accounts, even when those amounts are not assigned to a specific Goal. An individual Goal's Current contribution measure is assignment-specific.

Fix: Use the household comparison to discuss overall capacity, then use the Goal table and assignments to explain where the savings are allocated.

Retirement, cash-flow, and Gap Analysis results need a coherent spending plan and correctly timed income. A blank or implausible value can make a result look funded or underfunded for the wrong reason.

Fix: Enter a supportable spending amount and review future income with the correct owner, amount frequency, and start and end timing.

A manual override can hide an incorrect birthday, balance, spending value, retirement age, or income record.

Fix: Correct the source record when the client fact is wrong. Override only when the planning assumption should intentionally differ, and document why.

The Retirement projection is deterministic. It follows the selected timing, spending, income, taxes, assets, savings, returns, withdrawal order, horizon, and legacy assumptions. It is not a Monte Carlo probability of success.

Fix: Review Planned and Sustainable with the Portfolio, Spending, Income, and Gap Analysis views. Explain the assumption set rather than presenting one result as a guarantee.

Insights surface potential opportunities, concerns, and reminders. Some require more client context; some should be dismissed.

Fix: Open the source detail, confirm the fact, and use advisor judgment before adding an Insight to Changes.

A Change records the planning recommendation. A Task records the action someone must complete.

Fix: Write the recommendation as a Change, then create or link the advisor or client Tasks needed to carry it out.

Plan-hygiene problems now live in Office → Plan Cleanup, separate from Insights. Office Home provides orientation but is not a complete list of every missing field.

Fix: Review Plan Cleanup before relying on a plan that looks incomplete. Follow each material issue to its source record.

Completing setup hides the temporary Plan Setup navigation item. It does not prove that every assumption is correct.

Fix: Review the setup summary, then inspect material Goals, planning results, Guide visibility, and portal invitations before completing the flow.

Saving, visibility, and default selection are separate decisions. A client can receive the wrong first experience if an old Guide remains visible or no appropriate Guide is the default.

Fix: Preview the Guide, review visible Guides, and set the intended visible Guide as the client default before sending an invite.

Each adult has a separate signup link and linked email.

Fix: Use the Invite control on the correct adult, select the starting experience, copy that person's current link, and send it only to that person.

Confirm that:

If a result still looks wrong, trace it through Profile, saved assumptions, assignments, and linked-data freshness before adding another record or override.