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 8 of 10
J8. Role-specific reports and communications
- Why this step matters
- 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.
- Act as
- ISC Finance Secretary
- What to do
- Open the reports index, open the sanction fee report, switch the payer preset and watch the liable count change, then download a CSV.
- What you should see
- A report your active roles do not carry is refused by the server, at the page and at the download address alike.
- Requirement demonstrated
- Registration and Reporting FRS FR-027, FR-033 and FR-034, and FCEAD 2.2.2 for the sanction fee.
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 | 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 (you are here) | 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.