Track 01 / Mosque OS
Fix the admin that eats Fridays.
Room bookings, rotas and service info — pick one and make it simple.
01 / The challenge
Can you take one weekly mosque chore and halve the hassle?
One booking or rota often bounces across calls, texts and paper. Follow it, find the stuck point, and build a clearer path.
Choose this track for general services, volunteers and buildings. Teaching and learner progress fit Madrassah Next; donations and welfare casework fit AmanahTech.
02 / Starting points
Choose a problem to work on.
These are example challenges. You can also bring your own problem within this track. Aim for one complete user journey across the three-day build.
MOS-01A booking everyone can follow
The challenge
Build a simple room-booking journey for a community activity, from a request to a staff decision and a confirmation.
Show in your demo
Show a successful booking, a conflicting request and how staff resolve it. Compare the steps with the original process.
Start with
Create a fictional room timetable, opening hours and booking rules. Ask a mosque administrator what information they need before confirming a request.
MOS-02Find the right service
The challenge
Help a visitor find a mosque service, understand access arrangements and reach the right contact.
Show in your demo
Find a service on a phone, switch to an accessible or translated view, then show how staff correct an outdated listing.
Start with
Use a small directory of public service information. Record its source and review date; check language and access needs with intended users.
MOS-03Use less energy
The challenge
Help a facilities team spot avoidable energy use and decide what to change in its building schedule.
Show in your demo
Use sample readings to identify one issue, explain a suggested action and calculate estimated savings with assumptions visible.
Start with
Create sample meter readings, opening hours and tariffs. A dashboard or simulation is enough; physical hardware is optional.
03 / What to demonstrate
Make the improvement visible.
Your demo should show a working journey, who it helps and the evidence behind your decisions. For this track, useful evidence includes:
- Fewer steps or less time to complete a task.
- Clear ownership when a request needs attention.
- A service that works on a phone and is easy to update.
These are examples of evidence, not extra scoring categories. Every entry uses the same published judging criteria.
Collect only the information a service needs. Keep staff access separate from public information. Building projects can use simulated readings and should explain any assumptions behind savings.
04 / Prepare & stay informed
Start with people and a small dataset.
Talk to someone who does the task, map the current steps and agree what improvement would matter. If you cannot speak to a practitioner, state your assumptions and explain how you would test them.
The examples above suggest material you can prepare yourself. Use fictional records, public information or material you have permission to use. Event datasets, named mentors and partner tools are still to be confirmed.
Published by Faith Associates. This page is the reference for updates to this track.
Ask about this track