Derived values are fields Kerdora calculates from other saved client data. Manual overrides let the advisor use a different value when the calculation does not fit the planning decision.
Recognize the field state
A derived field displays the current calculated value and an edit control. When a manual override is active, the field uses the custom value and provides a control to return to the calculated value. The visual treatment can differ by workspace, so read the field help and override state instead of relying only on an icon color.
A standard manual field has no calculated source to restore.
Use an override
Review the current derived value and its source explanation.
Confirm the source data is complete.
Enter an override only when the client-specific assumption should differ.
Document the reason in the applicable note or planning context.
Revisit the override when the plan changes.
Use the restore control to clear the override and return to the current calculation. Restoring does not recreate old source data; it recalculates from what is saved now.
Where derived values appear
Goals can derive timing, spending, target balances, or savings from household records and calculator results. Insurance analysis can derive income, work years, resources, net worth, and other coverage inputs. Taxes can derive scenario inputs from Profile, account contributions, Social Security, entities, extracted returns, or supporting worksheets.
The exact source is field-specific. Do not assume two similarly named fields use identical records.
When source data changes
A field that remains derived can update when its source changes. A manual override normally remains fixed until it is changed or cleared. This is useful for a deliberate planning assumption but can become stale.
Review overrides after changes to household members, birth dates, income, spending, accounts, contributions, policies, Goals, or tax records.
Troubleshoot an unexpected value
Open the help or source explanation for the field.
Check missing people, dates, owners, amounts, and frequencies.
Confirm the expected account, Goal, policy, or scenario is included.
Look for an active manual or filed-line override.
Restore the derived value if the override is no longer intentional.
Reopen the analysis after correcting the source.
Do not override a value merely to make the result look expected. Fix the source when it is wrong; override only when the source is correct and the planning assumption intentionally differs.