The eight reports

Every number here is computed live from a fictional congregation — the same reports a church sees on its own people.

Your church's weekly care report.

This week: 13 of 40 people have at least one open flag.

Who the church hasn't seen in a while or is waiting on help, by shepherd.

Shepherd's Overview

For the senior pastor / XO and elders: how each shepherd’s group is doing compared with this church’s own normal.

Last 7 days · Updated daily · Oct 4 – Oct 11, 2026

Church

Grace Fellowship

Report window

Oct 4 – Oct 11, 2026

Generated on Oct 11, 2026, 3:30 PM CT

“Changed” compares with where things stood at the start of this period.

The headline

This week: 13 of 40 people have at least one open flag below — rhythm, deadline, roster or coverage.

Generating report…

Key

New or moved tier in the last 7 days
▲ worse▼ better— no change
Safety or deadline missed Away much longer / longer than usual Starting to miss / for information
A count of 0 is shown, never hidden.
Every mark and every alert ID ↓

1Away much longer than usual

1Deadline missed

3Away longer than usual

4Starting to miss

1Deadline approaching

1No shepherd assigned

1No attendance on file

2One visit on file

RankingAll Reach out only Reach out + Keep in mind

Rates asNumber Percent

Tile counts are people on this page carrying that alert, filters or no filters.

Filtered:GB-A1005One visit on file× clear the alert filterReach out + Keep in mind× clear the ranking filterBoth filters are in the address bar, so this exact view can be linked to.Clear both filters

DescriptionValueDir

On their own rhythm78.4%29/37▲

Counted: People on rhythm29

Out of: People with enough history to read37

DescriptionValueDir

Reached in time50.0%1/2▲

Counted: Reached before the deadline1

Out of: Cases that can be judged2

Crisis today 4 hours ·This week 72 hours ·Soon 7 days ·No rush 14 daysStill inside the deadline, not yet reached: 1

DescriptionValueDir

Roster this report can read92.5%37/40—

Counted: People with two or more attendance events37

Out of: People on the roster40

Nothing on this page matches GB-A1005 under the Reach out + Keep in mind ranking filter right now — as of Oct 11, 2026, 3:30 PM CT. That is an answer, not an empty table.

Groups with at least one person matching GB-A1005 under the Reach out + Keep in mind ranking filter — 0 of 8. Every rate above shows the two numbers it came from.

Confidential — prepared for Grace Fellowship volunteers. Do not forward.

End of the report. The Key, which explains every mark on this page, follows on the next sheet(s).

Key — every mark on this page

AlertIDRankingFieldWhat it means

Away much longer than usualID: GB-A1001Ranking: Reach outField: last attendanceWhat it means: Away 3½ times longer than their usual time between visits, or more.

Deadline missedID: GB-A1007Ranking: Reach outField: first call deadlineWhat it means: An open case passed its first-call deadline without a real person reaching them.

Away longer than usualID: GB-A1002Ranking: Reach outField: last attendanceWhat it means: Away between 2½ and 3½ times longer than their usual time between visits.

Starting to missID: GB-A1003Ranking: Keep in mindField: last attendanceWhat it means: Away between 1¾ and 2½ times longer than their usual time between visits.

Deadline approachingID: GB-A1008Ranking: Keep in mindField: first call deadlineWhat it means: An open case is still inside its first-call deadline, and nobody has reached them yet.

No shepherd assignedID: GB-A1006Ranking: For informationField: who is assignedWhat it means: Nobody owns this person by name, so nothing on this page has an owner either.

No attendance on fileID: GB-A1004Ranking: For informationField: attendance historyWhat it means: On the roster with zero attendance events — no rhythm can be read, and none is guessed.

One visit on fileID: GB-A1005Ranking: For informationField: attendance historyWhat it means: Exactly one attendance event — reading a rhythm needs at least two, so none can be read yet.

Rates

Reached in time — A real person reached them before their deadline passed.

Alert families — the badges on a person’s row, and the sections on their page

RhythmIDs: GB-A1001, GB-A1002, GB-A1003What it means: How this person's attendance compares to their own usual gap — never to anybody else's.

First-call deadlineIDs: GB-A1007, GB-A1008What it means: The first-call deadline set by the person's urgency at intake on an open case attached to this person.

RosterIDs: GB-A1006What it means: What the roster itself is missing about this person, such as nobody being assigned to them.

CoverageIDs: GB-A1004, GB-A1005What it means: Whether there is enough history to read a rhythm at all. Not a judgement about the person.

A badge on a person’s row is that family’s icon and how many of its alerts that person carries. Families with none are left off the row — the strip at the top of the page already shows every zero, and repeating four zeroes on every row would bury the counts that mean something. On a person’s own page every family gets a section, including the empty ones.

Ranking — how hard one line pulls

Reach outWhat it means: Act today. Someone is far off their own rhythm, or a first-call deadline this house set has run out.

Keep in mindWhat it means: Act this week. Starting to miss, or a first-call deadline still running with nobody on it yet.

For informationWhat it means: For information. Nothing here has a clock on it — it is context the other lines are missing.

A ranking describes the ALERT, not the person. A person’s tier — Starting to miss, Away longer than usual, Away much longer than usual — comes from their attendance and is the same arithmetic Return Invite Follow-Up uses, unchanged. Someone can sit at Starting to miss and still carry one Reach out line, because the first-call deadline on their open case ran out while they had only just started to miss visits. The ranking is what tells a volunteer which line to act on first.

The other marks

ExpandchevronA row with this at its right-hand end opens in place, without leaving the page or losing the reader’s spot in the list. Nothing is hidden behind it that changes a number — what opens is the evidence for the number already on the row. Turned the other way, at the top of the page, the same mark is the way back up.

