Terms & chronology
Configure academic study periods (terms) that drive planning grids, module elections, booking context, and filters across OrgHub.
Chronology is where you define academic study periods — commonly called terms or semesters — for your institution. Each term is a named, bounded window of academic activity: for example, “Winter Semester 2025/26” from October 2025 to February 2026. Terms live in OrgHub → Database → Chronology and become the shared time axis for planning, module elections, exam scheduling, room-booking context, and table filters across OrgHub.
A shared chronology matters because universities do not run on calendar months alone. Degree progress, elective elections, reassessment registration, and operational planning all need one agreed set of academic periods. When every team invents its own semester labels in spreadsheets, filters disagree, planning grids fragment, and cohorts cannot align intake and delivery to the same timeline. Chronology gives FuxamCMS a single master list of terms so curricula, cohorts, and module planning all speak the same language of time.
Why it matters
Academic terms are the institutional clock. They answer when teaching, elections, and reassessments are allowed to happen — not only for one faculty, but for the whole organization.
Without maintained terms:
- Planners cannot group modules by study period in a reliable way.
- Students lack a clear election window for optional modules.
- Courses, exams, and other OrgHub tables lose a consistent period filter.
- Cohort and curriculum work cannot map program sequence onto real calendar dates.
Chronology solves that by registering terms once as Database master data. Downstream areas reference those records instead of free-text semester names.
How this fits into Fuxam
Chronology is one of the four Database pillars in Academic structure, alongside modules, curricula, and rooms. Terms do not invent program content; they provide the time windows that planning and elections attach to.
| Related area | How Chronology connects |
|---|---|
| Academic structure | Chronology is the when pillar of Database master data |
| Curricula | Curriculum study periods organize the program sequence; institution terms from Chronology drive election windows and planning placement |
| Study programs and cohorts | Cohorts and cohort module planning use terms to place and move modules across semesters |
| Module planning | Planning grids group and select study periods from Chronology |
Key concepts
| Term | Meaning |
|---|---|
| Study period / term | A named academic window (for example, Winter Semester 2025/26) with start and end dates used across OrgHub |
| Term window | The main academic period boundaries defined by Start date and End date |
| Election window | The period defined by Election Start and Election End when students can elect optional modules for the term |
| Reassessment window | The period defined by Reassessment Registration Start and Reassessment Registration End when students can register for reassessment exams (when enabled) |
| Term code | An optional unique identifier for the term; Fuxam can auto-generate one if you leave it empty |
| Curriculum study period | A structural slot inside a curriculum (for example, Semester 1) — related conceptually to chronology, but not the same as an institution term record |
What a term controls
| Window | Field | Purpose |
|---|---|---|
| Term window | Start date, End date | The main academic period boundaries |
| Election window | Election Start, Election End | When students can elect optional modules for the term |
| Reassessment window | Reassessment Registration Start, Reassessment Registration End | When students can register for reassessment exams (when enabled for your institution) |
In this section
Create a term
Add a new study period with name, code, and start/end dates.
Edit a term
Update dates inline in the Chronology table and save changes.
Term effects on planning
See how terms drive the module planning grid and cohort planning views.
Roles and responsibilities
| Role | Typical responsibility |
|---|---|
| Academic / registry office | Own the institutional calendar of terms and keep names and codes consistent |
| Academic planners | Rely on terms when building module planning and cohort plans |
| Exam administration | Coordinate reassessment registration windows when that feature is enabled |
| Curriculum owners | Align elective election timing with Chronology dates and curriculum election settings |
Where to start
- Open Chronology and review existing terms so you do not create duplicates.
- Create terms for the next academic cycle (and any missing historical periods you still need for filters).
- Set Election and Reassessment windows after the core term window exists.
- Confirm terms appear correctly in module planning before large-scale placement work.
- Prefer editing future terms carefully once planning or enrollment data already references them.
Open Chronology
Go to OrgHub → Database → Chronology. The table lists all configured study periods for your institution.
Related pages
Academic structure
Overview of Database pillars: modules, curricula, rooms, and terms.
Curricula
Program blueprints that organize modules into study periods and electives.
Module planning
Plan which modules run in which terms and assign organizers.
Study programs and cohorts
Cohorts and program versions that consume curricula and term-scoped planning.