Launch & operation

1. Define the competition

• League or cup, season, audience and intended launch date.
• Entry windows, scoring, tie-breaks and any late entry.
• Primary publication or brand, sponsor and expected participation.
• Hosted address or integration needs, with an approval contact.

A planned date becomes a delivery commitment when the scope and dependencies are agreed.

2. Review the configured experience

Supply approved branding, sponsor destinations, prize terms and participant-facing wording. Review desktop and mobile, make a test entry, follow the scoring and return journey, and check the share card.

Confirm the source and cadence of standings or results, privacy and sign-in arrangements, and who approves a change. Testing and approval come before campaign launch.

3. Agree who does what

The launch plan records support contacts and hours, traffic expectations, the period covered and how problems or corrections are handled.

4. Operate and close the season

Participants return to follow their scores and rankings. For cups, new rounds open after the next confirmed draw under the agreed rules.

At completion, verify the final results and tie-breaks, confirm prize handling, and agree any reporting, retention, archive or next-season work. These are project decisions, not automatic additions to a demo.

Worked example: a hosted league edition

An example publication wants a season-long table competition reached from its sports section. It chooses a supported league and a hosted branded link, without an account integration.

1. The publication supplies: its approved name, logo and colours, sponsor artwork and destination, entry dates, prize terms if relevant, and an approval contact.
2. We configure: the competition identity, agreed entry and scoring rules, branding, sponsor placement, leaderboard, share cards and hosted delivery. We confirm the standings source and update plan.
3. They review: a test prediction, save and return journey, score and ranking, mobile layout, sponsor link and downloaded share card. Corrections are agreed before approval.
4. Before launch: both teams confirm the actual entry/data flow, support responsibilities and launch checklist. The publication then promotes the approved link through its chosen channels.

This describes the setup process, not a completed customer campaign or a promised delivery time. Payment stages and support commitments remain in the agreed proposal.