The Review Interface
Each check-in appears as a card with two photos side by side:
- Left photo: Your reference photo (what the checkpoint should look like)
- Right photo: The player’s submitted photo
Tip: The reference photo is watermarked to protect from screen copies.
Below the photos, you’ll see:
- The checkpoint instructions: These are your custom instructions or the default game instructions if none were specified. Always read these first – they are a key factor in your evaluation!
- Who submitted (player/team name)
- Whether this is an initial check-in or a recheck attempt
How to Review
Using Swipe Gestures (Mobile)
On touch devices, you can swipe the card:
- Swipe Right: Approve the check-in
- Swipe Left: Reject the check-in
Using Buttons
You can also use the buttons below each card:
- Approve: Accept the submission
- Reject: Decline the submission
Viewing Photos in Detail
To see a photo more clearly:
- Tap/click on either photo to view it fullscreen
- Zoom and pan to examine details
- Close the fullscreen view to return to reviewing
Tip: Use fullscreen view when you’re unsure – small details can help confirm whether the photo matches the reference.
Approving Check-ins
Approve a check-in when:
- The player followed the checkpoint instructions (this is key!)
- The player’s photo visually matches the reference photo
- Key landmarks or features are recognizable
- You’re confident the submission meets your requirements
Strict Mode: If you enabled Strict Check-ins, players wait for your approval before they can proceed. Review promptly so they’re not stuck waiting!
Rejecting Check-ins
Reject a check-in when:
- The player failed to follow the instructions (wrong pose, missing object, etc.)
- The photo doesn’t visually match the reference
- The photo is unclear or doesn’t show enough context
- Key landmarks or features don’t match
Adding a Rejection Reason
When you reject, you can optionally add a reason (up to 70 characters):
- Players see the reason on their results page
- Use clear guidance (e.g., “Wrong side of building” or “Photo doesn’t show the landmark”)
- Helpful reasons explain what went wrong so players understand
Handling Rechecks
If rechecks are enabled in your game:
- Players can resubmit a photo if they realize they made a mistake
- Recheck submissions are labeled as such
- Approved rechecks still give the player credit (with reduced penalty)
Revisit Requests
After the game ends, players can request a revisit of rejected check-ins:
- You’ll see a “Revisit requested” label on these
- The player’s objection/reason is displayed
- You can reconsider and change your decision if warranted
Real-Time Updates
The check-in review page updates automatically:
- New submissions appear without refreshing
- Approved/rejected cards disappear from the queue
- The count updates in real-time
Tips for Fair Reviewing
- Check instructions first: Did they follow the instructions? This is often the deciding factor
- Visual comparison: Compare the submitted photo against your reference for matching features
- Be consistent: Apply the same standards to all players
- Consider context: Weather, lighting, and crowds can affect photos
- Look for key features: Focus on distinctive landmarks, not minor details
- Give benefit of doubt: If it’s close, consider approving
- Use rejection reasons: Help players understand what to fix
- Review promptly: Keep up with submissions to track progress
When You’re Unsure
If you can’t tell if a submission meets requirements:
- Re-read the instructions: Did they miss a subtle requirement?
- View both photos in fullscreen for detailed comparison
- Look for matching landmarks, signs, or features
- When in doubt, approve – you can always adjust with time penalties if needed
No Check-ins to Review
When all submissions have been reviewed, you’ll see “No new check-ins to approve.” You can keep the page open – new submissions will appear automatically.