Budget review

An event budget belongs to an event and its operating organization. The Event Organizer records the event label, ticket quantity and current revision, then submits it for review. Submission freezes the revision the Budget Reviewer is being asked to consider. A reviewer records a decision, reason and decision time against the source revision. This keeps a later edit from being mistaken for the plan that was approved.

The budget has its own status from draft to submitted, approved or rejected, and finally completed when the required capacity and payment effects have been persisted. Approval is a decision about the plan; completion depends on what happened. A submitted budget for a company meeting can therefore be reviewed before admissions start, while its eventual completion waits for the admission and provider evidence from the actual event.

• Budget record. The budget links the event and organization and carries its status, revision and ticket quantity.
• Separate decision. The reviewer records an approve, reject or return decision with a reason against the event’s source revision.
• Completion evidence. Capacity and verified provider payment effects are checked separately before completion.

Name the people who may submit budgets and the independent reviewers who may decide them. Agree how a return differs from a rejection, what evidence the reviewer needs, and when a changed budget must be submitted again. Decide which provider records count as verified payment effects. Keep the review rule consistent across departments so a budget is never completed from a local status change alone.

Create a draft budget for an event with a stated ticket quantity. Submit it and record the source revision. Have a different person open the Submitted budgets screen, review the event, and record an approval with a reason. Then change the event. The reviewer should see that the earlier decision belongs to the previous revision. Finish by checking capacity and provider evidence independently before the budget is treated as complete. Repeat with a rejected budget and verify that its reason stays visible.

• Submitted budgets — Budgets awaiting a decision, with event, organization, quantity and revision.
• Budget status board — The budget lifecycle without hiding rejected work.
• Review decision log — Decisions, reviewers, revisions and reasons for later inspection.

Walk through budget submission and review and event approval. Review roles before giving an organizer decision rights.