ISC FCE Management Platform Evaluation MVP Sign in

Demo guide

What this environment is, how to use it, and what to expect from each of the ten journeys. Nothing on this page is a secret and nothing on it needs to be memorised.

Every person, event, organisation and document in this environment is fictional. The names are invented, the competitions are invented, and no real athlete, official or federation appears anywhere in the data.

This is an evaluation MVP prepared for the Registration Tool Temporary Working Group. It is not a live ISC system and it is not a system of record.

Your own workspace

Signing in gives you a private workspace: a complete copy of the reference data that belongs only to you. Nothing you do can be seen by another evaluator, and nothing another evaluator does can affect you.

Sign in and create my workspace Start the guided tour Read the terminology

The roles

In your own workspace you hold every role, so that you can walk all ten journeys from one account. Use the role simulator on the command centre to change which role you are acting as. It changes what you see; it never grants a permission your account does not hold.

Roles in this system
RoleScopeOnly one holder at a timeWhat the role is for
Bidding OrganiserBIDNoThe organisation preparing a bid. Owns its own drafts and nothing else.
Organising NACBOTHNoThe National Airsport Control of the bidding organiser. Sees bids revealed to it and its own delegation.
ISC DelegateBIDNoReads submitted bids and comments.
ISC PresidentBOTHNoFCEAD 2.1.1 directs applications to the ISC President. The Bid FRS role table does not list this role; we notify and grant read and comment access, and have asked the RTTWG to confirm.
ISC 1st Vice PresidentBIDNoReceives submissions, chases NAC approval, extends reviewer deadlines, records bid approval and the Plenary decision.
ISC Bureau MemberBIDNoReviews submitted bids and bulletins.
Competition Committee ChairBIDNoReviews bids for the disciplines of the chair.
ISC Finance SecretaryBOTHYesAccount-only role (July annex 1.5). Receives applications per FCEAD 2.1.1 and the sanction fee reports.
FAI ControllerBOTHYesAccount-only role. Releases bulletins, edits inherited and IBD fields, holds the licence fall-back list.
Chief JudgeBOTHNoManages judges and the judge reports; sends bulk email for missing data.
JudgeREGISTRATIONNoAppointed judge.
Jury PresidentREGISTRATIONNoHolds the Jury start list including Alternates.
Jury MemberREGISTRATIONNoOn-site or remote jury member.
Meet DirectorREGISTRATIONNoHolds the list of roles and persons permitted to submit protests.
Head of DelegationREGISTRATIONNoOne per delegation, may also be an athlete.
AthleteREGISTRATIONNoCompletes personal fields only; entries are submitted by the NAC.
ISC AdministratorADMINNoConfigures editions, fields, sporting rules, deadlines, fees and templates.

The ten journeys and what to expect

