A Meeting Delegation Checklist: Before, During, and After

A meeting delegation checklist should cover the whole handoff: preparation, the conversation, and the work afterward. Without that full view, an assistant can attend successfully while missing the only decision you needed, or produce good notes that nobody turns into an accepted next step.

Quick answer

Define the objective and authority before the meeting, preserve decisions and uncertainties during it, and review actions afterward. Use only supported attendance capabilities and approved sources. The checklist should name the owner who verifies each consequential outcome.

Righthand's task delegation and follow-up management provide useful starting points. Account access, meeting participation, messages, and shared-system updates each depend on the available connections and permissions.

Before: establish the assignment

Start with the reason for the meeting. Write the desired outcome in one sentence. Then supply the current agenda, approved documents, participant information, exact time zone, and meeting reference.

Check these boundaries:

• What the assistant may answer from approved facts.
• What it may ask as a clarifying question.
• Which information must remain internal.
• Which commitments require a person's approval.
• What happens if attendance or source access fails.

Ask the assistant to restate the objective and limits. This is an opportunity to catch a wrong document version or a misunderstood role before the meeting starts.

If attendance is not supported or appropriate, choose preparation and note processing instead. A useful fallback should preserve the task's purpose rather than pretend every meeting can be delegated in the same way.

During: distinguish facts from agreement

Whether a person or an assistant attends, the record should separate statements, decisions, requests, and suggestions. “The client asked about Friday” is not “Friday delivery approved.”

Capture corrections and uncertainty. If a speaker changes a date, the final answer should reflect the correction. If identity is unclear, do not attribute a binding decision to a guessed participant. Follow your approved practices for attendance and any notes or capture.

For unexpected requests, use the defined escalation route. The assistant should not expand its authority because the conversation feels urgent or because another participant assumes it can decide.

An illustrative project review

A small agency delegates support for a review of draft two. The goal is to capture consolidated client feedback and confirm the next review window. The assistant receives the current file and may ask clarifying questions, but cannot accept new deliverables.

The client requests an extra page and prefers Tuesday for the next review. The report labels the page as requested scope and Tuesday as a preferred time awaiting team confirmation. It also records the approved copy changes.

The account lead reviews the scope request, verifies Tuesday availability, and authorizes the follow-up. Only then do the proposed changes become commitments and calendar actions.

After: convert the record into owned work

Review the outcome against the original objective. Identify which answers are confirmed, what remains open, and which next steps need approval. Proposed tasks need an outcome, owner, date or dependency, and completion evidence.

Authorize specific updates through the connected accounts. Ask for the result of each action separately: draft prepared, message sent, event created, task accepted, or unresolved. Avoid the single status “meeting done,” which hides important differences.

Carry unresolved questions into the next appropriate review. A meeting report is not the end of the workflow when nobody owns the open items.

A complete delegation brief

Support Thursday's draft-two review. Prepare from the current presentation and scope document. Objective: capture consolidated feedback and the preferred next review window. Attendance depends on our supported setup and host arrangements. Ask clarification within that purpose. Keep internal resourcing private. Do not agree to extra deliverables or deadlines. Afterward, list approved changes, requested scope, proposed timing, and unknowns. Draft follow-ups for my review. Do not send, assign tasks, or change the calendar without authorization.

FAQ

Is this checklist only for AI assistants?

No. People also benefit from explicit context and authority. The connected-account and supported-capability checks are especially relevant to assistant workflows.

What is the most important review after the call?

Check commitments, dates, scope, and ownership first. Those details change what the team must do and should not be inferred from vague discussion.

How do we know delegation worked?

The original objective was met, consequential facts were accurate, and unresolved work has a named owner. Attendance or notes alone do not prove that.

Related resources

See executive assistant workflows and calendar management for preparation and coordination.