> ## Documentation Index > Fetch the complete documentation index at: https://docs.orriven.com/llms.txt > Use this file to discover all available pages before exploring further. # Sending email > A send is a template resolved against an audience: pick recipients, set variable values, preview per person, confirm, and keep the delivery record. The **Emails** page is where email actually goes out — and where every send is kept on record. A send takes a [template](/en/marketing/email-templates) and an audience; each recipient gets their own individually rendered message, with variables filled in for them. The page shows one table with two kinds of rows: **drafts** still being composed, and the immutable records of sends that already ran. ## Compose and send Click **Send email** and pick a template. Only templates with designed content can be picked — an archived or empty template cannot start a draft. The draft opens on its own page, with the subject prefilled from the template; edit it there for this send only. Filter or search the attendee table and tick people in — or apply a [cohort](/en/marketing/cohorts) to bring in a whole group at once. A hand-picked selection can be saved as a cohort with **Save as cohort**, reusable on any later send. A single send takes up to 2,000 recipients. Each of the template's own variables needs a **unified value** for this send — every recipient sees it, and all of them must be filled before sending. Under **Per-recipient values** you can override a value for one saved recipient; empty fields fall back to the unified value. Built-in variables (name, email, event, ticket type, …) fill themselves. The **Preview** panel renders one person's email exactly as the send will produce it — type a name to pick them. The preview reads the saved draft, so save first to see the latest changes. Sending is behind a confirmation: **type the subject line back** to confirm. The send goes out immediately — there is no scheduling — and the draft becomes a permanent send record. ## The send record Every send that ran is kept forever, with: * The subject, template and content **as they were at send time** — later edits to the template never touch the record. * The overall outcome: **Delivered**, **Partly delivered** or **Failed**, with a delivered count like `48/50`. * A per-recipient list on the send's detail page: each person's address, name and individual outcome. A failure for one recipient never stops the rest of the batch — the rest still deliver, and the failed rows say why. ## Rules to know * **A send = a template × an audience.** The template holds the design; the draft holds the audience, the subject and this send's variable values. * **Recipients resolve against the live attendee list at send time.** Someone whose registration was removed after you picked them simply drops out of the batch. * **All unified variable values must be filled** before the send button will go through. * **A sent draft is done.** It cannot be edited or re-sent; start a new draft from the same template instead. * **Send records are never edited and never deleted** — they are the proof of what went out, to whom. * **Test sends live on the template's page**, go to one address of your choosing, and are not recorded here — see [Email templates](/en/marketing/email-templates). * **Automations send through the same templates** but keep their own run history — see [Automations](/en/marketing/automations). ## Next Curate a recipient group once and apply it from any send draft. The attendee list your recipient picker filters and searches.