overview portal navigation

Portal overview

What the League360 members portal contains, who can sign in, and how the pages fit together across a season.


What this portal is

League360 is the administration portal for a grassroots football league. One deployment serves many leagues; each reaches its own at its own address, and nothing from one league is visible on another’s.

The portal owns the division structure — which teams are in which division, in which age group — and the banding engine that decides when a team should be somewhere else. It deliberately does not own fixtures. It does not generate them, schedule them or edit them. Fixtures and results arrive by weekly upload from the league’s own fixture platform, because the banding engine cannot rate a team without them.

The portal decidesThe fixture platform decides
Seasons, age groups, divisionsWhich fixtures exist and when they are played
Which division a team is placed inHow a score is captured
Team strength ratings and banding reviewsPublishing results and league tables
The structure publication handed to the countyKeying that structure in — a person’s job at their end

Nothing is published to the public yet

A league’s public address currently shows a holding page only: the league’s name and a sign-in link. No age groups, no divisions, no team names and no fixtures are published to anyone who is not signed in.

Everything described in this documentation is behind sign-in. The public-facing league website is still to be built.

The pages, and what each is for

The icon rail on the left carries the week’s work. Settings sits below a divider, away from it, because those pages are visited at the start of a season and then rarely again.

PageAddressWhat it is for
Division structure/Every age group, its divisions and the teams placed in them. The portal’s principal output.
Banding reviews/MembersThe season overview: what needs attention this week, banding readiness per age group, quick actions.
Weekly upload/Members/UploadThe fixture export and the referee export. Nothing is written until a preview is approved.
Referee marks/Members/RefereesMarks by referee, with runs of low marks flagged.
Reports/Members/ReportsExceptions. Currently: fixtures played with no result recorded.
Structure publications/Members/PublicationsPublished structures and the handover workbook for the county.
Settings/Members/SettingsDivisions, banding policy, purge. How the league is set up rather than what is happening in it.

Two further pages are reached by following a link rather than from the rail: /Division/{id} lists one division’s fixtures and results in date order, and /Team/{id} shows one team’s season, its record and its goals for and against.

Development age groups are treated differently

Age groups below U12 are development age groups. Scores are recorded there in the ordinary way — the banding engine needs them — but they are not published, no league table exists, and nothing derived from them is shown outside league administration.

This shapes several pages:

  • A development division is identified by colour, not by rank. Its position in the pecking order is held by the league and shown only when an administrator presses Reveal standing order.
  • A division page shows its fixtures to any signed-in member but withholds the scores at these age groups.
  • A team page shows no won/drawn/lost line and no goal totals — a record for one team is a league table with one row.
  • Ratings and banding metrics are never shown to a club. A club receives the plain-English reason for its own team only, never a number and never a comparison.
  • Administrator views that do show this material are watermarked Internal — not for publication.

From U12 upwards results are the point of the competition, and the same pages show scores normally. Movement between divisions at those ages comes from promotion and relegation on the sporting result, not from a banding review.

A season, in order

  1. Set the divisions up. Settings → Divisions. Create each division in each age group, give it its colour and its position. Position 1 is the strongest. This is not decoration — the position anchors every rating the engine computes.
  2. Set each development age group’s banding policy. Settings → Banding policy. Five values have no safe default and must be chosen by the league. Until they are, that age group refuses to generate a review.
  3. Upload the first fixture export. The division structure is read out of the file: a team appearing in a division’s fixture is a team in that division, and a division that does not exist yet is created. Preview first — nothing is written until you approve it.
  4. Upload each week thereafter. Fixtures first, then referee marks. Marks attach to fixtures by the export’s own Fixture ID, so the fixtures for a period must be loaded before the marks for it.
  5. Watch the season overview. It surfaces age groups with no policy, reviews that are ready, and results that were never entered.
  6. Run a banding review when one is ready. The preview creates no record and notifies nobody. The committee accepts, amends or rejects each suggestion and records a reason for any deviation.
  7. Publish the structure. A publication is created when the committee ratifies a review. It produces the Excel workbook the county keys in by hand.