---
name: automated-savings
description: Use when someone wants saving to happen before spending, by setting up scheduled transfers on payday to savings accounts, goal pots, or retirement contributions. Related to [[basic-budget]] and [[personal-budget]] (deciding how much to save), [[money-map]] (which accounts exist), and [[bill-autopay]] (automating outgoing bills, not savings). This one is the transfer schedule, not the plan behind it.
---

# Automated Savings

Saving by willpower competes with every purchase. Automated savings
removes the decision: a transfer runs on a schedule, right after money
arrives, so what remains is what can be spent. This skill designs those
transfers, sizes them so they survive a bad month, and sets a review so
they do not drift.

## Input required

- **Country**, since account types, tax wrappers, and employer schemes
  vary. Check the current official or provider source for rules.
- **Pay pattern**: how often, which day, and which account receives it.
- **Goals**: emergency cushion, near-term purchase, retirement, other.
- **Amounts affordable** after fixed bills, from a budget if one exists.
- **Accounts available**: names and types only, never numbers.

## Questions to ask first

Ask in **one batch of at most five questions**, skipping any already
answered:

1. How often are you paid, and into which account?
2. What are you saving for, and in what order of priority?
3. What can you move each pay period without missing a bill?
4. Which separate savings accounts or pots can you open or already have?
5. Does your employer offer payroll deductions or matching you could use?

## Method

1. **Rank the goals.** Usually a small cushion first, then high-interest
   debt, then longer goals; adjust to the user's situation and local
   rules, and say it is a default.
2. **Pick the amount per pay period**, not per month, so it matches the
   cash that arrives. Start lower than feels ideal; a transfer that
   bounces is worse than a small one that holds.
3. **Schedule the timing.** Run the transfer on or one day after payday,
   before bills pull. If pay lands late sometimes, schedule a day later
   rather than earlier to avoid overdrafts.
4. **Separate the destination.** Use a different account or named pot,
   ideally at a different institution or with no linked debit card, so
   moving the money back takes a deliberate step.
5. **Use payroll routes where they exist.** A split deposit or an
   employer deduction acts before the money reaches the main account.
   Ask the employer or read the current official guidance.
6. **Add a step-up rule.** Increase the amount after each raise or each
   year, for example by half of any raise. State this as a default.
7. **Test once.** Watch the first two cycles. Confirm the transfer ran,
   the balance cleared, and no fees or limits applied.
8. **Review quarterly.** Check amounts, goals, and whether any transfer
   has been paused and forgotten.

## Output format

A schedule table plus rules:

| Goal | From | To | Amount | Day | Step-up |
|---|---|---|---|---|---|
| Cushion | Main | Savings pot | amount | payday +1 | yearly |

Then: the first-two-cycles test, the quarterly review date, and one
rule for pausing ("pause for a named emergency only, and set a
restart date").

## Ground rules

- Never ask for account numbers, sort codes, card numbers, passwords,
  or ID numbers. Use nicknames for accounts.
- Do not give investment, tax, or product recommendations. Describe
  the capability and let the user's provider and local rules decide.
- Do not state rates, limits, or fees as facts; tell the user to check.
- Do not automate savings that would cause overdrafts or missed bills.

## Self-check before answering

- Is the amount sized to the worst normal month, not the best?
- Does the transfer run before spending, and after pay actually lands?
- Is the destination separate enough to resist casual withdrawal?
- Is there a review date and a pause rule?
- Did I avoid promising any rate, limit, or return?

## Common pitfalls

- **Setting it too high**, then cancelling after one overdraft.
- **Transfer before pay arrives**, causing fees or failures.
- **Set and forget forever**: the amount never rises with income.
- **Savings in the main account**, where it blurs into spending.
- **Raiding the pot** with no refill plan.
- **Ignoring debt costs** while saving at a lower return than the debt.

## Example prompt

> I am paid every two weeks on Friday. Design automated transfers so I
> build a small cushion first, then save for a trip, without risking
> overdrafts. Use nicknames for my accounts.

## Learn more

- [[basic-budget]] for deciding the amount to save.
- [[personal-budget]] for the fuller plan behind the transfers.
- [[money-map]] for seeing where each transfer lands.
- [[bill-autopay]] for the outgoing side of automation.