There is a moment when a law becomes something more than a text published in the Official Gazette.
It becomes a practical problem. It becomes a question posed to a headteacher who doesn't know where to begin, a teacher staring at an open Google Drive folder wondering whether what she's doing is even correct, an IT technician at a provincial secondary school who suddenly realises that setting up a server requires rather more than knowing the administrator password.
That moment arrived in May 2026.
What happened in May 2026 — and why it matters
Through Order No. 3,858/2026 of the Ministry of Education and Research, published in the Official Gazette of Romania, Part I, No. 392 of 8 May 2026, the Framework Methodology for the Development and Management of the Professional Portfolio of Teaching Staff was formally approved. This is not mere bureaucratic circularity. It represents a genuine shift in how the state understands the documentation, evaluation, and archiving of a teacher's career.
The provisions are clear in their consequences. Beginning with the 2026–2027 school year, every teacher will be required to maintain a comprehensive professional portfolio containing documents relating to professional activity, assessment, continuing development, and classroom work — including in digital form. That portfolio will carry weight at decisive stages of the career: the definitivat examination, the award of teaching grades, annual performance reviews, school inspections, staff mobility, and the granting of increments and prizes.
This is not, then, an optional tool — a folder a teacher might build when the mood takes her, or when the headteacher persists. It is compulsory. Schools have no more than sixty days from the date of publication of the order to produce their own internal procedure — the deadline falling on 6 July 2026 — a procedure to be brought to the attention of all teaching staff and published on the school's website.
The Ministry has announced its intention to create an integrated national platform. The Secretary of State enumerated modules for standardised assessment, financial management, records and electronic registers, together with a module for teacher portfolios and pupil portfolios, the platform's stated ambition being to reduce school bureaucracy. At the time the order was published, the project was still under evaluation at the Ministry of European Projects and Investment.
In other words: the promised national platform does not yet exist in operational form. Schools must manage now, with what they have.
This tension — between the Ministry's centralising ambition and the decentralised reality of several thousand educational institutions spread across Romania — is precisely the space in which open-source platforms become relevant.
What an e-portfolio compliant with the order actually means, technically
Before any conversation about software solutions can begin, one must understand what is actually being asked for. The professional portfolio may be kept in physical or digital form (an e-portfolio), including on online platforms or storage devices, and will be used to monitor the professional development of teaching staff. Should a teacher leave the institution or the system, the portfolio must be archived for three years.
This portability clause is essential, and it is frequently overlooked in public debate. A teacher transferring from a school in Suceava to one in Botoșani must be able to take with her — or hand over institutionally — a complete, ordered, and legible portfolio. If that portfolio resides in a personal Google Drive folder, or on an improvised server configured by an enthusiastic volunteer, portability becomes impossible or, more seriously, non-compliant.
The order explicitly stipulates that documents must be organised in strict chronological order of acquisition. The list of required documents is described as indicative, minimal, and non-exhaustive — adaptable according to the teacher's status and level of education.
The legal risk is not an abstract one: teachers who introduce false data or documents into their portfolios face disciplinary, civil, and, where applicable, criminal liability under the order.
A digital platform for an e-portfolio is therefore not simply a storage space. It is a legal infrastructure. It must guarantee the authenticity of documents, traceability of modifications, controlled access, and data portability. This is the framework through which the open-source platforms described below will be assessed.
Moodle — the de facto standard of Romanian digital education
Moodle is, without question, the best-known Learning Management System (LMS) in European and Romanian education. Present in universities, colleges, and secondary schools alike, it has enjoyed a natural advantage over its competitors in Romania — owing in part to the availability of local support communities and its integration into European digitalisation projects.
Moodle is particularly well suited to universities, schools, and organisations seeking a free, flexible, and scalable LMS. It supports varied learning formats — blended learning, the flipped classroom — and offers multilingual support for international audiences.
From the standpoint of compliance with Order MEC No. 3858/2026, Moodle presents several structural advantages. It provides native or extensible e-portfolio modules — among them Exabis Competence Grid, which allows documents to be aligned to competence standards. Moodle 4.5, released in October 2024, includes a Privacy API requiring plugins to support GDPR export and deletion workflows — an essential feature in managing teaching staff data.
Interoperability — that quality so frequently invoked in official documents without specifying what it means in practice — is well defined in Moodle's case: the platform allows complete data export in standardised formats (IMS Enterprise, SCORM, secured XML backups), a matter of real consequence when teaching staff move between institutions.
Moodle integrates with BigBlueButton, H5P, Turnitin, Microsoft 365, Google Drive, Zoom, Mahara, PayPal, Nextcloud, and Opencast — making it a natural centre for already-established digital ecosystems.
Its limitations in the Romanian context are equally real. Installing and administering a Moodle instance requires a level of IT expertise that few pre-university schools possess in-house. Security updates, database management, permissions configuration for hundreds of teachers — all of this demands time and specialist knowledge. The realistic solution for smaller schools is either managed hosting (with recurring costs) or a partnership with the county inspectorate, which might centralise the infrastructure.
Mahara — the portfolio as professional identity
If Moodle is an LMS with portfolio functionality, Mahara is the inverse: a portfolio system with professional networking functionality. This architectural distinction carries significant pedagogical and administrative consequences.
Mahara is an open-source e-portfolio platform designed to complement traditional LMSs, providing learners with a space to present their competencies, achievements, and projects. It supports reflective and competence-based learning, enabling the creation of personalised portfolios that can be shared with educators, colleagues, or prospective employers.
The native Moodle–Mahara integration — known in the international community as Mahoodle — combines structured course delivery with portfolio-based assessment. This is likely the optimal configuration for an educational institution wishing to cover both course management (Moodle) and the documentation of teachers' professional identity (Mahara) simultaneously.
Mahara allows a teacher to build a layered presentation profile: teaching activity, continuing professional development, publications, extracurricular projects — each section with configurable visibility. A headteacher might see one subset; an inspector, another; an assessment committee might access the complete portfolio. This corresponds precisely to the logic of Order 3858/2026, which provides for the portfolio to be used in different contexts — the definitivat, teaching grades, inspections, and staff mobility.
Mahara's interface may feel less intuitive than modern cloud-based LMSs, but with appropriate configuration and adequate support it offers considerable value to institutions seeking to document professional growth and encourage reflective practice.
ILIAS — the rigour of European public institutions
ILIAS (Integriertes Lern-, Informations- und Arbeitskooperations-System) is less well known in Romania than Moodle, yet it has a solid presence in public administrations and vocational training institutions across Germany, Switzerland, and Austria — systems with high standards of security and institutional compliance.
ILIAS is used by universities, public administrations, and corporate training departments, offering considerable flexibility through personalised learning pathways, assessments, and certifications. It is particularly well suited to sectors where compliance and reporting are critical — healthcare and finance among them.
ILIAS's distinctive advantage over Moodle, in the specific context of Order 3858/2026, lies in its internal Portfolio and Professional Blog module, integrated directly into the core source code without requiring external plugins. This reduces the risk of incompatibility during updates and simplifies long-term maintenance.
A further quality of particular relevance to Romanian school administrations: ILIAS permits the definition of strict portfolio templates at institutional level, enforced administratively, with no possibility for teachers to alter the structure. This means that all forty or eighty schools in a given county can use precisely the same structure required by the methodology — uniformly verifiable by inspectors. Structural standardisation of the portfolio, which is otherwise difficult to enforce in large organisations, becomes a simple administrative setting.
Nextcloud and OwnCloud — data sovereignty without LMS complexity
There is a practical argument for why some schools might prefer a private cloud solution over a full LMS: the scale of what is actually needed. If the requirement is exclusively the storage, organisation, and sharing of supporting documents — without course modules, without pupil management, without quizzes — then a complete LMS is a lorry hired to carry a handbag.
Nextcloud and OwnCloud address precisely this problem: they provide the infrastructure of a Google Drive or OneDrive, but installed on the school's own server, under institutional control. No teacher's document passes through American commercial servers. No advertising algorithm processes file metadata. The data remain in Romania, within the institution.
From a GDPR standpoint — which Order 3858/2026 invokes implicitly through its requirement for compliance with personal data regulations — staff will store personal data only on school equipment, use strong passwords, and configure devices to lock automatically after a short period of inactivity. Any data security breach must be reported to Romania's National Supervisory Authority for Personal Data Processing (ANSPDCP).
Nextcloud addresses these requirements through native functions: document versioning (a complete history of modifications to any file), access auditing (a full log of who accessed or downloaded a document and when), and support for digital signatures on files. Should an inspector wish to verify the authenticity of a portfolio document, the system provides chronological proof of access.
Nextcloud's limitation when compared with ILIAS or Moodle is clear: there is no internal portfolio logic — the structure must be built manually through folders and naming conventions. This means the school must impose through administrative procedures what an LMS enforces automatically through its architecture.
Mandatory technical requirements at implementation
Beyond the choice of platform, Order 3858/2026 implicitly imposes — through its references to GDPR and interoperability — a set of technical requirements that a school's IT team must satisfy regardless of the solution chosen.
Controlled hosting. The server on which the platform runs must be in an institutionally controlled environment: either the school's or inspectorate's own server, or an authorised hosting provider with an explicit data processing contract (DPA — Data Processing Agreement). The use of personal Google Drive or Microsoft OneDrive accounts is not compliant, since responsibility for teachers' personal data rests with the institution, not the individual.
Full data export. A teacher must be able to download a complete archive of her portfolio in a standard format — a zip file with documents indexed in HTML/XML — in the event of transfer to another educational institution. This requirement is directly linked to the three-year archiving clause and the provisions on staff mobility.
Granular permissions control. Not everyone who accesses a portfolio should see the same content. A trainee teacher, a headteacher, a general inspector, a committee awarding a teaching grade — each has different viewing rights. The chosen platform must permit precise configuration of these access levels.
Evaluation traceability. Every modification to a portfolio document must be recorded and verifiable. A backdated or post-inspection amendment represents an explicit legal risk: introducing false or forged data into a professional portfolio attracts disciplinary, civil, and potentially criminal liability.
A practical comparison: which platform suits which type of school
There is no universal answer to this question, but it can be structured along several decisive axes.
National colleges and large technical secondary schools — with in-house IT staff, the financial resources for hosting or a dedicated server, and an organisational culture oriented towards European projects — are the natural candidates for Moodle or the Moodle + Mahara combination. The complexity of the functionality is justified by the capacity for administration.
Lower secondary schools and mid-sized secondary schools — without dedicated IT staff, with limited budgets, whose primary requirement is compliance rather than pedagogical innovation — may find in ILIAS or Nextcloud solutions closer to their real implementation capacity. ILIAS for the coherence of a standardised portfolio; Nextcloud for documentary simplicity.
Networks of schools coordinated by county inspectorates — the most cost-effective and compliance-friendly scenario — could centralise a Moodle or ILIAS instance at county level, with separate instances per educational unit and centralised security and update management.
One caution is necessary: open-source LMS platforms reduce licensing costs and offer complete control over code and deployment, but they still require qualified IT staff for installation, maintenance, security, and updates. A compliance pilot should validate real user experiences before any large-scale roll-out.
The invisible infrastructure: what the headteacher cannot see, but without which nothing works
There is a paradox peculiar to digitalisation in Romanian public institutions: decisions are taken at policy or management level, but implementation falls on the shoulders of people who were consulted at no stage of the regulatory process.
A headteacher signs the decision to implement an e-portfolio. An IT teacher — perhaps a volunteer, perhaps with a reduced administrative timetable — is handed the task of installation. Between the decision and reality lies a technical and human abyss that no framework methodology can bridge through the language of an order.
This is, most likely, the deepest tension in Order 3858/2026: it regulates the product — the portfolio — without regulating the necessary infrastructure: the platform, the server, the IT expertise, the maintenance budget. The Secretary of State clarified that the portfolio may be realised not only digitally, but also in physical form, "because we appreciate that some schools may not have the means to do otherwise."
That sentence, offered as a pragmatic concession, is in reality a confession. The digitalisation of teacher portfolios in Romania is not, for the moment, a problem of platform selection. It is a problem of infrastructure. The open-source platforms described in this article are real, tested solutions, compliant with GDPR and with the spirit of the order. But they presuppose something that Romanian education policy has not yet resolved structurally: that someone knows how to install them, maintain them, and explain them to teachers.
Questions and Answers
Pertinent questions on Ministerial Order MEC No. 3858/2026 and open-source platforms for e-portfolios
1. Why is a personal Google Drive folder insufficient for a teacher's e-portfolio?
Order MEC No. 3858/2026 requires that data be hosted under institutional control, not that of the individual. A personal Google Drive account transfers legal responsibility from the school to the teacher — which contravenes GDPR, which obliges the educational institution, as data controller, to maintain technical and organisational oversight of documents containing personal data. Furthermore, portfolio portability at the point of transfer between schools becomes impossible to guarantee if the data reside in a private account.
Bear in mind: The legal data controller is the institution, not the teacher. Any cloud solution must have a signed DPA with the provider.
2. What is a DPA, and why does it matter for a school choosing a hosting service?
A DPA — Data Processing Agreement — is the contract by which a cloud service provider gives a legal undertaking to process data exclusively for the declared purpose, in compliance with GDPR, and not for commercial use. Without a DPA, the provider is an uncontrolled third party processing personal data belonging to teaching staff. In Romania, the absence of such a contract may attract sanctions from the ANSPDCP. Any open-source platform hosted externally — on a VPS or dedicated hosting — must be accompanied by such a signed document.
Bear in mind: Without a signed DPA, external hosting is not GDPR-compliant, however technically secure the platform may be.
3. What is the essential difference between Moodle and Mahara — and when does the "Mahoodle" combination make sense?
Moodle is an LMS — a system centred on delivering courses, tests, and class management, with portfolio functionality added through plugins. Mahara is a pure e-portfolio system, designed for documenting professional identity and career development. The "Mahoodle" combination — the native LTI integration between the two — is optimal when a school wishes simultaneously to manage courses (Moodle) and maintain a structured professional portfolio with role-specific visibility (Mahara). The two platforms complement one another; neither substitutes for the other.
Bear in mind: Moodle manages courses; Mahara manages professional identity. Together they cover the requirements of Order 3858/2026 in full.
4. What concrete advantage does ILIAS offer over Moodle for a network of schools coordinated by a county inspectorate?
ILIAS allows the definition of strict portfolio templates at institutional level, imposed administratively, with no structural modifications available to teachers. This means that all forty or eighty schools in a county may use exactly the same structure required by the methodology — uniformly verifiable by inspectors. Moodle offers greater flexibility, which is an advantage for institutions with active IT staff, but a disadvantage for networks requiring standardised compliance without uncontrolled customisations.
Bear in mind: ILIAS = rigid, centralised compliance. Moodle = flexibility at a higher administrative cost.
5. What does "evaluation traceability," as implicitly required by Order 3858/2026, mean in practice?
Traceability means that every document in the portfolio carries a verifiable modification log: who uploaded it, when, who subsequently altered it, and what version existed at the time of any given inspection. The order explicitly states that the introduction of false data or forged documents attracts disciplinary, civil, and criminal liability. Without technical traceability, this legal provision is unenforceable. Serious LMS platforms (Moodle, ILIAS) and Nextcloud offer native logging; ordinary files in a shared folder offer nothing equivalent.
Bear in mind: Traceability is not an optional feature — it is the technical guarantee underpinning the legal accountability the order prescribes.
6. Why is Nextcloud not an LMS — and in what circumstances is it nonetheless the right choice?
Nextcloud is a private cloud system: it provides storage, sharing, versioning, and access auditing, but has no internal portfolio logic, competence pathways, or assessment modules. It is the right choice for small or lower secondary schools with a single requirement: to replace a personal Google Drive account with a GDPR-compliant solution installed on the school's server, without the complexity of a full LMS. The portfolio structure must be built manually through folder conventions and administrative procedures — requiring organisational discipline rather than advanced technical expertise.
Bear in mind: Nextcloud = simple documentary compliance. It does not resolve portfolio structure — it replaces a non-compliant arrangement with a compliant one.
7. What is the deadline for producing the internal procedure, and what must it contain?
Under the order, schools have sixty days from the date of publication in the Official Gazette (8 May 2026) to produce their own internal procedure — placing the deadline at 6 July 2026. The procedure must establish: the concrete portfolio structure for the categories of teaching staff in the institution; the platform or storage method chosen; the rules governing access and visibility; and the archiving arrangement in the event of transfer or departure from the system. It must be published on the school's website and communicated to all teaching staff — neither step is optional.
Bear in mind: 6 July 2026 is the internal procedure deadline. Publication on the school's website is mandatory, not discretionary.
8. What concrete legal risks arise if a teacher introduces false documents into a portfolio?
Order 3858/2026 explicitly provides for threefold liability: disciplinary (institutional sanctions, including dismissal), civil (financial damages to the institution or affected third parties), and criminal (in accordance with legislation on forgery — Articles 320–323 of the Criminal Code). This provision transforms the portfolio from an administrative instrument into a document carrying the same legal force as an official record. The platform chosen must support this accountability technically — through traceability and by rendering backdating either technically impossible or readily detectable.
Bear in mind: A falsified portfolio may result in criminal proceedings. The platform must make backdating technically impossible, or at the very least detectable.
9. Why is the three-year archiving clause more significant than it first appears?
The clause stipulates that when a teacher leaves the institution or the system, the portfolio must be archived for three years. This implies: the platform must support full data export in a portable, non-proprietary format; the school or inspectorate must maintain access to the archive even after the teacher is no longer active in the system; and data may not simply be deleted upon departure. Without this export and long-term archiving function, any platform — however technically well configured — becomes non-compliant at the moment the first teacher leaves.
Bear in mind: Full export in a standard format (zip/XML/HTML) is not optional — it is a compliance requirement for staff mobility.
10. What is the fundamental tension in Order 3858/2026, and why do open-source platforms not resolve it entirely?
The order regulates the product — the portfolio — without funding the infrastructure required to produce it: the server, the hosting licence, the IT expertise for installation and maintenance, the training of teachers in its use. Open-source platforms (Moodle, ILIAS, Mahara, Nextcloud) are genuine, compliant, and tested technical solutions. But they presuppose that someone within the school knows how to install, update, and troubleshoot them. The Secretary of State implicitly acknowledged this tension when noting that the portfolio may also be kept in physical form, "because we appreciate that some schools may not have the means to do otherwise." Digitalisation without funded infrastructure is an obligation without the means to fulfil it.
Bear in mind: Open-source = zero licensing cost, not zero implementation cost. Without an IT budget and local technical expertise, any platform remains an aspiration.
Bibliography
-
Order MEC No. 3,858/2026 approving the Framework Methodology for the Development and Management of the Professional Portfolio of Teaching Staff, published in the Official Gazette of Romania, Part I, No. 392 of 8 May 2026 — lege5.ro
-
Edupedu.ro (2026). OFFICIAL: From the 2026–2027 school year, all teachers are required to submit a professional portfolio — edupedu.ro
-
Edupedu.ro (2026). OFFICIAL: By early July, all schools are required to produce their own internal procedure — edupedu.ro
-
DirectMM.ro (2026). The new methodology for teachers has been published in the Official Gazette — directmm.ro
-
G4Media.ro (2026). Professional portfolio to be compulsory for pre-university teachers from 2027 — g4media.ro
-
Ziarul Profit (2026). The Ministry of Education launches the new digital professional portfolio for teaching staff — ziarulprofit.ro
-
Overt Software (2026). Learning Management System (LMS) Comparison Report 2025–2026 — overtsoftware.com
-
Selleo (2026). Open Source LMS Comparison 2026 — selleo.com
-
People Managing People (2026). 15 Best Open Source LMS Platforms Picked for 2026 — peoplemanagingpeople.com
-
School Education Gateway (2018, updated). A concise guide to interpreting GDPR for use by schools and teachers — schooleducationgateway.eu
-
ISJ Timiș / ANSPDCP (2020). GDPR in Schools: A practical guide to processing personal data — isj.tm.edu.ro
-
Moodle.org — official Moodle 4.5 documentation, Privacy API, portfolio plugins
-
Mahara.org — official documentation, LTI integration with Moodle
-
ILIAS.de — official documentation, Portfolio and Professional Blog module
-
Nextcloud.com — official documentation, audit, versioning, and digital signature features
Author's Note
Limitations of this article
This article is built on legislative texts publicly available at the time of writing (May 2026), on the official documentation of the open-source platforms discussed, and on verified journalistic sources. I do not have access to the complete text of the framework methodology in the format processed by the Official Gazette — only to summaries and quotations from specialist education media (Edupedu.ro, G4Media, DirecMM). It is possible that certain technical details of the order are nuanced differently in the literal text.
I have not conducted any practical testing of these platforms in the specific context of Romanian schools in 2026. The comparisons are built on official documentation and international comparative analyses, not on pilot implementations in Romania. Anyone implementing one of these solutions will discover discrepancies from the descriptions here — specifics of local infrastructure, available versions, hosting restrictions imposed by county inspectorates.
Comparisons and tensions
Moodle and ILIAS are often presented as direct competitors. They are, in truth, different philosophies of institutional organisation: Moodle presupposes a living ecosystem, with continuous plugins and adaptations, whilst ILIAS promises stability and rigid structure. The first philosophy advantages institutions with active IT staff; the second, those that wish to operate with minimal administrative intervention after initial configuration.
The structural tension running through this article — and through the reality it describes — lies between regulation and capacity. Order 3858/2026 is, in terms of intent, a sound instrument: continuous professional documentation, career portability, accountability for the authenticity of data. But it presupposes a digital infrastructure that many Romanian schools do not possess and will not build without explicit resources. The legislative technique of mandating the product without funding the infrastructure is a recurring pattern in the digitalisation of Romanian public services.
Rhetorical choices in this text
I chose to open the article with a narrative register — "there is a moment when a law becomes something more than a text" — in order to anchor the reader immediately in the human dimension of the problem rather than the juridical one. The strategy draws on a reading of Knausgård applied to non-fiction: the specific quotidian (the headteacher who doesn't know where to begin, the technician with the admin password) as an entry point into the abstract (GDPR compliance, interoperability).
The nine-section structure follows a gradation from accessible to deep: a reader arriving with a practical question ("which platform should we install?") will find her answer in sections III–VI; a reader arriving with an older, more searching question will find, in section IX, the acknowledgement that the problem is not, in fact, technical.
The section on "invisible infrastructure" is deliberately constructed as an antithesis to the technical register of the preceding sections. If the rest of the article speaks in the language of expertise, this section speaks in the language of reality. The Secretary of State's remark is placed strategically, because it illustrates a self-contradiction: a compulsory order issued in full awareness that many of its intended recipients lack the means to comply with it.
I have not avoided — but have tried to manage — the risk of becoming didactic. The article does not teach; it describes and compares. The distinction is easily lost when writing about software and legislation. I hope I have not entirely lost it here.