Church Public Pages and Self Check-In | Announcements, Schedules, Giving and the Record
Church Public Pages and Self Check-In: The Front Door That Writes Its Own Records
Church public pages and self check-in solve a problem most church offices have stopped noticing because it has always been there: everything the congregation does reaches the office as a message, a slip of paper or a conversation, and someone then types it in.
A member wants to know the time of the Wednesday service and messages the secretary. A visitor wants to contribute to the building fund and asks for the paybill number, which is read out, mistyped and sent to nobody. An usher counts the congregation on a scrap of paper that reaches the office on Tuesday.
A department wants an announcement made and sends it to three people, one of whom puts it in the bulletin a week late. The office is a re-entry point for the whole church, and the re-entry is where information is lost, delayed and mistyped. A public layer removes it. A page anyone can open shows the announcements, the schedules and the contribution routes; a link anyone can tap checks them in; and each of those actions lands in the church’s own record without the office touching it.
The member who checks in is in the attendance record. The contribution is matched to the campaign. The announcement was published once, by the person authorised to publish it, and is the same everywhere.
This guide covers that layer: what the public pages are and how they differ from a website, announcements and keeping them current, schedules, contribution pages and M-Pesa, self check-in for services and events, first-timers, how public interaction reaches the internal record, sharing the pages, mobile-first design, who publishes and who approves, what should never be public, members’ names and children, sensitive announcements, multi-branch, events, measuring, accessibility, data protection and form security.
The value of church public pages and self check-in is that the congregation serves itself and the record stays true, and church public pages and self check-in that write directly into the church’s own data are what free the office from being a typist — which is why church public pages and self check-in are the part of the platform the congregation actually touches.
Table of Contents
- Why a Church Needs a Public Layer
- The Kenyan Church Context
- What the Public Pages Are
- Public Pages and the Church Website
- The Announcements Page
- Keeping Announcements Current
- Service and Programme Schedules
- Support and Serving Schedules
- Contribution Pages
- Contribution Pages and M-Pesa
- Campaigns and Transparency
- Self Check-In Links
- Self Check-In for Services
- Self Check-In for Events
- First-Timers Through Public Pages
- How Public Interaction Lands in the Record
- No Re-Entry
- Sharing the Pages
- Mobile-First and Data-Light
- Branding and Consistency
- Who Can Publish
- Approval Before Publishing
- What Should Never Be Public
- Members’ Names on Public Pages
- Children and Public Pages
- Bereavement and Sensitive Announcements
- Multi-Branch Public Pages
- Public Pages During Events and Conferences
- Public Pages and the Communication Channels
- Measuring Whether They Are Used
- Accessibility and Language
- Data Protection
- Security of Public Forms
- Systems and Costs
- Frequently Asked Questions
Why a Church Needs a Public Layer {#why-public}
The office as re-entry point has costs that are easy to stop seeing.
Information delayed between the person who has it and the person who needs it.
Errors introduced at every re-typing.
The secretary answering the same question dozens of times.
Announcements reaching some channels and not others.
Contribution details read out and mistyped.
Attendance reaching the record days late.
Visitors giving details that go nowhere.
A public layer means the congregation reads and acts directly, and church public pages and self check-in that let a member find the service time, contribute to a campaign and check in without messaging anyone have removed three re-entries, since church public pages and self check-in turn the office from a switchboard into an editor.
The Kenyan Church Context {#kenyan-context}
Local conditions make a public layer particularly useful.
WhatsApp is how information moves, and a link shared in a group reaches the congregation faster than any bulletin.
M-Pesa is how people give, and a contribution page with the right paybill and reference removes the mistyped number.
Phones are universal and QR codes are familiar from payment.
Many members do not use email and few visit a church website.
Announcements are made verbally and forgotten by Tuesday.
Multiple services, departments and fellowships each generate their own information.
Diaspora members want to give and stay informed from abroad.
Data cost matters, so pages must be light.
Church offices are small and frequently staffed by volunteers.
Each of these is what church public pages and self check-in must fit, and church public pages and self check-in designed for a congregation that checks email and visits websites would miss how a Kenyan congregation actually communicates.
What the Public Pages Are {#what-pages}
The public layer is a small set of pages that need no login.
An announcements page showing what the church has published.
Schedule pages showing services, programmes and support availability.
Contribution pages for tithes, offerings and campaigns.
Self check-in links and codes for services and events.
A visitor welcome or first-timer form.
Each is generated from the church’s own record rather than maintained separately.
Each is shareable as a link.
Each is branded to the church.
They are the church’s data made visible, since church public pages and self check-in that publish from the same announcements, events and campaigns the office manages internally are always consistent, and church public pages and self check-in maintained as a separate copy would drift from the record within a month.
Public Pages and the Church Website {#pages-vs-website}
The two are different things and both have a place.
The website is the church’s front door for people who do not know it: who we are, where we are, what we believe, how to visit.
The public pages are the church’s noticeboard for people who do: what is on this week, when the service is, how to give, check in here.
The website changes rarely; the public pages change weekly.
The website is built and hosted separately; the public pages come from the management platform.
The website should link to the public pages for announcements, schedules and giving.
The website article covers the front door, and church public pages and self check-in are the noticeboard behind it, since church public pages and self check-in linked from the website give a visitor a path from “who are you” to “here is this week’s programme” without the office maintaining two things.
The Announcements Page {#announcements}
The announcements page is the church’s noticeboard, published once and read anywhere.
Announcements entered by authorised people.
Ordered by date and relevance.
Categorised by department, service or audience where useful.
Expiring automatically after their date.
Linked from messages, groups and the website.
Readable in a minute on a phone.
One place, since church public pages and self check-in with a single announcements page mean the youth conference, the building fund update and the Wednesday service change are in one list every member can open, and church public pages and self check-in with announcements scattered across groups mean each member sees whichever they happened to be in.
The communication article’s channel discipline applies, and the announcements page is the reference the channels point to.
Keeping Announcements Current {#current}
An announcements page that is out of date is worse than none.
Expiry dates on every announcement so past events disappear.
A weekly review by whoever owns the page.
Departments submitting their own for approval rather than the secretary chasing them.
Removal of anything superseded.
A visible “updated” date.
Currency is trust, since church public pages and self check-in where the page still shows last month’s crusade are ignored, and church public pages and self check-in that expire announcements automatically stay current without anyone remembering to tidy.
Set expiry at publication.
Service and Programme Schedules {#schedules}
The most-asked question in any church office is when something is.
Service times per day and per branch.
Midweek programmes.
Fellowship and department meeting times.
Special services and their dates.
Changes for holidays and events.
Published from the events and departments records, so a change made internally appears publicly.
Answering the question once, since church public pages and self check-in with a schedule page the secretary can point to have ended the daily “what time is the service” message, and church public pages and self check-in that show the schedule from the same record the office uses are never wrong because the office updated one and not the other.
Support and Serving Schedules {#support-schedules}
Beyond service times, the church has schedules of who is available and who is serving.
Pastoral availability for counselling and prayer, with how to book.
Prayer meeting and intercession schedules.
Serving rotas for ushers, worship and media, visible to those on them.
Visitation and care team availability.
Published where public, restricted where the church prefers.
Some belong on a public page and some to a members-only view, and church public pages and self check-in that let the church choose per schedule what is public and what is for members keep pastoral availability visible without publishing every volunteer’s name, since church public pages and self check-in should show a visitor how to find help and show a volunteer when they serve without those being the same page.
The volunteer article covers rotas.
Contribution Pages {#contribution-pages}
A contribution page is where giving becomes a link rather than a read-out number.
The church’s giving routes: tithe, offering, specific campaigns.
The correct paybill or till and the reference format for each.
A tap-to-pay route where the platform supports it.
The campaign’s purpose and, where the church chooses, its progress.
Shareable so a member abroad or a visitor can give without asking anyone.
Every contribution matched to the giver and the purpose.
The mistyped paybill ends here, since church public pages and self check-in with a contribution page carrying the right details for each fund mean no one is guessing the number from a verbal announcement, and church public pages and self check-in that record each contribution against the campaign it was made to mean the treasurer never has to ask which fund a payment was for.
The tithe and offering article covers the giving record.
Contribution Pages and M-Pesa {#contribution-mpesa}
M-Pesa is the giving channel and the page should make it precise.
Paybill or till per fund, or one paybill with reference per fund.
The reference format stated and, where possible, prefilled.
STK prompt where available so the giver confirms on their phone.
Confirmation to the giver.
Matching by phone number where the reference is wrong.
Receipt where the giver wants one.
Precision is the point, since church public pages and self check-in that prompt a giver’s phone with the amount and the fund already set have removed the reference error, and church public pages and self check-in that show a paybill and hope the giver types the reference correctly will have a suspense pile every month.
The harambee article’s collection discipline applies to campaigns.
Campaigns and Transparency {#campaigns}
Campaign pages can show progress and the choice to do so builds trust.
Target and amount raised, where the church publishes it.
Pledges distinct from payments, as the harambee article insists.
Purpose and what the money has done.
Updates as the project advances.
Contributor privacy, with no names or amounts published without consent.
Progress motivates, since church public pages and self check-in with a building fund page showing the target and the total rising sustain giving where silence loses it, and church public pages and self check-in that show progress without naming contributors keep the transparency without the exposure.
Publish the total, never the list.
Self Check-In Links {#checkin-links}
Self check-in is a link and a code that write attendance into the record.
A link per service, event or gathering.
A QR code rendering the link.
Displayed at the entrance, on the screen and in the bulletin.
Shared in the group before the service.
The member opens it, identifies once, and is checked in.
Household check-in for families.
Phone-number route for those without smartphones.
The attendance article covers the discipline, and church public pages and self check-in are the public end of it, since church public pages and self check-in that put the code where the congregation can scan it in three seconds are what make per-person attendance possible at scale.
Self Check-In for Services {#checkin-services}
Sunday check-in has its own practicalities.
Codes per service so scans land on the right one.
Codes at every entrance.
Ushers who can help someone scan.
A desk for phone-number check-in.
Check-in open before the service and closed after.
Visible encouragement from the front.
Adoption grows week by week, and church public pages and self check-in introduced with explanation reach a majority of the congregation within a few months, while church public pages and self check-in that appeared as a code with no word from the pulpit stay at a fraction.
The attendance article’s introduction section applies.
Self Check-In for Events {#checkin-events}
Events and conferences use the same mechanism with registration in front.
Registration link published on the announcements page.
Registrant record created.
Check-in link or code at the event.
Session check-in for multi-session events.
Capacity visible.
Attendance report after.
The events article covers logistics, and church public pages and self check-in give an event a public registration page and a check-in code from the same record, since church public pages and self check-in that carry a delegate from registration through check-in to the attendance report never require the office to type a name twice.
First-Timers Through Public Pages {#first-timers}
A visitor’s first interaction with the church may be a public page.
A welcome page with what to expect and when to come.
A first-timer form asking for a name and a number, briefly.
A check-in that recognises a new person and flags them.
The record created and passed to visitor follow-up.
A visitor who found the church through a friend’s shared link and registered themselves before arriving is a visitor the church already knows, and church public pages and self check-in that create the visitor record from that first form mean the welcome team has a name on Sunday, while church public pages and self check-in without a visitor route leave the front door to chance.
Keep the form light, since a visitor asked for six fields has been given paperwork rather than a welcome.
How Public Interaction Lands in the Record {#lands-in-record}
The principle that makes the public layer valuable is that every public action becomes an internal record.
A check-in becomes an attendance entry against the member.
A contribution becomes a giving entry against the giver and the fund.
A registration becomes an event registrant.
A first-timer form becomes a visitor record.
A pledge becomes a pledge entry.
No copying, no typing, no delay.
The record is the same one the office uses, since church public pages and self check-in that write into the church’s own database mean the treasurer sees the contribution and the pastor sees the check-in the moment it happens, and church public pages and self check-in that produced a separate spreadsheet to be merged later would have recreated the re-entry they exist to remove.
Verify it, since a public form that emails the office is not a public page in this sense.
No Re-Entry {#no-reentry}
The office’s job changes from typing to reviewing.
Announcements approved rather than typed.
Contributions matched automatically with exceptions reviewed.
Attendance flowing in rather than collected.
Registrations appearing rather than compiled.
Visitor records created rather than transcribed.
The time returns to pastoral and organisational work, and church public pages and self check-in that remove re-entry give a volunteer secretary back most of their week, since church public pages and self check-in are the difference between an office that processes and one that serves.
Where a re-entry remains, ask why, since it is usually a public page that does not yet exist.
Sharing the Pages {#sharing}
A page nobody opens does nothing, and sharing is where the congregation reaches it.
Links in the church’s messaging groups, weekly.
QR codes on the screen, at the entrance and in print.
The website linking to each page.
Department leaders sharing their own announcements’ links.
A short memorable address where the platform allows.
Links in messages, not attachments, since a link opens and an attachment downloads.
WhatsApp is the distribution channel here, and church public pages and self check-in shared as a link in the congregation’s groups every Friday reach more people than any bulletin, while church public pages and self check-in that exist but are never shared reach only those who remembered the address.
Mobile-First and Data-Light {#mobile-first}
The congregation is on phones, many on limited data.
Pages that load fast on a modest connection.
Minimal images.
Readable without zooming.
Tap targets large enough for a thumb.
Working on older handsets and browsers.
Check-in in three taps.
Contribution in as few steps as M-Pesa allows.
Test on the phones members actually carry, since church public pages and self check-in that load in two seconds on a basic phone are used, and church public pages and self check-in heavy with images that stall on data are abandoned before they open.
Branding and Consistency {#branding}
The pages are the church’s and should look like it.
Name, logo and colours.
Consistent across announcements, schedules, contribution pages and check-in.
Contact details on every page.
The same tone as the church’s other communication.
Recognisable so a member knows they are on the church’s page and not a lookalike.
Consistency is also security, since church public pages and self check-in that always look the same are harder to imitate, and church public pages and self check-in with the church’s identity on every page let a giver see they are contributing to the right place.
Who Can Publish {#who-publishes}
Publishing authority should be defined and enforced.
The secretary or communications role as the publisher.
Department leaders able to submit for their department.
The pastor or a designated leader approving.
The treasurer controlling contribution pages, since the paybill on a public page is the church’s money.
Role-based, since church public pages and self check-in where anyone with a login can publish will carry announcements nobody authorised, and church public pages and self check-in with defined publishers and approvers carry only what the church intended.
The volunteer and department articles cover roles.
Approval Before Publishing {#approval}
Public pages speak for the church and an approval step is worth the delay.
Submission by the department or person with the information.
Review by the approver for accuracy, tone and appropriateness.
Approval or return with comments.
Publication with expiry set.
Audit of who published what.
Fast, since an approval process taking days will be bypassed with a group message.
Proportionate, since a routine service time change needs less scrutiny than a campaign launch.
The step catches the error before the congregation sees it, and church public pages and self check-in with a same-day approval habit publish accurately, while church public pages and self check-in that publish whatever was submitted will eventually publish something the church regrets.
What Should Never Be Public {#never-public}
Some information belongs to members or leadership and must not reach the public pages.
Members’ contact details.
Attendance records, aggregate or individual.
Giving records and contributor names.
Pledge lists.
Pastoral notes and prayer requests with personal detail.
Internal meeting minutes.
Financial statements beyond what the church chooses to publish.
Children’s information.
Staff and volunteer personal details.
Leadership disputes.
The public layer publishes what the church says to everyone; everything else stays inside, and church public pages and self check-in configured so that only announcement, schedule, contribution and check-in content can be public have the boundary built in, while church public pages and self check-in that could expose member data through a misconfiguration need the boundary checked.
Members’ Names on Public Pages {#members-names}
Names appear in church life and their appearance on public pages needs consent.
Serving rotas name volunteers.
Announcements name leaders, speakers and organisers.
Celebrations name people.
Bereavement notices name families.
A public page is visible to anyone with the link, including people outside the church.
Consent for a name to appear publicly, particularly for volunteers on rotas.
Members-only views for rotas and celebrations where the church prefers.
Leaders and speakers in their public role are different from volunteers on a rota, and church public pages and self check-in that keep rotas to a members-only view while announcing the guest speaker publicly have drawn the line sensibly, since church public pages and self check-in that publish every usher’s name to the internet have shared something those ushers may not have agreed to.
Children and Public Pages {#children}
Children’s names, images and details should not appear on public pages.
Children’s ministry announcements without children’s names.
No photographs of children on public pages without parental consent and a clear purpose.
Children’s check-in handled on the internal, not the public, layer.
Youth events announced without listing young people.
The safeguarding position applies to publication as much as to contact, and church public pages and self check-in that carry no children’s data publicly are safe by design, while church public pages and self check-in that published a Sunday school photo with names have created a risk no announcement justified.
Confirm the church’s safeguarding policy and qualified advice govern what may be published.
Bereavement and Sensitive Announcements {#sensitive}
Some announcements concern people at their most vulnerable and public handling needs care.
Bereavement notices with the family’s consent to what is said and where.
Hospital and illness notices only with the person’s consent, and never with diagnosis.
Funeral arrangements as the family wishes them shared.
Prayer requests generalised or kept to members-only channels.
Removed after their time.
The communication article’s bereavement section applies, and church public pages and self check-in that carry a funeral notice the family approved on the announcements page serve the community, while church public pages and self check-in that published a member’s illness without asking have exposed something deeply private to anyone with the link.
Ask first, every time.
Multi-Branch Public Pages {#multi-branch}
Churches with several sites need pages per branch and pages for the whole.
Branch schedules and announcements.
Church-wide announcements appearing on every branch page.
Contribution pages per branch or church-wide, as the church’s finances are structured.
Check-in codes per branch and service.
Branch identity within the church’s branding.
Central approval with branch submission.
The branch article covers the structure, and church public pages and self check-in that give each branch its own page under the church’s identity serve members at that site, since church public pages and self check-in with a single page for a church of five sites would show every member four sites’ announcements they did not need.
Public Pages During Events and Conferences {#events}
Events generate a burst of public interaction and the pages should carry it.
Registration page from the event record.
Programme and session schedule.
Venue and directions.
Contribution page where the event has costs to cover.
Check-in codes per session.
Live updates on the announcements page.
Post-event thanks and follow-up.
The event’s whole public face on the platform’s pages, and church public pages and self check-in that carry a conference from registration to check-in to the attendance report have handled it without a separate tool, while church public pages and self check-in used only for Sunday leave events to a spreadsheet and a group.
The events article covers the rest.
Public Pages and the Communication Channels {#channels}
The pages and the channels serve different purposes and should reinforce each other.
Channels push: a message says something is on.
Pages pull: the page holds the detail.
Messages should carry a line and a link, not the whole announcement.
The page is the source; the channels are the pointers.
Reduced message length and frequency, since the detail lives on the page.
The communication article’s discipline is served by the pages, since church public pages and self check-in let a weekly message say “this week’s announcements are here” with a link rather than ten paragraphs, and church public pages and self check-in as the reference mean every channel points to the same current information.
Measuring Whether They Are Used {#measuring}
A few figures show whether the public layer is working.
Page opens per week.
Check-ins as a share of headcount.
Contributions through the page as a share of total giving.
Registrations through the page.
First-timer forms submitted.
Questions to the office about things the pages answer, which should fall.
Check-in share and contribution share are the two that matter, since church public pages and self check-in reaching seventy percent check-in and most campaign giving through the page have become the congregation’s habit, and church public pages and self check-in whose opens are flat and whose check-in share is low have not been shared or explained enough.
Accessibility and Language {#accessibility}
The pages should serve the whole congregation.
Language the congregation uses, which may mean more than one.
Plain wording.
Large enough text.
Working with screen readers where members use them.
Phone-number routes for members without smartphones.
Printed versions for members who prefer paper, from the same content.
Assistance from ushers for anyone struggling with a scan.
Inclusion is the church’s character, and church public pages and self check-in that offer a check-in desk beside the QR code serve the elder who does not scan, since church public pages and self check-in that work only for the young and connected have excluded members the church most wants to see.
Data Protection {#data-protection}
Public pages collect and display data and the Data Protection Act applies.
Check-in collects identity and presence.
Contribution pages collect payment details.
First-timer forms collect contact details.
Registration collects attendee information.
Display of names on public pages is disclosure.
Collect the minimum on each form.
State on each form what is collected and why.
Consent for any use beyond the immediate purpose, including future communication.
Names displayed publicly only with consent.
Retention defined for form submissions.
Confirm obligations with qualified advice, and church public pages and self check-in should be configured to whatever position that establishes, since church public pages and self check-in that collect a visitor’s number for a welcome and then add them to every campaign list have used the number beyond what was asked.
Security of Public Forms {#security}
Anything public can be misused and the forms should be protected.
Contribution pages verified as the church’s, since a lookalike page with a different paybill is fraud.
Check-in links that cannot be used to check in others without their identity.
Rate limiting so forms cannot be flooded.
No member data returned by a public form.
Administrative access to the pages restricted.
The church’s official links shared from official channels only.
The contribution page is the sensitive one, since church public pages and self check-in whose giving page is reached only through the church’s own links and carries its branding are what members trust, and church public pages and self check-in should be introduced with a warning that the church will never message a different paybill.
Tell members what the official links are.
Systems and Costs {#systems}
The public layer is part of church administration software and its connection to the record is what to assess.
Announcements page published from the internal announcements record with expiry.
Schedule pages from events and departments.
Contribution pages per fund with M-Pesa integration and matching.
Campaign progress display with contributor privacy.
Self check-in links and QR codes per service and event, writing to attendance.
Phone-number check-in route.
First-timer form creating a visitor record.
Registration pages creating registrants.
Members-only views for rotas and sensitive content.
Publisher and approver roles with audit.
Multi-branch pages.
Mobile-first, data-light rendering.
Pricing commonly from around KES 3,000 monthly for a small church to more for larger or multi-site churches.
Implementation should begin with the announcements page and the schedule, since those answer the questions the office is asked daily, and the contribution page for the main funds, since that removes the mistyped paybill.
Then self check-in with explanation from the front.
Then registration and first-timer forms.
Share the links weekly from the first week, since church public pages and self check-in that are not shared are not used.
Weigh it against the secretary’s week, since church public pages and self check-in that end the daily “what time is the service” message and the monthly suspense pile of mistyped contributions have returned hours to a volunteer every week.
Frequently Asked Questions {#faqs}
What is the difference between public pages and our website?
The website is the front door for people who do not know the church — who you are, where you are, how to visit. The public pages are the noticeboard for people who do — this week’s announcements, service times, how to give, check in here. The website changes rarely and is built separately; the public pages change weekly and come from the management platform. Link one to the other.
Why not just post announcements in the WhatsApp group?
Because each member sees only the groups they are in, the announcement scrolls away, and it is retyped for every channel. Publish once on the announcements page, with expiry, and send a line and a link to the groups. The page is the source; the channels point to it. Message length and frequency fall as a result.
How does a contribution page stop mistyped paybills?
By carrying the correct paybill or till and reference for each fund on a page members open rather than a number read out and remembered, and where available by prompting the giver’s phone with the amount and fund already set. Each contribution is matched to the giver and the campaign automatically, so the treasurer never asks which fund a payment was for.
What does “lands in the record” actually mean?
That a check-in becomes an attendance entry, a contribution a giving entry, a registration a registrant, and a first-timer form a visitor record — in the same database the office uses, the moment it happens, with nobody typing. A public form that emails the office for someone to enter is not a public page in this sense.
Whose names can appear publicly?
Leaders and speakers in their public role, and anyone who has consented. Volunteers on rotas should be on a members-only view unless they agreed to be public, since a public page is visible to anyone with the link. Children’s names and images do not belong on public pages, and bereavement or illness notices appear only as the family or person approved.
Who should be allowed to publish?
A defined publisher, department leaders submitting for their departments, an approver, and the treasurer controlling contribution pages since the paybill on a public page is the church’s money. Approval should be same-day and proportionate, or it will be bypassed with a group message.
How do we protect the giving page from fraud?
Share it only from official channels, keep the church’s branding consistent so a lookalike stands out, and tell members plainly that the church will never message a different paybill. A church public pages and self check-in contribution page reached through the church’s own links and carrying its identity is what members learn to trust.
How do we know it is working?
Check-in as a share of the headcount and contributions through the page as a share of giving. When both are high, the congregation has made the pages a habit; when page opens are flat, the links have not been shared or explained enough. Questions to the office about things the pages answer should fall — that is the office’s week coming back.