The person and the choice
Sam Brooks's decision starts before any input is entered
Sam Brooks, an operations manager choosing between a stable role and a growth-stage offer, is the fictional decision-maker in this worked example. Sam's current job has dependable benefits and a short commute; the new offer has higher salary, a signing payment, equity, more remote days, and transition risk. The goal is to turn that situation into a traceable case without pretending the assumptions describe a future that is certain.
The choice is not simply between the largest and smallest displayed values. It is whether the modeled result gives Sam Brooks enough evidence to act, which number affects current cash, which number remains conditional, and which unanswered term could reverse the interpretation.
The profile is deliberately realistic rather than universal. Readers should borrow the method—document facts, normalize units, run the engine, reconcile outputs, vary one assumption, and record omitted risks—not copy Sam Brooks's inputs into a different situation.
What is known
Build the evidence ledger before building the scenario
Each offer's cash terms, eligibility dates, benefit costs, retirement rules, vesting calendar, paid leave, location schedule, work hours, commute, transition payments, clawbacks, and written contingencies belong in the factual input set. Those items anchor the base case. They receive the label “input” only when a document, record, or current policy supports them; otherwise they remain an assumption even if the value feels likely.
Sam should compare complete offer letters, bonus and commission plans, benefits summaries, retirement terms, equity documents, schedule and location policy, leave rules, signing or relocation clawbacks, contingencies, and the current employer's retention terms. For the worked example, the visible input table highlights the fields that explain the result while the typed fixture supplies the calculator's complete validated object.
That distinction prevents a common reporting problem: showing six attractive inputs while hidden defaults do most of the calculation. The fixture is tested against the schema, and the displayed lead metric is recalculated by the production engine. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
| Field | Value | Role |
|---|---|---|
| Current role | $110,000 base; 3 office day(s)/week | Input |
| New offer | $120,000 base; 1 office day(s)/week | Input |
Preparing the inputs
What Sam Brooks has to normalize before pressing calculate
One-time and recurring items must be separated, equity assigned to vesting years, benefits valued consistently, work costs subtracted, and total job time measured over the same projection horizon for every offer. The normalization step creates a common clock and compatible units, but it does not erase restrictions or uncertainty. Cash remains cash, time remains time, and conditional value remains labeled.
In this case, the three operational layers are normalized annual compensation, job costs, time, and transition, and durability, priorities, and break-even. Each is prepared separately so the engine can connect them in the right order.
A useful preflight check is to ask whether every percentage has a defined base, every annual amount has a recurrence rule, every date belongs to the correct period, and every scenario value has an owner. Ambiguous units are resolved before calculation, not explained away afterward. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
Sam Brooks's result is reproducible because the fixture, engine path, and assumptions remain separate.
Why these assumptions
Choose a base case that can be defended, not one that flatters the outcome
Signing payments, bonus expectation, equity vesting, benefits, office attendance, commute cost and time, unpaid extra work, relocation or equipment costs, growth assumptions, and projection horizon can flip the leader. The base fixture selects explicit values for those variables so the result can be reproduced. It does not claim they are the most likely values for every reader.
For Sam Brooks, the strongest assumption is the one closest to a written term or recent observed pattern. The weakest is a future outcome controlled by a market, employer, client, schedule, or household event. Those two should never carry the same confidence label.
A conservative case should stress one credible downside without changing unrelated facts. A favorable case should do the same in the other direction. This structure shows which variable causes the spread instead of producing two opaque bundles. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
Calculation walkthrough
Follow one case through the actual PayArith engine
The engine builds year-by-year offer ledgers, calculates expected and recurring compensation, subtracts transition and work costs, divides by total job time, accumulates value, estimates break-even, and keeps personal priority scores outside dollar totals. The audit table below is derived from that engine result. The article does not reimplement the formulas, which prevents prose examples from drifting away from the calculator's validation, ordering, and rounding behavior.
Adjusted job value subtracts costs from expected compensation because a dollar required to take or perform the job is unavailable to the household. Effective hourly value then exposes differences hidden by annual totals. The formula block names the central relationship, while the step rows reconcile how the fixture reaches its displayed output. Each calculated value is labeled separately from the assumption that feeds it.
To audit the calculation, start with the first row and ask where its basis came from. Then carry the output into the next relevant stage. If a value cannot be traced, it should not be used as the reason for Sam Brooks's choice.
| Step | Basis | Calculated result |
|---|---|---|
| Current role | $129,670 expected total − $3,619 costs | $126,051 adjusted; $58/hour |
| New offer | $163,800 expected total − $1,191 costs | $162,609 adjusted; $78/hour |
What the outputs mean
Translate every result back into the decision
Year-one adjusted value captures immediate economics; recurring adjusted value removes one-time distortion; cumulative value shows when leads persist; effective hourly value includes job time; priority score records stated preferences without pretending they are cash. For Sam Brooks, those are not interchangeable scorecards. The metric that best describes long-term modeled value may be the wrong metric for a near-term cash constraint.
The headline strip is a navigation aid, not the whole analysis. The audit explains composition, the scenario chart explains conditional range, and the projection explains timing. A decision should cite the specific view that supports it. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
The text alternative under each chart repeats the plotted values in a table. That supports readers who cannot use the visual and also makes the numerical comparison easier to reconcile against the engine audit. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
The next view keeps the fixture constant and exposes the numerical spread. Read it to locate a decision boundary, then use the table to reconcile the plotted values without relying on color or shape.
| Scenario | Calculated value | Reference value |
|---|---|---|
| Current role | 126,050.8 | 126,050.8 |
| New offer | 162,609.2 | 152,609.2 |
The chart does not rank personal outcomes. It shows how the defined engine metrics move; the surrounding article explains whether the spread is liquid, recurring, sensitive, or incomplete.
The counterfactual
Change one condition and explain why the answer moves
The new offer can lead in Year 1 because of signing cash, fall behind after the payment disappears, then recover if equity vests as modeled or salary growth exceeds the current role. That alternative changes the relevant engine inputs while leaving the rest of the case intact. The resulting difference is therefore attributable to a named condition rather than a collection of favorable edits.
If the ranking changes, Sam Brooks has found a decision boundary. The next task is to verify how plausible that condition is and whether the household can tolerate being wrong, not to average the cases into a false point estimate.
If the ranking does not change, inspect the size and timing of the remaining lead. A numerically stable result can still be impractical when its value is illiquid, delayed, reversible, or dependent on staying in the role. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
What matters now
Separate current cash, recurring economics, and later value
Signing cash can pay transition costs or strengthen savings immediately, but it may carry a clawback. Benefits and lower job costs improve monthly economics without appearing as payroll, while equity may not fund near-term obligations. This is the part of the example most likely to affect an immediate action. A household cannot pay a current obligation with a future scenario value, even when both appear in the same long-term comparison.
Base salary can compound through raises; recurring benefits persist while eligible; equity depends on vesting and value; commute repeats every working year; and a role with better growth may change future earnings beyond the modeled horizon. The projection makes that sequence visible but does not predict persistence. It repeats the stated growth, schedule, vesting, cost, or availability assumptions across the chosen horizon.
A good decision memo records three numbers: the Year 1 cash consequence, the recurring annual difference after one-time effects, and the cumulative result at a horizon the person may realistically remain. That memo is more informative than one lifetime total. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.
A single-year lead can disappear, widen, or reverse. The projection uses the same stated horizon so timing remains visible rather than being compressed into one lifetime total.
| Period | Primary path | Comparison path |
|---|---|---|
| Year 1 | 126,050.8 | 162,609.2 |
| Year 2 | 255,771.2 | 319,268.4 |
| Year 3 | 389,271.3 | 480,099.1 |
| Year 4 | 526,664.5 | 645,226.4 |
| Year 5 | 668,067.5 | 804,779.3 |
Use the projection to ask when value appears and which assumption repeats. Do not treat the final point as more certain merely because it is farther to the right.
Outside the output
The engine can be right while the decision is still exposed
Bonus, equity, future raises, return-to-office policy, workload, promotion, employment duration, and benefit premiums are uncertain. A transparent range is more honest than one supposedly precise winner. The worked example isolates those uncertainties rather than hiding them inside a single expected label.
The main risk is accepting compensation that exists only under several favorable assumptions while giving up a known role, tenure, coverage, flexibility, or a short commute that has immediate household value. That risk is not an arithmetic defect; it is information outside or beyond the model. It belongs beside the result because it affects how much confidence Sam Brooks should place in the numerical lead.
Manager trust, role scope, learning, mission, stability, schedule control, caregiving fit, health coverage, commute reliability, and future marketability deserve a separate decision ledger beside the financial model. None of those factors should be converted into invented dollars merely to force one total. A separate qualitative ledger keeps them explicit and allows Sam Brooks to choose a financially lower path for a stated reason.
Decision takeaway
What Sam Brooks can responsibly conclude from this worked case
This fixture proves how a validated set of a multi-offer job decision inputs travels through PayArith's production calculation engine. It proves the arithmetic relationship and the displayed reconciliation; it does not prove that future assumptions will occur.
Before acting, Sam Brooks should ask: Which offer terms are written, recurring, contingent, clawed back, vesting-dependent, policy-dependent, or still subject to manager discretion? The answer should update a named input or document an unsupported risk. Either outcome improves the decision more than adding another generic scenario.
The practical takeaway is to choose from the range that the household can fund and tolerate, using the metric tied to the actual objective. The highest modeled value is relevant only after its timing, availability, fragility, and nonfinancial cost are acceptable. In this a multi-offer job decision analysis, that boundary is applied to Sam Brooks's stated facts and assumptions.