ChangedflagThis mark is new, or moved tier, in the last 7 days. It is worked out fresh every time, from the same history this whole report uses — never kept from an old copy.

▲Direction▲ ▼ —Which way it moved over the same window: ▲ worse, ▼ better, — no change.

What clears ittickThe one smallest thing that makes this line go away — not general advice, but this person’s own numbers, worked out for them specifically.

No single actionstruckThere is no single action that clears this one. A deadline already passed, for instance, can’t be un-passed — reaching out today is still the right thing to do, it just won’t make this particular mark go away.

Tile edgetop edgeA thin colored line along the top of a number tile, and the only color the tile wears: rust means safety or a missed deadline, amber means longer than usual, plain means just information. The number itself is what’s big — that’s the thing to actually look at. A number printed in green is good news: nobody on this roster is carrying that alert.

12 weekssparkline12 weekly readings of the same rate, oldest on the left. The scale always runs 0–100%, so a small wobble is never drawn to look like a collapse. A tinted band is a week with no reading at all — nobody had enough history yet — and the line breaks there instead of joining through it, with the blank weeks counted beside it. The line and its last dot are colored by how this group moved across those 12 weeks: green for getting better, amber for getting worse (a deeper rust if much worse), gray for about steady. The arrow beside it always agrees with the line, and the numbers underneath say the same thing again with no color at all.

Percentile0–100Where one group’s rate sits among the groups whose rate can be read at all, in quarters: Top quarter (75+) · Upper half (50+) · Lower half (25+) · Bottom quarter (0+). The rank and the size of the field are printed with it, because a percentile among six groups is a different claim from a percentile among six hundred. A house with one group gets no percentile at all — there is nothing to be a percentile of.

Own wordsquoteAn intake narrative or a volunteer’s note, printed exactly as it was written, with its date and — for a note — who wrote it. Nothing in a quotation is summarised, rewritten, shortened or given a mood by this build. Longer text folds at about 600 characters behind a “show the rest” link, and both halves are on the page.

Words withheldplaceholder“(words not authorized for display)” stands where a person’s words would have been when the intake record does not carry permission to display them — including when the consent question was never asked at all. The words stay in the record and are not shown; the absence is shown instead, because a blank space would read as somebody having nothing to say.

0Honest zero0A tile reading 0 means nobody carries that alert right now, and a section reading (0) means nothing in that family came up for this person. Zero tiles and zero sections are never hidden, and an empty table is always replaced by a sentence that says what the zero means and when it was true.

%Number / percenttoggleEvery rate on this report shows the count, the percentage, and the total it came out of — all three, every time. The switch above the table only decides which one is printed big; the other two never go away. Pick a view and share the link — whoever opens it sees the same view you were looking at.

Service track chips

Service track chips — shown after a client’s name for every track currently in process; nothing shown means nothing is open right now.

IDID walkBNBenevolenceSCSobriety coachingCNCoaching, Counseling & RecoveryHSHousingEMEmploymentATAttendance & follow-ups

Generating report…

Every number on this report is recomputed twice — once for today and once for the start of the report window — so nothing here is read back from a stored snapshot. That is what takes the moment.

Show this report on a good week

See what it looks like when everyone is coming as often as usual and nobody needs a return invite.

Demonstration data — every person shown is fictional. Grace Fellowship.

Who came back, and how?

11 of 73 people have had care reopened.

The win-back story, step by step.

They're back! Who came home after the church reached out.

?Example data

For the Shepherding Pastor(s) and the connections team: which outreach steps bring people back, and the next step to work.

Follow every person the church contacted after they drifted away, from first review to coming back, and see which step loses the most people.

Report window: A single saved example — no window

Church

Grace Fellowship

Report window

A single saved example — no window

Generated on Oct 11, 2026, 3:30 PM CT

This report reads one saved example with no history behind it, so there is no window to compare against and no “Changed” column.

The headline

So far: 11 of 73 came back and are connected to a person.

Generating report…

Key

Half or more of the outreach list lost stepping into this stage
The biggest drop in an outreach list — the one step to fix first
Counted, never named — see the Key
—No “changed” on this report; there is no history to earn one
A count of 0 is shown, never hidden.
Every mark and every stage ↓

73Picked for outreach

11Connected to a person

Rates asNumber Percent

Every tile is measured against the same 73 people picked for outreach.

The last twelve weeks

no weekly history

Week-by-week history starts once check-ins are connected.

StageOut of 73 invitedChange from the step beforeWhat it means

1Picked for outreach73of 73 · 100.0%starting pointEveryone the church set out to invite back.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)40of 40 · 100.0%

Gone (1–3 years)22of 22 · 100.0%

Long-gone (3+ years)11of 11 · 100.0%

That is as far as this report can go. It knows how many people are at picked for outreach and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

2Reviewed62of 73 · 84.9%73 → 62−11 · −15%A person looked at the name and decided whether outreach was the right thing.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)34of 40 · 85.0%

Gone (1–3 years)19of 22 · 86.4%

Long-gone (3+ years)9of 11 · 81.8%

That is as far as this report can go. It knows how many people are at reviewed and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

3Approved52of 73 · 71.2%62 → 52−10 · −16%Outreach was agreed. Nobody is contacted before somebody says so.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)30of 40 · 75.0%

Gone (1–3 years)15of 22 · 68.2%

Long-gone (3+ years)7of 11 · 63.6%

That is as far as this report can go. It knows how many people are at approved and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

4Reached40of 73 · 54.8%52 → 40−12 · −23%A message or a call went out. Reaching is not replying.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)26of 40 · 65.0%

Gone (1–3 years)11of 22 · 50.0%

Long-gone (3+ years)3of 11 · 27.3%

That is as far as this report can go. It knows how many people are at reached and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

