Create and plan your first Weekend Mission

Create your first mission

1. Open Insights and select Missions. Overview contains your existing insights; Missions is the adventure section.
2. Open the Weekend Missions entry. If current Pro or trial access is needed, review the purchase screen before continuing.
3. Set up the Adventure Profile. Choose interests you actually want to spend free time on, add exclusions and practical limits, and save it with the navigation-bar action.
4. Read Privacy and generation and choose an available model. PCC requires a separate explicit choice on this installation.
5. On the request screen, confirm that your saved profile is being used. Expand Adjust this weekend if you want to add wishes or choose an area.
6. Create the mission. Grant current-location access if requested, use a manual area, or deliberately select No specific place for an at-home suggestion.
7. Wait for the real generation stages to advance. Close the screen through its navigation control if you want to cancel.
8. Read the activity, schedule, Why this fits, Preparation, forecast and place details. Accept with I'm in if the outing suits you.
9. If useful, save Preparation as a Task and add the mission to Calendar. Review and save each editor separately.
10. After the outing, choose Mark completed. Give an optional rating and reason, or leave without rating; completion stays saved.

Save lasting preferences; describe this weekend once

Put recurring preferences in the Adventure Profile: the interests you enjoy, exclusions, travel preference and feasibility needs. Ongoing written wishes belong there too. These are editable choices. You do not have to fill in the profile again for every request.

Use Adjust this weekend for something temporary, such as wanting to go out alone this Sunday or spend less time travelling. Current-weekend wishes take precedence over ongoing wishes where they conflict, but hard requirements and exclusions remain. Editing these wishes does not edit the saved profile.

Examples to adapt in your wishes

These are example requests you can edit. They are not generated missions.

• I would like a short museum visit this weekend, with enough time to get home before dinner.
• This time I want music rather than crafts. Please keep the trip close to the area I choose.

Choose where the search starts

Opening the request screen does not request location. An ordinary generation request obtains your current location when needed, using the existing permission or the standard permission prompt. If you prefer another starting area, use Area and select a result with the search field and map. This sets the search origin; the model still chooses the destination for the mission.

No specific place is an explicit request for a weather-independent, at-home activity. Use it when that is what you want to do, not as a way to make the model guess your location. An indoor venue still needs a real destination. A request to check the weather is not permission to obtain your position.

What the loading screen means

The screen reports work as it happens: using preferences, finding a destination, checking details, writing the adventure and preparing its checklist. At-home requests omit destination work. A stage can take longer than another or be revisited during a permitted correction; the list is not a time estimate.

Some response problems are corrected internally while loading continues. Missing user input, a permission problem or an unavailable model can still require your action. Closing the flow cancels the request. Mement does not continue on another model without your choice and does not fill the gap with a stock mission.

Review before accepting

Read the activity itself as well as its title. Why this fits explains its relation to your preferences. Preparation should describe actions needed before the outing, and an empty list can be appropriate when there is nothing to arrange.

The destination map is a read-only preview. The forecast in If conditions change covers the scheduled mission window and, where retained, identifies the destination. Admission, opening hours and prices may change or be missing from public sources. An unknown price is not a free-entry promise. Follow any explicit booking action before setting off.

For an unaccepted suggestion, Not for me collects rejection feedback. Create another mission lets you revise wishes before explicitly generating a replacement. An accepted mission is not silently rewritten when you edit preferences. The replacement action is absent after acceptance.

Save preparation when you need to do it earlier

After acceptance, use the Task button at the top of Preparation. The normal editor opens with a title for that particular mission and the full checklist in Notes. Keep the proposed wording or edit it, then save. The linked button subsequently opens this saved Task.

After you save changes to the Task's Notes, the Preparation card updates, including when you clear Notes. Admission links retained by the mission remain separately available. The Task is an ordinary saved record: resetting Weekend Missions does not silently delete it. The link between the two stays on this installation, so another device may not reopen the same exported record through that button.

Without a saved preparation Task, Mement schedules its fallback preparation reminder for Friday at 18:00 in the device's time zone before the mission weekend. Late acceptance can produce a near-immediate reminder before the mission starts; acceptance at or after its start schedules none. Delivery still depends on notification permission and system settings. Saving the Task cancels this fallback. Set the Task's own reminder if you need one.

Set aside time in Calendar

The Calendar action beside the schedule opens the system editor with the mission's proposed time, description and available destination details. Choose the calendar and review the time before saving. Cancelling does not create an event.

The Calendar event and the mission have separate completion and storage. Updating or deleting one is not a promise that the other changes too. A retained link to an exported event belongs to the current installation; check the event in Calendar if that link is unavailable.

Finish the outing and keep its details

Mark completed saves completion and then offers an optional rating and reason. Closing feedback does not undo completion. Learn from mission feedback uses bounded preferences and may derive tentative notes for later requests; it does not retrain Apple's model or change your explicit profile choices.

Missions shows up to three recent resolved adventures. All opens Mission History. Any retained outcome with resolved content can open its read-only details, including skipped, rejected or ended missions, not just completed ones. Viewing history does not change the recorded outcome.

If you decide not to do an accepted mission

Closing the details or going Back leaves an accepted mission accepted. Use End this mission when you want to stop it. A mission whose scheduled window passes can also become expired; these outcomes remain distinct from completion.

Ending the mission can cancel its feature-owned preparation reminder. An exported Task or Calendar event is still a separate saved record. Review it yourself if the outing is no longer in your plans.

When a request cannot finish

For location trouble, check the permission or choose an area manually. For a weather or place-service error, follow the specific recovery shown; location permission alone cannot make WeatherKit or a venue website available. If a hard accessibility or facility requirement cannot be established, changing an unrelated wish should not be expected to solve it.

For an unsupported generation language, use the explicit English option if it is offered and write the request wishes in English. For model availability or quota problems, check the chosen route rather than repeatedly resubmitting the same request. Your wishes are preserved for recovery, but no successful output or fixed completion time is guaranteed.

Questions before you start

Continue reading