Fib.Code
A co-funded training course differs from a commercial one in a single respect: it follows rules that somebody actually checks.
Participants, employers and funding operators are entitled to know in advance how a service will be delivered, what it will require of them and what they will be left with afterwards. This page states it without generalities. Remote services are delivered in line with the Remote Learning Services Standard — Annex 5 to the Rules of the Development Services Database; the principles set out in sections 02–10 apply to all of our development services.
45 min
cycle with a hands-on task
14 days
to report on learning outcomes
0
audio and video recordings
40037
our BUR provider ID
We do not take programmes off the shelf. Before a service is published we establish with the client who will attend and under what conditions they will work. Only then do we design the programme, the learning outcomes and the methods.
We establish what participants are genuinely responsible for in their organisation and which of those duties the training is meant to improve.
We check what participants already know. Material the group finds obvious is dropped; the gaps take its place.
We establish which systems and versions the organisation runs, so that exercises match what participants will see on their own screens the next day.
For remote services we also agree on the tool, the working format, camera and microphone availability and any constraints on the client's infrastructure.
The planned format has to be workable in the conditions participants actually have. A method that cannot be run on the client's network is worthless to both sides.
We teach through application. Participants work on situations from their own environment rather than textbook examples — in Microsoft 365 and Azure courses that means configuring their own tenant alongside the trainer's demonstration; in information security courses, analysing their organisation's real processes and documents.
A brief walk-through of the topic and a live demonstration — not an hour-long lecture.
Participants perform the task themselves, in their own or in a prepared environment.
We review the outcome, catch the mistakes and only then move on.
Every remote service is scripted to include at least one activity requiring independent work by the participant for every 45 minutes of the session.
Participants perform the configuration on their own systems, in parallel with the trainer.
Not "any questions?" thrown at the screen, but a question put to a specific person.
Work on a situation from the participant's organisation or on a case from our audit practice.
A short quiz after each module, discussed immediately — the result shows at once what needs revisiting.
Participants show what they achieved; the group sees different ways of solving the same task.
Time allocated in the script, not an afterthought "if we have a minute left".
Participants are not spectators in our courses. That is a methodological assumption rather than a courtesy — without performing the task yourself, competence in these fields simply does not develop.
Taking part in a remote service requires no purchases and no installation. We keep the requirements at a level met by an ordinary office workstation and an average phone.
A computer, tablet or phone. Sessions work on mobile devices as well.
A connection capable of carrying video — a standard office or home link is enough.
A microphone is needed to take part in the exercises. A camera is recommended but not required.
Sessions run in Teams. Participants can join through a browser, without installing anything.
The remote environment is our responsibility, not the participant's. A technical fault is not a reason to lose part of a course.
We help participants join, test the connection and resolve access problems.
We respond to dropped connections, resend the link, switch to audio-only participation where needed or repeat a section of the material.
We help with access to the materials and to the form used to verify learning outcomes.
Support channels — an e-mail address and a telephone number — are given in the information sent before the service. If a fault makes delivery impossible, we switch to a backup connection or agree a new date; participants bear no consequences of a problem that arose on our side.
Teaching materials — slide decks, workplace instructions, checklists and document templates — are original works prepared for the purposes of the specific service.
Materials are prepared by the person delivering the service. Fib.Code holds the rights required to use them in the service and to make them available to participants.
Materials are provided for the participant's own use in connection with the service. Participants keep them after the course and may use them in their professional work.
Redistribution, resale and commercial use — including running your own courses based on them — require our consent.
Trade names, screenshots and vendor documentation are used solely within the limits permitted by law, for teaching purposes. Remote services run on licensed Microsoft 365 and Microsoft Teams software.
For every service we confirm the scope of rights and the rules of access to materials to the client in writing.
We record neither video nor audio, we do not archive the chat and we do not run automatic transcription. This is a deliberate decision and it follows directly from what we do.
Our courses take place in the participant's real environment: identity configuration, security settings, permission structures, security management documentation. A recording of such a session would amount to a detailed description of a client organisation's safeguards — an artefact whose very existence increases risk instead of reducing it. A firm advising on information security does not create such artefacts.
A recording captures participants' image and voice, and processing that data is necessary neither to deliver the service nor to document it — the minimisation duty under Article 5(1)(c) GDPR argues against recording. Consent would have to be freely given, and where an employee is sent on a course by their employer, freely given consent is hard to argue.
Knowing that a session is being recorded is remarkably effective at stopping people from talking about their organisation's real problems. Those conversations are the most valuable part of our courses.
Through the session script, a record of the activities carried out, an attendance summary, the results of outcome verification and participant surveys. The Remote Learning Services Standard does not require sessions to be recorded — it points to precisely this kind of evidence.
Recording part of a service is possible in exceptional cases, agreed with the client and with the consent of every participant.
Learning outcomes are verified twice: during the sessions and after they end.
Control questions and quizzes discussed immediately after completion — they serve correction, not grading.
A test or a practical task performed by the participant independently.
Every participant receives individual information on the degree to which the learning outcomes were achieved, together with a certificate containing the elements required by § 14 of the regulation on the register of development service providers.
The assessment instrument is prepared and administered by a validator, not by the person who delivered the sessions. Separating those roles is a rule here rather than an exception — a trainer does not assess the results of their own work.
The scope of delivery data is agreed with the client before the service begins. As standard we provide:
The scope of processing of participants' personal data is described in the privacy notice provided to every participant before the service begins.
Before each delivery the trainer verifies that the materials are current. In our fields this is not a formality — legislation, standards and the naming and configuration of cloud services change more than once a year.
A course built on two-year-old content is sometimes worse than no course at all.
Comments concerning a service are accepted in writing, by e-mail and by telephone — telephone reports are confirmed in writing. We respond within fourteen days.
Deadlines, reporting channels, the register and the remedies available where a complaint is upheld are described separately.
Participants may also rate the service in the Development Services Database survey they gain access to after the course. That rating goes straight to PARP, bypassing us entirely.
We will check whether the service can be published in the Development Services Database and build the programme around your team's actual duties.
This standard applies from 28 July 2026. Legal basis: the Rules of the Development Services Database together with Annex 5, the Remote Learning Services Standard, and the Regulation of the Minister of Funds and Regional Policy of 28 July 2023 on the register of development service providers (Journal of Laws 2023, item 1686). Fib.Code Sp. z o.o. is listed in the Development Services Database on the basis of its ISO 9001:2015 certificate covering training services; provider ID: 40037. This page does not replace the provisions of the contract concluded with the client — in the event of any discrepancy, the contract, the BUR Rules and generally applicable law prevail. Fib.Code Sp. z o.o., ul. Rynek 29, 32-300 Olkusz, Poland, VAT ID 637-220-84-21.