5Replied19of 73 · 26.0%40 → 19−21 · −53%The person answered. This is the first stage that needs something from them rather than from us.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)14of 40 · 35.0%

Gone (1–3 years)4of 22 · 18.2%

Long-gone (3+ years)1of 11 · 9.1%

That is as far as this report can go. It knows how many people are at replied and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

6Returned12of 73 · 16.4%19 → 12−7 · −37%They came back — attended again.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)9of 40 · 22.5%

Gone (1–3 years)2of 22 · 9.1%

Long-gone (3+ years)1of 11 · 9.1%

That is as far as this report can go. It knows how many people are at returned and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

7Connected to a person11of 73 · 15.1%12 → 11−1 · −8%Somebody is walking with them now. This is the stage the whole cycle exists to produce.

Who is at this stage — every division this build actually holds

Drifted (3–12 months)8of 40 · 20.0%

Gone (1–3 years)2of 22 · 9.1%

Long-gone (3+ years)1of 11 · 9.1%

That is as far as this report can go. It knows how many people are at connected to a person and which outreach lists they are in; it does not know WHO, and it will not guess. This count comes from a saved example, not a live connection — real names will show here once check-ins are connected.

The biggest drop: 21 of the 40 people we reached haven’t replied yet. Each outreach list’s own worst step is named in its row below, with the reason a person wrote down.

DescriptionValue

Care reopened, of everyone picked for outreach11of 73 · 15.1%

Counted: People walking with somebody now11

Out of: People picked for outreach73

DescriptionValue

Replied, of everyone reached19of 40 · 47.5%

Counted: People who answered19

Out of: People a message or a call went out to40

The three outreach lists, and where each one leaks

Outreach listPicked for outreachReturnedConnected to a person

Drifted (3–12 months)409of 408of 40

Step by step — the arithmetic, checkable

Picked for outreach Reviewed40 34−15%

Reviewed Approved34 30−12%

Approved Reached30 26−13%

Reached Replied26 14−46%

Replied Returned14 9−36%

Returned Connected to a person9 8−11%

Biggest drop: Reached → Replied — Reached → replied is the steepest drop: most first outreach here is a single text. A follow-up phone call has closed roughly half of this gap in past cycles.

Gone (1–3 years)222of 222of 22

Step by step — the arithmetic, checkable

Picked for outreach Reviewed22 19−14%

Reviewed Approved19 15−21%

Approved Reached15 11−27%

Reached Replied11 4−64%

Replied Returned4 2fewer than 5 — shown as a count

Returned Connected to a person2 2fewer than 5 — shown as a count

Biggest drop: Reached → Replied — Reached → replied again, and worse: contact info this old is often stale. About a third of the phone numbers on file for this outreach list bounced; the deacons are cross-checking against this year's directory.

Long-gone (3+ years)111of 111of 11

Step by step — the arithmetic, checkable

Picked for outreach Reviewed11 9−18%

Reviewed Approved9 7−22%

Approved Reached7 3−57%

Reached Replied3 1fewer than 5 — shown as a count

Replied Returned1 1fewer than 5 — shown as a count

Returned Connected to a person1 1fewer than 5 — shown as a count

Biggest drop: Approved → Reached — Approved → reached: this outreach list's addresses and numbers are the oldest on file. A mailed card has outperformed a call here, and only two of eleven have a working number on record.

The highlighted step in each outreach list is the one with the largest count-based drop; a rate on fewer than 5 people is shown as a count instead — small groups deserve names, not percentages. Each outreach list’s cause line is human-authored context that is not derivable from the counts, and it says so rather than reading as a finding.

Confidential — prepared for Grace Fellowship volunteers. Do not forward.

End of the report. The Key, which explains every mark on this page, follows on the next sheet(s).

Key — every mark on this page

StageWhat it means

1Picked for outreachWhat it means: Everyone the church set out to invite back.

2ReviewedWhat it means: A person looked at the name and decided whether outreach was the right thing.

3ApprovedWhat it means: Outreach was agreed. Nobody is contacted before somebody says so.

4ReachedWhat it means: A message or a call went out. Reaching is not replying.

5RepliedWhat it means: The person answered. This is the first stage that needs something from them rather than from us.

6ReturnedWhat it means: They came back — attended again.

7Connected to a personWhat it means: Somebody is walking with them now. This is the stage the whole cycle exists to produce.

The order is fixed and each stage is a subset of the one before it, so a count can never go up as you read down. Every stage is shown against the SAME total — everyone picked for outreach — as well as against the stage immediately before it, because “half of the people we reached replied” and “a fifth of the outreach list replied” are two different facts and a reader is owed both.

The other marks

Tile edgetop edgeThere is no drift tier on this report, so the thin edge along the top of each stage tile is not a person’s own severity — it is how much of the outreach list was lost stepping INTO that stage, read off the same step arithmetic the row below it already shows in numbers: rust at half or more lost, amber at a quarter to a half, plain under a quarter or too few people for a rate at all. The cut points are a first pass, not yet a PO ruling the way the five-person rate floor is.

Twelve weeksblank sparklineThe same twelve-week Sparkline the rest of the suite draws real weekly history with, and it is blank on this report — on purpose, not by omission. This report reads one static seeded cycle with no dates behind it, so there is no earlier week to recompute any rate at, the same reason this page carries no “Changed” column. A drawn shape would be invented; the blank line is the honest answer.

Biggest droprustThe one step in an outreach list that loses the most PEOPLE — a count, not a rate, so a steep percentage on four people cannot outrank a shallow one on forty. Ties go to the earlier step, because the earliest leak is the one worth plugging first.

