Turn program meetings into assigned commitments

A program meeting ends with venue, partner and volunteer coordination to complete. Turn the agreed checklist into owned tasks that remain attached to the meeting.

Before you start

Use an authorized workspace with readable calendar events and the Meeting preparation and Meeting commitments plugins enabled. Both plugins start disabled. Confirm the meeting exists in the workspace and choose valid task assignees.

Explore the nonprofits workspace with fictional records. Use it to inspect the shared screens and simulated actions; configure real forms or provider connections in a workspace you control.

Work through this example

A fictional Common Table planning meeting agrees to confirm a venue, contact volunteer captains and prepare participant information.

Record. Use the stored program meeting and write one task for each agreed commitment.

Assign. Give each task a named owner and set dates that leave time to resolve changes before the event.

Check. Record venue confirmation, captain responses and approved participant information before completing their respective tasks.

Complete the workflow

1. Run Meeting preparation from Plugins to find upcoming, non-cancelled meetings in its 48-hour window. Open the source meeting and review the customer context.

2. After community program review, agree the next steps with the team. For this example: Confirm the venue discussion; follow up with the partner; assign volunteer coordination.

3. Open Meeting commitments, select the stored meeting and enter the agreed tasks with descriptions, due dates and valid assignees. A plan supports one to ten tasks.

4. Choose Review workflow, then Request approval. Inspect the source, dates and owners before selecting Approve & create tasks.

5. Inspect the execution result and open the created tasks in Tasks & approvals. Complete or update them as the commitments are fulfilled.

Check the result

Program follow-up tasks with owners, dates and source context. Each task has an owner and date, and the source meeting remains available when someone needs to understand the commitment.

Adapt it for your business

Build program or event records through a source extension when these need their own operating process.

For a coded variation, use Build an extension and include this example’s decision, owner and completion check in your development brief. Keep customer identity and task history in the shared services.

What to check

If the meeting is missing, check the calendar connection and source record. If a preview becomes stale, prepare it again. The preparation report identifies meetings; research or transcript extraction needs an additional implemented step. Enter the agreed checklist explicitly for this workflow.

Plugins must be enabled for their operations to run. Hosted infrastructure and connected providers may have costs; AI conversations use your configured model. Keep each human decision required by the action’s policy, and verify the result in the source screen before relying on it.