A good team challenge is one skill, one clear rule set and one deadline. In Uplink, the social feed inside the Play 2 Earn Sports app, a challenge is a Living Post: you post it, players join, entries come in as video or photo, members vote, and the result is posted. This guide walks through each decision so the challenge is fair and easy to judge.
On this page
Why run challenges at all
Challenges give players a reason to practice between sessions without the coach standing over them. A short, filmable task such as juggling, wall passes or free throws turns solo practice into something the team sees and talks about. They also give quieter players a way to be noticed for effort and improvement, not only for game-day moments.
The key is keeping it simple. A challenge that needs a long explanation, special gear or a referee will get few entries. A challenge a ten-year-old can understand from one sentence and film in a driveway will get many.
Pick the right skill
Choose a skill you already coach and want players to repeat. Good challenge skills share three traits:
- Countable or clearly judged. Touches in 30 seconds, made shots out of ten, or a clean technique you can see on video.
- Safe to do alone. No contact, no partner needed unless a parent or teammate can help safely, and no risky surfaces.
- Short. The whole attempt fits in under 60 seconds of video.
If you are unsure, browse the sport pages under Uplink challenges for ideas with rules, filming notes and age versions already written.
Run a team challenge in 7 steps
-
Write the rules in plain words
State the task, the time limit, what counts, and what voids an attempt. For example: "Juggle with feet and thighs only. Count stops when the ball touches the ground or your hands. One continuous take, no cuts." Clear rules prevent arguments later.
-
Choose who can join
Decide whether the challenge is for one team, an age group or the whole club. Set the post's visibility to match: public, club-only or private. For youth teams, club-only or private is usually the right choice.
-
Set the phases and dates
A Living Post moves through phases: open to join, entries submitted, voting, and result. Give each phase a date. A week to submit and three days to vote works well for most teams.
-
Decide how the result is chosen
You can name judges, let signed-in members vote, or use both. Judges suit technique challenges where quality matters; a member vote suits fun or creative ones. Write the method into the rules before anyone enters.
-
Name your judges
If you use judges, pick adults who know the skill, such as assistant coaches or a coach from another age group. Tell them the scoring rule and the date they need to finish.
-
Post it and remind the team
Post the challenge in Uplink and mention it at practice. A short demo video of you or an assistant doing the task helps players see exactly what is expected.
-
Share the result
When voting closes, the tally is revealed and the result is posted. Congratulate the winner, and also call out the most improved entry or best effort so more players feel recognized.
Writing rules that hold up
Most disputes come from rules that leave something unsaid. Before you post, check that your rules answer these questions:
- What exactly is being counted or judged?
- How long is the attempt, and when does the clock start?
- Is it one take, or best of several?
- What voids an attempt (cuts in the video, a hand touch, stepping over a line)?
- How are ties decided? Ties are the organizer's call, so state your tiebreak in the rules, for example "earliest entry wins" or "judges pick".
Keep the rules to a short paragraph or a few bullets. If they run longer, the challenge is probably too complex.
Judges, voting or both
Each method has strengths, and the choice should fit the challenge.
| Method | Works best for | Watch out for |
|---|---|---|
| Judges only | Technique, form, accuracy | Judges need time; give them a clear scoring rule |
| Member vote only | Fun, creative or trick challenges | Popularity can beat skill; keep it light |
| Judges plus vote | Bigger club challenges | Say in the rules how the two are combined |
Member voting in Uplink is limited to signed-in members, with one vote per account per challenge, and the tally stays hidden until voting closes. That keeps early leaders from snowballing and keeps the focus on the entries. For a full walkthrough, see how Living Post voting works.
Setting a deadline that works
Deadlines that are too long lose momentum; too short and players with busy weekends miss out. A few patterns that work:
- Weekly challenge: post Monday, entries close Sunday night, vote Monday to Wednesday.
- Two-week challenge: good for harder skills where players need time to improve.
- Weekend challenge: quick, fun tasks during a tournament weekend or break.
Put the deadline in the post and in the first line of any reminder.
Keeping it safe for youth players
Youth challenges need a little more care. Uplink supports guardian-managed athletes, and for players under 18 the public never sees birth date, contact details or location. Achievements and XP of minors are hidden from the public unless a guardian opts in.
On your side as organizer:
- Use club-only or private visibility for youth teams.
- Ask players to film at home or at the field with no school logos, street signs or house numbers in view.
- Never ask players to film other people's children without consent.
- Keep tasks non-contact and age-appropriate.
The safe sharing guide for youth teams covers this in more detail.
Questions
One week for entries and a few days for voting suits most teams. Harder skills can run two weeks so players have time to improve before they submit.
That is your call as organizer. Say in the rules whether a player submits one entry or can replace it with a better one before the deadline.
Ties are the organizer's call, so state the tiebreak in the rules before the challenge opens. Common choices are a judges' decision or a shared win.
You choose the visibility when you post it: public, club-only or private. Moderators can also restrict or remove posts if something goes wrong.