The steparrowThe move from one stage to the next, printed as both counts and, where the group is big enough, the share lost between them. A rate on fewer than 5 people is shown as a bare count instead — small groups deserve names, not percentages, and “−50%” on four people is a sentence about two people wearing a statistic.

Counted, never namedpeopleThis report can tell you how many people are at a stage and which outreach lists they are in. It cannot tell you WHO, and it does not pretend to: the Check-In connector that would record a particular person moving from reached to replied builds inside Lost Sheep P1 and has not landed. Expanding a stage gives you every division this build actually holds, and then says where it stops. Welcome Home List names the people who came back; it is a separate seeded record and its numbers do not join to these.

0Honest zero0A stage reading 0 means nobody has reached it, and no stage is ever hidden for being empty. All seven are always listed, in order, against the same total.

—No changed flagabsentEvery other report in this suite carries a “Changed” column earned by recomputing itself at the start of the report window. THIS ONE DOES NOT, and the absence is the honest answer rather than an oversight: it reads a static seeded record with no history behind it, so there is no earlier moment to recompute at. A flag derived from nothing would be exactly the lie the rest of the suite spends two passes per request avoiding. It arrives when the Check-In connector does.

Generating report…

Reading the saved example and dividing every stage by the outreach list it came from.

Demonstration data — every outreach list shown is fictional. Grace Fellowship.

Whose paperwork is stuck, and where?

2 of 5 open document chains are stuck past the expected wait.

The document chain, and where it's stuck.

ID Walk

For caseworkers and volunteers, daily, and the Shepherding Pastor(s) clearing the bottlenecks: each person’s next step on their ID and documents.

Every open ID-document chain — birth certificate, Social Security card, Texas ID — where each one is, and which are stuck waiting on an agency.

Last 12 weeks · Updated daily · Jul 19 – Oct 11, 2026

Church

Grace Fellowship

Report window

Jul 19 – Oct 11, 2026

Generated on Oct 11, 2026, 3:30 PM CT

Days waiting are counted to the moment this report was generated; the weekly readings and the completed count cover these 12 weeks.

The headline

2 of 5 open document chains are stuck past the expected wait as of Oct 11, 2026, 3:30 PM CT; 1 chain was completed in the last 12 weeks.

Generating report…

Key

Safety or deadline missed Away much longer / longer than usual Starting to miss / for information
The link each chain is on now
A count of 0 is shown, never hidden.
Every mark and every expected wait ↓

2 of 5 open document chains are stuck past the expected wait.

5Open chains

2Stuck past the expected wait

1Completed, last 12 weeks

A document arrived, by weekWeek to Oct 11: 0 of 5 open6 of 12 weeks had a document arrive.

Every open document chain, stuck first. Read each row left to right: who, the three links of the chain with the one it is on now ringed, how long that link has waited, where it stands, and who shepherds it.
Person	The chain	Days waiting	Where it stands	Shepherd
Annette KowalczykIDGB-1006 · 1 of 3 in hand	Birth certificate — In hand Social Security card — Past expected wait, the link this chain is on now Texas ID card — Not yet Social Security card (replacement) requested 23 days ago — 9 days past the expected wait of about 14.	23 dayssince it was requestedexpected in ~14	Past expected wait	Priya Nair
Jerome TateIDGB-1007 · 0 of 3 in hand	Birth certificate — Past expected wait, the link this chain is on now Social Security card — Not yet Texas ID card — Not yet Birth certificate requested 19 days ago — 4 days past the expected wait of about 15.	19 dayssince it was requestedexpected in ~15	Past expected wait	Tomás Rivera
Faye LindholmIDGB-1008 · 2 of 3 in hand	Birth certificate — In hand Social Security card — In hand Texas ID card — Requested, the link this chain is on now Texas ID card requested 9 days ago — expected in about 21 days.	9 dayssince it was requestedexpected in ~21	Requested	Elena Cho
Carlos Mendez-RuizIDGB-1009 · 0 of 3 in hand	Birth certificate — Requested, the link this chain is on now Social Security card — Not yet Texas ID card — Not yet Birth certificate requested 5 days ago — expected in about 15 days.	5 dayssince it was requestedexpected in ~15	Requested	Dana Whitfield
Odessa GrimesIDGB-1010 · 1 of 3 in hand	Birth certificate — In hand Social Security card — Ready to request, the link this chain is on now Texas ID card — Not yet Birth certificate arrived 16 days ago; Social Security card (replacement) has not been requested yet.	16 dayssince the last document arrivednot requested yet	Ready to request	Priya Nair

Completed in the last 12 weeks — 1 chain

Lorenzo Pruitt GB-1005all 3 in hand by Sep 29

Confidential — prepared for Grace Fellowship volunteers. Do not forward.

End of the report. The Key, which explains every mark on this page, follows on the next sheet(s).

Key — every mark on this page

Where a link isWhat it means

Past expected waitRequested, and it has waited at least as long as this link's expected wait without arriving. Time for a human to check on it.

RequestedRequested, and still inside this link's expected wait. Nothing to chase yet.

Ready to requestEverything before it is in hand and nobody has requested it yet. The chain names no expected wait for this, so it is never called stuck — the days it has sat ready are still printed.

Not yetCannot start until the link before it is in hand.

In handThe document has arrived, and a volunteer recorded it in hand.

The chain, and what it expects

Link, in orderAgencyExpected waitFee

Birth certificateAgency: Texas Vital Statistics (DSHS) — or the birth state's registrarExpected wait: ~15 daysFee: ~$23 (estimate — confirm at first walk)

Social Security card (replacement)Agency: Social Security Administration (form SS-5)Expected wait: ~14 daysFee: Free

Texas ID cardAgency: Texas DPS (Identification Certificate)Expected wait: ~21 daysFee: ~$16 (estimate — confirm at first walk; fee-waiver eligibility unverified)

