How to run foster check-ins that fosters actually complete

If your foster check-in completion rate is under 60 percent, the problem is not your fosters. It's the system you're asking them to use. Here's the design that takes completion from 40 percent to 85 percent without adding a single guilt-laden reminder.

Every foster coordinator has had this week. You sent the check-in request on Monday. By Friday, 14 of 38 fosters responded. You spend the weekend personally messaging the other 24, half apologize and half promise to "do it tonight," and on Monday you start over. The completion rate stays around 40 percent. The director asks why we don't have good data on the dogs. You don't have a good answer that isn't "because I'm one person."

The instinct is to blame foster engagement. Don't. Fosters who signed up to take a dog into their home for free are, by definition, engaged. If they're not completing your check-ins, the check-in is wrong, not them.

Why most check-ins fail

The check-in formats we see at struggling rescues almost always share three traits:

1. They live in the wrong channel. An email to someone who lives in text messages, or a group-chat ping that gets buried under 80 other messages, is not a check-in. It's a hope.
2. They take too long. A 12-question Google Form with required free-text fields takes 8 minutes. Fosters do it once, hate it, and skip the next three.
3. They have no acknowledgement. The foster fills out the form, nothing happens. No "got it, thanks," no visible record of their submission. They start wondering whether it even mattered.

Fix those three things and the math changes. Here's the design that works.

Design rule 1: meet the foster in their channel

For most rescues in the U.S., that channel is SMS. Open rates run above 95 percent within an hour. Email open rates, at best, run 30 to 40 percent. If you're sending check-in requests by email, you're losing more than half your completion rate at the delivery step, before the foster has even seen the question.

The pragmatic version: send the prompt as a text message with a single link to a one-page form. Don't ask them to log in. Don't ask them to install anything. The link opens, the form is two screens, they're done in 60 seconds.

Design rule 2: ask five things, not twelve

A good weekly check-in asks for exactly enough to spot a problem and nothing more. The five questions that earn their keep:

• Eating and drinking normally? Yes / Some concerns / No
• Energy and behavior? Same as last week / Better / Worse
• Any health concerns? One line of text, optional
• How are you doing as a foster this week? Great / Fine / Could use a check-in call
• One photo. Optional but encouraged. This is the one that keeps fosters coming back.

Notice what's missing: weight, exact food amounts, vet appointment confirmations, training notes. Those belong in the dog's record, updated when they actually change, not collected weekly from a volunteer. Asking for them in the check-in is what turns a 60-second task into an 8-minute chore.

Design rule 3: cadence matches the dog, not the calendar

Weekly check-ins for every dog are a fairness ritual, not an operational one. A dog who has been in foster for six months and is eating fine does not need a weekly questionnaire. A dog who came in last Tuesday with kennel cough needs a check-in every 48 hours.

The cadence that works:

• First 14 days in a new home: every 3 days
• Days 15 to 60: weekly
• After day 60 with no flags: every two weeks
• Any "Some concerns" or "Worse" response: automatic 48-hour follow-up

Fosters intuitively understand this. They stop feeling pestered about the easy dogs and start feeling supported on the hard ones. Completion rates go up because the asks feel proportional to the work.

Design rule 4: close the loop, visibly

The single biggest completion-rate lever, after channel and length, is acknowledgement. When a foster submits a check-in, they should immediately see:

1. A confirmation that it was received
2. A list of their last few check-ins so they know it's a real record
3. If they flagged a concern, a clear "the coordinator will follow up by [time]"

This isn't a nice-to-have. The absence of acknowledgement is the signal fosters use to decide whether the check-in matters. If their last six submissions disappeared into a void, the seventh isn't coming.

Design rule 5: escalate only what needs escalating

The coordinator's job is not to read 60 check-ins a week. It's to respond to the 4 that surfaced a problem. A check-in system that doesn't separate "fine" from "needs attention" is just a different kind of inbox.

Configure the workflow so that:

• All-green check-ins file themselves on the dog's record
• Any concern triggers a coordinator task with the dog name, the foster name, and the specific flag
• A missed check-in (no response within 48 hours) triggers a single, soft re-prompt, then a task for the coordinator if the second prompt is also ignored

Under this model, your coordinator opens the system Monday morning to a list of 4 to 6 dogs that actually need their attention, not 60. The same person now has the bandwidth to make those follow-ups substantive instead of rushed.

The benchmark to aim for

Healthy rescues run on these numbers:

• Completion rate within 48 hours: 80 percent or better
• Completion rate within 7 days: 92 percent or better
• Coordinator time per check-in cycle: under 90 minutes a week, total
• Average check-in length for the foster: under 90 seconds

If you're hitting those, your foster program is generating its own medical and behavioral history without your coordinator having to chase it. That's the whole point of structured check-ins. They are not extra work. They are how you stop doing the work you're doing now.

What this looks like for the director

For a director, the test is simpler. Ask your coordinator: "Without opening anything, tell me which of our active dogs had a concerning check-in this week." If they can answer in under 10 seconds, your check-in system is working. If they have to scroll a chat or open a spreadsheet, it isn't, no matter what the completion rate looks like.