Facilitate a service team check-in
See this course’s project requirements
A service leadership portfolio containing a community-need brief, shared-role sheet, pilot plan, decision record, evidence note, and reflective handoff.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A community-need brief with comment counts, a bounded service purpose, an existing asset, and a verification question.
- A shared-leadership sheet with four roles, decision boundaries, participation options, and a decision rule.
- A pilot plan with a $7 sample materials budget, permission limits, access checks, stop rules, and cleanup.
- A check-in agenda and decision note assigning the four-label revision and preserving out-of-scope ideas.
- A service-evidence note with classified counts, limited conclusions, and one user-focused improvement.
- A service leadership portfolio with return-of-findings note, specific reflection, and a documented revision.
Review and revise
Use these criteria to check your work and choose what to improve.
- Community grounding: counts the supplied feedback accurately, preserves an existing asset, and chooses a modest service purpose without claiming representative community consent.
- Shared leadership: gives four roles meaningful outputs and input before decisions, distinguishes host authority, and records a fair decision and handoff process.
- Responsible pilot: reconciles the materials budget, honors tabletop-only permission, and names accessible setup, stop conditions, and cleanup responsibilities.
- Contribution and reflection: separates outputs from outcomes, reports the limited simulated results honestly, and links a specific leadership lesson to a revised host handoff.
Want more background?
The idea in everyday life
A team check-in is useful when it reveals progress, concerns, and decisions. It should allow quieter participants to contribute without being put on the spot. Written input and short turns can help. The leader’s task is to clarify the next action and preserve agreed limits, not to reward whoever speaks longest.
Help each person share what they have noticed, then agree what the team should do next.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Write a ten-minute agenda with progress, concerns, one decision, and next steps. Give each role a contribution route, including a written option, and avoid requiring anyone to share personal reasons for that preference.
- 2
Sort the supplied updates into completed work, a quality issue, available resources, and an out-of-scope idea. Name the four-label readability issue as the decision that must be resolved now.
- 3
Compare a focused revision with the suggested room redesign. Use the service purpose, time, and permission boundaries to explain why the focused revision belongs in this pilot and the redesign does not.
- 4
Record the decision, owner, reviewer, due point, and any objection. End with a read-back that lets participants correct the record; role-play both spoken and written participation using the fictional updates.
See how it works.
Fictional practice: Lee has drafted twelve labels; Ari reports that four use small text; Pat has materials for fourteen; Jo hears a suggestion to redesign the whole room. The check-in gives each person a minute, then identifies one decision: revise the four unreadable labels before the tabletop review. The room redesign goes into a later-ideas list because it exceeds scope. Ari offers written examples instead of a spoken report. Jo records Lee as revision owner and Ari as reviewer, due at the next practice session. The team leaves with a specific handoff rather than a general request to “make everything better.”
Did you cover these?
- Updates are classified correctly
- Written participation is included
- The decision has owner, reviewer, and due point
What to finish
A check-in agenda and decision note assigning the four-label revision and preserving out-of-scope ideas.
Watch for this
Letting an exciting new idea consume the meeting before current access problems are addressed.
How can I tell I understand it?
You can demonstrate all three checks using your lesson deliverable and explain the reason for each decision.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read the sections on defining community needs, choosing participants, interpreting responses, and using results. Page displays CC BY-NC-SA 4.0; no survey or examples are copied.
Access: Public reading verified without an account; optional further reading, no paid course or certificate required.
Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.
Source & access notes · checked 2026-09-10
Read action ownership, timing, resources, communication, and current-plan criteria. Original course scenario emphasizes shared leadership and community accountability rather than reproducing its template.
Access: Public reading verified without an account; optional further reading, no paid course or certificate required.
Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.