These waits and fees are ESTIMATES written into GraceBridge before the first real walk confirms them, and they are printed here so a reader can see exactly what “stuck” is measured against. A link is called stuck only when it has been requested and has waited at least this long.

The other marks

Current linkringThe earliest link in the chain that is not yet in hand — the one the chain is on now. Days waiting, and the status at the end of the row, are about this link.

→Chain orderarrowThe order the chain works in: each link waits on the one before it — the Social Security card on the birth certificate, the Texas ID on the Social Security card.

Row tonedotThe suite’s own severity, and nothing new: rust when a link in the chain is past its expected wait, amber when the current link is requested and still inside it, plain when the current link is ready and nobody has requested it yet.

9Days waitingnumberWhole days, counted to the moment the report was generated, from the line printed under the number: since the current link was requested; or, if it has not been, since the document before it arrived; or since the walk opened; or since the case opened.

12 weekssparklineOne reading per week for the last 12, oldest on the left: of the chains open at any moment that week, the share that had a document arrive inside it. Each is a full recomputation from the same records with later ones filtered out. The scale is fixed at 0–100%. A tinted band is a week when no chain was open — there was nothing to read, so the line breaks rather than drawing a zero, and the number of blank weeks is printed beside it.

Back to the reportschevronThe one icon on this page, at its top-left: the way back to the reports index. No row on the board opens or hides anything — every chain is shown whole.

0Honest zero0A count of 0 on this page means nobody is in that state right now, and it is printed, never hidden. A board with no open chain is replaced by a sentence saying so and as of when.

Service track chips

Service track chips — shown after a client’s name for every track currently in process; nothing shown means nothing is open right now.

IDID walkBNBenevolenceSCSobriety coachingCNCoaching, Counseling & RecoveryHSHousingEMEmploymentATAttendance & follow-ups

Generating report…

Reading every case that asked for ID documents and its records, then recomputing each chain at the end of each of the last twelve weeks.

Demonstration data — every person shown is fictional. Grace Fellowship.

Every Alert and Why

2 of 14 checks needed a person; 1 was checked and needed no action.

Every alert GraceBridge raised, who was told, and how the church responded.

Alert History

For the Shepherding Pastor(s) and executive pastor: every alert, who was told, and what was done.

Last 12 weeks · Updated daily · Jul 19 – Oct 11, 2026

Church

Grace Fellowship

Report window

Jul 19 – Oct 11, 2026

Generated on Oct 11, 2026, 3:30 PM CT

Decisions, alerts and outcomes are counted over these 12 weeks, to the moment this report was generated.

The headline

2 of 14 weekly checks needed a person — 1 needed no action, none are still waiting for a reply (as of Oct 11, 2026, 3:30 PM CT).

Generating report…

Key

act now reach out soon keep in mind for information
Checked — no action neededa person reviewed it and no action was needed
A count of 0 is shown, never hidden.
Every level, every delivery and every outcome ↓

2 of 14 checks needed a person; 1 was checked and needed no action.

14Decisions, last 12 weeks

1Act now

2Reach out soon

1Keep in mind

2Alerted a human

Alerted a human, by weekWeek to Oct 11: 2 of 61 week with alerts.

Of the 2 alertsText service accepted it1Delivered0Not delivered0Sent to the text service0No way to send yet (texting not set up)0No way to send yet (texting not set up)1No crisis contact set0Send failed0Checked — no action needed1Acted1Acknowledged0Not yet0

Every decision GraceBridge recorded in the last 12 weeks, most serious first and newest first. Read each row left to right: the level, when and which decision, who it was about, what fired, who was alerted, and what came of it.