The ten journeys
JourneyWhat it showsWhat to expectRequirement
J1. An organiser drafts a bid in confidence Show that a bid can be written over several sittings on the FCEAD Annex 2 form, and that nobody outside the organiser can see it while it is a draft. The bid saves section by section. It appears for your organisation only. A recipient of a share can read or comment but can never re-share. Bid FRS FR-001 to FR-006: drafting on the official form, saving progress, confidentiality of drafts, controlled sharing.
J2. The NAC is brought in Show that the organising NAC sees the bid only when the organiser reveals it, and that NAC approval is recorded as evidence rather than assumed. Before the reveal the NAC cannot find the bid at all, and answers 404. After it, the NAC can read the bid and comment on it, everywhere the bid appears, but can never edit it. The bid stays visible to that NAC after it is submitted. A NAC other than the one named on the bid still answers 404. The approval evidence is stored with the bid. Bid FRS FR-009 and FR-010: NAC visibility on reveal, and NAC approval evidence in either form.
J3. Submission into the ISC review Show the submission deadline, the blocked window and the late bid rule working as real behaviour rather than as labels. Submission is open, refused, then accepted as a late bid needing a two thirds majority. Reviewers are assigned and the review clock starts. Bid FRS FR-007, FR-008 and FR-015: the submission window, the blocked period and reviewer assignment.
J4. Review, revision and the Plenary decision Show comments, a revision request, the deadline extension and the recorded Plenary outcome, each by the role entitled to it. Each action is available only to the role that holds it. The submitted content is never edited in place: a new version is written. Bid FRS FR-011 to FR-020: review, revision, extension, approval and the Plenary record.
J5. Organiser Agreement and the two bulletins Show the Organiser Agreement Request generated from the approved bid, and both Official Information Bulletins with inherited fields locked. Inherited content carried from the approved bid is locked to the organiser and editable only by the FAI Controller or the 1st Vice President. FCEAD 2.3, 2.4.4 and 3.1: the Organiser Agreement Request, inherited bulletin content and the publication deadlines.
J6. Provisional entries Show a NAC submitting a provisional entry and the organiser acknowledging it, with the 75 day ceiling enforced against the clock. The window closes 75 days before the competition start date, computed from that date and not from the Opening Ceremony. Registration and Reporting FRS FR-008 to FR-014: provisional entries and the 75 day ceiling.
J7. Final entries, people and the sporting rules Show final entries built from people and teams, checked against Appendix 1, with FAI Sporting Licence validation. Team sizes are checked against the Appendix 1 ruleset version. Licence checks run against a labelled mock provider, never a live FAI service. Registration and Reporting FRS FR-015 to FR-026 and FR-036 to FR-040.
J8. Role-specific reports and communications Show the eight reports, each bound on the server to the role that needs it, and the bulk email that can target only people with data missing. A report your active roles do not carry is refused by the server, at the page and at the download address alike. Registration and Reporting FRS FR-027, FR-033 and FR-034, and FCEAD 2.2.2 for the sanction fee.
J9. Administration Show the configuration an ISC Administrator owns: editions, the field catalogue, the sporting rules, deadlines, fees and the role matrix. A non-hideable field is refused with an explanation. A moved deadline changes the computed date everywhere it is shown. Registration and Reporting FRS FR-028 to FR-032, and clause 1.5 of the 15 July annex for account-only roles.
J10. Audit and history Show that every change made in the previous nine journeys is recoverable with its before value, its after value and its reason. Everything you did is there. Nothing on any screen edits or deletes an entry, because no such route exists. Registration and Reporting FRS FR-035, and the audit expectations in the Bid FRS.

What is outside our control

Known external dependencies
DependencyWho owns itWhat it means here
Production FAI Sporting Licence API accessFAI ITIssued only after Plenary approval. Licence checks here run against a clearly labelled mock provider with the same field mapping and the same error cases.
The FAI Sporting Licence API ManualRTTWGRequested and not yet received. The adapter is written to the field list in the requirements until it arrives.
The Performance Bond amountISC Finance SecretaryThe evaluator retains historical fixture amounts. The official 2026 schedule includes bond tiers and differs from the historical sanction fee. Confirm applicable event-year rates and grouping before enabling official financial values.
Which roles pay the Sanction FeeRTTWGThe FCEAD and the registration field sheet name different sets. Both ship as presets, the FCEAD one is the default, and the question has been asked.
Which roles may lodge a protestRTTWG and the Competition RulesSet by the rules of each discipline, not by the FCEAD. The list here is configuration with a stated default.
Email deliveryDeploymentNothing is posted to the internet from this environment. Sending writes rows to a delivery log you can read on screen.

If something does not work

Tell us what you were doing, which role you were acting as, and what you expected instead. The audit trail records what happened, so a description in ordinary words is enough for us to find it.

Support: isc-evaluation@starttechagency.example. We answer during European working hours.

This page deliberately contains no passwords, no keys and no connection details. Sign-in is by one-time link, so there is nothing to write down.