V3 - Places and Plans Backend Brief
Events and Plans Event
What we currently call
PublicPlanin the database will now be called Event.An Event is created by a Page and broadcast to strangers.
Plans and Events happen at a Place Page by default. At creation, a custom Location can be used instead: a house address, dropped pin or broader area.
Private Plan and Open Plan
These are social arrangements created by a personal profile, at a Place Page by default or around an Event, and shared with friends. A custom Location is an optional alternative when creating the arrangement.
Attendance
Events keep the existing Interested / Going attendance states. Reuse that attendance model for Plans: an invited user can mark Interested or Attending. On a Plan, Attending means Going; it is not a third attendance state.
Objects
| Object | Meaning |
|---|---|
| Location | An optional alternative to a Place Page, chosen at creation when the venue is private or undefined. It can describe a precise point (address or coordinates) or a broader area. It does not create a POI or Page, and an area does not require a precise point. |
| Page | A public identity with content and publishing capabilities. Its two forms are Host Page and Place Page. Publishing requires an authorized manager; an unmanaged Place Page can remain informational. |
| Place / Place Page | One persistent public point of interest, with its own page and geographic location. Keep the existing Place identity. Examples: a restaurant, pub, yoga studio, park, viewpoint or market square. |
| Host Page | The same Page model and publishing capabilities, without a physical destination of its own. Examples: a DJ, independent yoga teacher or events organiser. A Plan cannot be made at a Host Page. |
| Event | An activity published by a Host Page or Place Page, with a set time, at a Place Page by default. At creation, a custom Location can be chosen instead, as a point or area. Existing Interested / Going attendance remains. |
| Private Plan | A personal profile's arrangement at a Place Page by default, optionally at a custom Location, or around an Event. Selected friends are invited in chat. It has a creator/admin and attached group conversation. Invitees can mark Interested or Attending. |
| Open Plan | A personal profile's arrangement at a Place Page by default, optionally at a custom Location, or around an Event. It is shown in the feed and on the map for all their friends. Friends can mark Interested or Attending. It sends no individual invitations and does not appear in chat. |
Place and Place Page remain one POI object, and the default destination for Plans and Events. Location provides flexibility when a Place Page does not apply. Every POI has its own page; choosing a private address, dropped pin or area does not create a POI.
At creation, select either the default Place Page or a custom Location. A custom Location can be a point or an area: the exact venue can remain undecided. These are alternative ways to specify where the arrangement happens; a Place Page does not require an additional custom Location.
A public POI can remain unclaimed and unmanaged indefinitely. A park or viewpoint does not need a separate Page type just because nobody manages it. Claiming a Place grants Page management; selecting it as an Event or Plan location does not.
Place Page default and Location examples
| Example | Location | Place Page |
|---|---|---|
| Restaurant, pub or yoga studio | Select its Place Page: the default flow. | Yes; may be claimed and managed. |
| Park, viewpoint or market square | Select its Place Page: the default flow also covers public POIs. | Yes; can remain unclaimed and unmanaged. |
| Plan at my house | Choose a custom Location using the private address or point. | No; making a Plan does not create a public listing. |
| Event in the desert | Choose a custom Location using a dropped pin, or an area if no exact point is set. | No Place Page is required. The Event still has a publishing Page. |
| “Anyone want to go to the pub tonight in this area?” | Create an Open Plan with a custom area Location. The specific pub is undecided. | No Place Page needs to be selected at creation. |
A home address follows the Plan's audience rules and is not added to public Place search. Open Plan visibility in the feed and map remains limited to the creator's friends. An area-based arrangement keeps its area meaning on the map; do not represent it as a falsely precise venue or pin.
Two delivery phases
| Phase | Scope |
|---|---|
| 1 Private Plans, Open Plans, Locations and admin-created Place Pages | NEO admins populate Place Pages and their content. Personal profiles create Plans at Place Pages by default, with an optional custom point or area Location at creation. Plans reuse Interested / Going attendance. |
| 2 User-created Pages and Events | Users create Host Pages and Place Pages, or claim existing Place Pages where eligible. Both Page types can publish Events at Place Pages by default, with an optional custom point or area Location at creation. Plans can then be made around those Events. |
Phase 1
Every public POI has its own Place Page. NEO admins create and maintain these pages initially. Making a Plan at an applicable Place Page is the default flow. At creation, a personal profile can choose a custom Location instead: a private address, dropped pin or broader area, without creating a Place Page.
Private Plan: select the friends to invite. Each selected friend receives an invitation in chat and can mark Interested or Attending. Receiving an invitation does not automatically mark them as attending. The Plan has an attached group conversation, using the existing group-chat membership and admin rules.
Open Plan: create the same kind of arrangement without selecting invitees. It appears in the feed and on the map for all the creator's friends, rather than in chat. Friends can mark Interested or Attending; they are not automatically marked as attending.
For example, “I'm going to this pub at seven” is an Open Plan at a Place Page. “Anyone want to go to the pub tonight in this area?” is an Open Plan with an area Location and no pub selected yet. Friends see either in the feed or on the map and can mark Interested or Attending. Open means open to that friend audience.
Both Plan types have a creator/admin, an activity, a time, a Place Page or custom Location, and attendance responses. Both appear on the map for their permitted audience.
Creating a Plan at a Place Page
A personal profile chooses a Place Page by default, then sets the activity, time and Plan type. At creation, they can choose a custom point or area Location instead. A Private Plan invites selected friends in chat; an Open Plan appears in the feed and on the map. Friends can mark Interested or Attending.
The solid Place Page links show the default. Dotted Location links show the optional alternative at creation: a house, dropped pin or area where the venue is undefined. Choosing this alternative creates no Place Page.
Phase 2
A user can create either type of Page and, with the appropriate permission, manage it. If the POI already exists, they can claim its existing Place Page where eligible instead of creating a duplicate. An approved claim grants management while preserving the Place's ID, content, media and existing Event and Plan references.
Host Pages are introduced in this phase. Place Pages already exist from Phase 1; this phase adds user creation, claiming and management to them. Public POIs can continue to have unmanaged Place Pages.
Host Pages and Place Pages can both publish Events. Events happen at a Place Page by default, with the option to use a custom point or area Location at creation. A Host Page can publish an Event at a restaurant or public park, or choose desert coordinates or an area without a defined venue. Users can make a Plan around that Event, but cannot make a Plan at the Host Page itself.
Selecting a Place as an Event location does not grant management of its Page or imply venue endorsement, approval or a booking. Whether NEO requires venue approval for particular Events remains undecided and is separate from the location model.
Creating an Event from a Page
A Host Page selects the Place Page where its Event happens, or chooses a custom point or area Location at creation.
A Place Page normally publishes Events at its own Place. For example, the pub publishes a quiz Event, and the venue defaults to that same pub.
As a rare edge case, a Place Page can publish an Event at another Place Page, or at a custom point or area Location. The publishing Page and the venue are separate references; they can point to the same Place, but do not have to.
“Publishing Place Page” and “Venue Place Page” are roles, not new Page types. For the usual pub quiz, both references identify the same pub. A Host Page has no venue of its own, so its Event uses the selected Place Page or custom Location.
Editable source: Mermaid source.
Creating a Plan at an Event
A personal profile opens an Event and creates a Private Plan or Open Plan around attending it. The Plan references the Event and uses its Place Page by default, or the custom point or area Location chosen when the Event was created.
The Plan uses the Event's time and chosen Place Page or custom Location. Private Plans still invite through chat; Open Plans appear in the feed and map. Event attendance stays Interested / Going; invited Plan users can mark Interested or Attending.
Editable source: Mermaid source.
Essential backend data
Keep the current Place model, personal profiles and friendships. The rows below are in delivery order.
| Phase | Record | Essential data |
|---|---|---|
| 1 | Location | Optional custom alternative to a Place Page. Store either point coordinates/address or an area boundary/reference, with an optional label. An area does not require an exact point or venue. Respect the Plan's audience. |
| 1 | Place / Place Page | Existing Place ID, geographic location, current Place data, page content and media. May remain unclaimed and unmanaged. |
| 1 | Private Plan | ID, creator personal profile, Place Page reference by default or a custom point/area Location, activity, time, lifecycle status, selected friends, chat invitations, attendance responses and group conversation. |
| 1 | Open Plan | ID, creator personal profile, Place Page reference by default or a custom point/area Location, activity, time, lifecycle status, feed post and attendance responses. Visible to the creator's friends in both feed and map. |
| 1 | Plan attendance | Reuse the existing Interested / Going state model for each responding personal profile and Plan. Attending is the Plan label for Going. Keep invitation delivery and attendance response distinct. |
| 2 | Host Page | ID, creator, page content, publishing identity and authorized managers. No physical destination of its own. |
| 2 | Place Page user creation and claiming | Creator or claim, claim status and authorized managers on the same POI. Preserve its existing identity and content. |
| 2 | Event | ID, publishing Host Page or Place Page, activity, time with time zone, Place Page reference by default or a custom point/area Location (separate from the publishing Page; default to its own Place when a Place Page publishes), lifecycle status and existing Interested / Going attendance. Do not require both spatial alternatives. This is the object previously called PublicPlan. |
| 2 | Private Plan and Open Plan Event support | Event reference on the existing Plan objects. The Event supplies its time, chosen Place Page or custom Location, and Event details. |
Delivery checks
- Phase 1 defaults to admin-created Place Pages, with an optional custom point or area Location at Plan creation. Private Plans use chat invitations; Open Plans appear in both feed and map.
- A park, viewpoint or market square can have an unmanaged Place Page. A house, dropped pin or area Location creates no Place Page. “Pub tonight in this area” works without choosing a pub or exact point.
- Phase 2 adds Host Pages, user creation and claiming of Place Pages, Events published by either Page type, and Plans around Events.
- Plans and Events use a Place Page by default, or a custom point/area Location chosen at creation. A Plan around an Event uses that Event's chosen place or area. A Host Page is never the destination.
- A Place Page's Event defaults to its own Place: the pub hosts its quiz at the pub. Allow the rare alternative of another Place Page or a custom Location; keep publisher and venue references independent.
- Preserve Event Interested / Going attendance. Apply the same model to Plans: invitees can mark Interested or Attending, and an invitation never automatically marks them as Going.
- Map the existing database
PublicPlanobject to Event. Keep Private Plan and Open Plan distinct from that Event model.
Use the prototype to confirm the detailed screens and group-chat controls.
References
- NEO Roadmap.
- Place and Place Page.
- Host and Create Personal Plan.