Phasing, sequencing and splitting
In the section Management
A ministry framework becomes a training plan: phases, an order, prerequisites — and competencies you can split.
A vocational training program arrives as a list of competencies and hours. That is not yet a plan: it lacks the order, the prerequisites, the split into phases, and the flexibility to cut a competency in two when the workshop is only free every other week.
This screen does that work — and it is what makes sequencing automatable afterwards.
Programme, séquence
L'onglet « Séquence » organise le déroulement du programme : des phases réordonnables avec leur patron d'horaire et leur volume d'heures, une frise qui projette les compétences sur les jours de formation (AM et PM), et la liste des compétences séquencées que l'on réorganise par simple glisser-déposer. Chaque ligne porte sa durée, la ressource qu'elle exige — atelier mécanique, salle de conférence — et les locaux qui peuvent la donner. C'est cette déclaration-là que le solveur consomme ensuite : sans elle, un horaire peut placer une compétence d'atelier dans une salle de cours. Pour un responsable de centre, c'est l'outil qui transforme un référentiel en plan de formation réaliste.
From framework to plan
Competencies at the official grain
Each competency carries its official code and duration, with the program's total hours at the top. This is the breakdown everything else feeds on: sequencing, progress, reports.
The prerequisite graph, readable
Competencies chain through arrows, independent ones stay apart, and a panel translates every link into plain sentences — "competency 01 is a prerequisite for competencies 03 and 05". Nothing left to interpret.
Reorderable phases
The program splits into phases you reorder, each able to carry its own schedule pattern.
A timeline, drag and drop
Sequencing projects onto weeks, AM and PM, and adjusts with the mouse. A refused move names the rule that blocked it — prerequisite, simultaneous block — instead of showing a forbidden cursor.
Splitting a competency
A competency does not have to be delivered in one block: split it and move its fragments to where the workshop, the teacher or the calendar allow.
Modelling pedagogical constraints instead of leaving them in one coordinator's head is what lets an engine produce a valid schedule afterwards. It is the differentiator against tools that stop at a list of competencies.
Features in depth
- Calendars and schedule patternsWorking days, holidays and the shape of the week are set once — everything else conforms to them.
- Offline attendanceTaking attendance does not depend on the network.
- WorkflowsA trigger, an action, and information moves without anyone having to watch a screen.
- ManagementThe reference data everything else rests on — and the cockpit that watches it.
Learn more?
Would you like more information? Don't hesitate to contact us!
PO Box 653
Prévost, Quebec
J0R 1T0