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

# How Flo's Rules work

> What your Rules listen for, the ones you start with, and why they only propose.

A Rule runs on its own, as you, when something happens: a call ends, Echo's recording lands, you log a message, a task falls due. You find your Rules under **Flo › Rules**, where you can turn each one off. A Rule shows its last run and its runs this week once it has run.

## What a Rule can listen for

| When | Fires |
| - | - |
| A schedule | At a time, every day, every weekday or once a week |
| An application moves to a stage, or sits in one | Once per move, or after a number of days |
| No activity | On an application, job or candidate quiet for a number of days |
| A meeting ends, or its outcome is saved | Once per meeting |
| You log a call or message | Once per log, on the channels the Rule names, and optionally only about someone at a stage |
| One of your calls ends | Once per call with a guest Hire knows by email, even before it is a meeting |
| Echo's recording of your call lands | Once per recording |
| One of your tasks falls due | Once per task and due date |
| You decide one of Flo's proposals | Once per proposal, approved, denied or expired |

A Rule fires once for each thing that happens. It never fires on what its own runs did, and it stops for the day at its daily limit.

## The Rules you start with

Every member has these, on. If your agency requires two-step sign-in, they wait for you to turn them on.

| Rule | When | What Flo does |
| - | - | - |
| Update the Job from client calls | A transcript is saved on a call with a job's client | Proposes the job's fields, including its interview rounds, CV target and fee months, and the client's verdicts on candidates, and drafts its ideal candidate |
| Review new applications | An application arrives on a job you review | Reviews the CV against the job's profile. It never moves or closes anyone |
| New job from a briefing | Echo records a client briefing and the client has no live job | Proposes the job, with title, salary, fee, location, hiring manager, must-haves, interview rounds, CV target and fee months |
| After a candidate interview | Echo records a candidate interview | Proposes the candidate's fields, the outcome and, when shortlisted, a task to get the CV out |
| Client said yes or a round passed | You log a call or message saying the client wants to interview someone, booked a day for a round, or they passed a round | Proposes the next stage, and the booked CCM with its prep and keep-warm tasks, or a task to agree times |
| Offer: confirm start date and fee | An application moves to Offer | Proposes a task to confirm the start date and fee |
| Offer accepted: move to Placed | You log a call or message giving the start date of someone at Offer | Proposes moving them to Placed |
| Placed: propose the Placement | An application moves to Placed | Proposes the placement with the start date, guarantee and payment terms the logged words gave, and the salary, fee and billing contact from the application and job. You fill in the rest on the card |
| File my voice logs | A voice log you recorded in Echo lands | Saves your words as a note on the call's record or the one record you named, and proposes the rest. A log that names several records waits for you to pick. See [Voice logs](/guides/how-to/connect-echo#what-hire-reads-from-echo) |
| Morning brief | Weekdays at 08:00 | Puts one row in Needs you that opens your brief: replies you owe, who is stuck 5+ working days, who is in interviews and your open roles. See [Read your morning brief](/guides/how-to/read-your-morning-brief) |

Once a placement exists, Hire adds its invoice and aftercare tasks from its dates. See [Manage a placement](/guides/how-to/manage-a-placement).

## Why Rules only propose

Flo adds facts with their source on its own: a meeting's type, a guest matched by email, an activity line. Anything that changes a stage, a field, an owner or money, or makes a record, waits in **Tasks › To review**. That includes filling an empty field. See [How Flo approvals and Undo work](/guides/explanation/flo-approvals-and-undo).

The cards from a recorded call are the same ones the meeting shows, so opening the meeting later shows them once, ready to approve.

## When a run gets stuck

Each Rule's **Runs** tab lists what it did. A run that could not finish reads **Stuck** and says why.

* **A run of steps** has **Retry from this step** on the step that stuck. Steps that already finished are not done again.
* **A run where Flo follows your instructions** has **Retry**. Flo can't pick up part way, so Retry starts the same instructions again on the same record, as a new run. What the first try already did is not done again: a note, a task or a card it made stays the only one. Pressing Retry twice starts one run.


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