# Create, review, and share a plan

Use this guide to turn an idea into a private draft and then, only when the user is ready, publish invitations. Creating or editing a draft does not contact anyone.

## Choose how to start

### Start from a recommendation or saved idea

1. Open **Ideas**.
2. Find and open the relevant Domino Card.
3. Choose its invitation action when it is available.
4. Domino opens **Create Invite** with the idea or place already selected.

The invitation action may appear after the card is expanded or liked, depending on the card state.

### Create an invite directly

Use the create control in Domino's primary navigation when the user already knows what they want to plan:

1. Open **Create**.
2. Choose **Create invite**.
3. Select the place or fixed event.
4. Continue into **Create Invite**.

Do not tell the user to create an Ideas List first when they already have a concrete plan.

### Save an idea instead

If the user is not ready to pick people or a time, choose **Create idea** rather than **Create invite**. A created idea can be used later and does not imply commitment or outreach.

## Complete Create Invite

Review every visible section before continuing:

1. **Place or event:** confirm the correct real-world subject. Use the place picker if it needs to change.
2. **People:** select the intended recipients. Use **Add someone** for a private Friend in Mind when the person is not already listed.
3. **Date & Time:** enter the actual start date and time. Preserve the user's timezone and do not invent a time from vague context.
4. **RSVP deadline:** choose when Domino should evaluate whether the plan has enough accepted responses.
5. **Minimum guests:** set the tipping threshold to at least two people. If the visible flow offers a maximum capacity, review that too.
6. **Title and description:** confirm that the invitation accurately describes the plan.
7. **Connection behavior:** if **Connect on signup** or a similar control is shown, explain that it concerns a recipient who later creates or claims a Domino account; it does not connect a typed name immediately.

Selecting a person for a draft does not notify them.

## RSVP deadline and tipping

A plan tips when the required number of people RSVP **In** by the RSVP deadline. If it does not tip, Domino can automatically cancel it.

Explain the mechanics before publishing:

- the minimum is the number of accepted RSVPs needed;
- the RSVP deadline is not necessarily the event start time;
- a maximum capacity can close further acceptance even when a link still opens;
- a draft has no live tipping state yet;
- changing the deadline or minimum after publication can affect the plan and may require updated communication.

Do not use “confirmed” merely because invitations were delivered. Confirmation comes from RSVP state.

## Review Invite

Choose the review action after the required information is complete. Domino can ask the host to check availability or complete another access step before showing the final invitation review.

At **Review Invite**, verify:

- the exact place or event;
- date, time, and timezone;
- RSVP deadline and tipping threshold;
- every selected recipient;
- which people Domino can reach directly;
- which people require host sharing;
- the message or link that will be presented.

If a required fact is missing, choose **Back** and correct it. Do not guess merely to enable the send control.

## Save a private draft

The user can leave or save the private plan without publishing. A saved draft appears under **Drafts** in **My Dominos**.

Accurate completion language is:

> The draft is saved in My Dominos. Nobody has been invited yet.

Do not call a draft a sent invitation.

## Publish and delivery

The final control varies according to recipient reachability:

- **Send invites** can send supported Domino delivery to eligible recipients;
- **Create invite link** or **Create invite links** creates link-based invitations for host sharing;
- a mixed audience can produce both Domino delivery and links the host must send manually.

After the action, read the completion sheet rather than summarizing from intent. It can distinguish:

- recipients getting a text from Domino;
- failed or suppressed Domino delivery;
- Friends in Mind or other recipients who will not get a Domino text;
- links the host must share themselves.

Creating a plan does not prove every recipient was contacted.

## Share a returned link

If Domino opens **Share invite link** or **Share invite links**:

1. Review the displayed message and intended recipient.
2. Choose **Share link** or copy the link/message.
3. Send it through Messages, email, or another channel chosen by the user.
4. Choose **Go to plan** when finished.

Copying a link is not delivery. Say “the link is ready to send” until a separate channel confirms delivery.

## After publication

The canonical plan page becomes the place to inspect RSVP and delivery state, edit permitted details, add more invitees, manage progress, or cancel the plan. Continue with [Manage a plan, invitees, logistics, or cancellation](/docs/web/manage-a-plan-and-invitees.md).

For the recipient journey, use [Open an invitation, join, RSVP, and add it to a calendar](/docs/web/respond-to-an-invitation.md).

## Recovery and edge cases

- If the user saved a draft, return to **My Dominos → Drafts**.
- If they abandoned an unsaved optimistic draft, do not promise it exists.
- If the final control is disabled, check time, RSVP deadline, minimum guests, place/event identity, and audience.
- If Domino says some recipients require manual sharing, do not repeatedly publish to try to force automatic delivery.
- If the wrong person was selected, go back before publishing. After publication, manage the roster from the plan page.
- If the plan was published by mistake, use the cleanup guidance in the management guide; deleting, discarding, and canceling have different meanings.

## LLM answering guidance

- Ask whether the user has a specific plan or is still collecting ideas before choosing the entry path.
- Name the visible completion state: draft saved, invitations sent, link created, or manual sharing still required.
- Explain tipping when the user asks why a plan is awaiting RSVPs or was automatically canceled.
- Never claim a typed Friend in Mind received anything unless the returned delivery state proves it.
- If a connected assistant is acting instead of explaining web clicks, follow the relevant SMS, MCP, or API confirmation protocol.