Step 2: Discuss with your school

Accessibility links

Step 2: Discuss with your school

Breadcrumbs

Discuss with your school

You need to discuss your intention to apply for Headstart and the course you would like to study with your school’s Headstart Coordinator. Your school's support for your application is essential.

Think about the commitments and understand what is required.

Course content

For most courses you will need to attend a lecture and a tutorial each week which is approximately 3 to 5 contact hours per week.

Some courses are different, for example:

  • Design courses — for most design courses you are required to attend a lecture and a computer workshop (as opposed to a tutorial).
  • Language courses — each week you are required to attend one lecture and a set of tutorials, which often amounts to 5 hours of contact (class) time.
  • Science courses — for most science courses you are required to attend a lecture each week and a tutorial or laboratory session (these alternate each week during semester). Class time for science courses often amounts to 4 contact hours per week.

Class times

You can select your class times to work in with your school timetable once the USC class timetable is released on 23 January 2017.

We will be in touch with you in early January with information about how to do this so be sure to check your emails regularly and keep your email address up-to-date.

Attend your Headstart Orientation on 20 January to find out more about studying at USC, including help on selecting your class times.

Need help?

Contact Student Central.

Back to top

Searching {{model.SearchType}} for "{{model.Query}}" returned more than {{model.MaxResults}} results.
The top {{model.MaxResults}} of {{model.TotalItems}} are shown below, ordered by relevance ({{model.TotalSeconds}} seconds)

Searching {{model.SearchType}} for "{{model.Query}}" returned {{model.TotalItems}} results, ordered by relevance ({{model.TotalSeconds}} seconds)

Searching {{model.SearchType}} for "{{model.Query}}" returned no results.

No search results found for

{{model.ErrorMessage}}