To run a virtual journey challenge, convert team steps into distance along a named route, show progress on a single daily screen, set a weekly pace so teams know whether they are ahead, and finish with a reveal at the destination. Fairness controls keep the journey honest.
What a virtual journey adds to a step challenge
A plain step challenge says “you walked 9,214 steps today”. A virtual journey says “your team has walked 61 per cent of the way to Phuket”. The second sentence is easier to repeat, easier to picture and easier to celebrate. It also gives a long programme a shape: a start, a halfway marker, a last stretch and a finale.
India’s corporate wellness market was worth US$664.5 million in 2025 (Grand View Research, 2026), but the reason a journey works is not market size. It is that people are already carrying a phone that counts steps, and a destination gives those steps a story. The incentive-trip flavour (a Phuket, a Maldives, a Kathmandu) is especially at home in Indian companies that run outbound rewards.
Step 1: choose the route and the length
Pick a destination that means something to your audience: a real incentive trip they are working towards, a city your company is opening in, or a pilgrimage route. Work backwards from the programme length and from a realistic daily average.
| Input | Example decision |
|---|---|
| Programme length | Six weeks |
| Expected daily steps per person | A middle figure your audience can reach |
| Team size | Eight to ten |
| Route length | Sized so a typical team arrives in the last week |
Aim for a route that the average team reaches near the end. If the leaders arrive at week three, the rest stop trying; if no team arrives, the finale is flat. Check your assumption after week one against the real numbers and adjust the pace, not the rules.
Step 2: build milestones along the way
Break the route into legs with names and a short line about each: the first leg is the airport, the third is the island ferry. Reaching a milestone should trigger a post on the feed and, if you have them, a badge. Six to eight milestones across a six-week programme is plenty.
Write the milestone text in advance. It is easier to be witty when you are not also running the programme.
Step 3: configure the daily screen
A journey lives or dies on one screen. The HSBC Wellness Expedition dashboard answers four questions at once: how many steps today, what is my streak, how is my team doing against today’s target and how far is the journey to the finale. Build yours to answer the same questions without scrolling.
Include a clear line for manual entries. If your rules do not count them, show them as not counted, rather than silently dropping them.
Step 4: set a weekly pace
Weekly pace is the distance a team should cover each week to arrive on time. Show it next to actual progress: “Team Lotus is 4 per cent behind pace.” Pace turns a vague feeling into a question the team can answer: do we need a boost day, or an earlier start tomorrow?
Update the pace figure weekly and announce it in a notice. Resist daily commentary, which becomes noise.
Step 5: protect fairness, visibly
Journeys run for weeks, which means shortcuts have time to spread. Four controls matter:
- Exclude manual entries so that only phone sensor data counts.
- Daily cap so that one long hike does not decide the leg.
- Pause sync for people who are ill, on leave or travelling without their phone, so that they are not penalised for stopping.
- Review unusual days with a conversation before any adjustment.
State these in the rules page on day one. Participants forgive a rule they knew; they resent a rule invented in week three.
Step 6: keep the community alive
A team chat and a community feed keep people coming back on the days when the step count is not the draw. Encourage photos of walks, short posts about where people went and tags for team members. Make sharing revocable, so a participant who posted a picture can remove it. Moderate lightly; this is a workplace feed.
Step 7: design the finale
The finale can be a live event, a webinar, an all-hands slot or a simple results post. What matters is that the destination is reached in public. Announce the winning team, the most consistent walker and the most improved. Close the programme by thanking everyone who took part, not just the winners, and share a total: combined steps, distance covered and participation against invitations.
Common mistakes
Setting the route too short. A fast first week ends the contest early.
Hiding the rules. Participants will find the edge cases; publish the answers first.
No catch-up mechanism. Boost days and weekly pace give lagging teams something to aim at.
Forgetting the denominator. “5,000 participants” means nothing without the number invited.
A sample six-week story arc
Weeks one and two are the departure: short legs, many milestones, quick wins. Weeks three and four are the long middle, where the programme most often loses people; schedule a boost day, a team photo prompt and a halfway celebration here. Week five is the final approach, with the weekly pace figure shown at the top of the screen. Week six is arrival: a countdown, a last push and a finale post.
Write the milestone messages and the halfway post before launch. When the programme is running, you will be answering permission questions and reviewing flagged days, not composing speeches.
How Sociana handles this
Sociana’s step challenges with Health Connect and Apple Health store a start date, goals and daily caps, and show journey progress and weekly pace in programme apps. Team targets and boosts let departments compete, and streaks add recognition. The unified leaderboard shows Teams, Individuals and Games, groups hold the teams, and the timeline feed carries the community posts.
The HSBC Wellness Expedition, which ran from 1 September to 15 October 2026, was a team walking programme with a daily dashboard of steps, streaks, team progress against a daily target and an expedition journey bar to the finale. Its lessons: one daily screen drives return visits, and pausing sync and excluding manual entries are fairness controls, not afterthoughts. Read the HSBC Wellness Expedition case study. The Road to Phuket programme is a related example of a destination-themed challenge with daily exports for consistency, improvement and variance.
Frequently asked questions
Can the route be a real map?
The journey is a progress bar and milestones set by the organiser, not a turn-by-turn map. Name the legs and publish the story; do not promise GPS tracking.
What if people have different phones?
Participants on Android use Health Connect and those on iPhone use Apple Health. Test both before launch, and give a short help page for permissions.
How do we handle people who join late?
Decide in advance. Either they start from zero with the team’s pace as a reference, or the team average fills their days. Publish the rule.
Can we link the journey to a real trip?
Yes, as a reward. The app records participation; arranging the trip itself is your own process.
Related reading
Glossary: journey progress, weekly pace, health connect and Apple Health, streak. Occasion hubs: wellness and step challenges, employee programmes and incentive travel. Find a pacing sheet in templates and checklists.