Understanding Commitments

Commitments are how you capture work your group needs to track together—the tasks people promise to handle within and between meetings. They keep your group moving forward while keeping internal work internal.

← Back to Overview

What Commitments Are

A Commitment is when one team member promises to handle a task for the rest of the group. It's work that your group needs visibility to, but that doesn't need to appear on organizational reports.

Examples of Commitments:

• "Jordan will update volunteer contact info every Friday, starting this week"
• "Alex will schedule the venue tour and send calendar invites by Tuesday"
• "Maria will follow up with the three vendors who submitted bids by end of week"
• "Wei will send out meeting notes by tomorrow morning"

These are important promises that your group needs to track together.

Where You Capture Commitments

Meeting Space is where you capture Commitments during full group meetings.

When someone says "I'll handle that," you're hearing a potential Commitment. Capture it so everyone knows who's doing what.

How Commitments Are Tracked

Once you capture a Commitment in a meeting, JOD helps make sure it doesn't get forgotten. Here's how:

Commitments persist across meetings:

• When you capture a Commitment in a meeting, it automatically appears in your next meeting agenda
• It continues appearing in each subsequent meeting agenda until it's marked as completed or deleted
• Once you review and mark a Commitment as done in a meeting, it's automatically removed from future agendas

You can also see all Open Commitments in the Planner:

• The Planner has an "Our Open Commitments" section showing all active commitments for your group
• You can see who's responsible for each commitment and when it's due
• This gives you a complete view of all outstanding commitments without waiting for the next meeting

When to Use Commitments

Use Commitments when:

• Someone promises to handle a task between meetings
• The work is important to your group but doesn't need organizational-wide visibility
• You need visibility within your group to who's doing what

Ask yourself: "Does this need to appear on organizational reports, or is it enough for our group to track it internally?"

If internal tracking is sufficient, use a Commitment.

What Makes Commitments Different

This is a feature, not a limitation. Not everything needs to be visible at the organizational level. Commitments let you track important work within your group while keeping your strategic reports focused on strategic agreements and execution.

If something needs to be visible on organizational reports, use a Decision or Action instead.

Commitments vs. Decisions

It's easy to confuse these, so here's the key difference:

Commitment:

"Jordan will update the volunteer database this Friday"

• Tracked within the group
• Not on strategic reports
• Internal group visibility

Decision (Strategic):

"Launch pilot youth leadership cohort in Chicago and Atlanta by June"

• Strategic agreement
• Shapes how you activate strategy
• Appears on strategic reports

When in doubt, ask: "Does this need to appear on organizational reports?" If not, it's probably a Commitment.

What Makes an Effective Commitment

Be Specific About Who and When

❌ "Someone will schedule the tour soon"

✅ "Alex will schedule the tour by Tuesday"

Use actual names and real dates. Vague commitments don't get done.

Follow Through

Commitments build trust. When you say you'll do something, do it. If you can't, let the group know as soon as possible.

How Commitments Work with Other Tools

Commitments often support your strategic work:

The strategic Decision: "Shift 50% of newsletter content to feature youth voices, starting in April"

Supporting Commitments:

• "Wei will draft the April newsletter by March 25"
• "Jordan will collect three youth stories by March 20"
• "Alex will review and provide feedback by March 27"

The Decision is strategic and appears on reports. The Commitments are the work that makes it happen, tracked within your group.

When strategic work requires follow-through tasks, use both tools together. Capture the strategic agreement as a Decision, and capture the supporting work as Commitments.

Practical Tips

During Meetings:

• Keep your ears open for "I'll handle that" or "I can do that"
• Capture who, what, and by when
• Read them back before the meeting ends: "So Alex is scheduling the tour by Tuesday, and Jordan is updating the database this Friday, right?"

After Meetings:

• Use the Email Results Now feature to share Commitments with the group
• People respond better to clear action lists than long meeting notes

Between Meetings:

• Check in on Commitments—are they getting done?
• If someone can't fulfill a Commitment, they should let the group know
• Address patterns: if Commitments consistently aren't happening, investigate why

Common Questions

Can one person make multiple Commitments?

Yes, but be realistic about capacity. Better to commit to fewer things and actually do them.

What if a Commitment doesn't get done?

Address it at your next meeting. Understand what got in the way. Remake the Commitment with a new timeline if it's still needed.

Should we capture every task as a Commitment?

No. Only capture things where the whole group needs visibility to who's doing what. If it's routine work that doesn't need group awareness, you don't need to capture it.

The Bottom Line

Commitments help your group track work effectively. They create accountability within your group without generating organizational reporting overhead.

Use them for work that your group needs to track together. When something needs organizational visibility, use a Decision or Action instead.

Learn about Decisions → | Learn about Actions → | See the workflow →

Updated on: 05/01/2026