> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# File a change request

> Change a locked budget: collect your changes in a draft, see what they do to your program, and submit them for approval with a reason.

Once a budget cycle is locked, a change to its forecasts goes through a change request. Your
changes collect in a draft, **Your pending changes**, until you submit them with a reason.
The budget changes only when owner or finance approves.

Owners, finance and program managers file change requests.

**The result:** your changes are with the approvers, with a reason and their impact on your program's budget, and you are told by email when they decide.

## 1. Make the change

Open the forecast and change it as usual, or add a new one. When the change would alter the
locked budget, Zeno Budget refuses the save and offers **Add to change request** (or
**Propose deleting it**). Choose it.

The change is added to **Your pending changes**:
*Added to your pending changes. The budget changes once the request is submitted and approved.*

Add as many changes as belong together. Each is a line of your draft.

> Push the Youth Mentoring summer camp from June to July and cut it to \$14,000. The budget is
> locked, so add it to my change request.

## 2. Check the impact

Open **Change requests** and select **Your pending changes**. Each line shows the forecast,
program, category, the change (for example *$18,000 → $14,000, from Jun 1 to Jul 1*) and its
effect **Over the cycle**.

**Impact** shows what the lines do to your program, category by category and month by month,
ending in **Program net**, with a headline such as *The budget spends \$4,000 less over the
cycle*. Owners and finance also see the organization's cash week by week.

Tick and untick lines to see the impact of some of them. To fix a line, choose **Change**;
saving replaces that line. **Remove** takes it out.

## 3. Submit it

Under **Submit for approval**, give it a **Title** (what it changes, in a few words) and a
**Why** (what the approver should know). Choose **Submit**, or **Submit k of n** to submit only
the ticked lines; the rest stay behind in a new draft.

Owner and finance are emailed. The budget does not change until one of them approves.

## Follow it

The request's **Timeline** records each step: submitted, comments, the decision. You can
**Add a comment**, which emails the approvers.

* **Remind the approvers** emails them again, once a day at most.
* **Withdraw** stops the request waiting for a decision; the budget stays as it is.

You are emailed when the request is approved, partly approved, rejected or sent back.

## If it is sent back

The status reads **Sent back for revisions**, with the approver's comment. Change or remove
lines, then choose **Submit it again**.

## If it is partly approved

Some lines went into the budget and the rest were rejected. The request shows which, line by
line, as **Approved** or **Not approved**, and the byline shows how much was approved. File a
new request for anything you still want.

## When a change is refused outright

A change that would move forecasts in two locked cycles at once is refused. Split it by date:
end the forecast at the first cycle's close, and propose the rest as a new forecast in the
second.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.