Checklist

Async Meeting Readiness & Handoff Checklist

An interactive readiness checklist to decide whether work should be done asynchronously and to prepare clear handoffs, summaries, decision asks, and artifact locations so async work is predictable, discoverable, and actionable.

Interactive Tool

Async Meeting Readiness & Handoff Checklist

Use this checklist to confirm that a topic is a good candidate for asynchronous work, and to prepare clear handoffs so contributors know what to do, by when, where outputs will be stored, and who decides. Fill the form once and post the resulting summary in your chosen async channel (document, thread, ticket). This creates a consistent signal that speeds response and reduces confusion.

A concise one-sentence reason for doing this async (why it matters).
Write a one-sentence purpose. Example: 'Decide a preferred vendor for X by collecting structured evaluations.'
List files, data, or prework contributors must provide. Include links or ticket IDs where possible.
Who needs to read, comment, recommend, approve, or decide? Use names or roles and expected action (e.g., Review: Alice — provide scored feedback).
Describe the response type (comment, vote, decision), and what constitutes a complete response (e.g., filled scoring table, final comment, signed approval).
Who has final decision? Pick the closest match or choose Other and specify.
Name the person, role, or committee (leave blank if not needed)
Set an expected turnaround to avoid bottlenecks. Consider timezones and urgency.
E.g., 'By EOD next Tuesday'
Use this template when posting the async request. Example: 'TL;DR: [one-line summary]. Purpose: [one-sentence]. Inputs: [links]. Ask: [what decision or input is needed]. Deadline: [date/time]. Decision owner: [name]. How to respond: [instructions].',
Provide links/paths to docs, tickets, spreadsheets, recordings, and the preferred place to store final artifacts. Use a single canonical location when possible.
If responses are missing or blocked, who should be notified and how? Include names/roles and channels (e.g., Slack #ops, email to manager).
Recommendations for channel (doc, thread, ticket), subject prefixes, headings to use, tagging conventions, file naming, and how to attach artifacts so items are discoverable.
Ensure information parity across timezones and accessibility needs. Check any that apply.
Select Yes to post the async request using the details above.
Anything else the team should be aware of before starting.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.