Budget request log
RegisterWhat has been asked for against a project, who is deciding, and what they said — with what is still waiting at the top.
No balance, and no authority
Two absences, both deliberate. There is no budget balance because a total assembled from whatever this tool happened to see would be a planning number built on a partial view. And approving here approves nothing: it records that a person with the authority told you their answer. Software that appears to grant spending authority is software somebody will rely on.
Queried is a state, and it is where things sit
Requests are rarely refused outright. They come back with a question, and then they sit — which is why Queried is its own state and is colored as still yours rather than as a refusal. What is owed sorts to the top of the register.
Where it sits
Changes to what the project is doing belong in the change request log, what is going wrong now in the issue log, and what might in the risk register. Buying something specific is a purchase requisition.
A record of requests and answers. CompliMaint holds no budget, tracks no balance, subtracts nothing from any allocation, and confers no authority on anybody to approve or spend. It is not an accounting system and makes no determination about accounting treatment or tax. Everything runs on your device.
Questions people ask
- Does it track my budget balance?
- No, and this is the most important thing to know about it. It holds no budget, no allocation and no running total. A balance calculated here would be a number somebody planned from, built out of requests this tool happened to see and blind to everything else your organization spent. What it holds is the requests and the answers.
- Does approving a request here approve anything?
- No. Approved is a state you set after somebody told you they had approved it. This tool confers no authority on anybody, knows nothing about your approval thresholds, and enforces no limit. It is a record of a decision, not the decision.
- Why is it kept per project?
- Because a request only makes sense against the thing it is for, and a flat list of requests across everything is unreadable within a month. A project here is a piece of work that is not a job — nobody accepted an estimate for it and it carries no contract sum. You can create one straight from the picker.
- What is the difference between this and a change request?
- A budget request asks for money. A change request asks to change what the project is doing, which sometimes costs money and sometimes does not. They are separate because the conversations are separate, and because a change with no cost still needs a decision.