Glossary
Continuous assessment: the mark is built as you go
Continuous assessment spreads validation across the whole unit: several submissions, each marked and commented. You know where you stand before the final week, and you adjust while it still counts. The weight of every piece is published before the first assignment.
Validation spread over time
Continuous assessment validates a unit through a series of staggered submissions rather than a single sitting. Each one comes back annotated, with the criterion behind the mark and the move expected next time. The weight of every piece is published in the syllabus when the unit opens, so before the first assignment.
- Several staggered submissions rather than one sitting
- Every submission comes back annotated, with the criterion applied
- The weight of each piece appears in the syllabus from the opening
The life of a submission
On the Web and Mobile Development programme, a unit is validated through three successive code deliveries: each one is reviewed, commented and extended with one further requirement. Progress reads from one delivery to the next, giving student and instructor alike a faithful picture of the level reached.
- 01
1 — The brief
Published with its marking scheme and its date. You know what will be examined before you start producing.
- 02
2 — The work
You work within the planned independent study time, with taught sessions available to unblock hard points.
- 03
3 — The marking
The submission comes back annotated line by line, with the expected reasoning and the criterion behind the mark.
- 04
4 — The follow-up
The next submission builds on what is held and adds one requirement: progression is what gets assessed.
Programmes assessed continuously
2 catalogue programmes put “Continuous assessment” to work: 240 credits and 2400 taught hours in total. The official rule holds throughout — one credit stands for 25 hours of work, 10 of them taught. Every line below is recomputed from the programme page: level, duration, credits, taught volume and fees in Guinean francs appear exactly as filed in the official catalogue.
| Programme | Level | Duration | Volume | Fees |
|---|---|---|---|---|
| Web and Mobile Development | Bachelor's degree | 2 years | 120 credits · 1200 taught hours | 5 200 000 GNF per year |
| Digital Marketing | Bachelor's degree | 2 years | 120 credits · 1200 taught hours | 4 600 000 GNF per year |
Your questions, our answers
How many submissions per course unit?
Two to four depending on the unit. The exact number and the weight of each appear in the syllabus issued at the opening.
Is there also a final assessment?
On units that carry one, it is announced in the syllabus with its weight. On the others, validation rests entirely on the staggered submissions.
Can I improve a mark during the unit?
Progression counts: the most recent submissions weigh more where the syllabus provides for it, and it says so from the start.
Explore next
- Assessment taskAssessment tasks at IHETC: formats, marking scheme published in advance, conditions and place in validating credits.
- Marking schemeIHETC marking schemes: criteria published in advance, weighting, annotated marking and the review route.
- Assessment panelIHETC assessment panels: composition, role, framework applied and when they intervene in a programme.
- Oral defenceOral defence at IHETC: format, length, panel questions, assessment criteria and the preparation offered during the programme.
- Capstone projectThe capstone project in IHETC programmes: a single subject spanning the programme, staged deliverables, supervision and final defence.
- PortfolioProfessional portfolio: expected content, how to structure one piece, its place in IHETC programmes and its use in interviews.