Managed Learning Operations

Managed Learning Operations is a recurring engagement. IETERNUS runs the day-to-day operation of your learning system inside an agreed boundary — so training stays assigned, current, measurable, governed, and maintainable after the build project ends.

Learning systems rarely fail on launch day. They decay. A procedure changes and the module does not. An administrator leaves and the enrolment logic leaves with them. Renewals slip because no one owns the expiry report. This service holds that operating load on a fixed cadence, with named artifacts and a written boundary, instead of leaving it to whoever has time that week.

IETERNUS is not an LMS vendor. We operate the platform you already have, at the permission level you grant.

Six operating domains

Scope is agreed per engagement and written down. Each domain is either inside the boundary or outside it. There is no implied middle.

Governance

• Ownership map naming who approves content, platform changes, and releases
• Release calendar covering scheduled and unscheduled changes
• Scheduled content and system reviews with fixed dates, not intentions
• Decision log recording what changed, who approved it, and why
• Standing governance meeting with an agenda and a written outcome

Platform Operations

• LMS administration within an agreed boundary and permission level
• Publishing and deployment of approved packages
• Enrolment and assignment workflows, including rules by role, site, or group
• Training matrices maintained against the current role structure
• Platform configuration changes and functional testing before release

Content Operations

• Content inventory covering every live asset, its owner, and its review date
• Version control and source-file management
• Scheduled review windows and minor maintenance edits
• Assessment maintenance: item review, mapping to objectives, pass rules
• Retirement and archiving of superseded material so it stops circulating

Records and Reporting

• Completion, expiry, and exception reporting on a fixed schedule
• Renewal tracking with forward visibility of upcoming expiries
• Records held in an agreed structure and location
• Coverage reporting by role, team, or location

Quality and Accessibility

• Consistency checks against agreed templates, terminology, and standards
• Accessibility review that supports accessibility improvement and alignment with agreed standards
• Pilot testing with a named review group before wide release
• Release gates: nothing publishes without passing the agreed checks

Workflow Improvement

• AI-assisted content operations under human review, with the review step named and mandatory
• Template and standard reuse, so repeat work stops being rebuilt
• Automation of repetitive operational tasks such as report assembly and enrolment updates
• Documented workflow changes, so improvements survive staff turnover

The monthly rhythm

The cadence is fixed and visible. A typical month runs:

• Operations and reporting. Enrolment and assignment run. The completion, expiry, and exception report is issued.
• Maintenance window. Approved content edits, assessment updates, and retirements are worked through the queue.
• Release. Changes pass the quality, accessibility, and functional checks, then publish against the release calendar.
• Governance review. Decisions are logged, risks and blockers are raised, and next month’s queue is agreed.

Quarterly, the operating boundary, the release calendar, and the content inventory are reviewed together and adjusted in writing.

Responsibility boundary

What is not included

These exclusions are permanent and are restated in the engagement boundary:

• No 24/7 helpdesk and no out-of-hours incident cover
• No unlimited content production — new builds are scoped separately
• No unlimited support or open-ended request volume
• No legal or regulatory compliance sign-off, and no certification of any kind
• No LMS software development or custom platform engineering
• No learner personal-data processing beyond the agreed boundary
• No HR or disciplinary decisions arising from completion records

How an engagement starts

1. Inventory. Every live asset, assessment, assignment rule, and report is listed with its owner and status.
2. Access. Platform permissions, source files, and storage locations are granted at a defined level and recorded.
3. Baseline. A starting report on completions, expiries, exceptions, and content age — the reference point for everything after.
4. Agreed boundary. A written document naming what IETERNUS operates, what you retain, what is excluded, and the monthly cadence. Operations begin once it is signed off.

Exit and handoff

You can take the operation back in-house at any agreed point. The engagement is built so that this is straightforward rather than disruptive. On exit you receive the operating runbook, the current content inventory and version register, source files, the ownership map and decision log, the release calendar, report definitions, and a written operating model describing how the cadence runs. Administrative access is returned or transferred to your named owner. Records, inventories, and documentation are kept in formats the client can open without IETERNUS.

Where this sits

Build produces the learning system. Operate keeps it working. Managed Learning Operations is the destination for organisations that have already invested in content and now need that investment to hold its value — assigned to the right people, current against the real procedure, reportable when asked, and maintainable by someone other than the person who happens to remember how it was set up.

Need coverage while hiring? Explore the 90-Day Learning Operations Bridge.

Who it is for

• L&D teams without a dedicated operations owner
• operations, safety and compliance functions
• HR and people teams carrying mandatory training
• training and custom-learning agencies
• product enablement teams
• organisations between L&D hires

Problems this solves

• Modules and procedures have drifted apart, and nobody can say which content is current.
• LMS administration sits with one person, undocumented, and stops when that person is unavailable.
• Renewals and expiries are tracked in a spreadsheet that is rebuilt from scratch before every audit.
• Assignment rules are inconsistent, so learners are enrolled in the wrong training or in none.
• A build project delivered good material that has had no scheduled review since launch.
• Reporting can show completions but cannot show exceptions, overdue records, or coverage by role.
• Small content changes queue for months because no maintenance window exists.

What you get

• Operating boundary document
• Ownership map and decision log
• Release calendar and release notes
• Content inventory and version register
• Training matrix by role and location
• Monthly operations report
• Completion, expiry and exception report
• Assessment maintenance record
• Accessibility and consistency check record
• Operating runbook
• Quarterly governance review pack
• Exit and handoff pack

How the work runs

The engagement starts with an inventory and an access baseline, then a written operating boundary that names what IETERNUS operates and what the client retains. From there the work runs on a fixed monthly cadence: operations and reporting, a maintenance window, a scheduled release, then a governance review that sets the next month's queue. Changes move through defined release gates rather than ad hoc requests, and every decision is recorded in the decision log. Quarterly, the boundary, the release calendar, and the content inventory are reviewed together and adjusted in writing.

A good fit when

• A learning system already exists — built by IETERNUS or by someone else — and now needs an owner.
• Training is mandatory, recurring, or role-based, and expiry tracking matters.
• The organisation wants a written boundary and a named cadence rather than open-ended support.
• There is an internal sponsor who can approve releases and answer subject-matter questions.
• Platform access can be granted at an agreed permission level.

Not a fit when

• You need a 24/7 helpdesk or out-of-hours incident response.
• You want unlimited content production folded into a recurring fee.
• You need a supplier to sign off legal or regulatory compliance on your behalf.
• You need custom platform engineering or LMS software development.
• No learning system exists yet — start with a build or architecture engagement instead.

Where this sits: Operate — keep learning assigned, current, measurable, governed, and maintainable · All services

Learning topic: Learning Operations and LMS