This page answers a few common questions that come up after reading the other pages.

It is not a full walkthrough or technical reference. For that, see Walkthrough, Formula Reference, and Modeling Assumptions.

Why calculate annually instead of monthly?

Reserve fund studies are built as annual planning models.

Costs are forecast by fiscal year, contributions are set through annual budgets, and reserve fund cash flows do not usually follow a perfectly smooth monthly pattern in practice. A monthly model could be built, but in most reserve fund studies it would add complexity and assumptions without clearly producing a more reliable result.

The Reserve Sense Benchmark Method therefore uses one consistent annual model.

The Legacy Method also computes its values on an annual basis. The real issue is not annual versus monthly. The real issue is whether the annual model uses coherent timing assumptions and is applied consistently.

Why do cash flows use different timing?

The Benchmark and the cash flow schedules serve different purposes.

The Benchmark is an idealized, point-in-time model. It uses one fixed set of timing assumptions so that Benchmark Balances and Benchmark Contributions have a clear meaning. It calculates each component separately. In that model, expenditures are applied first, interest is earned during the year, and contributions are added at the end of the year. That makes the Benchmark conservative and internally consistent.

A cash flow schedule is different. It is a practical planning tool for a pooled reserve fund. In real life, money moves continuously throughout the year, components can effectively borrow from the shared fund balance, and expenditures do not occur in a perfectly isolated vacuum. For that reason, cash flow schedules are commonly presented using the standard reporting convention that treats that year’s income as available within the same year.

In that sense, the Benchmark timing rules are stricter and more conservative, while the cash flow schedules are a little more flexible and forgiving as practical planning tools.

Does the Reserve Sense Benchmark Method have anything like Reserve Requirements?

Not as a separate shortcut formula.

In the Legacy Method, future-year Reserve Requirements are commonly carried forward from the report-year formulas through a simple formula.

That shortcut is convenient, but it is not mathematically appropriate. Each component’s Benchmark values change over time, especially during replacement years. The RR formula assumes that ARFA does not change over time, so it cannot track those changes properly.

The Reserve Sense Benchmark Method does not use that kind of shortcut. Instead, it recalculates the Benchmark directly for each fiscal year being modeled, using the component’s updated age, remaining life, projected replacement cost, and the rates used in the study.

For each year, the sum of each component’s values produces that year’s:

  • Ideal Opening Balance
  • Ideal Contribution
  • Ideal Closing Balance

Those values are calculated from that year’s component state and that year’s assumptions. They are not created by simply rolling one year’s result forward.

Why not keep using the Legacy Method if it is familiar and seems "close enough"?

Because the problem is not just that the Legacy Method is approximate. The problem is that, in its commonly used form, it does not operate as one coherent year-by-year funding model.

That matters in practice. The Legacy Method does not produce errors that are reliably high or reliably low. Depending on the component’s age, lifespan, and the rates used, its recommended ARFA may be above or below the mathematically consistent Ideal Contribution.

So "close enough" is not something the user can safely assume. The method can miss in either direction, and the size of the mismatch is created by the math itself, not just by uncertain inputs. The difference is not merely theoretical or marginal. It materially changes the projected funded position. Over time, especially when RR is carried forward through a full study period, the gap can grow large enough to change real budgeting decisions.

The problem becomes more serious across a full study period. In common practice, later-year RR values are carried forward using a flat nominal ARFA. Over time, that can cause the projected funding path to drift far away from a coherent Benchmark result.

Familiarity is understandable, and existing spreadsheets can create real inertia. But those are workflow reasons, not mathematical advantages. Once a more coherent method is available without adding extra work to each file, the question becomes why an inconsistent method should still be preferred.

The Reserve Sense Benchmark Method was built to avoid that problem. It does not change the goal of Benchmark funding. It calculates that goal through one internally consistent model, so the balances and contributions mean the same thing from year to year.

Do I need to build these formulas manually?

No.

The Reserve Sense Benchmark Method is a published method, so it can be implemented in any suitable tool. But you do not need to build and maintain the formulas yourself.

Reserve Sense software applies the Reserve Sense Benchmark Method directly and handles the Benchmark calculations automatically. It recalculates each fiscal year’s values and handles staged replacements, one-time expenditures, funding model calculations, and annual rate updates, so you can focus on inspection, analysis, and advice rather than maintaining spreadsheet formulas.

Curve edge