Request-and-publish workflow in detail
Hospitality is a two-way street, and Sociana's workflow reflects both directions. Outbound, the organiser creates requests, of text, choices, dates or documents, such as ID, PNR, flights, room preferences and pickups, and the participant responds in the app. Inbound, the desk verifies each field, makes allocations offline or through imports, and publishes the resulting arrangements as My Stay, My Flights, My Journey, liaison and cab cards. Between the two, status states track progress and reminders chase the pending. Because the same engine handles both ends, a change on the desk side, such as a new hotel, can be published to the right group in minutes. The workflow is a core Sociana capability and the backbone of destination conclaves and government workshops. Its limit is clear: it records and publishes, it does not procure. Design the request list carefully, because each extra field is another chase for the desk.
How Sociana uses it
Requests are defined in the hospitality module and shown in participants' apps; verification and publication happen in the operations workspace.
Example
A hospitality-heavy conclave requested travel details, verified them and published each delegate's arrangements.