An operating dashboard for a ward presidency. What was decided, what has to happen by Sunday, and who owns it.
Before Sunday
Sample data. Every item here is invented, and wardOS computes this list rather than storing it.
The line that matters
A shared spreadsheet can hold the same rows. What it cannot do is know the difference between coordinating work and recording something that was told to you in confidence. That boundary is enforced in the database, in the import rules, and on every public page.
When something is genuinely sensitive, wardOS stores a link to where it already lives. Never the content.
What it runs
Built first for an elders quorum, because that is the calling I hold. The shape underneath is the same for Relief Society, Young Men, Young Women, Primary and Sunday School: a presidency, callings with dates on them, and work that has to survive being handed to whoever comes next.
The agenda builds itself out of whatever is still unresolved, so nobody arrives having forgotten what was left open. What gets decided becomes a commitment with an owner and a date.
Anything carried from one meeting to the next is counted, so work that keeps being deferred is visible instead of quietly repeating.
Who is teaching, what on, and whether they have been asked yet.
The rotation, the slots that are still empty, and who has not been asked in a while.
A link you text out. Nobody needs an account at the other end of it.
Published to a page members reach from a QR code in the foyer.
Everyone in this calling leaves it eventually, usually with little notice, and the person called next inherits whatever was in your head. That is the actual failure mode in ward leadership, and it is not a filing problem.
So work in wardOS belongs to the seat, not the person. When a counselor is released, the whole queue moves to whoever is called next, with its history intact. Nobody has to write a handoff document, because the tool already is one.
It is an independent tool that I built for my own presidency. It is not affiliated with, endorsed by, or integrated with any official Church system, and it does not read or store membership records.
That presidency is mine. There is nobody else yet and no numbers to quote, which means an early conversation actually shapes what gets built. I would rather hear how you run things than show you what I have built.
Help shape it
wardOS is early enough that a conversation still changes what gets built. There is nothing to install, nothing to sign, and no demo to sit through.