Organize teams and responsibilities, prepare services and events, and preserve what your organization learns—all in a shared space built around the work.
We’re preparing for early access and will follow up personally with interested organizations. Features are still being developed and tested; access begins with a conversation.
How it works
A foundation for the week ahead.
For administrators, team leaders, and volunteers in churches, ministries, mission organizations, and nonprofits.
01
Make responsibilities clear.
Begin with the ministry areas, teams, and responsibilities you know. Connect people to their teams and build on that foundation as you work.
Read moreRead less about make responsibilities clear+
The foundation follows four levels: your organization, its ministry areas, the teams within them, and the responsibilities those teams carry. Start with a useful picture of your ministry; you can add to it as planning reveals more of the work.
For example, preparing supplies for an outreach event can belong to the logistics team. That gives the work a place in the organization beyond the person handling it on a particular day.
02
See the work that belongs to you.
My Workspace brings together work relevant to your assignments, teams, and role.
Read moreRead less about My Workspace+
Your workspace reflects your team memberships, leadership relationships, and assigned tasks within your access permissions. Tasks carry their service, responsibility, and deadline context with them.
A volunteer can find their assigned work; a team leader can see the teams they lead. Each person has one workspace that brings their relevant work together.
03
Prepare services and events together.
Bring tasks, assignments, deadlines, and requested information together for a service or event. Start from a saved pattern when the work repeats.
Read moreRead less about preparing services and events together+
A saved service pattern describes the work that normally repeats. Creating a dated service copies its tasks, default assignments, deadline rules, and requests for information.
Each dated service or event gives the preparation its own place. The team can supply the requested details and adjust the work for that particular occasion.
04
Carry recurring work forward.
Set up an active weekly pattern to prepare upcoming services automatically. Choose how many weeks ahead to prepare, then adjust each service as needed.
Read moreRead less about carry recurring work forward+
Once a weekly pattern has its schedule and repeatable work saved, you can enable automatic preparation and choose a window of one to twelve weeks ahead.
Existing services keep their own edits. Changing the pattern does not rewrite services already prepared, so review those individually when plans change.
05
Keep what your ministry learns.
Keep practical knowledge in your organization, so instructions, contacts, and lessons remain available as people and roles change.
Read moreRead less about keeping what your ministry learns+
An entry can hold a short explanation, a useful link, supporting files, or a service contact. Examples include instructions for opening the building or the details of the company that maintains the heating system.
Entries begin as private drafts. You choose when to share them and who can read them. Connect information to the team or responsibility it supports, so that understanding remains available when someone new steps in.
06
Notice something. Keep it with the work.
Record an observation while carrying out a task, and request follow-up when it would help. Completing the task keeps that observation in its history.
Read moreRead less about observations and follow-up+
For example, equipment may be ready for an outreach event even though a volunteer noticed an intermittent fault. They can complete the preparation task, record what happened, and ask for follow-up.
The observation stays connected to the task and service where it arose. Authorized leaders can review and resolve the follow-up separately, preserving what was noticed and how it was handled.
07
Record what matters afterward.
Choose the information you want to record after a service or event. Metrics are optional, with text, number, currency, and yes-or-no fields.
Read moreRead less about record what matters afterward+
Define the questions on a service pattern; each new service keeps the definitions it started with. If you choose no metrics, there is nothing extra to fill in.
Authorized administrators and participating team leaders can save partial answers and make corrections later. A blank answer stays unrecorded; zero and “no” are valid answers.
08
Everyone can contribute. Not everyone needs an account.
Include people in your teams whether or not they use Themelios themselves. An authorized team leader or administrator can record progress and completion on their behalf.
Read moreRead less about participating without an account+
Someone can belong to a team and have assigned responsibilities without signing in. They can carry out their work while an authorized leader keeps the shared record up to date.
When a task is completed on someone’s behalf, Themelios records both the person who did the work and the user who recorded its completion.
Keep people informed
Connect the work with what you share.
Prepare bulletins, reuse announcements, and bring requests for information or follow-up to people’s attention.
01
Take the stress out of bulletin creation.
Bring the program, key information, and announcements together without starting from scratch. Review the layout and publish a print-ready PDF.
Read moreRead less about preparing bulletins+
The bulletin connects to a dated service, so organization details and information already supplied for that service can be reused. You can prepare an area yourself or identify a contributor or reviewer.
Preview the layout and download a proof before publishing. A published print edition preserves the content that was distributed; later corrections create another edition.
Phone-friendly digital editions, public links, and QR access are part of the planned direction.
02
Reuse announcements where they belong.
Give an announcement its public wording, relevant dates, and an availability window. Select eligible announcements for a bulletin without retyping them.
Read moreRead less about reusing announcements+
For example, one announcement for an upcoming event can remain available for several weeks. Service-linked announcements can reuse known details while keeping the public message separate from the operational service.
The bulletin builder lets you choose available announcements individually or add them together. You can shorten, arrange, or remove the bulletin’s copy without changing the source announcement.
The current publishing destination is the bulletin. Website and social destinations are planned; marking an announcement available does not publish it externally.
03
Bring attention to the next step.
In-app notifications let people know when service information is requested or an observation needs follow-up. The work remains available in My Workspace.
Read moreRead less about in-app notifications+
A request for service information can notify its designated team member when they have an active account and their notification settings allow it. An observation marked for follow-up can notify the relevant team leaders and organization administrators.
Themelios’s notification voice is designed to explain what changed and what needs attention calmly, without turning routine work into an emergency. Opening a notice does not complete the work.
Planned text notifications will also help reach team members who don’t have a Themelios account.
A practical example
Preparing for a weekly outreach.
Your team’s regular outreach preparation becomes a weekly service pattern. Themelios uses it to prepare upcoming dates with tasks, default assignments, deadlines, and information requests.
For each outreach, the team can adjust the work and supply the requested details. Packing instructions, equipment notes, and useful contacts can live in Knowledge and Resources, ready for the next person who steps in.
The approach
Start with the work you actually have.
Begin with what you know about your organization. As everyday work reveals more responsibilities or teams, that foundation can grow with your understanding. Service patterns reflect your own repeatable work; metrics collect only what you choose to ask for.
Knowledge entries start as private drafts. Sharing is a separate choice. Automatically preparing a service does not publish announcements or send messages.
Planned pricing
Include your people. No per-user fees.
One flat rate with notification and storage allowances included. Additional usage costs extra.
Allowances will cover email and text notifications, along with storage for bulletins, shared knowledge, images, and files. Prices and included quantities have not yet been announced.
Have a question about Themelios?
Tell us what you have in mind. We’ll follow up personally.
Themelios is intended to stand on its own. A native connection with Dialogos is part of the product direction, with a straightforward add-on process for customers who want both.