Purpose
Ground a transcript or meeting note in the actual calendar record so later processes know who was expected and why the meeting existed.
When to use it
- A transcript lacks attendee names or meeting purpose.
- You need to verify organizer, attendees, duration, or invite agenda.
- Calendar context may change the meaning of action items or decisions.
Inputs
- Meeting time window
- Calendar account or exported invite
- Optional transcript title or meeting URL
Outputs
- Meeting metadata
- Expected attendee roster
- Invite agenda and attachments
Steps
- Search calendar events by time window, title, conferencing URL, and organizer.
- Prefer the exact invite over fuzzy title matches.
- Extract organizer, required attendees, optional attendees, agenda, attachments, and location.
- Mark attendee data as expected attendance, not proof of who actually spoke.
- Return conflicts or multiple possible matches for human review.
Quality checks
- The selected calendar event overlaps the transcript time.
- Organizer and attendee fields are sourced from the invite, not inferred from transcript text.
- Cancelled or rescheduled instances are handled explicitly.
Failure modes
- Recurring meetings produce the wrong instance.
- A transcript title is generic and matches multiple events.
- Calendar permissions hide attendees or attachments.
Privacy notes
- Calendar invites often expose private guests, dial-in links, and attachments.
- Store only the context required by downstream processes.
- Do not publish attendee lists without review.
Example prompt
Given this transcript time window and title, find the matching calendar event. Return attendee roster, organizer, agenda, attachments, and match confidence.
Example structured output
{"event":{"title":"Ops review","organizer":"Dana","start":"2026-06-02T09:00:00-07:00","end":"2026-06-02T09:45:00-07:00"},"attendees":["Dana","Lee","Morgan"],"agenda":["Order guide v2","routing exceptions"],"matchConfidence":"high"}