A teacher pension estimate is a result built from a member record, a plan formula, and assumptions about a future retirement. Two different results do not automatically mean the system made an error. First compare what went into each run; then investigate if the underlying record changed unexpectedly.
Retirement date can change several inputs at once
Moving the proposed date may add service, change the salary years used in an average, affect age-based factors, or change whether an early-retirement reduction applies. A later date can raise an estimate for one reason and lower it for another. Compare dates only after noting which assumptions the estimator updates automatically.
Plans use different designs. CalSTRS publishes age factors tied to its member’s age and benefit structure. Illinois TRS Tier II has its own age and service conditions, and Texas TRS uses tier-specific eligibility and reduction rules. None of those examples sets a rule for another system.
A new salary year can change the averaging period
For a plan that uses a final-average salary, a new year may enter the period used for the calculation while an older year drops out. If the newly included pensionable pay is higher, the average may rise; if it is lower, the average may fall. Systems define pensionable compensation and the averaging window differently, so a raise on a contract does not guarantee an immediate increase in the estimate.
Check the salary history and the dates it covers before attributing a change to the formula. A statement’s school-year or fiscal-year earnings may differ from W-2 wages or a calendar-year raise.
Service transactions change the record only when posted
A completed purchase or redeposit can add service under the plan’s rules; a refund can remove service tied to the refunded membership. An estimate may not reflect a transaction merely because you submitted payment or an application. Confirm that the system has completed the transaction and that the new service appears in the member record used for the estimate.
Also check whether the service counts for the benefit calculation, retirement eligibility, or both. Some special service credits have different treatment for different purposes.
A payment option can change monthly income
The maximum member-only pension and a survivor option are different payment promises. A continuing benefit for a spouse or beneficiary commonly lowers the member’s monthly amount, with the size depending on the plan’s available options and assumptions. That reduction is not necessarily an early-retirement penalty or a data error.
Compare the same payment option, beneficiary information, and survivor percentage across estimates. Check whether an automatic option or default beneficiary setting changed between runs.
| Input | What may change | First check |
|---|---|---|
| Retirement date | Service, age factor, eligibility, reduction | Same date and posted service |
| Salary period | Average pay as years enter or leave window | Covered pay by plan year |
| Service transaction | Credited service after purchase, redeposit, or refund | Posted transaction and its eligibility purpose |
| Payment option | Member monthly amount and survivor continuation | Same option and beneficiary assumptions |
| Projection | Future service or salary assumptions | Current record vs projected scenario |
Projection assumptions make two estimates unequal
One estimate may use service earned to date; another may project continued work or future salary growth. Calculators may also differ from an annual statement because of update timing, a different retirement date, or data inputs that have not posted to the system record. Official tools explain their own assumptions, and those assumptions are not interchangeable across systems.
Before deciding that the pension changed, write down the date of each run, service total, pensionable salary or average, tier, formula or age factor, reduction, payment option, and projected future work or pay. If the tool does not show an input, ask the system what it assumed.
- Save both dated estimates and their printed assumptions.
- Match tier, service, salary, and payment option.
- Change only one scenario input and rerun the official estimator.
- Check whether any underlying member record changed.
- Ask the system to explain an unexplained record or formula change.
Change one input at a time
To understand what drives a difference, make a controlled comparison. Keep the plan tier, salary, service, and payment option fixed while changing only the retirement date. Then restore the original date and change only the survivor option or a service transaction. Use the plan’s own estimator and save each result with its assumptions.
This method helps identify whether the change comes from another year of service, a new salary period, an age factor, a reduction, a payment choice, or a changed record. Avoid comparing a calculator that projects several future years with a statement based on current posted service as though they were the same scenario.
For example, if a later date increases projected service but lowers the monthly estimate, inspect whether that date also crosses an age threshold, introduces a reduction or changes the salary window. If the amount changes after selecting a survivor option while all other inputs remain fixed, the payment choice is the likely driver. These comparisons reveal a cause; they do not replace the system’s formal calculation.
When a changing estimate needs follow-up
Follow up if tier or membership date changes without explanation, service disappears, pensionable salary drops despite unchanged covered pay, a completed purchase is missing, or the calculator and statement disagree after you match their dates and inputs. Ask the system which record field or rule caused the difference and request a written explanation. Payroll can confirm earnings and work dates; the retirement system confirms how they affect credited service and benefits.
Keep dated PDFs or screenshots of estimates, plus the inputs and any written response. An estimate is not the final award, but a consistent history makes it easier to spot a data error before a retirement application is processed.