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

# Plays

> Signal-triggered playbooks with task-based execution tracking

# Plays

Plays are signal-triggered playbooks. When a signal fires, a play can be recommended and executed as a series of ordered tasks.

## How Plays Work

1. A signal fires (e.g., renewal risk critical, engagement decay)
2. PILLAR recommends an appropriate play template
3. The play is assigned to an owner and activated
4. Tasks within the play are executed in order
5. Progress is tracked against an SLA (default: 72 hours)

## Play Lifecycle

| State     | Description                       |
| --------- | --------------------------------- |
| DRAFT     | Created but not yet started       |
| ACTIVE    | In progress, tasks being executed |
| PAUSED    | Temporarily paused                |
| COMPLETED | All tasks finished                |
| ABANDONED | Play canceled before completion   |

## Play Tasks

Each play contains ordered tasks with titles, descriptions, assignees, and completion tracking. Tasks guide the team through a structured response to the triggering signal.

## Task System

Beyond play tasks, PILLAR has a general task system for platform-driven actions:

* **Sources**: Next-best-action recommendations, signals, plays, MQL handoffs, manual creation
* **Priority levels**: Critical, high, medium, low
* **Categories**: Call, email, meeting, review, play execution, lead qualification, escalation
* **Status tracking**: Pending, in progress, completed, dismissed (with reason)

## Playbook Evolution

The [Playbook Evolution](/data/playbook-evolution) engine adds a closed-loop effectiveness layer on top of plays. It tracks which play templates produce the best outcomes for which account segments, computes win rates and average time to completion, and generates data-driven recommendations for which play to run next based on historical performance and signal context. See [Playbook Evolution](/data/playbook-evolution) for full details.