Skip to main content

Initial Teacher Training In-Year Record 2009/10

Back to C09053

Initial Teacher Training In-Year Record 2009/10

Summary of changes from 2008/09 to 2009/10

return to index

Version 1.1 Produced 2009-08-21

This summarises the changes that were made in specification from 2008/09 to first publication in 2009/10. The revision History summarises all changes since the 2009/10 specification was released.

Summary of changes

  • The coverage was changed to include all ITT students, and not only students starting in a reporting period
  • Following clarification from the Independent Safeguarding Authority that ISA numbers will not be issued until November 2010, guidance was added to the Student.ISANUM field to indicate that this field will not be required for 2009/10
  • A new field to record the mode that a student was reported as for the TDA census in their first year, Student.CRMODE was added
  • References to GTCE's TTR2 forms in the Frequently asked questions were changed to the current reference, PR01
  • Codes 0, 1, 3 and 7 were made no longer valid in Student.ITTSCHMS. (Note: Codes 1,3 and 7 have been subsequently reinstated in release 1.2 of the coding manual)
  • The Data collection process document was amended to reflect the change in process that allows individual records to be excluded from transmission to GTCE and/or TDA, and a new TEST-COMMIT process

Following feedback from institutions, the layout of the manual was improved, and the Field list and detail page can now be sorted by both field description and field name. There is also a new 'Valid entries' link at the top of relevant pages which links directly to the 'Valid entries and labels' section of field pages.

(Please note: XML files must be encoded with UTF-8 if they contain characters beyond the standard ASCII character set. Institutions are advised to specify the encoding used in their XML files (i.e. <?xml version="1.0" encoding="UTF-8" ?>) and to ensure that their files are actually saved with that encoding. Files with an explicit encoding declaration other than UTF-8 will be rejected. Files with undeclared encoding will be assumed to be UTF-8. If encoding is not specified or does not match the actual file encoding, institutions are warned that there is a risk that data contained in the files may be changed on submission to HESA.)

Contact Liaison by email or on 01242 211144.