Before you read a recommendation, look at what went into the calculation. Are the numbers yours, or are they defaults the tool filled in? Did you enter your actual take-home pay or your gross salary? Did you account for all your fixed expenses, or just the obvious ones?

A recommendation is only as good as the inputs it is based on. If you entered rough estimates, treat the output as directional. It is useful for orientation, but not precise enough to make major decisions from. If you entered careful, verified figures, you can put considerably more weight on the result. The report itself can't tell you which situation you're in. That call belongs to you.

Good decision reports distinguish between results that rest on solid data and results that depend on projections or estimates. High-confidence outputs are typically built on things you can verify: your current salary, an existing loan balance, a tax rate you can look up. Low-confidence outputs depend on something you're estimating or predicting: future income growth, investment returns, how long a job search might take.

When confidence is low, the recommendation is still useful. But think of it as a starting point rather than a conclusion. A useful mental exercise is asking what would have to change for the recommendation to flip. If a small shift in one assumption reverses the answer, that assumption is worth examining more carefully before you act on the output.

Decision reports sometimes surface flags. Conditions that could significantly change the outcome if your situation differs from a standard assumption. A common example is around tax filing status. If the tool assumes you're a single filer when you're actually married filing jointly, that one assumption can shift estimated take-home pay by thousands of dollars a year.

Flags are worth taking seriously because they usually point to the input categories where small changes have the biggest downstream impact. If a report flags your emergency fund as below the recommended level, it's not just noting a data point. It's telling you that your current setup creates financial vulnerability that affects the whole picture.

The right response to a flag isn't to dismiss it. It's to check whether it applies to your actual situation, and if it does, to consider how the recommendation changes once you account for it.

A downloadable PDF of your decision report captures your inputs and outputs at a specific moment in time. It's a snapshot. Something you can file, share, or refer back to later. It's not a permanent financial plan, and it shouldn't be treated as authoritative just because it's formatted like a document.

PDF reports are useful for showing a financial professional what you've already worked through, for keeping a record of decisions and the reasoning behind them, or for comparing your situation across different time periods. If you're sharing a report with someone else, make sure they understand the inputs it was built on. A recommendation that made sense with your specific numbers might look very different with a different set of figures.

Reading a decision report well means starting with the inputs, taking confidence indicators and flags seriously, and understanding what kind of data underlies each number. The recommendation is a starting point, not an endpoint. The more you understand about where the figures came from, the better equipped you'll be to know how much weight to give them and when to dig deeper before you act.