Questions, considerations, assumptions

We came up with these questions, considerations and assumptions, for discussion:

1. The prototype will be aimed at Feedback to Applicants who have been rejected by institutions.
N.B. Should Feedback automatically form part of the selection process, no matter whether the Application be rejected or the Applicant made an Offer ?

2. Needs to support:
- Code and associated text maintenance by the institutions
- Feedback to the Applicant by the institution
- The ability to provide Feedback via 'Free Text', as well as calling up codes.

3. A key objective of the project is to implement something which will have insignificant impact on the institutions; in terms of time and money spent.

4. Codes and associated text are most likely to come from the institutions and, possibly, faculties within the institutions, rather than applying a national standard set.
N.B. The responses from an Art & Design institution may be very different from those from a Science oriented institution. A set of nationally agreed responses will, almost certainly, be too broad and of little real use to the Applicants.

5. It should be possible to provide Feedback to an Applicant, who has requested it, at any point in their Application process, i.e. not restricted to Choices where the Application has not moved on to another institution.

6. Would it be 'useful' for an Applicant to be able to request Feedback via UCAS's systems ?
N.B. A risk associated with this is that if made easy (and why not ?) it will encourage Applicants to always request Feedback, which may overburden the HEIs.

7. The requirement is for a Demonstrator, hence, is there a need to support UCAS, CUKAS, GTTR and UKPASS institutions ? Suggest just UCAS. However, will this satisfy the institutions broadly enough ?

8. How will the prototype Feedback be made visible to the Applicant ?

9. Will the Applicant still receive an Email or Letter ?

10. How will the prototype Feedback combine with that already available in Apply09 ?

11. Will the prototype transactions instantly update TOPAZ ?

12. Will a CSU operator be able to see the results of what happens in the prototype ?

13. Will the prototype replicate TRACK ?
N.B. This will not be necessary if TOPAZ is updated.

14. How far 'down the pipe' do we need to go with the prototype, e.g. do we want/need to accommodate 'Extra' Applications ?

15. Bearing in mind that Route 'B' is disappearing, in its current form, does it need to be catered for in the prototype ?
N.B. GTTR will remain sequential.