The steps
- List the servers. Use first names and an initial, or initials alone. Tick the experienced ones as senior; there is no need for ages or birthdates.
- Set the Masses and counts. Enter each weekend Mass and how many servers it needs, and add feast days such as Christmas Eve as one-off services.
- Mark families and pairs. Give brothers and sisters the same family name so they serve the same Mass on a weekend, which is how they arrive.
- Add the dates away. School holidays, exam weeks and family trips go in as date ranges, so nobody is scheduled when they cannot come.
- Choose the rules. Turn on a senior server at every Mass, families together and not twice in one weekend, and set a monthly limit for younger servers if the parish wants one.
- Build, review and print. Build the rota, check the open places and their reasons, move anyone by hand if needed, then print the rota by Mass for the sacristy and by person for families.
Worked example: a small team and the rules at work
Take one family of two servers (Leo, who is senior, and Mia) and one more senior server, Quinn, for a parish with a Saturday Vigil and a Sunday Mass, two servers at each, in December. That is 16 places. With the senior rule, families together and not twice in one weekend, PewRota fills 12 of them and leaves 4 open. It does not break a rule to fill them; it says why, place by place:
"3 people are trained for Altar server, and none can take it: 1 already serving at this service; 2 already serving another service that weekend."
Three servers cannot cover four places a weekend when nobody serves twice. The fix is people, not rules: one more trained server, or a family willing to serve at both Masses (tick "happy to serve twice on one weekend").
In the larger sample parish in the rota builder, 13 servers, 6 of them senior, cover three Masses a weekend for a whole quarter with every place filled.
Children's details
Servers are usually children, so keep the list short: a first name and an initial, what they are trained for, their family, their dates away. PewRota never asks for a birthdate, an age, an address or a phone number, and a column of birthdates in a pasted spreadsheet is ignored. The list stays in the browser on the parish computer. Read keeping minors' names off the cloud for the reasons.
Common mistakes
- Pairing two new servers at one Mass. The senior rule prevents it.
- Splitting siblings across the Vigil and Sunday, so a parent drives twice.
- Forgetting school holidays and exam weeks, when families travel.
- Scheduling the keenest few every week. A monthly limit and the fairness report keep it even.
- Posting full names of children online.
Build one now in the rota builder; the sample parish has servers, families and senior servers already entered.
Sources
Checked on 28 September 2026. PewRota applies your parish's own policy; it ships no liturgical rules. Where your diocese, your parish safeguarding policy or your clergy say something different, follow them.
- PewRota's rota builder. Every example on this page is built by the same solver the rota builder runs, at build time, and pinned by a test.
- Children and the UK GDPR, the UK Information Commissioner's Office guidance (last updated 15 May 2026). Guidance on handling children's personal information, including a section on sharing it; opened 28 September 2026.