Level	When	Person	What fired	Who was alerted	Outcome
Crisis	Oct 9, 3:27 AM CTTier 2 reply screen	Rosa DelgadoGB-0996	Crisis language (1 phrase) Crisis — Tier 2 reply screen for Rosa Delgado: Crisis language (1 phrase). Handed to text and accepted — held to the verified recipient, not to Dana Whitfield (recipient lock on). Accepted is not confirmed delivered. Checked — no action needed by Dana Whitfield 59 minutes after. Why — the policy's reason crisis language detected in a Tier 2 reply (1 phrase) — routed to a human immediately	Text service accepted itHanded to text and accepted — held to the verified recipient, not to Dana Whitfield (recipient lock on). Accepted is not confirmed delivered.	Checked — no action needed59 minutes after · Dana Whitfield
Reach out soon	Oct 11, 1:25 PM CTintake read	Marcus BoydSCHSGB-1002	Needs a call today Reach out soon — intake read for Marcus Boyd: Needs a call today. No one — this decision raised no alert. Acted on: a note signed by Susan Marsh 1 minute after. Why — GraceBridge's own reasoning needs a call today — flagged for human review immediately	No alertNo one — this decision raised no alert.	Acted1 minute after · Susan Marsh
Reach out soon	Oct 11, 12:27 PM CTintake screen	Marcus BoydSCHSGB-1002	Declared crisis-today at intake Reach out soon — intake screen for Marcus Boyd: Declared crisis-today at intake. Not sent — nothing is set up to send it (meant for Dana Whitfield). Acted on: a note signed by Susan Marsh 59 minutes after. Why — the policy's reason seeker declared crisis-today — human review immediately	No way to send yet (texting not set up)Not sent — nothing is set up to send it (meant for Dana Whitfield).	Acted59 minutes after · Susan Marsh
Keep in mind	Oct 8, 1:27 PM CTintake read	Grace OkaforBNGB-1001	Service Track: Bills & essentials stabilization (Benevolence arm) (medium confidence) Keep in mind — intake read for Grace Okafor: Service Track: Bills & essentials stabilization (Benevolence arm) (medium confidence). No one — this decision raised no alert. Acted on: a note signed by Priya Nair 22 hours after. Why — GraceBridge's own reasoning Reduced hours plus a new caregiving cost may outlast one bill; a short stabilization plan is worth offering.	No alertNo one — this decision raised no alert.	Acted22 hours after · Priya Nair
For information	Oct 10, 9:27 AM CTintake screen	Delia ReyesBNGB-1003	Nothing — no crisis language, no crisis declared For information — intake screen for Delia Reyes: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Oct 8, 12:27 PM CTintake screen	Grace OkaforBNGB-1001	Nothing — no crisis language, no crisis declared For information — intake screen for Grace Okafor: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Oct 4, 3:27 PM CTintake screen	Carlos Mendez-RuizIDGB-1009	Nothing — no crisis language, no crisis declared For information — intake screen for Carlos Mendez-Ruiz: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Oct 3, 5:27 PM CTintake screen	Rosa DelgadoGB-0996	Nothing — no crisis language, no crisis declared For information — intake screen for Rosa Delgado: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Sep 21, 3:27 PM CTintake screen	Marisol QuinteroCNGB-1004	Nothing — no crisis language, no crisis declared For information — intake screen for Marisol Quintero: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Sep 20, 3:27 PM CTintake screen	Jerome TateIDGB-1007	Nothing — no crisis language, no crisis declared For information — intake screen for Jerome Tate: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Sep 10, 3:27 PM CTintake screen	Odessa GrimesIDGB-1010	Nothing — no crisis language, no crisis declared For information — intake screen for Odessa Grimes: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Aug 30, 3:27 PM CTintake screen	Annette KowalczykIDGB-1006	Nothing — no crisis language, no crisis declared For information — intake screen for Annette Kowalczyk: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Aug 15, 3:27 PM CTintake screen	Faye LindholmIDGB-1008	Nothing — no crisis language, no crisis declared For information — intake screen for Faye Lindholm: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised
For information	Jul 31, 3:27 PM CTintake screen	Lorenzo PruittGB-1005	Nothing — no crisis language, no crisis declared For information — intake screen for Lorenzo Pruitt: Nothing — no crisis language, no crisis declared. No one — this decision raised no alert. Why — the policy's reason no crisis language found and no crisis declared	No alertNo one — this decision raised no alert.	Nothing raised

Every one of the 2 alerts has a human outcome recorded — 0 not yet (as of Oct 11, 2026, 3:30 PM CT).

Confidential — prepared for Grace Fellowship volunteers. Do not forward.

End of the report. The Key, which explains every mark on this page, follows on the next sheet(s).

Key — every mark on this page

LevelWhat it means

CrisisWhat it means: Crisis language was found — in an intake story or in a reply on the after-care journey. GraceBridge called for a human immediately.

Reach out soonWhat it means: A human was called for without crisis language: the person declared crisis-today on their intake, or GraceBridge judged the story needed someone to reach out soon.

Keep in mindWhat it means: No human was called. GraceBridge named a service track of care at medium or high confidence — a suggestion a volunteer carries in person, never an automated offer.

For informationWhat it means: GraceBridge read it and raised nothing — no crisis language, no crisis declared, and no service track named, or one named at low confidence.

Who was alerted, and whether it went

DeliveryWhat it means

Text service accepted itWhat it means: The text service took the message. That means queued, not read: a queued message can still come back undelivered. The delivery read-back upgrades this row when the provider confirms.

DeliveredWhat it means: The text service came back and confirmed it arrived. While the recipient lock is on, it arrived at the house's verified recipient, not at the designated contact — the row says which.

Not deliveredWhat it means: The text service came back and said it did not arrive. Nobody was told. The crisis pin on the casework dashboard is the surface.

Sent to the text serviceWhat it means: Recorded before run 169, when this product wrote “sent” the moment a provider accepted a message. It means the same thing “Text service accepted it” means now; nothing confirmed it arrived.

No way to send yet (texting not set up)What it means: A contact is configured but texting is not set up on this house, so nothing was sent. The crisis pin on the casework dashboard is the surface.

No crisis contact setWhat it means: No crisis contact is set for this house, so nothing was sent. The crisis pin on the casework dashboard is the surface.

Send failedWhat it means: Every way tried to send it refused or dropped the message. Nothing reached anyone.

Whether it deserved to be

OutcomeWhat it means

Checked — no action neededWhat it means: A volunteer looked and recorded that no action was needed. Counted here whatever else happened on the case — it is the answer this log exists to keep.

ActedWhat it means: A volunteer contact or a signed volunteer note was recorded on the case after the decision.

AcknowledgedWhat it means: A volunteer recorded that a human has it, and no contact or note has been recorded since. Seen, not yet acted on.

Not yetWhat it means: Nothing a human did about this decision is on record yet.

The other marks

Row tonedotThe row’s level and nothing else: rust for act now and reach out soon, amber for keep in mind, plain for information. Rows are grouped most serious first — act now, then reach out soon, keep in mind and information — newest first within each.

▸WhydisclosureOpens the one sentence of why that was written when the decision was made: GraceBridge’s own rationale on a read, the crisis policy’s reason on a screen. Never the person’s story or reply, and never the crisis phrases that matched — a screen records how many matched, not which. A rationale that repeats 5 or more words of the person’s own story in a row is withheld, and so is GraceBridge’s rationale for a person who did not consent to their story being shown; the row says which.

12 weekssparklineOne reading per week for the last 12, oldest on the left: of the decisions GraceBridge recorded that week, the share that alerted a human. The scale is fixed at 0–100%. A tinted band is a week with no decision at all — there was nothing to read, so the line breaks rather than drawing a zero, and the number of blank weeks is printed beside it.

