Everything Sunday needs, on one page.

An operating dashboard for an elders quorum presidency. Lessons, assignments, service, cleaning, the agenda, and the Sunday program.

Before Sunday

Sunday lesson, 24 AugustNeeds teacher
Building cleaning, 30 AugustPartially filled
Quorum service projectOpen
Sunday programReady for review

Sample data. Every item here is invented, and wardOS computes this list rather than storing it.

The line that matters

It holds the logistics. Never the confidences.

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.

Belongs in wardOS

Who is teaching on Sunday, and whether they know yet
The building cleaning rotation
Service project logistics and signups
Agenda items, and what was decided about them
Quorum budget lines
The published Sunday program

Never in wardOS

Worthiness concerns
Financial need
Counseling notes
Private family circumstances
Confidential presidency discussion

When something is genuinely sensitive, wardOS stores a link to where it already lives. Never the content.

What it runs

The meeting decides. Sunday delivers.

The presidency meeting

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.

ProposedOn agendaCommittedDone

Lessons

Who is teaching, what on, and whether they have been asked yet.

Service and cleaning

The rotation, the slots that are still empty, and who has not been asked in a while.

Signup forms

A link you text to the quorum. Nobody needs an account at the other end of it.

The Sunday program

Published to a page members reach from a QR code in the foyer.

Built for the day you are released.

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 quorum administration, 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.

Two things worth saying plainly.

wardOS is not a Church product.

It is an independent tool, built by a quorum member for his 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.

It is not in use anywhere yet.

There are no customers to point at and no numbers to quote. The first real test is one presidency, for one full Sunday cycle. If that is earlier than you want to be involved, it honestly is.

Request a demo

Have a look with your own quorum in mind.

Tell us which seat you serve in and we will walk you through it. There is nothing to install and no account to create first.