These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Pilgrimage / Religious Tourism
- Features
- Pilgrim Services
Pilgrim Services
Keep each dated accommodation, meal, transport or visit arrangement with its group.
OverviewPilgrim Service Dates×
Pilgrimage / Religious Tourism · Pilgrim Services
New
Pilgrim Service Dates
Pilgrim services
| Group | Service type | Service date | Provider | Confirmed quantity | |
|---|---|---|---|---|---|
| PG-3238 | Accommodation | 14 Oct | PRV-387 | 480 | |
| PG-1133 | Meal | 15 Oct | PRV-606 | 120 | |
| PG-2834 | Transport | 10 Oct | PRV-697 | 90 | |
| PG-4415 | Visit | 12 Oct | PRV-747 | 730 | |
| PG-4841 | Accommodation | 04 Oct | PRV-253 | 540 |
6 of 6 records
PRV-387Pilgrim services · PS-51080
AccommodationGroupPG-3238
Service date14 Oct
Confirmed quantity480
What you can do
Arrange services around the journey
Each service record belongs to a pilgrim group. Group Coordinator selects accommodation, meal, transport or visit, then records the service date, provider and confirmed quantity. This makes it possible to review the arrangements for a particular departure without treating a meal and a vehicle movement as the same kind of work. The group link provides the travel context; each service line provides the dated detail.
The service date should be checked against the group’s departure and return period during operating review. If the group changes its travel dates, Group Coordinator revisits the affected services and confirms the provider and quantity again. Provider is written on the service record, so the team should agree a consistent provider naming convention. It can then find all arrangements for a named group and compare the dates before briefing the leader.
How the work is organized
- Group link. Every service points to its pilgrimage group record.
- Service type. Accommodation, Meal, Transport and Visit identify the kind of arrangement.
- Service detail. The date, provider and confirmed quantity carry the operational handoff.
Consider a group departing early and returning several days later. The coordinator may record a meal for departure day, accommodation for the first night and a visit on the following day. Each arrangement has its own provider and quantity. A change to the participant count prompts a review of the service quantities before the group’s final briefing.
What to agree during setup
Decide which team member owns each type of service and how a provider name should be written. Agree whether confirmed quantity means people, meals, rooms or another unit for the service type used. Tell reviewers where source confirmation is retained in the team’s operating process. The record can carry the service type, provider, date and quantity; the team must use those values consistently.
Keep transport services and dispatched trips distinct. A service line represents the group’s arrangement; a trip represents an assigned vehicle, driver, route and journey status. When both apply, Group Coordinator and Dispatcher should compare dates and participants at the handoff. This avoids treating a service line as proof that a driver and vehicle have been scheduled.
Check the handoff on an actual case
Create the group’s planned service dates and ask Group Coordinator to read them back against the travel window. Compare the quantity with the participant count. Have Dispatcher inspect the transport service before approving a related trip. If a provider or date changes, update the service record and repeat the review with the leader. Use the services by group report to verify the final list, including type, date and provider.
What your team sees
- Pilgrim Service Dates — Review service dates, providers and quantities for group arrangements.
- Pilgrimage Groups — Open the parent group to confirm its leader and travel window.
- Trip Dispatch Board — Check the separate journey plan when a transport service leads to a trip.
Follow the work through
See group and service preparation, then trip dispatch. Review implementation for the first operating cycle.
What it keeps track of
Data model- Pilgrim services
- Accommodation, meal, transport and visit services arranged for a pilgrimage group.
- Pilgrimage groups
- Pilgrim groups travelling together with departure, return, leader and participant count.
- Trips
- Planned and dispatched journeys carrying pilgrim groups between origin and destination.
Who uses it
Permissions- Group Coordinator
- , Dispatcher and Admin prepare and review arrangements.
- Operations Manager
- Checks group context for the journey.
Set up Pilgrimage / Religious Tourism your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.