confsched publishes your calendar to the site you already have, then plans which week each thing goes in the bulletin, on the screens, or in front of a team.
Works on its own. Connects to your church system if you have one.
Events and groups come across from your church system with their schedules, photos, rooms and sign-up links. Then you decide what the public sees, and where each thing gets promoted.
Run the whole agenda: tracks, time blocks, sessions, speakers, signups and capacity. Attendees browse with no login. Teams attending together see what nobody has covered while it still matters.
Somebody in the office is keeping the website in step with the church system by hand, and it is always a little bit wrong. The dates, the room, the sign-up link and the photo are already in there.
Events and groups come across with their schedules, pictures, rooms and registration links. Change it at the source and the website follows.
A listing is a filter with a look: Adults, Students, Serving, Connect Groups. Each gets its own web address and its own embed, so pages can go wherever they belong.
Month, days, agenda, photo wall, cards, grid, by time, or a searchable list. The same events, arranged for the question a visitor is actually asking.
Which week does the Ladies Tea go on the front of the bulletin? Is the Angel Tree still on the screens? Did anyone put the Thanksgiving meal on the website? That plan is usually a spreadsheet, a notebook, or nothing.
Click a week and get everything going out in it, grouped by where, with the wording editable right there and a Copy that gives you the lines to paste.
The bulletin wants words, and offers the description you already have to start from. Signage wants a note about the artwork. The website highlight wants nothing, because the description itself is what goes out.
Three separate things have to be true before a visitor sees something, and the console tells you which one is missing rather than leaving you to guess.
Where you have a church system, it decides what may be published at all. We never go around that, and we say plainly when it is what is holding something back.
Optional, and off until you ask for it. With it on, anything new waits for a person. That person can be given approval and publishing and nothing else.
Every decision is logged with who made it and what changed, append-only, filterable, and searchable by the name of an event.
Your church system is where your data belongs and we never try to replace it. These columns are about where the work still lands once it is in there.
| Capability | confsched | A church system alone | A website calendar plugin | A spreadsheet |
|---|---|---|---|---|
| Getting what is on, onto your website | ||||
| Events and groups pulled with their schedules, photos, rooms and sign-up links | ✓ | ~ | ✗ | ✗ |
| Several arrangements of the same events: month, agenda, photo wall, cards, a searchable list | ✓ | ✗ | ~ | ✗ |
| Its own web address per listing, and an iframe that sizes itself | ✓ | ✗ | ~ | ✗ |
| Works as a plain link, for a church app menu item or a QR code | ✓ | ✓ | ✗ | ✗ |
| Filter chips a visitor can use: age, who it is for, day, time | ✓ | ✗ | ✗ | ✗ |
| Rename a category for the public without renaming it at the source | ✓ | ✗ | ✗ | ~ |
| Set what a listing opens on, and what it opens grouped by | ✓ | ✗ | ✗ | ✗ |
| Deciding what the public sees | ||||
| Honors your church system’s own publish flag, always | ✓ | ✓ | ✗ | ✗ |
| Optional approval by a person before anything new appears | ✓ | ✗ | ✗ | ✗ |
| Hold one thing back for good, and have syncing leave it alone | ✓ | ~ | ✗ | ✗ |
| Says which of the three gates is keeping something off the site | ✓ | ✗ | ✗ | ✗ |
| Write a better description for the website without touching the source | ✓ | ✗ | ~ | ✗ |
| Give one person approving and publishing and nothing else | ✓ | ~ | ✗ | ✗ |
| Planning the promotion | ||||
| Lanes you define: bulletin, website, signage, a Thursday email | ✓ | ✗ | ✗ | ~ |
| A thirteen-week forecast of everything going out, in one grid | ✓ | ✗ | ✗ | ~ |
| One date, several dates, or a run, without a recurrence rule | ✓ | ✗ | ✗ | ~ |
| The item’s own dates drawn behind the plan, so a run can stop the day before | ✓ | ✗ | ✗ | ✗ |
| Warns when something is scheduled after the event is over | ✓ | ✗ | ✗ | ✗ |
| A week view with the wording, and a Copy that gives the lines to paste | ✓ | ✗ | ✗ | ~ |
| Each lane asks for what it needs: words, a note about artwork, or nothing | ✓ | ✗ | ✗ | ✗ |
| Tells you when an item is also scheduled outside the weeks on screen | ✓ | ✗ | ✗ | ✗ |
| Keeping track | ||||
| Every decision logged with who made it and what changed | ✓ | ~ | ✗ | ✗ |
| Filter that log by review, publishing, promotion or access | ✓ | ✗ | ✗ | ✗ |
| Search it by the name of an event or a lane | ✓ | ✗ | ✗ | ✗ |
| Sign in with a passkey, or a link; no passwords | ✓ | ✗ | ✗ | ✗ |
| One person administering several churches | ✓ | ✗ | ✗ | ✗ |
A church system publishes a feed and usually has its own app, which is why that column carries ticks in the first group. What none of them has is a second place to decide what the public sees, or anywhere at all to plan which week something goes in the bulletin.
The thing confsched was first built for, and still the only scheduler that asks it: most conference apps help one person build a personal agenda, and have no idea your team of six just booked themselves into the same three breakouts and missed an entire track.
Tracks, time blocks, sessions, speakers with photos and bios, rooms, capacity and signups. Plenary, breakout and roundtable are different things and behave differently.
Conflicts, uncovered time blocks, tracks nobody has touched, and the sessions everyone piled into. The question a team lead asks on the drive home, answered while there is still time to act.
Multi-gigabyte uploads that resume, transcoded to adaptive video. Decks as PDF so they open in the browser. Watch a talk beside its slides, resuming on whichever device you pick up.
Subscribe and your agenda stays in step as the schedule changes. Installs to a home screen, caches so it loads on venue wifi, and shows what is happening now in the venue's own time zone.
A room change or a cancellation writes a notice everyone sees, including people who never gave an email, and it flows into the calendar subscription.
Ratings, comments and kudos to the speaker, exports of every signup and attendee, and a usage view showing what drew interest and what nobody touched.
| Capability | confsched | A typical conference app |
|---|---|---|
| Personal agenda for one attendee | ✓ | ✓ |
| Team coverage: who is covering which breakout | ✓ | ✗ |
| Shows the tracks nobody on your team has touched | ✓ | ✗ |
| Flags four people booked into the same session | ✓ | ✗ |
| Attend with no login and no install | ✓ | ✗ |
| Speakers upload their own recordings and slides | ✓ | ✗ |
| Nothing reaches attendees until an organizer reviews it | ✓ | ~ |
| Watch the talk beside its slides, resuming where you stopped | ✓ | ✗ |
| Playback position follows the person, not the device | ✓ | ✗ |
| Embeds into the event site you already have | ✓ | ~ |
| Live calendar subscription that stays in step | ✓ | ~ |
confsched fills in what a church management system does not do, rather than duplicating it, and it drops into the website you already have.
From the team behind TPxi Go and DisplayCache, with fifty-plus open-source TouchPoint® tools already in the wild. Other church systems are adapters, not rewrites.
One snippet for WordPress, Squarespace or Wix, sized to its content so it never scrolls inside your page. Or take the plain address, which is what TouchPoint®’s own app wants.
Nothing here depends on a ChMS. Type your events in by hand if you like. Integration adds convenience; it is never the price of entry.
Show us what you are keeping in step by hand, and we will show you what it looks like pulled across and planned out. Already have an account? Sign in.