Most people see a number. This is what a real tax position looks like.
PRISM shows the structure behind the result—so the position, the drivers inside it, and what would make it change are visible before the consequence becomes something you have to live with.
A tax number is an output. A tax position is the state behind it.
The number shows the result. The position shows what is shaping it.
Because the number may look finished long before the position is actually understood.
This isn't an estimate. It's your current position.
There is a moment when the answer looks complete.
The spreadsheet is filled out.
The calculator returned a result.
The number looks finished.
That usually feels final.
But the number does not show what is shaping it.
It does not show what assumptions are carrying it.
It does not show what would change if the situation moved.
That is where most people stop too early.
A calculator gives you an answer.
A real position shows:
- what the outcome is
- what is driving it
- what thresholds are starting to matter
- what remains unresolved
- what would make it change later
That is the difference between a static result and a modeled state.
The number may be accurate.
The position is what makes it usable.
Decision Preview
This is what a real tax position looks like.
This is a real modeled position, not a simplified example.
This is how real positions present themselves.
The result is visible. The structure behind it is what makes the position legible.
This position is being shaped by high ordinary income, current-year withholding that is not keeping pace, and threshold effects that materially affect the result.
The effective rate reflects the blended burden across the full modeled position.
The marginal rate shows where the next dollar lands.
The remaining position shows that liability and payments are not currently aligned.
That is what turns a result into a usable view of the current state.
This preview is visible now. It is not preserved.
If this changes, the context behind it is lost and must be rebuilt.
See the position first. Preserve it before the structure disappears.
A preview shows the current state.
A Decision Record preserves it so it can be:
- revisited later
- rerun when inputs move
- compared against another path
- connected to another decision
- returned to with the context still intact
Without that, the result is temporary.
Without that, the logic fragments:
- part memory
- part screenshots
- part rework
- part guesswork
Without a record, the reasoning is lost the moment the session ends.
With a Decision Record, the reasoning stays attached to the outcome.
Turn this into a Decision Record you can continue working from.
This is where the decision becomes yours—and stays usable.
See the position before it gets reduced to a number you have to explain later.
Run a real scenario and see the current position, the drivers behind it, and what would make it change.
Because the number may be immediate. The consequences usually are not.
You either keep the reasoning attached to the outcome—or try to reconstruct it later.