Sharing Your Running Journey: Three Templates and a Privacy Check

A useful running update can be a few honest sentences. You do not need a personal best, a route map or a dramatic recovery story. Sharing can be public, limited to people you choose, or a note you keep for yourself.

Choose the template that fits your purpose. Copy the text, replace the bracketed fields and delete anything you do not want to disclose. These are original editorial prompts, not a researched formula for engagement.

Weekly training update

Use this to describe the week without treating a streak or mileage total as its only result.

This week's intention: [what I hoped to do]
What happened: [sessions, rest or changed plans; numbers optional]
Context I want to share: [only what is useful and comfortable]
One observation: [what helped, felt different or remains uncertain]
Next step: [keep, change, rest or review]
Response preference: [encouragement / one specific question / no advice needed]

Fictional example—not a customer story:

I planned three easy outings this week. I completed two and kept the other day as rest when my schedule changed. Preparing my clothes in advance helped on Tuesday; the evening slot was less practical. Next week I'll review the timing instead of adding a make-up run. I'm sharing a check-in, so encouragement is welcome; no training advice needed.

The example does not hide a failure or claim a transformation. It simply describes a decision. You can be honest without sharing why a personal circumstance changed.

Race reflection

Use this to distinguish what you intended, what happened and what you would reconsider. A finish time is optional, and a withdrawal or decision not to start can be a legitimate subject.

Event context I choose to share: [distance or broad description; name optional]
My intention: [finish, execute a plan, enjoy the event or another goal]
What happened: [factual sequence; start/finish status and numbers only if wanted]
Conditions that mattered: [relevant context without private details]
A decision I made: [what I changed and why, to the extent I want to share]
What I learned or still wonder: [observation, not a universal training rule]
Next step: [recovery, review or another appropriate action]
Thanks / permission: [name others only with their agreement]
Feedback preference: [welcome question or no advice needed]

Avoid turning “this worked for me” into “everyone should do this.” You can celebrate a result without judging another runner's pace, and you can describe a difficult day without having to end on a motivational lesson.

Ask a specific question

Use this when you want an answer rather than a general review of your training.

My question: [one specific thing I want help thinking through]
Relevant context: [experience, goal or constraint; only what is needed]
What I have already tried: [brief factual summary]
What I noticed: [observation, including uncertainty]
What kind of response would help: [experience / clarification / options to discuss]
Boundary: [what I do not want assessed or disclosed]

For example: “I have two possible lunchtime slots and keep losing one to meetings. What practical scheduling approaches have worked for you? I'm asking about calendar logistics, not a new training program.”

When responding, ask what the person wants help with before prescribing a solution. The feedback guide's question-first approach offers prompts for that conversation. A public comment thread does not replace appropriate professional advice for medical concerns.

A brief check before sharing

• Audience: Is this for yourself, selected people or a public feed? Check the actual destination rather than assuming every account or group is private.
• Location: Does a route, start/end point, street sign or caption reveal a home, workplace or routine you would rather not disclose? A text-only description can be enough.
• Other people: Ask before including identifiable photos, names, tags or someone else's story. Remove those details if permission is uncertain.
• Screenshots: Check the entire image for names, notifications, account details, health metrics and maps. Inspect the final cropped/redacted copy, not just the original screen.
• Timing and context: Does the post reveal where you are now or when a location is routinely unattended? Share less detail or post later if that better fits your preference.
• Feedback: Say whether you want advice, encouragement, a particular answer or no response.

You do not need to complete a public post. Keeping the note private is always an option, and information someone else can see may be copied or reshared.

Use the platform's current privacy documentation

Official Strava documentation checked September 8, 2026:

• Activity Privacy Controls explains activity audiences and individual overrides. Changing the default activity audience does not retroactively change past activities.
• Edit Map Visibility explains hiding some or all of a map. Map visibility is separate from activity audience, applies to Strava activities rather than being passed to other services, and does not guarantee that a hidden place cannot be inferred from other information.

Use those official instructions for the current controls; then review the particular activity or image you intend to share. A screenshot you publish elsewhere is a separate copy. This guide does not claim that a single setting removes all location clues or changes every older activity.

For other platforms, consult their own current audience and privacy documentation. No Instagram menu path or TrainingPlan dashboard sharing workflow is assumed here.

Choose the amount of sharing that fits

A private journal, direct conversation, group update or public post can serve different preferences. There is no required posting frequency and no need to manufacture either success or struggle to satisfy an imagined audience. You can omit pace, distance, personal circumstances or the entire update.

If you mainly want a record, use paper, your own notes or the training log template. The run—and a sensible rest decision—does not depend on being published.