Before this, events at a member organisation were approved by hand in iMIS. Staff checked each event there and moved it along themselves.
We built an approval route to take over that routine, and Julian did the build. A new event lands on an Event Approvals page in the organisation’s online hub. The system finds approvers from their roles in iMIS and emails them a link to the event as members will see it. Local group events go through membership, finance and leadership. Head office events skip membership. Community outreach events skip finance unless they have extras like raffles and auctions. One approval from each group moves the event on. The final approval sets the event active and sends a copy to two shared inboxes.
Each step is still a person’s call. Approvers can approve an event or send it back, and the organiser can fix it and resubmit. Judging whether an event fits the organisation, and where its money goes, needs someone who knows the context.
To check your own office, look at how a new event gets signed off. If someone checks records and then chases the next approver by email, you have the same job.