The person and the choice
Taylor Morgan's decision starts before any input is entered
Taylor Morgan, a clinical operations specialist comparing two work arrangements, is the fictional decision-maker in this worked example. Taylor is comparing a $90,000 salaried role with a $40 hourly role whose weekly schedule ranges from 36 to 45 hours and may include overtime. 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 Taylor Morgan 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 Taylor Morgan's inputs into a different situation.
What is known
Build the evidence ledger before building the scenario
Base salary or wage, expected schedules, paid weeks, overtime eligibility and multiplier, leave treatment, benefits, retirement, office pattern, recurring work costs, commute, and required unpaid time should be verified separately for each job. 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.
Taylor needs the offer letters, classification and overtime statement, guaranteed-hours language, scheduling and cancellation policy, shift rules, paid-leave policy, benefits eligibility, retirement terms, attendance expectations, and any collective agreement. 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan's stated facts and assumptions.
| Field | Value | Role |
|---|---|---|
| Salary base | $90,000 | Input |
| Salary extra time | 5 hours/week | Assumption |
| Hourly base | $40/hour | Input |
| Overtime multiplier | 1.5× | Assumption |
| Hourly expected schedule | 40 regular + 5 overtime hours/week | Assumption |
| Projection | 5 years | Input |
Preparing the inputs
What Taylor Morgan has to normalize before pressing calculate
Hourly work needs explicit weeks and regular-versus-overtime hours; salary needs an estimate of uncompensated extra time. Both sides need the same benefit scope, cost categories, annual horizon, and total-time definition. 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 annualized schedule and overtime, benefits, leave, and work costs, and total job time and break-even pay. 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan's stated facts and assumptions.
Taylor Morgan'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
Guaranteed weekly hours, overtime access, overtime eligibility, paid weeks, unpaid leave, salaried extra hours, benefit eligibility, shift cancellation, office attendance, and commute can overturn a simple advertised-rate comparison. 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 Taylor Morgan, 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan's stated facts and assumptions.
Calculation walkthrough
Follow one case through the actual PayArith engine
The engine annualizes salary and three hourly schedule scenarios, calculates overtime, aligns paid leave, adds employer value, subtracts work costs, totals job time, projects annual value, and solves bounded break-even rates, hours, or salary. 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.
Dividing salary by 2,080 assumes 52 paid forty-hour weeks and ignores extra time. The model uses actual paid and worked schedules so adjusted hourly value describes value per modeled hour of life committed to the job. 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 Taylor Morgan's choice.
| Step | Basis | Calculated result |
|---|---|---|
| Salary | $96,480 cash + $12,050 employer value | $105,632 adjusted; 2,185 hours |
| Hourly expected | $103,282 cash + $10,918 employer value | $111,114 adjusted; 2,328 hours |
What the outputs mean
Translate every result back into the decision
Annual cash shows payroll income; adjusted recurring value adds comparable employer value and subtracts work costs; total job time includes required time; effective hourly value combines numerator and denominator; break-even identifies a conditional boundary. For Taylor Morgan, 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan'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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan'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 |
|---|---|---|
| conservative | 90,282.7 | 105,632 |
| expected | 111,113.8 | 105,632 |
| strong | 122,444.4 | 105,632 |
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
At 36 hours without overtime the hourly role may trail; at 45 hours with an overtime premium it may lead, while the salary result changes mainly through unpaid extra time and benefits. 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, Taylor Morgan 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan's stated facts and assumptions.
What matters now
Separate current cash, recurring economics, and later value
Salary usually smooths payroll across weeks. Hourly cash can fall when shifts disappear or unpaid time increases and rise sharply when dependable overtime is available, producing a wider household budgeting range. 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.
Salary growth compounds from a stable base, while hourly earnings depend on rate growth and available hours. Benefits, leave, retirement, training, and promotion paths may diverge even when first-year adjusted value is close. 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan'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 | 105,632 | 111,113.8 |
| Year 2 | 108,634.4 | 114,332.8 |
| Year 3 | 111,726.9 | 117,648.4 |
| Year 4 | 114,912.1 | 121,063.5 |
| Year 5 | 118,192.9 | 124,581 |
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
Hours, overtime, cancellations, extra salaried work, leave use, eligibility, commute, and future raises are uncertain. Conservative and strong schedules should bracket the plausible range without calling either a forecast. The worked example isolates those uncertainties rather than hiding them inside a single expected label.
The decisive risk is relying on overtime that is technically possible but operationally scarce, or ignoring recurring unpaid salary hours because they never appear as a deduction on a paycheck. 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 Taylor Morgan should place in the numerical lead.
Schedule control, fatigue, predictability, shift choice, caregiving, legal protections, promotion path, union coverage, and the ability to disconnect after a shift can justify a lower modeled annual total. None of those factors should be converted into invented dollars merely to force one total. A separate qualitative ledger keeps them explicit and allows Taylor Morgan to choose a financially lower path for a stated reason.
Decision takeaway
What Taylor Morgan can responsibly conclude from this worked case
This fixture proves how a validated set of a salary-versus-hourly comparison 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, Taylor Morgan should ask: Which hours are guaranteed, which qualify for overtime, how are cancelled shifts and leave paid, and when do benefits begin or end as hours change? 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 salary-versus-hourly comparison analysis, that boundary is applied to Taylor Morgan's stated facts and assumptions.