Back to the reportschevronThe one icon on this page, at its top-left: the way back to the reports index.

0Honest zero0A count of 0 on this page means nothing of that kind was recorded in the window, and it is printed, never hidden. A log with no decision on it is replaced by a sentence saying so and as of when.

Service track chips

Service track chips — shown after a client’s name for every track currently in process; nothing shown means nothing is open right now.

IDID walkBNBenevolenceSCSobriety coachingCNCoaching, Counseling & RecoveryHSHousingEMEmploymentATAttendance & follow-ups

Generating report…

Reading every case's decision records and the later records that say what a human made of them, then counting each of the last twelve weeks.

Demonstration data — every person shown is fictional. Grace Fellowship.

Who has quietly stopped coming?

8 of 40 people are off their own rhythm.

Who has fallen off their own rhythm, and how badly.

Return Invite Follow-Up

?Example data

For the Shepherding Pastor(s), who assign the calls, and the shepherds who make them: this week’s list.

Who has fallen off their own rhythm, and how badly — ranked by how far each person is from their own baseline, never by raw days off.

Last 7 days · Updated daily · Oct 4 – Oct 11, 2026

Church

Grace Fellowship

Report window

Oct 4 – Oct 11, 2026

Generated on Oct 11, 2026, 3:30 PM CT

“Changed” compares with where things stood at the start of this period.

The headline

8 of 40 people are off their own rhythm as of Oct 11, 2026, 3:30 PM CT — longest away first below, by how far each is from their own baseline.

Generating report…

Key

New or moved tier in the last 7 days
▲ worse▼ better— no change
Safety or deadline missed Away much longer / longer than usual Starting to miss / for information
A count of 0 is shown, never hidden.
Every mark and every alert ID ↓

1Away much longer than usual

3Away longer than usual

4Starting to miss

29On their own rhythm

3Not enough history

TableOff rhythm only (8)Everyone (37)

Rates asNumber Percent

Tile counts are everyone on the roster in that tier, filters or no filters.

Seed datafreshest record Oct 1137 of 40 have enough history— details

Where this data comes from

Seed dataExample — seeded demonstration data

Most recent record on file: Oct 11 — how fresh the underlying data is, not the moment this report ran.

NameRhythmRatioShepherdChanged

1Odette BranniganAway much longerevery 9d — been 33d3.7×Priya Nair▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1001Away much longer than usualField: last attendanceRanking: Reach outChanged: ▲Message: Odette Brannigan usually comes about every 9 days, and it has now been 33 days — 3.7 times that rhythm. Call today — this is the longest gap on the page, not a busy week. (GB-A1001)What clears it: One visit clears this outright — attendance on file for Odette Brannigan resets the gap from 33 days to zero, and nothing here reads as starting to miss under 15.8 days (1.75× a 9-day rhythm). There is no heavier tier above this one; left alone the gap just grows.

Attendance record — the primary receipt

Jun 1
Jun 10
Jun 19
Jun 28
Jul 7
Jul 16
Jul 25
Aug 3
Aug 12
Aug 21
Aug 30
Sep 8

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 9 days. Last seen Sep 8, 33 days before this report ran.

In Odette’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Odette Brannigan, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Odette — Shepherd’s Overview’s person page

2Winifred AchebeAway longerevery 30d — been 87d2.9×Renee Foster—

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1002Away longer than usualField: last attendanceRanking: Reach outChanged: —Message: Winifred Achebe usually comes about every 30 days, and it has now been 87 days — 2.9 times that rhythm. Worth a call this week rather than a text. (GB-A1002)What clears it: One visit clears this outright — attendance on file for Winifred Achebe resets the gap from 87 days to zero, and nothing here reads as starting to miss under 52.5 days (1.75× a 30-day rhythm). Left alone it becomes Away much longer than usual in 17.7 days.

Attendance record — the primary receipt

Aug 20
Sep 19
Oct 19
Nov 18
Dec 18
Jan 17
Feb 16
Mar 18
Apr 17
May 17
Jun 16
Jul 16

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 30 days. Last seen Jul 16, 87 days before this report ran.

In Winifred’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Winifred Achebe, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Winifred — Shepherd’s Overview’s person page

3Margaret EllisonAway longerevery 8d — been 21d2.7×Dana Whitfield▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1002Away longer than usualField: last attendanceRanking: Reach outChanged: ▲Message: Margaret Ellison usually comes about every 8 days, and it has now been 21 days — 2.7 times that rhythm. Worth a call this week rather than a text. (GB-A1002)What clears it: One visit clears this outright — attendance on file for Margaret Ellison resets the gap from 21 days to zero, and nothing here reads as starting to miss under 14 days (1.75× a 8-day rhythm). Left alone it becomes Away much longer than usual in 6.7 days.

Attendance record — the primary receipt

Jun 24
Jul 2
Jul 10
Jul 18
Jul 26
Aug 3
Aug 11
Aug 19
Aug 27
Sep 4
Sep 12
Sep 20

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 8 days. Last seen Sep 20, 21 days before this report ran.

In Margaret’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Margaret Ellison, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Margaret — Shepherd’s Overview’s person page

4Walter KimAway longerevery 10d — been 25d2.5×Elena Cho▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1002Away longer than usualField: last attendanceRanking: Reach outChanged: ▲Message: Walter Kim usually comes about every 10 days, and it has now been 25 days — 2.5 times that rhythm. Worth a call this week rather than a text. (GB-A1002)What clears it: One visit clears this outright — attendance on file for Walter Kim resets the gap from 25 days to zero, and nothing here reads as starting to miss under 17.5 days (1.75× a 10-day rhythm). Left alone it becomes Away much longer than usual in 9.7 days.

Attendance record — the primary receipt

