Manage Calling Proposals From Start to Finish
CallingHelper is a web application that helps wards, branches and stakes track calling proposals, approvals, interviews, sustainings and settings apart — all in one workflow, so nothing is left half-finished and nobody has to ask where a calling stands.
The problem it solves
Most units track callings in whatever was closest to hand:
- a spreadsheet
- Google Sheets
- Excel
- Trello
- email threads
- handwritten notes
- somebody's memory
Those work until a calling has to pass through several people. A proposal waits on an approval, then on an interview, then on a sustaining, then on a set apart — and in between, the only record of where it stands is in one person's head. Stop tracking calling proposals in spreadsheets, email and notes. CallingHelper gives wards and stakes a dedicated workflow for managing callings from proposal to completion, and a plain answer to the question every leader actually asks: what is this waiting on?
What a calling workflow looks like
A proposal moves through a sequence of steps. Not every calling takes the same route — a ward proposal and a stake proposal follow different paths, and a release skips the approval steps entirely — but the shape is the same:
- Proposed A leader records the calling, the proposed member, the unit and the organization.
- Review and approval A ward proposal starts with bishopric approval. A stake proposal goes to the stake presidency, and can be sent to the bishop of the member's ward for consultation.
- High Council approval * Part of the stake workflow — a ward calling does not normally reach this step. Each council member's vote is recorded, and unanimous approval from the active members moves the proposal on.
- Meet with the member The interview, where the calling is extended and accepted.
- Sustaining Tracked as its own step, with a working list of who is ready to be sustained.
- Setting apart The last thing that gets forgotten. It has its own list too.
- LCR entry * A checklist of what still needs to be recorded. CallingHelper does not connect to LCR and is not a system of record.
- Completed The proposal is archived and stays in the calling history.
* Conditional. High Council approval belongs to the stake workflow; a ward calling is approved by its bishopric and does not normally reach the council. The LCR step is a reminder to record the calling in the Church's own system, not an integration with it.
What CallingHelper does
-
Calling proposal tracking
Every proposal in one list, showing the step it is on and what it is waiting for — not buried in a spreadsheet tab.
-
Calling approval workflow
Each step records who was assigned it, what they decided and when. A step can be answered yes or no, or put on hold with a date to come back to.
-
High Council calling approval
In the stake workflow, individual council votes are recorded and counted, so it is obvious who has responded and who has not.
-
Working lists for every stage
Separate lists for bishop consultation, High Council, members to meet with, sustainings, settings apart and LCR entry.
-
Configurable email reminders
Steps can send scheduled reminder emails to the leaders who need to act. Each reminder has its own on/off switch, schedule and recipient list.
-
Reports and history
Vacant callings, calling history, member callings and archives, so the record survives a change of clerk.
Built for wards and for stakes
A ward or branch runs its own approval path, starting with bishopric approval; a stake runs a longer one that can include consulting the bishop of the member's ward and taking the proposal to the High Council. Both work in the same system, and permissions decide what each leader sees — a bishopric member does not get the stake's queue, and a clerk does not get somebody else's interviews.
Compare ward and stake calling management side by side.
Reminders, only where you want them
Several steps can generate reminder emails so a proposal does not stall silently: pending workflow steps, High Council approvals, members waiting to be met with, sustainings and settings apart. Each reminder type is configured on its own — turn it on or off, set how often it runs, and choose which callings' holders receive it. A unit that only wants a weekly nudge about settings apart can have exactly that.
Getting started
There is no self-registration. Send a request and an administrator reviews it and creates the account; the first time you sign in, a short guided introduction walks you through the vocabulary and the steps. The application is available in English, French, Spanish, Italian and Portuguese.