> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gettap.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Action completion

> Whether the things your team promised in meetings actually happened.

Action completion measures follow-through: of the commitments made in conversations, how many were actually done.

It's the number that most directly predicts whether an event produced pipeline or just business cards.

<Frame caption="Follow-through, per person">
  ![The action completion view showing how many committed actions each team member has completed.](https://cdn.gettap.co/docs/images/screens/teams-insights-action-completion.png)
</Frame>

## Where the numbers come from

Meeting analysis extracts commitments from each transcript — "I'll send the pricing", "I'll introduce you to our solutions engineer" — and creates [follow-ups](/en/leads/follow-ups). Completion is the share of those that get marked done.

<Note>
  This only works if your team marks follow-ups complete. A team that does the work but never ticks the box will show a completion rate near zero. Agree where completion is recorded — Tap or your CRM — and be consistent.
</Note>

## Reading it per member

The view breaks completion down per person, so you can see who closes loops and who accumulates open promises.

<Warning>
  Low completion is more often a capacity problem than an attitude problem. A rep who captured eighty leads at a conference and completed a third of their follow-ups is drowning, not slacking. Read completion **next to** capture volume, never on its own.
</Warning>

## What to do about it

<AccordionGroup>
  <Accordion title="High volume, low completion" icon="water">
    Overloaded. Reduce their capture load, redistribute the follow-ups, or accept fewer leads worked properly. More coaching won't create hours.
  </Accordion>

  <Accordion title="Low volume, low completion" icon="circle-question">
    Something is wrong that the numbers won't tell you. Have the conversation — it could be tooling, training, territory, or something outside work entirely.
  </Accordion>

  <Accordion title="High volume, high completion" icon="star">
    Find out what they do differently and make it the team's default. This is the most under-used thing in the view.
  </Accordion>

  <Accordion title="Everyone is low" icon="users-slash">
    That's a process problem, not a people problem. Usually either follow-ups aren't being marked complete, or the team has no protected time for follow-up after an event.
  </Accordion>
</AccordionGroup>

## Making completion better

<Steps>
  <Step title="Block time straight after the event">
    The single highest-impact change most teams can make. Follow-ups completed within 48 hours convert dramatically better than ones done a fortnight later, and the context is still in the rep's head.
  </Step>

  <Step title="Cap what one person captures">
    A rep who can work forty leads properly and captures a hundred has produced sixty cold records and a worse completion rate.
  </Step>

  <Step title="Make completion visible weekly">
    Reviewed weekly it's a working habit. Reviewed quarterly it's a performance review, which is far less useful and much less welcome.
  </Step>

  <Step title="Fix the recording, not just the doing">
    If completion looks bad but the work is happening, the problem is where completion gets recorded. Fix that before coaching anyone.
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.