Begin of the insertion**As a** mobile userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I Begin of the insertionwant** to create either a one-time meeting or a recurring meeting series from he appEnd of the insertion Begin of the deletion want to** \[enter objective\]End of the deletion
**so that** Begin of the insertionI can quickly set up meetings in the right project and start planning the agenda.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion### Acceptance CriteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionThe Meetings module top bar includes a **“+”** button.

* Tapping **“+”** opens a dropdown with at least these options with the explanatory text:

* **One-time**

* **Recurring**

* Selecting an option starts the corresponding creation flow.End of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion**Project context handling**End of the insertion Begin of the deletion **Technical notes**End of the deletion

* Begin of the insertionIf the user is **already in a project context** through the project filter in the top bar, the flow skips project selectionEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertionuses the current project as the meeting’s project.

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionIf the userEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertion**not in a project context**, the first step is a **Project selector** bottom sheet:

* Includes search input and a scrollable list of projects.

* Once a project is selected, the flow continues to the creation form.


**One-time meeting creation flow**

* Selecting **One-time** opens a form titled **“New one-time meeting”**.End of the insertion Begin of the deletion this feature visible?_End of the deletion

* Begin of the insertionThe form contains (at minimum, per mockup):

* **Title** (required and in focus when opening)

* **Location** (optional)

* **Date** (required and pre-filled with tomorrows date as in the desktop)

* **Start time** (required and pre-filled with 10:00 as in the desktop)

* **Duration** (required and pre-filled with 1h as in the desktop)

* The form has actions:

* **Cancel** (closes the flow; no meeting created)

* **Create meeting** (enabled only when required fields are valid)

* On successful creation:

* The app navigates to the newly created meeting detail screen.

* The meetingEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertioncreated with **status = Draft**.

* The meeting opens on the **Agenda** tab with an **empty state** (per mockup), indicating agenda/sections can be added.

* A confirmation snackbar/toast is shown (e.g., “One-time meeting created”).


**Recurring meeting series creation flow**End of the insertion Begin of the deletion it not visible?_


**Translation considerations**End of the deletion

* Begin of the insertionSelecting **Recurring** opens a form titled **“New recurring meeting”**.

* The form contains (at minimum, per mockup):

* **Title** (requiredEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the deletion phrasesEnd of the deletion in Begin of the insertionfocus when opening)

* **Location** (optional)

* **Date** (required and pre-filled with tomorrows date as inEnd of the insertion the Begin of the insertiondesktop) (used as first occurrence date or start date for scheduling)

* **Start time** (required and pre-filled with 10:00 as in the desktop)

* **Duration** (required and pre-filled with 1h as in the desktop)

* **Frequency** (required and pre-filled with &quot;Every week&quot; as in the desktop)

* **Interval** (required and pre-filled with &quot;1&quot; as in the desktop)

* **Meeting series ends** (required and pre-filled with &quot;Never&quot; as in the desktop)

* The form has actions:

* **Cancel**

* **Create meeting series** (enabled only when required fields are valid)

* On successful creation:

* The app navigates to the meeting series template screen.

* The series is created with **status = Draft**.

* The template opens with an **empty state** (per mockup) and copy indicating the template will be used when new meetings in the series get created.

* A confirmation snackbar/toast is shown (e.g., “Meeting series created”).


**Validation &amp; error handling**End of the insertion Begin of the deletion key languages_&nbsp;


**Out of scope**End of the deletion

* Begin of the insertionRequired fields mustEnd of the insertion Begin of the deletion <br>


_Set the_ **ToEnd of the deletion be Begin of the insertionvalidated inline; the Create CTA remains disabled until valid.

* If creation fails (network/server):

* Show an error message and allow retry without losing entered form data.

* If the user attemptsEnd of the insertion Begin of the deletion informed/consulted teams** _fieldEnd of the deletion to Begin of the insertiondismiss the form with unsaved changes:

* PromptEnd of the insertion Begin of the deletion include all teams necessaryEnd of the deletion to Begin of the insertionconfirm discard (unless product standards specify otherwise).


### Technical Notes

<br>

### Permissions and Visibility Considerations

* Only users with permission to create meetings in a project can:

* See the project in the picker (or select it)

* Create meetings/series in it

* User can only select project where they have permissions to create meetings.


### Translation Considerations

* Localize:

* Dropdown items: “One-time”, “Recurring”

* Form titles: “New one-time meeting”, “New recurring meeting”

* Field labels: Title, Location, Date, Start time, Duration, Frequency, Interval, Meeting series ends

* Buttons: Create meeting, Create meeting series

* Empty state messages and snackbars


### OutEnd of the insertion Begin of the deletion be informedEnd of the deletion of Begin of the insertionScope

* Creating meetings outsideEnd of the insertion the Begin of the insertionMeetings screen entry point (e.g., from other modules).

* Editing agenda/template content as part of the creation form (creation ends with empty agenda/template states).

* Inviting participants or managing email/calendar integrations during creation.End of the insertion Begin of the deletion changes._End of the deletion