Reading a person's profile

A profile is one page, not a set of tabs. Everything Scout holds about someone is on it, arranged so the read comes first and the record sits beside it.

How the page is laid out

At the top, the identity card: photo, name, status pill, contact details, tags, and a pencil for Edit person.

Below that, two columns.

On the left, what Scout has to say.

• What Scout noticed is the charcoal card, dated Updated {date} on the right. It carries the narrative paragraph and Suggested next steps.
• Engagement & rhythm gives the one-word trend (Trending up, Slipping, Steady) with a sentence of context like "Was Needs Attention in Q2 2026.", then a row per domain: giving, serving, groups.
• Journey is the milestone timeline, oldest first: Added to Scout, Joined {group}, Joined {team}, Started Giving, First Check-in.

On the right, the record. A rail of collapsible sections: Household, About {first name}, Pastoral record, Groups & teams, Serving, Giving, Saved lists. Collapsed, each shows a count and one freshest fact. Scout remembers which ones you leave open.

Before you reach out

Two lines to read first.

Who last made contact. The contact block carries a line like "Nic followed up · Aug 4". It is deliberately visible to anyone who can open the profile, because it exists to stop two staff members calling the same person on the same afternoon. It states the fact of contact and never the words.

What Scout noticed. The narrative names a behavior, a timeframe, and a person, and compares it to that person's own baseline. It never guesses at motive or feeling. If it says something is new for someone, that is a comparison against their own pattern.

Reaching out

Email {first name} opens your mail client. The phone number is a tel: link. In the peek panel both sit under Reach {first name}.

Draft a check-in asks Scout for a first draft. A Check-in draft box appears with an editable subject and body, Copy, and Open in email, under the line "Scout wrote a first draft. Make it yours before you send it."

Add to my follow-ups puts the person on your own list and confirms with "Added to your follow-ups · due in a week".

Writing it down

Add note, or the Pastoral record section, opens a box placeheld "Add a note about {first name}...". Three checkboxes travel with it. Tick Prayer request if it is one; prayer notes carry a Prayer chip and sit a step lower in the visual order than an ordinary note. Tick Ask someone to check on them when what you wrote needs a pastor's eyes, and the note also lands on the People to check on worklist, with your note as the context. Tick Keep with the care team for a counseling conversation or anything else that should not sit at ordinary staff visibility: the note is then visible only to your confirmed care set and admins — pastors and admins until a care set exists — plus whoever wrote it. It carries a Care team only chip for the people who can see it, and it stays out of Scout's AI summaries and the shared prayer list.

Notes need Write pastoral notes to add and View pastoral notes to read. A person without those does not see the Pastoral record section at all.

The same section holds two worklists, Worth a look and To check on, with the buttons that close them out: Worth celebrating, Had a conversation, Followed up. Each records who did it and when. Verbs are past tense on purpose, since they claim something you actually did.

Tags, household, and the rest of the rail

+ Add tag searches your existing tags and creates a new one from the same box.

Household is the family structure. Groups & teams is a read-only ledger, so adding someone to a group happens on the group's page rather than here. See Members, leaders, and join requests.

Giving is stripped entirely for anyone without View giving data, along with Scout's narrative. That is covered in What each permission controls.

Pausing someone's serving

Pause serving sits in the header for anyone with Edit people. It opens a small popover with two choices: Where to pause (All teams, or one of their teams by name) and How long to pause (2 weeks, A month, Until I resume it). While paused, Scout does not offer them for any slot the pause covers; a pause on one team leaves them available on the others. The person is not told. Nothing reaches churchHQ, and nobody on the team sees a reason.

Once set, the chip reads Serving paused and opening it shows the scope and the end date, with Keep paused and Resume serving. Resume serving clears every active pause on the person, not one team. A dated pause ends itself; an open one waits for someone to resume it.

It is the same act as the Pause their serving? question on a serving-strain row of the dashboard, for the case where there was no notice.

CHECK FIRST is the one chip with no control behind it. It is derived from the nightly run for someone Scout has classified at risk, and it appears and disappears on its own.

What is not here

• No delete. Retiring someone is Edit Person → Status → Archived.
• No recalculate. Scout's read is written by a nightly batch and there is no refresh button. A new record shows thin-data language for a few weeks.
• No tabs. If someone tells you to check the Notes tab, they mean the Pastoral record section in the right rail.

Next

• What Scout's statuses mean
• Working your list on the dashboard