When recruiting a small group, decide what to tell the people reading the announcement, those who confirm and those who will keep an eye on your return. A small group can still share a link with a large audience. YAMAP’s trip plan and activity log are separate features. Use the official guidance on access to get the plan to the people who need it and keep the rest of the itinerary private.
Keep the public announcement and the participant plan separate
Start by writing down four things: the announcement, the detailed plan for participants, what to send to family or another safety contact, and the post-hike log. This is the editorial team’s way to decide who needs each item. It isn’t a four-step recruitment feature in YAMAP.
Put what people need to decide whether to join in the announcement. Include the possible mountain or route, date, estimated walking time, required experience or equipment, number of places and how to ask questions. Decide separately whether a widely visible announcement needs the precise meeting point, participants’ contact details or car information.
After people confirm, give them the actual meeting location and time, itinerary, contact method and what to do if plans change. Give companions the full details they need to participate safely. Choose who receives the information while keeping the plan clear.
If you are recruiting two people, for example, announce the requirements and route outline first, then send the detailed plan to those who confirm. This shows how to send different information to different people. Group size alone can’t guarantee experience, compatibility or safety.
Check whether the link shares the plan or invites people to join
YAMAP’s trip-plan sharing guide says that in ordinary use, only you and the people you’ve added to the plan can see it. If you send a share URL, anyone who has that URL can view the plan.
If you put the share URL in a public announcement, people outside the original group could see the plan even if the group itself is small. Before sending, check whether it’s the URL for viewing the plan or the link for asking to join. Similar labels can lead to different actions.
YAMAP’s guide to adding companions explains that the person who receives an invitation link can see the plan outline, ask to join and become a member if the plan creator approves. This approval process is for joining the plan. Anyone with the share URL can view the plan without that approval.
Open the plan and review the title, notes and itinerary before checking the recipient and type of link. The sources reviewed here don’t establish whether you can disable a link sent to the wrong person or whether it expires. You can check the guidance without publishing a private plan or sending its link widely as a test.
Review the plan’s details and decide who needs to hear about changes
YAMAP’s guide to creating a plan says you can enter your own title and notes, including a meeting point and public transport details for companions. There are also fields for the start date, number of days and expected group size. A trip plan can contain more detail than an announcement. Consider where it will go.
The same guide explains that for a set route, you can adjust estimated times to your pace and add breaks or overnight stays. Keep the itinerary complete and choose how to give it to the people who need it.
The presence of personal details in a form doesn’t establish what the share URL displays. The sources don’t establish what each field shows to a recipient. Leave unnecessary personal details out of notes and check current guidance or official support if the audience is unclear.
YAMAP’s guide to adding companions says YAMAP members get notified when the plan is saved or edited and can see it in the app. A notification alone doesn’t establish that everyone has read the change. If the meeting time or route changes, we suggest using the agreed contact method to make sure participants know.
Share the plan with your safety contacts and handle the post-hike log separately
You can keep the announcement limited and still give the plan to the people watching for your safe return. YAMAP’s guide to saving and submitting explains that submitting shares the plan with registered emergency contacts and partner local authorities. Saving alone doesn’t send email to emergency contacts.
YAMAP says you can add companions who don’t have accounts. Automatic emails are not sent to those companions or their emergency contacts. Check that the plan reached them and the people expecting them back, even if their names are on the plan.
Check what your chosen feature sends and to whom, and arrange to get the plan to everyone who needs it. Trip-plan filing requirements vary by area. Meet any applicable filing requirements and share the plan with your safety contacts even if you keep the announcement limited.
After the hike, a restricted-audience list can limit an activity log to selected YAMAP users. Membership changes apply to every log using that list. This setting is for activity logs. The share URL for a trip plan has its own rules. Ask separately about publishing a participant’s photo or name in the log.
Decide who needs what and check the link before sending
Before recruiting, decide what belongs in the announcement, the detailed plan, the message to your safety contacts and the post-hike log. Give each recipient the details they need and leave unnecessary personal contact information and precise meetup instructions out of a widely visible announcement.
On YAMAP, anyone who has the plan’s share URL can view it. Check how that differs from an invitation approval, what happens when you save or submit a plan, and how restricted activity logs work. Before sending, check the recipient, the type of link and the plan’s contents. Confirm that participants know about changes.