Commitment Extraction

Output Schema

Return ONLY valid JSON matching this schema:

{
  "commitments": [
    {
      "action": "what was promised",
      "deadline": "ISO date or null",
      "deadline_source": "explicit|inferred|none",
      "recipient": "name or email",
      "cognitive_load": "high|medium|low",
      "confidence": 0.0-1.0
    }
  ]
}

Extraction Rules

1. One commitment per distinct promise — if the user promises three things in one email, return three entries.
2. Include deadline if mentioned or inferable — "by Friday" is explicit, "before the board meeting next Tuesday" is inferred. If no deadline, set to null with deadline_source: "none".
3. Cognitive load from scope — "high" for multi-step deliverables (write a report, build a prototype), "medium" for standard tasks (review a document, send a file), "low" for quick actions (forward an email, confirm attendance).
4. Confidence reflects certainty — 0.9+ for explicit "I will" statements, 0.6-0.8 for implicit promises, below 0.5 for borderline cases.
5. Recipient from context — use the email's To field if commitment is to the direct recipient, or extract the name if promising to a third party mentioned in the email.

Worked Examples

Example 1: Explicit promise with deadline

Email to: [email protected] Subject: Q1 Report

Body: "Hi Sarah, I'll send you the quarterly report by end of day Friday. Let me know if you need anything else."

Output:

{
  "commitments": [
    {
      "action": "Send quarterly report to Sarah",
      "deadline": "2026-02-27",
      "deadline_source": "explicit",
      "recipient": "[email protected]",
      "cognitive_load": "medium",
      "confidence": 0.95
    }
  ]
}

Example 2: Implicit promise

Email to: [email protected] Subject: Re: Budget question

Body: "Good question — let me check with finance and get back to you."

Output:

{
  "commitments": [
    {
      "action": "Check with finance about budget question and respond to James",
      "deadline": null,
      "deadline_source": "none",
      "recipient": "[email protected]",
      "cognitive_load": "medium",
      "confidence": 0.75
    }
  ]
}

Example 3: Social pleasantry (NOT extracted)

Email to: [email protected] Subject: Re: Catch up

Body: "Great seeing you at the conference! We should definitely grab lunch sometime. Take care!"

Output:

{
  "commitments": []
}

Example 4: Commitment by someone else (NOT extracted)

Email to: [email protected] Subject: Re: Project update

Body: "Thanks for the update. Sarah mentioned she'll have the designs ready by Wednesday. Looking forward to seeing them."

Output:

{
  "commitments": []
}

Example 5: Multiple commitments

Email to: [email protected] Subject: Re: Sprint planning

Body: "I'll take the API refactoring ticket and the database migration. I should have the API work done by Thursday, and I'll start on the migration next week. I'll also review Tom's PR before the end of today."

Output:

{
  "commitments": [
    {
      "action": "Complete API refactoring ticket",
      "deadline": "2026-02-26",
      "deadline_source": "explicit",
      "recipient": "[email protected]",
      "cognitive_load": "high",
      "confidence": 0.9
    },
    {
      "action": "Complete database migration",
      "deadline": null,
      "deadline_source": "inferred",
      "recipient": "[email protected]",
      "cognitive_load": "high",
      "confidence": 0.85
    },
    {
      "action": "Review Tom's PR",
      "deadline": "2026-02-24",
      "deadline_source": "explicit",
      "recipient": "[email protected]",
      "cognitive_load": "low",
      "confidence": 0.9
    }
  ]
}

Example 6: No commitments

Email to: [email protected] Subject: Re: Invoice

Body: "Thanks for sending the invoice. The payment was processed yesterday and should appear in your account within 2-3 business days."

Output:

{
  "commitments": []
}