Plans and events
Turn a conversation into something people can actually join.
PostLane keeps time, place, visibility, invitation, cancellation, and safety context attached to the conversation that produced the plan.
Conversation to plan
A useful post or chat can become a plan without asking people to rebuild the context somewhere else. The plan records the practical details while the original conversation remains understandable.
Plans may be visible to friends, invited people, or only the people included in a private plan. Events may be public, friends-only, invite-only, or limited to a circle.
States people can understand
Invited or joined
Participation and RSVP context show who the plan is for without exposing it beyond its visibility.
Canceled
A canceled plan or event keeps enough context to prevent people from following outdated details.
Stale
Old or inactive plans should not look like current invitations.
Location-aware
A useful meeting place can be shared with the intended group without turning precise location into a public profile attribute.
| State | What it means | Available next step |
|---|---|---|
| Invited | The person is included within the plan's visibility but has not confirmed participation. | Accept, decline, or leave the invitation unanswered. |
| Going | The RSVP records intended participation for the people who may see it. | Review changes, use Check-In context, or update the RSVP. |
| Canceled | The plan or event should no longer be followed as current. | Keep the cancellation context and avoid the outdated location or time. |
| Stale | An old or inactive item is no longer presented as a current invitation. | Create a new plan rather than reviving ambiguous details. |
Launch boundary
PostLane launch plans and events do not imply payments, wallets, paid tickets, payouts, or marketplace transactions. Current product proof uses fictional free or local examples only.
Continue with PostLane
PostLane is preparing for launch.