May 29
Jun 8
Jun 18
Jun 28
Jul 8
Jul 18
Jul 28
Aug 7
Aug 17
Aug 27
Sep 6
Sep 16

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 10 days. Last seen Sep 16, 25 days before this report ran.

In Walter’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Walter Kim, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Walter — Shepherd’s Overview’s person page

5Bernard OseiStarting to missevery 14d — been 32d2.3×Tomás Rivera—

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1003Starting to missField: last attendanceRanking: Keep in mindChanged: —Message: Bernard Osei usually comes about every 14 days, and it has now been 32 days — 2.3 times that rhythm. Say hello before it becomes a gap. (GB-A1003)What clears it: One visit clears this outright — attendance on file for Bernard Osei resets the gap from 32 days to zero, and nothing here reads as starting to miss under 24.5 days (1.75× a 14-day rhythm). Left alone it becomes Away longer than usual in 2.7 days.

Attendance record — the primary receipt

Apr 8
Apr 22
May 6
May 20
Jun 3
Jun 17
Jul 1
Jul 15
Jul 29
Aug 12
Aug 26
Sep 9

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 14 days. Last seen Sep 9, 32 days before this report ran.

In Bernard’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Bernard Osei, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Bernard — Shepherd’s Overview’s person page

6Louise FontaineStarting to missevery 7d — been 15d2.2×Priya Nair▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1003Starting to missField: last attendanceRanking: Keep in mindChanged: ▲Message: Louise Fontaine usually comes about every 7 days, and it has now been 15 days — 2.2 times that rhythm. Say hello before it becomes a gap. (GB-A1003)What clears it: One visit clears this outright — attendance on file for Louise Fontaine resets the gap from 15 days to zero, and nothing here reads as starting to miss under 12.3 days (1.75× a 7-day rhythm). Left alone it becomes Away longer than usual in 2 days.

Attendance record — the primary receipt

Jul 11
Jul 18
Jul 25
Aug 1
Aug 8
Aug 15
Aug 22
Aug 29
Sep 5
Sep 12
Sep 19
Sep 26

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 7 days. Last seen Sep 26, 15 days before this report ran.

In Louise’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Louise Fontaine, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Louise — Shepherd’s Overview’s person page

7Hollis BramwellStarting to missevery 7d — been 15d2.2×unassigned▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1003Starting to missField: last attendanceRanking: Keep in mindChanged: ▲Message: Hollis Bramwell usually comes about every 7 days, and it has now been 15 days — 2.2 times that rhythm. Say hello before it becomes a gap. (GB-A1003)What clears it: One visit clears this outright — attendance on file for Hollis Bramwell resets the gap from 15 days to zero, and nothing here reads as starting to miss under 12.3 days (1.75× a 7-day rhythm). Left alone it becomes Away longer than usual in 2 days.

GB-A1006No shepherd assignedField: who is assignedRanking: For informationChanged: —Message: Nobody is assigned to Hollis Bramwell — pick a shepherd, because every other line on this list is waiting on someone to own it. (GB-A1006)What clears it: One name clears this — put any volunteer in the shepherd field for Hollis Bramwell. This line reads the field being empty and nothing else, so filling it in is the whole of the fix.

Attendance record — the primary receipt

Jul 11
Jul 18
Jul 25
Aug 1
Aug 8
Aug 15
Aug 22
Aug 29
Sep 5
Sep 12
Sep 19
Sep 26

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 7 days. Last seen Sep 26, 15 days before this report ran.

In Hollis’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Hollis Bramwell, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Hollis — Shepherd’s Overview’s person page

8Carol JenningsStarting to missevery 7d — been 13d1.8×Renee Foster▲

Why this name is here — and what would clear it

AlertFieldRankingChangedMessage

GB-A1003Starting to missField: last attendanceRanking: Keep in mindChanged: ▲Message: Carol Jennings usually comes about every 7 days, and it has now been 13 days — 1.8 times that rhythm. Say hello before it becomes a gap. (GB-A1003)What clears it: One visit clears this outright — attendance on file for Carol Jennings resets the gap from 13 days to zero, and nothing here reads as starting to miss under 12.3 days (1.75× a 7-day rhythm). Left alone it becomes Away longer than usual in 4.8 days.

Attendance record — the primary receipt

Jul 14
Jul 21
Jul 28
Aug 4
Aug 11
Aug 18
Aug 25
Sep 1
Sep 8
Sep 15
Sep 22
Sep 29

Baseline is the median gap between these 12 events (not the average — one long gap should not flatter or ruin the reading): 7 days. Last seen Sep 29, 13 days before this report ran.

In Carol’s own words

Verbatim. Nothing here is summarised, rewritten or given a mood.

No intake record is attached to Carol Jennings, so there are no words of their own on this page. A case is attached only when the full name on it matches exactly one name on the roster — see the foot of this page for how many open cases that rule could and could not place. No case was ever attached here — this is not a person with nothing to say.

Everything on Carol — Shepherd’s Overview’s person page

8 rows — longest away first, by how far each person is from THEIR OWN baseline, never by raw days off. Every rate below shows the two numbers it came from.

DescriptionValueDir

On their own rhythm29of 37 · 78.4%▲

Counted: People on rhythm29

Out of: People with enough history to read37

DescriptionValueDir

Roster this report can read37of 40 · 92.5%—

Counted: People with two or more attendance events37

Out of: People on the roster40

Not enough history yet — 3 people of 40Expand ↓

Fewer than two attendance events on file for each person below — no baseline can be computed yet, so nobody here is scored or flagged as off rhythm. They stay on the page instead of disappearing from the math.

Isabel Concannon1 attendance event on file
Faye Delacroix-Nwosu1 attendance event on file
Marcus WhitfieldNo attendance recorded yet