The camp scoreboard

Team standings and individual standings, the tie-break rules, the full-screen view for a hall, and why the scoreboard never leaves the console.

2026-08-10
On this page

A camp's Scoreboard tab ranks teams and youths from what was recorded in the field. Nothing to compute, nothing to keep up to date.

Nothing is stored, everything is recomputed

There is no score table. Totals are rebuilt from the recording sheets every time the screen opens.

That is deliberate. A stored total lies the day someone corrects an entry, and corrections happen, since participation stays writable after the fact. What is recomputed never drifts out of sync.

A team total is not the sum of its members

You enter 50 for the Blues. That value is copied onto every member present, so the youth's own history can later say "he was in the team that scored 50". But the team total stays 50.

Adding up the members would give fifty times the headcount, and the standings would mechanically crown the largest team.

The team that counts is the most specific one: for a Tuesday activity, it is the Tuesday team if there is one, the whole-stay team otherwise. Without that rule a point would count twice.

Individual standings count individual work only

A youth's points come from individual activities only.

Their team's points sit alongside, in a lighter weight, but they rank nobody. Adding them would put every member of a team level at the top, and the individual standings would stop saying anything about the individual.

The tie-break rules

In this order, and they are written under the table.

  1. Points.
  2. Activities won. In a ranked activity, winning is coming first. In a points activity, it is having the best score, and a score of zero wins nothing: when nobody scored, nobody won.
  3. Attendance.

Whatever is still level after those three is a genuine tie. Both teams carry the same rank and the screen says so. Settling it quietly on alphabetical order would be a display lie.

An attendance not written down is not an attendance

On the recording sheet, an untouched row counts as present: that is what makes checking three hundred youths possible.

The scoreboard counts only what was written. Otherwise a camp where nobody recorded anything would show perfect attendance, and that figure will one day be used to answer a parent.

Three views

  • Teams: the standings, with points, activities won and attendance rate.
  • Individual: the same standings for youths, with search by name.
  • By activity: the run-through, activity by activity. It answers "why do the Blues have 120?". A total without its detail cannot be challenged, and a scoreboard that cannot be challenged is a scoreboard nobody believes.

The hall view

The Full screen button shows the standings large, readable from the back of a hall, and refreshes itself while scoring continues outside. The Esc key leaves it.

If there is no team at all, the individual standings are shown instead: proclaiming an empty scoreboard because the camp only plays individually would make no sense.

The printout

The print button puts both standings on one sheet, with the tie-break rules printed on it. A table pinned to a wall without its rule of calculation produces exactly the scene you want to avoid: two leaders redoing the sums in their heads in front of the youths.

The printout carries no age and no health data. It says who won, nothing else.

Who sees the scoreboard

The Record activities permission (YOUNG_SCORE) is enough: whoever entered the points is entitled to see the standings they feed.

The scoreboard never leaves the console. It appears on no public page of the camp, because it names young people, often minors. Making a ranking visible from the internet is a privacy decision, not a side effect.

All Young articles
Need help?
Quick answers and support in your language.
Help center