90-Day Learning Operations Bridge

The 90-Day Learning Operations Bridge is fixed-term operational cover for a learning function that still has to run while something else is being resolved. It has a defined start, a defined three-part structure, and a defined end at day 90.

This is stabilisation work. It is not an argument against hiring. A Bridge is designed to run alongside active recruitment, and to protect the permanent role rather than compete with it. A permanent hire who arrives to a documented operation, a cleared queue, and a written runbook starts from a stronger position than one who inherits an undocumented backlog and a system nobody can explain.

When a Bridge is the right instrument

• An active vacancy in a learning operations or L&D delivery role.
• Parental or medical leave with no internal cover for the recurring work.
• A backlog that has outgrown the team while the normal schedule continues.
• Headcount approval that has not yet been decided, with a function degrading in the meantime.
• An LMS left unstable after a migration or upgrade — drifted assignments, unreliable records, broken links.
• A role-design problem: the previous job description no longer matches the work, and nobody is sure what the permanent post should be.

How the 90 days run

Days 1–30 — Inventory and stabilisation

We establish what exists, what is broken, and what is at risk. That means a full inventory of courses, curricula, source files, and the systems they live in; a review of LMS configuration, assignment rules, enrolment errors, expired records, orphaned content, and broken links; and a list of every live and pending request with its current owner. Issues are ranked as compliance-critical, business-critical, or cosmetic. Blockers preventing people from completing required training are ranked first and actioned in this block rather than queued behind lower-priority work.

Outputs: Learning Operations Inventory, System State Note, Triage Register, and an interim working cadence so the function is not running on memory.

Days 31–60 — Governance and backlog reduction

We put ownership and cadence in place, then work the queue against it. Requests move to a single documented intake route with stated prioritisation rules. An ownership map records who approves content accuracy, who decides priority, and who owns each curriculum. The backlog is cleared in priority order, with anything deliberately not cleared recorded and explained. Reporting is rebuilt so that completion, overdue status, and assignment accuracy can be produced on a stated schedule by role, team, or location.

Outputs: governance model, request intake route, Backlog Reduction Log, and a restored reporting pack on a fixed cadence.

Days 61–90 — Documentation, operating model, and the handoff decision

We write the operation down so it survives the end of the engagement. The runbook covers every recurring task step by step, with the system used, the frequency, the responsible role, and the known failure modes. The operating calendar fixes review dates, reporting dates, and maintenance windows. We then describe the permanent role from the work as it actually turned out over 90 days, including realistic workload, and prepare the options paper for day 90.

Outputs: Learning Operations Runbook, operating calendar, Role Definition Brief with a first-90-days plan for the incoming person, and the Handoff Pack.

What we need from you

Three dependencies decide whether a Bridge works. System access at administrator level, or the equivalent, to the LMS, content repositories, and reporting. A named internal contact who can answer questions inside the working week. Decision authority for content accuracy and priority order — we operate the system, we do not own the subject matter, and accuracy questions have to reach someone who can settle them.

What the Bridge does not replace

• Not a permanent hire. It is interim cover with an end date built into the scope.
• Not an LMS implementation project. Selecting, configuring from scratch, or migrating a platform is separate work with its own scope.
• Not a content production contract. Course and module production is scoped and agreed separately.
• Not compliance sign-off. We make the state of training visible and the evidence retrievable. The regulatory judgement stays with your accountable people.

Three honest exits at day 90

1. Hand to a new internal hire. The runbook, role brief, and handover sessions transfer the operation to the person you recruited.
2. Continue into Managed Learning Operations. The cadence established during the Bridge becomes an ongoing operating arrangement.
3. Stop. You keep a documented, stable operation and run it yourselves. This is a legitimate outcome and the documentation is written on the assumption that you might choose it.

Who it is for

• l&d teams with an open or unfilled role
• hr and operations leaders covering a leave of absence
• organisations stabilising an lms after migration or upgrade
• compliance, safety and quality training owners
• heads of people or capability awaiting headcount approval
• training agencies covering client-side learning operations

Problems this solves

• The person who ran learning operations has left, and assignments, enrolments and reporting are now handled ad hoc by whoever has time.
• Course assignments and completion records drifted after an LMS migration or upgrade, and nobody trusts the reports.
• Update requests arrive through inboxes and chat threads with no intake route, no priority order, and no named owner.
• A backlog of content and configuration requests has grown past the point where the current team can clear it alongside normal work.
• Managers cannot get a reliable overdue or completion report for their own teams.
• No documentation exists for recurring learning operations tasks; the knowledge sat with one person and left with them.
• A headcount decision is pending and the function is degrading while it is being decided.

What you get

• Learning Operations Inventory — assets, curricula, source files, systems, and current owners
• System State Note — LMS configuration, assignment rules, enrolment errors, orphaned and broken content
• Triage Register — issues ranked by risk with immediate actions and dates
• Governance Model — ownership map, decision rights, and content accuracy approvals
• Request Intake Route — a single documented path for new and change requests, with prioritisation rules
• Backlog Reduction Log — what cleared, what remains, and why it remains
• Restored Reporting Pack — completion, overdue, and assignment accuracy on a stated cadence
• Learning Operations Runbook — every recurring task, step by step, with system, frequency, owner, and failure modes
• Operating Calendar — review dates, reporting dates, and recurring maintenance windows
• Role Definition Brief — the permanent post described from the work as it actually turned out, with a first-90-days plan for the incoming person
• Day 90 Handoff Pack and options paper
• Weekly written status note throughout the engagement

How the work runs

The Bridge runs on a fixed 90-day clock split into three 30-day blocks, each with a stated output at its end. Work is done inside your systems, under your naming conventions and your approvals, so nothing has to be migrated back when the engagement closes. A weekly written status note records what moved, what is blocked, and what needs a decision from you. The handoff pack is assembled from day 61 onward, so the day-90 decision is made with documentation in hand rather than under time pressure.

A good fit when

• A learning operations or L&D delivery role is vacant and recruitment is underway or about to start.
• Someone is on parental or medical leave and the function still has to run to a schedule.
• An LMS is unstable after a migration or upgrade and daily administration has degraded.
• A backlog has outgrown the team and there are dates that cannot move.
• Headcount approval is uncertain, or nobody can yet describe what the permanent job should actually be.

Not a fit when

• You want indefinite substitution for a permanent post. The Bridge is 90 days and is designed to end.
• You need an LMS selected, implemented, or migrated. That is a system project with its own scope, not operational cover.
• You need high-volume content production. Course and module production is scoped separately as a build engagement.
• You need someone to sign off regulatory or legal compliance. We make the state of training visible and the evidence retrievable; the accountable judgement stays with your own accountable people.
• You cannot grant system access, name an internal contact, or provide decision authority on content accuracy within the 90 days.

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

Learning topic: Learning Operations and LMS