Church Ministry & Organisation Platform
The most organisationally complex system I have built
Developed while employed by a previous organisation; copyright remains with them. Shown here to illustrate technical capability only.
A church's organisation is not a company org chart
Four associations across an eight-level hierarchy, and one person holds different identities and permissions under each of three overlapping structures — an ordinary member of one association, the lead of a ministry team, and the head of a small group, all at once. Paper and scattered spreadsheets stop coping at that size.
Six modules, two years
Organisation, membership, ministry teams, small groups, course commerce and reporting — analysis, schema design, front-end build and testing, maintained since launch.
One question can only have one answer
Attendance arrives by three routes: on-site check-in, proxy check-in and late check-in. All three have to answer the same question — did this person complete the course, and are they eligible for the next one. Written as three rule sets, eligibility would eventually contradict itself. So the three differ only in where the record comes from; the judgement exists once. Miss this and the system starts behaving oddly about six months after launch.
FAQ
Got a system where the rules tangle?
Complex organisations and interlocking workflows go wrong when each rule gets its own implementation. Tell us about yours.
Request a quote