Formats
Programmes are built to run inside a working week, not as a residential event. The same curriculum can be taken asynchronously, as a live cohort, as a blend of the two, or as a short board briefing. The choice is an operational one for the commissioning organisation.
Options
Participants work through modules in their own time inside a completion window agreed at scoping. Coordinators see progress. Live contact is limited to a scheduled office hour. This format suits distributed teams and roles that cannot block a calendar for half-days.
A facilitated group moves through the same sequence on a shared timetable. Sessions are used for debrief and disagreement, not for reading slides aloud. Attendance is recorded. The format suits groups that need a common conversation as much as a common text.
Recorded modules carry the explanation; live sessions carry the practicum and the arguments. Most organisational commissions land here. It keeps contact hours honest and still produces a file an audit function can read.
Four 90-minute sessions, or a subset, for six to ten people. These can run online or on the client’s premises. There is no module journal unless the board asks for one. The product is a shared list of questions and a short written recap for the secretariat.
Platform
The default is our own learning portal. It runs in a current browser, requires no installation, and is intended for use on a corporate device. Single sign-on can be configured so that participants do not hold a second password. Progress can be exported as a CSV file for the organisation’s coordinator or learning system.
Where a client already runs a learning management system and prefers to keep activity there, we package modules in standard interchange formats and support an agreed import. Completions still need a mapping to the outcomes we have written; a tick that a file was opened is not a completion record.
Accessibility is part of the delivery standard rather than an optional extra. Recordings carry captions and a transcript. Colour combinations are checked for readable contrast. Navigation is possible from the keyboard. If a participant needs a different format, the coordinator raises it during scoping or during the cohort; we do not wait for a complaint to consider the request.
Language
English is the base language of every module. It is the language in which outcomes are first written and in which version control is kept. Dutch delivery is offered on request, with a translation lead time agreed before the cohort is opened. We do not run a silent machine translation and call it a local edition.
Sector examples are adapted. A pensions operations pathway does not use a leveraged trading desk as its default case. A treasury pathway does not pretend that a defined-benefit valuation is the daily object of the work. The methodology — outcomes first, application in the check, documented limits — does not change with the sector.
Time
Most programmes open a few weeks after scoping, once levels, language and the coordinator list are confirmed. A Dutch translation or an LMS import lengthens that interval by the time those tasks actually take, not by a standard marketing figure.
A typical cohort runs six to twelve weeks. Board briefings can be completed in two to four weeks. We would rather stretch a calendar than compress application into a single intensive week that nobody can use.
The recommended load is two to three hours a week, including the check of understanding. Live sessions, where used, are additional and are booked at scoping.
A window is set at the start. Late completions can be accepted once, with the coordinator’s agreement. An open-ended window is not offered, because an audit file needs a date on which the cohort closed.
Data
We need a name, a work e-mail address, and an organisational identifier so that a completion can be attached to the right person in the right cohort. We do not need national identification numbers, payroll data, health information, or a copy of a passport. Optional telephone numbers are used only when a live session has to be rearranged.
Participant data is stored in the European Union. Hosting and platform providers operate within the Union. Retention follows the schedule in the Privacy Policy: long enough to produce the completion record the organisation commissioned, and no longer than that schedule allows.
If you already have an LMS, bring the constraint to the first call. If you do not, the portal is the default and we will say what SSO and export look like for your group size. A briefing request is the right next step; we do not open a sandbox for an unnamed cohort.