Start with obligations, not yield
List expected payments by time: today, in the coming weeks, in several months and later. For each, note whether the date is known, whether the expense can be postponed and what delay would cost. Then make a corresponding resource table: amount, earliest confirmed access date, exit conditions and possible loss. Do not replace that date with “usually fast.” If a resource depends on a sale, amount and access time may both be uncertain. It cannot then be treated unconditionally as cash for a mandatory payment.
An example of a timing gap
Suppose a person has 360,000 roubles. Of this, 60,000 is available immediately, 120,000 only on day 60 and another 180,000 on day 120. These are educational constraints, not a claim about withdrawal rights under a real contract. An 80,000 payment is due on day 45. Total capital is much larger than the expense, but confirmed accessible funds by that date are only 60,000. The gap is 20,000. A large total in an app does not pay a bill on time by itself.
Several scenarios can be tested: part of the next rung becomes available earlier under the contract; the expense is agreed to be postponed; or new confirmed income appears. Describe each option separately with its costs and constraints. Do not simply assume penalty-free early exit or an effortless sale. If no option is confirmed, the deficit remains in the table. Acknowledging it is more useful than claiming full coverage from the total balance. The method identifies a calendar problem; it does not choose the solution.
Different money serves different functions
An operating balance covers ordinary near-term payments. Funds for a known future purchase have a defined purpose and date. A reserve covers selected unexpected scenarios. More distant capital may serve another function. This is a functional description, not a required number of accounts: accounting “envelopes” can exist within one system. The important point is that the same amount is not assigned in full to every task at once. A separate account creates no extra capital, and a separate label without reconciliation does not prevent double counting.
Stress-test the ladder
Build the ordinary calendar first. Then move access to one resource later in your mind or add an unplanned expense before the nearest maturity. Look not only at the ending balance but at the minimum balance along the path. This stress test is not a forecast of event probability. It shows which assumption supports the ability to pay. If several rungs depend on one infrastructure or counterparty, different dates do not remove the common dependency. Liquidity and reliability must be checked separately.[2](#source-save-risk)
What is easy to confuse
A ladder does not guarantee a higher return and is not a way to predict future rates. More rungs can make control harder, while one very large rung can leave a timing gap. A later-period yield cannot automatically be applied to an earlier period. Consider renewal, settlement and withdrawal dates when they apply to the chosen resource. A verifiable table of obligations and access is enough to begin; the choice of a specific product is outside this concept. The [emergency fund](/guides/emergency-fund/) guide discusses the purpose of an emergency reserve in more detail.
Check how rungs are renewed
After funds actually arrive, the next rung does not appear automatically. Decide whether the money remains available for near-term obligations or receives a new time restriction. If the table assumes that the whole amount will be placed again, check whether it will overlap with an already assigned payment. Keeping a separate free-balance line after each obligation makes it clear what can really be reassigned without double counting. For uncertain future income, the new rung should remain a scenario until its amount and date are confirmed.
The [savings risk map](/guides/savings-risk/) continues the separate checks of preservation, operational access and purchasing power; a timing ladder answers only part of those questions.