> ## 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 to file a recording

> After a call, file Echo's recording on the right record and approve what Flo found in it.

When a meeting ends, open it on the **Meetings** page. Flo reads what was said and proposes everything to file. Nothing changes until you approve it.

1. Open the meeting from **Meetings**: under **Past** on the List, or on the calendar, where a past call shows **N updates to review**.
2. Read **Flo found N things to file**. Each card says what it changes and, for the outcome, the words that show it and when they were said.
3. Select **Approve N** to approve the ticked changes, or **Deny**. Untick a change to leave it out. To change a value first, open it in **Tasks › To review** and select **Edit**. A change that can't be undone is approved on its own.

## What Flo proposes

* **Outcome.** One of the meeting type's choices, such as **Advance** for a CCM or **Brief taken** for a client briefing. Approving it files the meeting with that outcome. It changes nothing else.
* **Application stage.** Only when the candidate has one live application that fits.
* **Agreed to be sent.** When the candidate says yes to being put forward to a client, on their one live application at that client. See [Send a CV to a client](/guides/how-to/send-a-cv-to-a-client).
* **Candidate fields.** Role, company, salary, notice period, motivation, push factors and pull factors the candidate said. Every change waits for you, even on an empty field. A value the record already holds is left as it is, and Flo says so.
* **Task.** A follow-up someone said on the call. After a candidate interview that shortlists the candidate for their one live job, also **Ready for CV out**, naming the candidate and the job.
* **New job.** After a client briefing with a company that has no live job, Flo says **there's a new job** and proposes it with its title, salary range, fee, location, hiring manager and must-haves. When the client said them, it also proposes their interview rounds in order, how many CVs they want to see and the months of salary the fee counts on. Approving it adds the job in Briefing.
* **Contact job title.** When a client contact says their own role, Flo proposes it as their job title. A title they already hold is left as it is.

The outcome needs a record. If the meeting isn't linked to one, choose it under **About** and save the outcome yourself.

## Calls Echo recorded

With [Echo connected](/guides/how-to/connect-echo), the meeting shows **Recorded by Echo** and the call's length. **Open in Echo** opens the session in the Echo app. On the meeting's page, **AI Notes** holds Echo's notes and **Transcript** what was said. In the side sheet, **Echo's notes** sits above the transcript. When Echo's recording of a client briefing or a candidate interview lands, your [Rules](/guides/explanation/flo-rules) read it within seconds, so its cards are waiting when you open the meeting. Flo reads any other recorded call the first time you open it.

A transcript you paste or upload is read as soon as you save it. Replacing it makes Flo read it again.

A recording Echo made with no calendar event, such as a phone call, is filed from **To file** on the Meetings list. See [Your Echo recordings](/guides/how-to/connect-echo#what-hire-reads-from-echo).

## Calls Echo didn't record

The meeting says **Echo didn't record this call**, and the calendar shows **Not recorded · add notes**.

1. Select **Add notes** and say how it went. Select **Type instead** to type. The meeting needs a record under **About** first.
2. Select **Done**. Your words are saved as a note on the record, and Flo proposes the rest from them.

You can still pick the outcome yourself in the form below.


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