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

# Planning Worksheet

> The three-part worksheet that captures your automation plan before your engineers start integrating.

Once you've worked through the [Planning Engage Automations](/onboarding/planning/engage-automations) guide (and, if you're using Reputation, [Planning Reputation Automations](/onboarding/planning/reputation)), this worksheet is where you write the plan down. Fill it in, send it back to your Reach contact, and we'll review it with you — flagging anything that doesn't fit the supported model and confirming the fields against our schema-mapping format before your engineers start integrating.

It has three parts. They build on each other: the audiences you need determine the data you must send.

## Part 1 — Automation inventory

Every Engage automation you want to pre-populate for your tenants. One row per automation.

| Column                   | What to capture                                                                                                                                          |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Automation name**      | What tenants will see (e.g. "Win back lapsed customers").                                                                                                |
| **Business goal**        | One plain-English sentence: what outcome it drives.                                                                                                      |
| **Trigger type**         | Broadcast, segment-entry, or date-based (see [the three trigger types](/onboarding/planning/engage-automations#the-three-trigger-types-and-only-three)). |
| **Channel**              | Email, SMS, or both.                                                                                                                                     |
| **Message copy (draft)** | Subject + body draft. Rough is fine — it surfaces which customer data the message needs.                                                                 |

## Part 2 — Audience translation

For each automation, the segment that defines its audience — translated from the business goal into fields and operators.

| Column                        | What to capture                                                                                                                                                     |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Automation**                | Links back to a Part 1 row.                                                                                                                                         |
| **Audience in plain English** | "Customers who used us before but haven't been serviced in 30 days and have nothing booked."                                                                        |
| **Segment definition**        | The same audience as conditions — fields, operators, and any [related-record questions](/segments/segments#related-record-conditions-counts-across-a-relationship). |
| **Buildable?**                | Buildable today · buildable once you send additional data · needs a walkthrough with Reach.                                                                         |

## Part 3 — Data checklist

Every field referenced across all your segments and messages, rolled up into a single list. This is what your engineering team scopes against.

| Column                 | What to capture                                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Field**              | The customer attribute or related-record field (e.g. `cleaning.service_date`).                                   |
| **Source**             | Which of your records it comes from, and the schema it belongs to.                                               |
| **Concept**            | Contact, transaction, location, or a custom schema (see [How Reach models your data](/data-sharing/data-model)). |
| **Sync status**        | Already syncing · needs to be added · derived/rolled-up.                                                         |
| **Expose to tenants?** | Whether tenants should see/segment on it, and the friendly name + description if so.                             |

<Tip>
  Bring edge cases and "I'm not sure this fits" rows to your Reach contact early. Most apparent blockers turn out to be reframings — and the ones that don't are worth catching before your engineers build against them.
</Tip>