Coordination and Handoff Problems
| Worker Use Case | Calendar, Project, and Status Coordination |
| What it does | Knowledge workers lose significant time each week to coordination overhead: preparing for meetings, writing status updates, logging actions, and tracking what changed since the last check-in. An AI worker handles this by monitoring connected systems including calendar, email, CRM, project management tools, and task lists, and assembling the relevant context automatically. Before a meeting it produces a briefing. At end of week it produces a status summary. When a project milestone is approaching it surfaces the open blockers. When an action item is overdue it flags it without waiting to be asked. |
| What triggers it | A time-based trigger such as end of day, start of week, or meeting in 30 minutes, a project state change such as a milestone reached or deadline passed, or a direct request from a user who needs a status overview. |
| What it produces | Meeting briefs, weekly status reports, action item summaries, and project coordination updates, formatted consistently and ready for immediate use. |
| Where the human sits | The manager, project lead, or account owner reviews the output, adjusts priorities based on context the system cannot see, and decides what actions to take. The AI surfaces the information; the human decides what it means. |
| Where it shows up | Executive teams managing multiple workstreams, project managers running complex programmes, account managers handling multiple client relationships, and operations teams coordinating across distributed teams or sites. |
| Why it matters | This is the only card where the AI acts proactively without waiting for a request. That makes it structurally different from every other card in the library. Workflow Orchestration is time-based and stateful. Dialogue and Interaction is reactive and session-based. That distinction is why the two capabilities are listed separately, and this card is the clearest demonstration of the difference. |
Examples
- Calendar prep assistant — checks upcoming meetings, retrieves relevant account history, open actions, and prior meeting summaries, and produces a pre-meeting briefing for each scheduled event
- Weekly prep coordinator — assembles a weekly briefing from calendar events, open tasks, recent emails, and project status updates, giving the user a structured view of priorities before the week begins
- Project status report generator — reads task completion data, milestone progress, and open blockers from connected project tools and produces a formatted status report for distribution to stakeholders
- Email to event tracker worker — reads email threads about an upcoming event or project, extracts tasks, deadlines, and owners, and populates a structured tracker without requiring manual data entry
- Scrum assistant — monitors sprint board activity, summarises progress toward sprint goals, identifies blockers, and produces a daily standup summary for the engineering team
- Store readiness assistant — checks completion status across all pre-opening or pre-event tasks, flags outstanding items, identifies responsible owners, and produces a readiness report for the operations manager
| Worker Use Case | File, Content, and Repository Organisation |
| What it does | Over time, shared drives, email archives, content repositories, and document libraries become unusable. Files are named inconsistently, stored in the wrong places, duplicated across folders, or simply lost. An AI worker reads the content of files, infers what they are and what they contain, applies a consistent taxonomy, suggests or executes subject to human approval a reorganised folder structure, flags duplicates, identifies files that are outdated or superseded, and produces a map of the repository that makes it navigable again. |
| What triggers it | A repository audit task, a migration project, a new team member unable to find what they need, or a periodic scheduled cleanup workflow. |
| What it produces | A reorganised or proposed reorganisation of the file structure, a duplicate and outdated file report, a consistent naming convention applied across a file set, and a repository map showing what is where. |
| Where the human sits | A person reviews the proposed reorganisation before any files are moved or deleted. Nothing is executed without explicit human confirmation. This is the clearest application of the Review and Control principle in the entire library. |
| Where it shows up | Operations teams managing large shared drives, legal teams with extensive document archives, content teams with large creative asset libraries, and IT teams managing document migration projects. |
| Why it matters | This card is easy to underestimate because it sounds like housekeeping. But in large organisations, inaccessible institutional knowledge is one of the most expensive forms of waste. The inability to find what already exists drives redundant work across every other card in this library. Solving the findability problem is not an administrative task. It is an organisational capability decision. |
Examples
- Google Drive file organiser — reads file names and content across a shared drive, infers the correct folder structure, suggests or applies a consistent taxonomy, and flags duplicates and outdated files for human review before deletion
- Promotional email cleanup assistant — reviews a backlog of marketing and promotional email content, identifies outdated campaigns, flags superseded offers, and recommends which items to archive or delete
- Document version control assistant — identifies multiple versions of the same document across a repository, determines which is the current approved version, and proposes an archiving structure for older versions
- Content repository audit worker — scans a content library for items that are past their review date, have no assigned owner, or are inconsistent with current brand or policy standards, and produces a remediation report
- Knowledge base maintenance worker — monitors a customer-facing or internal knowledge base for articles that are outdated, contradictory, or generating repeated support escalations, and flags them for review and update
- Search index optimisation assistant — analyses search queries that return no useful results from an internal knowledge base and recommends new content, tagging improvements, or structural changes to close the gaps
| Worker Use Case | Meeting Intelligence and Action Capture |
| What it does | A meeting happens, live or recorded, and the AI worker handles everything that follows it. It transcribes the conversation, identifies speakers, extracts the decisions made and the actions assigned, notes the open questions that were not resolved, produces a structured summary, and pushes the actions into the relevant systems: the project tracker, the CRM, the task manager, or the team’s shared workspace. The result is that the meeting produces a complete, accurate record without anyone spending time after the call writing notes or chasing down who agreed to do what. |
| What triggers it | A meeting recording becoming available, a live meeting transcript completing, or a calendar event marked as concluded with a recording attached. |
| What it produces | A meeting transcript, a structured summary of key discussion points, a decisions log, an action item list with owners and suggested due dates, and open questions flagged for follow-up. Where connected systems are available, actions are logged directly into project or CRM tools. |
| Where the human sits | The meeting organiser or a designated participant reviews the summary and action list before it is distributed or logged, corrects any misattributions or misunderstandings from the transcript, and confirms action ownership with the relevant people. |
| Where it shows up | Executive and leadership teams running high volumes of decision meetings, sales teams logging client call outcomes into CRM systems, project teams tracking decisions across long programmes, and cross-functional teams where meeting accountability is a persistent problem. |
| Why it matters | Calendar, Project, and Status Coordination covers time-based coordination — preparing for what is coming. This card covers what happens after the moment passes. Together they form a complete coordination loop: brief before, capture after, track in between. Meeting intelligence is one of the most widely deployed AI patterns in practice precisely because it solves a problem every knowledge worker recognises immediately — the gap between what was agreed in a meeting and what actually gets recorded and acted upon. |
Examples
- Meeting summary worker — transcribes a recorded or live meeting, identifies speakers, and produces a structured summary of key discussion points and decisions reached
- Action item capture assistant — extracts assigned actions from a meeting transcript, identifies the owner and any stated deadline, and formats them into a task list ready for import into a project or task management tool
- CRM update from call worker — takes a sales call transcript and automatically logs the outcome, next steps, and account notes directly into the CRM, removing manual post-call data entry
- Compliance audit trail generator — creates an immutable, searchable record of what was said in regulated interactions such as financial advisory calls or sensitive negotiations, for compliance officer review
- Decision log generator — extracts formal decisions made during a meeting, timestamps them, and appends them to a running project decision record for future reference
- Follow-up communication drafter — takes the action items captured from a meeting and drafts reminder communications to the relevant participants, with a financial services firm already running this as a live agentic workflow