# The Sunday log

> One page for the person holding the clock on a phone: when the service started, each part, the adults in the room and five numbers, with Planning Center's counts filled in.

For: Leader, Pastor, Admin, Owner
Canonical: https://emmauos.com/docs/sunday-log

Open **Today → Sunday** on a phone. Leaders and up. Each service time your church set has its own log.

## During the service

1. Press **Start this Sunday's log**, then **Started** when the service begins.
2. Tap each part as it begins: Welcome, Worship, Message, Response. Next week starts with the same parts.
3. Type the **Adults in the room** at the message.
4. Press **Ended**.

Everything saves as you tap. The screen stays awake while the log is open, where the phone allows it.

## The five numbers

Adults, kids, first-time guests, next steps taken and serving. Planning Center fills in what it can:

- **Kids** and **Serving** from Check-Ins counts for that day's event times.
- **Adults** from a Check-Ins headcount whose name contains "adult".
- **First-time guests** and **Next steps taken** from EmmauOS's own guest visits and connect cards, when your church has one service.

A number filled in this way shows **from Planning Center**. Type over it and it shows **corrected**, with what Planning Center said. Clear it to go back to Planning Center's number.

Under **First five minutes**, count errors, changes and misses. They help the team see what to fix next week.

## The format check

An admin picks your service format once: 60, 75 or 90 minutes, in **Settings → Connections → Planning Center → Guests**, beside the service times. Until then there is no check.

Each format starts with minutes per part: 60 is Welcome 5, Worship 20, Message 28 and Response 7; 75 is 5, 25, 35 and 10; 90 is 5, 30, 40 and 15. An admin can set your own under **Minutes per part**, or through the API and your AI assistant. They must add up to the format, and **Use the default minutes** puts them back. The check then measures against your minutes.

Each Sunday the log then shows a few plain lines comparing the format with the Services plan and with the parts you tapped:

- the total, and the minutes of any part that moved;
- whether the response kept its time, since it is never the part that should shrink;
- plan changes made after Thursday;
- whether the pre-service items were written by Thursday.

There is no score. The Overview's Sunday card adds one quiet line, such as "4 minutes over · 2 changes after Thursday". EmmauOS only reads the plan and never changes it.

## From Needs you and the apps

This week's Sunday is the first card on [Needs you](/docs/needs-you), and it opens this log; once the log is in, the card shows who was in the room, first visits and next steps. The iPhone and Android apps open the same log from that card, with big buttons for each part and the five numbers, and keep the screen on while the service runs. Everything saves to the same place as the web.

## On the Overview

The **Sunday** card shows the last weeks, each service added together, and guests as a share of adults. Many churches see first-time guests at 2 to 4 percent of adults.

Counts only. The Sunday log never holds a name.

## From an AI agent

A leader's agent can read a Sunday with *get-sunday-log* and fill in or correct it with *log-sunday*, under the leader's name. See [AI agents](/docs/ai-agents).
