Lesson 4: Steward check-in scripts

These are copy/paste messages stewards use to keep things clean, kind, and moving.

A) NeedsInfo request (clarification)

“Thanks. To match this cleanly, I need: time window, location, scope size, and what done looks like. Aim for something that fits in one session (30–90 minutes).”

B) Shrink scope (when the request is too big)

“This is a real need, and it’s currently too large to match safely. Can you pick the smallest 30–90 minute version of this that would genuinely help?”

C) ReadyToMatch confirmation (before creating match)

“Confirming: you’re requesting [scope] at [time window] in [location], and ‘done’ means [done definition]. Yes?”

D) Match confirmation (with boundaries)

“Matched: [Helper] + [Requester] Time: [scheduled] Scope: [scope] Done looks like: [done] Reminder: if anything changes, message early so we can reschedule cleanly.”

E) Completion nudge

“Quick check: did this match happen as planned? If yes, please mark it completed so we can close the loop.”

F) Clean closure (stale request)

“I’m going to close this for now so it doesn’t hang in limbo. If you still want help, repost as a smaller request with a new time window.”

G) Overload check-in (private)

“Saw your pulse check. No fixing needed. Do you want fewer matches this week, smaller scope, or a pause? We can protect your capacity.”

H) Boundary reinforcement (scope creep happened)

“Pausing here to keep the agreement clean. The extra items are a new request. Let’s close this match as completed for the original scope.”

I) Feed redirect (someone posts an operational request in Mighty)

“Thanks. Please log this in VT360 using the request template so it can be triaged and matched. We keep operations out of the feed for clarity.”