- Assessment for transition: weeks 1-4, to get the students ready to study with tasks that do not contribute to the final grade (or not much).
- Assessment for development: from week 5, more prating assessment exercises which can contribute to final marks.
- Assessment for achievement: Weeks 7 to 13, where the bulk of the summative assessment is contributing the bulk of final grades.
Thirteen weeks is a very long time and if the assessment for achievement was left until the end, a student would have difficulty seeing the connection with the development. Also it would make me very nervous, if most of the assessment was at the end of the course. Software developers and other project managers are trained to place "milestones" so that there are no unpleasant surprises at the end of a project. As a student I avoid courses which have large end of semester assessments (and I would not design a course that way).
Deborah refers us to "Assessment in First Year University: A model to manage transition" (Taylor, J. A. 2008).