Guided evaluation
Ten steps, in the order the work actually happens. Each one says why it matters, which role to be, what to do, what you should see, and which requirement it demonstrates.
Step 4 of 10
J4. Review, revision and the Plenary decision
- Why this step matters
- Show comments, a revision request, the deadline extension and the recorded Plenary outcome, each by the role entitled to it.
- Act as
- ISC Bureau Member
- What to do
- Comment on a submitted bid, request a revision, extend a reviewer deadline as the 1st Vice President, then record the Plenary decision.
- What you should see
- Each action is available only to the role that holds it. The submitted content is never edited in place: a new version is written.
- Requirement demonstrated
- Bid FRS FR-011 to FR-020: review, revision, extension, approval and the Plenary record.
Sign in to walk this step. The tour links below go to the real screens, not to a demonstration copy of them.
All ten steps
| Step | Journey | Act as | Where it goes |
|---|---|---|---|
| Step 1 | An organiser drafts a bid in confidence | Bidding Organiser | FCEs and bids |
| Step 2 | The NAC is brought in | Organising NAC | FCEs and bids |
| Step 3 | Submission into the ISC review | ISC 1st Vice President | Reviews and actions, The simulated date |
| Step 4 (you are here) | Review, revision and the Plenary decision | ISC Bureau Member | Reviews and actions, FCEs and bids |
| Step 5 | Organiser Agreement and the two bulletins | FAI Controller | Bulletins, Documents |
| Step 6 | Provisional entries | Organising NAC | Provisional entries |
| Step 7 | Final entries, people and the sporting rules | Organising NAC | Final entries, People and teams, FAI validation |
| Step 8 | Role-specific reports and communications | ISC Finance Secretary | Reports, Sanction fee report, Communications |
| Step 9 | Administration | ISC Administrator | FCEAD editions, Registration fields, Deadline rules, Roles and permissions |
| Step 10 | Audit and history | ISC Administrator | Audit trail |
Every link above goes to the working screen, not to a mock of it. If a screen refuses you, that is the server applying the permission model, and it is a result worth recording.