The result: the request is decided, the approved lines are in the budget, and the requester has been told why.
1. Read the request
The title, the requester, the cycle, the programs and the net change sit at the top, with the requester’s reason quoted beneath. Lines lists each change. Two notes can appear on a line:- Changed since it was proposed: approving it would undo that. Someone changed the forecast after the request was made. The line cannot be approved; send the request back so the requester can bring it up to date.
- Looks like the same change as another line. The request asks for both. Check whether it should.
2. Read the impact
Impact shows what approving would do:- The program. Each program the request touches, category by category and month by month, ending in Program net.
- The organization’s cash, week by week. Whether cash would go below zero, how low it would fall and when, how many more weeks would end below the reserve, and cash at the end of the cycle. The chart draws Without the request, With it, and the Reserve.
3. Decide
Under Your decision:
Send back and Reject need a Comment for the requester saying why. A comment is
welcome on an approval too.
The requester is emailed the decision. The request keeps the impact you approved on, shown
from then on as What it changed.
If the decision is refused
The impact has changed since it was shown means something moved the numbers while you were reading: another decision, or a forecast edit. Read the impact again and decide. Decisions in an organization are made one at a time, so two approvers cannot apply conflicting changes at the same moment.With your assistant
An assistant can find what is waiting, explain a request and its impact, and remind you of it. It cannot decide:What change requests are waiting on me? Summarize each one’s effect on our lowest cash week.When your assistant draws the change request card in the chat, the decision buttons on it are yours to click; the assistant cannot press them. Or decide in the console.