Insights surfaces planning findings derived from the current client data. Open Planning → Changes → Insights. Use Insights to identify possible opportunities, concerns, and reminders, then apply advisor judgment before creating a Change.

These labels describe the finding, not its certainty. A rule cannot know every client circumstance.

Insights are organized into the planning areas Insurance, Cash Flow & Goals, Investments, Tax Planning, and Estate & Beneficiaries. Expand a group to review its findings. Use the kind key to narrow the current tab to Suggested changes, Observations, or Reminders.

The group tells you where to investigate; it does not decide which professional owns the recommendation. A tax finding may still require CPA coordination, and an estate finding may require an attorney.

Dismissal is reversible. Restore a dismissed finding when new client facts make it relevant.

Expand it and read the explanation. Use Open details when available to inspect the source account, Goal, policy, income, tax scenario, or other subject.

Some findings include a detail grid with the current value, target, gap, date, account, or other inputs used by the rule. Treat those values as a review trail, not a substitute for opening the source record. A finding can be mathematically correct and still be inappropriate because the plan is incomplete or the client has an off-platform arrangement.

Confirm:

Common source-data checks include:

If a finding changes or disappears after you correct source data, that is expected. Insights are recalculated from the current plan rather than maintained as manually edited recommendations.

Choose Add to Changes, select the visible category, edit the recommendation, decide how it should be presented, and set an optional target date.

The Change should describe the advisor decision, not simply repeat the rule. Add linked Tasks for execution.

For example, a finding about insufficient umbrella coverage may support a Change such as “Obtain a $2 million umbrella policy after confirming the required auto and homeowners liability limits.” Linked Tasks can capture the advisor's quote request and the client's application. The Insight identifies the issue; the Change records the adopted recommendation; the Tasks record the work.

Reminders do not offer Add to Changes. They are date-driven review prompts. Dismiss the reminder after you have handled it or leave it available until the review is complete.

Dismiss when the finding is factually inapplicable, already addressed outside the rule's visibility, immaterial, or deliberately not recommended. Keep enough advisor context in Notes or the planning record when the reason will matter later.

Dismissal does not change the underlying client data. Use Dismissed to review prior decisions and Restore when you want the finding returned to active review. Added to Changes preserves the relationship to the linked Change. Restoring a converted finding removes that linked Change and returns the finding to active review, so confirm that you intend to remove the adopted recommendation before restoring it.

Plan Cleanup contains missing or inconsistent data that weakens the plan. It lives under Office → Plan Cleanup. Fix cleanup issues at the source.

Insights contains findings that can remain valid even when the data is complete. Do not create a client recommendation from a missing-field warning that should be corrected internally.

Examples of Plan Cleanup work include a missing balance, owner, payment amount, or inconsistent record. Examples of Insights include a possible coverage gap, a savings or debt opportunity, an investment concern, an estate or beneficiary review, or a planning deadline. Resolve cleanup first when the missing fact can materially alter the Insight.

Rules can cover household milestones, cash flow, savings, debt, Goals, Investments, insurance, Taxes, Estate, beneficiaries, property, Social Security, and other planning relationships. The set evolves with the product.

Rules use the saved client data and derived values available to them. A finding is only as reliable as those inputs.

Some cash-flow and protection findings use values derived from the broader plan rather than one visible field. Investment findings can depend on holdings and classifications. Goal findings can depend on account assignments, timing, and return assumptions. Tax findings depend on the selected scenario and modeled records. Open the source and understand the comparison before discussing it with the client.

Kerdora does not guarantee that every planning issue appears as an Insight. Thresholds and rule logic are product defaults, and the current Insights workspace is not a user-configurable rule engine. Continue the normal professional review even when To review is empty.

These examples describe the kinds of relationships Kerdora can surface. The exact set changes as the platform evolves, so use the labels and evidence on the current card rather than relying on a fixed catalog.

Clients do not see the Insights review workspace, dismissed findings, or advisor decisions that were not added to Changes and included in a Guide. This lets the advisor review noise and context before delivery.

After adding a finding to Changes, rewrite it in clear client-ready language and decide whether that Change belongs in the client's Guide. The full advisor Changes workspace also remains separate from the portal. Client-assigned Tasks are delivered through the Tasks experience; they are not a substitute for including the recommendation in a Guide.

For a meeting review, start with Office Home and Plan Cleanup, then use Insights and Changes together. Use the top-right Insights indicator or the Changes side panel when you need a quick review without leaving the current workflow. Return to the full Insights tab when you want to work systematically by status and planning area.

Insights should make review faster; they do not replace the advisor's analysis.