What "course delegation" actually means at Refonte Learning
Course delegation is the operational model that lets a person or a small studio deliver a course, cohort, or mentoring track on Refonte Learning without being a full-time employee, and without being a purely passive licensor of a video file. It is a middle path: the platform handles enrollment, payments, learner support tooling, credentialing, dispute handling, and the legal wrapper. The delegated instructor, or the delegated mentor working under a lead instructor, handles the teaching craft: syllabus design, live sessions, feedback, project review, and the small daily judgments that decide whether a learner actually progresses.
The word "delegation" is doing real work here. It is not a synonym for outsourcing, and it is not a synonym for freelancing. Delegation at Refonte specifically refers to the arrangement where a lead course owner (which may be Refonte itself, a partner studio, or an independent instructor) authorizes another qualified professional to deliver some or all of the learner-facing activity on their behalf, under the lead's syllabus and quality bar, with the platform as the contractual counterparty to the learner.
In 2026, this model matters more than it did two or three years ago for three reasons. First, live and cohort-based learning has continued to grow faster than pure self-paced video, and one human cannot personally mentor 300 learners at once. Second, the practitioner talent pool that learners actually want to learn from (senior MLOps engineers, staff data engineers, principal SREs) has zero interest in becoming a full-time instructor. They will contribute four to eight hours a week if the arrangement is clean. Third, regulators in the EU, the UK, and several US states have tightened rules on how educational providers must disclose who is actually teaching a course. Delegation, done well, is compatible with those rules. Delegation, done sloppily, is a compliance landmine.
The rest of this article walks through the concrete mechanics of how Refonte course delegation works in 2026: who applies, how they are approved, how the syllabus is scoped, how sessions are scheduled and quality-checked, how revenue flows, how learners are told, and how the relationship winds down when a course is retired or a delegate steps away. It is written for practitioners who are considering supplying teaching work to the platform, and for internal reviewers who need a single reference on the end-to-end flow.
The three roles in a delegation arrangement
Every delegation on Refonte Learning has three named parties, and it is worth being precise about them before going further, because the rest of the process is essentially a set of rules about how these three interact.
The first role is the course owner. This is the entity that holds the syllabus, the assessment design, the learning outcomes, and (subject to the IP terms) the underlying course materials. The course owner is accountable for the pedagogical shape of the course. If a learner complains that "the module on feature stores does not match what the sales page promised," the course owner is the party who has to answer that. The course owner may be Refonte's in-house curriculum team, a partner training studio, or an independent senior instructor who built the course from scratch.
The second role is the delegated instructor or delegated mentor. This is the person who actually shows up to run live sessions, review submissions, hold office hours, grade capstones, or run 1:1 mentoring calls. In some courses there is one lead instructor and several delegated mentors handling cohorts or breakout groups. In others, the course owner has delegated the entire delivery to a single instructor because the owner is a working practitioner who cannot commit to weekly live time. The delegate is bound by the same quality bar as the owner and works under the owner's syllabus.
The third role is Refonte Learning as the platform. Refonte is the contractual counterparty to the learner. When a learner buys a seat, they buy it from Refonte. When they need a refund, they ask Refonte. When they raise a safeguarding or conduct concern, they raise it with Refonte. Refonte in turn holds contracts with the course owner and, where relevant, directly with each delegated instructor. This matters because it means the learner is never left holding a bag when a course owner and a delegate disagree. The platform absorbs that risk and resolves it upstream.
Understanding this triangle is what makes the rest of the process readable. A lot of the friction people encounter when they first look at delegation, whether as a would-be instructor or as an internal reviewer, comes from collapsing two of these roles together. If you are considering whether to teach yourself or delegate, the teach or delegate pillar guide breaks down the tradeoff on a role-by-role basis. Keep the three roles distinct in your head and the workflow below stops looking bureaucratic and starts looking like a set of sensible checks.
Step 1: application and eligibility
The entry point for anyone who wants to supply teaching work under a delegation arrangement is the instructor application. You can become an instructor on Refonte Learning through a single form that captures your professional background, the domains you feel qualified to teach or mentor in, the format you want to work in (live cohort, async review, 1:1 mentoring, capstone judging, curriculum authoring), and the weekly hours you can realistically commit.
The application asks for things that a lightweight platform would not bother with. We ask for links to work you have actually shipped: a GitHub org, published papers, conference talks, a portfolio site, a company page describing a system you built. We ask for two professional references who can confirm the seniority claim. We ask you to describe, in your own words, a technical concept in your domain to a hypothetical learner two levels below you, because the ability to compress and translate expertise is not correlated with seniority as tightly as people assume.
Eligibility in 2026 is not primarily a credential check. It is a fit check across four axes:
- Domain depth: can you actually do the thing you propose to teach, at the level a paying professional learner expects.
- Communication: can you explain it without either patronizing or drowning the learner.
- Reliability: will you show up to the sessions you commit to, on time, prepared, for the full length of the cohort.
- Conduct: no unresolved disputes, no pattern of unprofessional behavior with previous learners or employers, and a willingness to sign onto the platform's code of conduct.
A meaningful minority of applicants are declined at this stage not because they lack technical depth but because they cannot commit reliable weekly hours. Delegation is a poor fit for someone who can only give unpredictable ad-hoc time. Those applicants are usually redirected to one-off guest sessions or advisory work, which have lower reliability requirements. Others are declined because their domain is one Refonte does not currently run cohorts in, in which case we hold the application for the next quarterly review.
Approved applicants move into onboarding. Rejected applicants receive a written reason and are welcome to reapply after six months, or immediately if they think the rejection was based on a misunderstanding of their background.
Step 2: mentor approval and scoping
Approval to be listed as an eligible instructor is not the same as approval to deliver a specific course. Once an applicant is accepted into the pool, the next step is being matched to a course and going through the delegating mentor approval process for that specific delivery.
This two-stage design is deliberate. A senior data engineer might be perfectly qualified in the abstract, but not the right delegate for a course whose syllabus leans heavily on Snowflake when their production experience is exclusively BigQuery. Or they might be an excellent fit for the syllabus but unable to cover the specific time zone the cohort is running in. Rather than making the initial application try to predict every possible course-level fit, we split the decision.
A course-level approval typically involves three artifacts. First, the syllabus itself, so the delegate knows exactly what they are signing up to teach and can flag any modules they would want to modify or hand off. Second, the previous cohort's retrospective, so the delegate can see what worked, what did not, and where the current learner-facing pain points are. Third, a scoping call between the course owner, the delegate, and a Refonte program manager, where the three parties align on responsibilities: which live sessions the delegate runs, which submissions they grade, which office hours they staff, and what the escalation path is when they need a decision from the owner.
The scoping call is the single most important part of the delegation process, and it is the part most often shortchanged in a hurry. If the delegate leaves that call unclear on whether they are allowed to modify a specific module, or whether a specific type of learner request should be escalated, that ambiguity will surface later as either an unhappy learner or an unhappy owner. A thirty-minute investment here saves days of rework later.
The output of scoping is a delivery brief: a written document that both the owner and delegate countersign, describing exactly what the delegate will do for the duration of the cohort, what discretion they have, and what they must escalate. Refonte keeps this brief on file, and it is what we refer back to when adjudicating any later disagreement.
Step 3: contracting, IP, and legal wrapper
Once scoping is done, the paperwork phase starts. There are typically three documents involved: the platform-level instructor agreement (signed once when you first join the pool), the course-specific delivery agreement (signed for each cohort or engagement), and, where the delegate is contributing new material, an IP addendum.
The platform-level agreement covers the standing terms of working with Refonte: conduct, confidentiality, data handling, non-circumvention, tax status, dispute resolution. It is the umbrella document. Delegates are strongly encouraged to read it carefully rather than skim, because it references several other operational policies by name.
The delivery agreement is short and specific. It names the cohort, the dates, the hours, the fee or revenue share, and the scope from the delivery brief. It is essentially the delivery brief plus commercial terms.
The IP addendum only appears when a delegate is authoring new material rather than delivering existing material. If you are running a cohort using a course owner's existing syllabus and slides, no IP addendum is needed: the owner keeps ownership of what already existed. If, during delivery, you produce new worksheets, new capstone rubrics, new supplementary videos, the addendum defines who owns those new artifacts and on what license terms they can be reused by the platform, the owner, or you. Practitioners considering this arrangement should read the platform's summary of how IP is treated under the delegation model before signing.
A delegation contract is not a license to use the Refonte brand freely. Delegates are permitted to describe themselves publicly as "instructor for course X on Refonte Learning" or "mentor on Refonte Learning's cohort in Y," but not as "Refonte instructor" without qualification, and not in ways that imply employment. This distinction matters both for regulatory reasons (misrepresenting employment status has tax consequences in several jurisdictions) and for brand reasons.
The tax and cross-border piece is worth flagging even in a high-level overview. Delegates are engaged as independent contractors in most jurisdictions, which means they are responsible for their own income tax and, where applicable, VAT registration. Refonte issues the paperwork needed to file cleanly, but does not withhold taxes on the delegate's behalf. Delegates operating from jurisdictions with specific requirements should consult the course provider terms-of-use summary for the specifics.
Step 4: delivery mechanics inside a live cohort
Once contracting is done, the delegate is added to the cohort's operational tooling. In 2026, that stack looks similar across most Refonte cohorts, though details vary by domain. There is a learning-management surface where learners access materials and submit work, a scheduled video platform for live sessions, a chat channel for the cohort community, and an internal instructor channel where owners, delegates, and program managers coordinate.
The rhythm of a typical cohort week for a delegated instructor includes: one or two live sessions of ninety minutes each, roughly two to four hours of async review of learner submissions, one office hour, and coordination time with the course owner and other delegates. That comes to somewhere between eight and twelve hours per week for a standard cohort of thirty to fifty learners. If a delegate is running smaller pods or 1:1 mentoring, the shape shifts but the total time envelope is similar.
Two delivery patterns are worth calling out because they are where new delegates most often stumble. The first is submission review turnaround. Learners paying for a live cohort expect feedback within a defined window, usually 48 to 72 hours. A delegate who lets submissions pile up for a week is functionally worse than a good async course, because the learner was told to expect timely feedback and did not get it. If your week is unpredictable, build in a fixed review block and defend it. The second is live session preparation. "I know this material cold" is not the same as "I have a plan for this session." A senior engineer who winged it in front of colleagues at work can absolutely wing it in front of learners, but learners will notice, and the retrospective at the end of the cohort will show it in the feedback scores.
During delivery, the course owner is available for escalations but is not the day-to-day face of the course. The delegate is. This is by design: the whole point of delegation is that the owner has offloaded the recurring delivery burden. When something genuinely needs the owner (a syllabus-level dispute, a request to change a graded rubric mid-course, a safeguarding concern), the delegate escalates through the internal instructor channel and gets a response typically within one business day. The Refonte program manager is copied on every escalation and adjudicates when the owner and delegate cannot agree.
Step 5: revenue mechanics and payouts
Refonte's delegation model has a specific commercial structure, and understanding it is important both for delegates deciding whether to accept an engagement and for owners deciding how to price a cohort. Rather than describing every possible variant, the summary here focuses on the standard live-cohort case; edge cases (advisory-only, capstone judging, guest sessions) follow the same principles at smaller scale.
When a learner buys a cohort seat, the gross revenue is first reduced by payment-processing fees and any promotional discounts that apply. What remains is the net cohort revenue. From net cohort revenue, Refonte deducts its platform share, which covers hosting, learner acquisition, support, credentialing, and the operational overhead of running the platform itself. What remains after the platform share is the instructor pool, which is distributed between the course owner and any delegated instructors according to the terms in the delivery agreement.
The specific splits vary by course and by the mix of owner vs. delegate contribution. In a course where the owner built the whole syllabus and materials but has delegated all live delivery, the owner typically retains a majority share and the delegate takes a substantial delivery fee. In a course where the delegate is essentially co-authoring and co-delivering, the split moves closer to parity. The precise mechanics and worked examples are covered in the article on course delegation revenue split, which we recommend reading before signing any delivery agreement.
Payouts happen on a defined schedule rather than on every transaction, because cohort revenue accrues over time (some learners pay in installments, some request refunds within the refund window, some upgrade). Refonte's standard schedule pays out monthly, in arrears, for revenue that has cleared the refund window and any chargeback risk. Delegates who need to plan cash flow should read the course provider payout schedule so they understand when a cohort that closes in March will actually turn into money in their account.
Two specific gotchas are worth naming. First, chargebacks and refunds within the refund window are clawed back from the pool before distribution, which means a delegate's payout for a given month depends on the net-of-refunds figure, not the gross. Second, cross-border payments incur FX conversion at whatever rate the payment rails give us on the day, which can shift the final number by a small but noticeable amount. Neither of these is unusual for professional-services work, but delegates coming from a salaried background sometimes find the variability jarring in the first month.
Step 6: learner disclosure and honesty
A delegation model only works if learners know what they are buying. If a learner enrolls in a cohort believing that a named senior practitioner will personally teach every session, and in fact a delegate they have never heard of is running the sessions, the learner has been misled. This is bad ethics and, increasingly in 2026, bad law: consumer-protection regulators in the EU and several other jurisdictions have made clear that material facts about who delivers an educational service must be disclosed before purchase.
Refonte's policy on this is straightforward and non-negotiable. Every course page names the course owner and, where applicable, the delegated instructors who will actually deliver the cohort the learner is buying into. If the delegate changes between cohorts, the page is updated. If a delegate has to step in mid-cohort because another delegate falls sick, learners are notified within one business day. The learner disclosure obligations article covers the exact wording standards and the notification workflow.
Disclosure is not just a compliance exercise. It also shapes the learner's experience for the better. A learner who knows in advance that they will be mentored by a specific delegated engineer, with a specific background, can calibrate their expectations and questions. They can look up the delegate's public work and come to the first session already engaged. Trying to hide the delegate, on the other hand, creates a background anxiety in the cohort that surfaces as passive-aggressive feedback later.
One subtlety worth naming: disclosure does not mean the delegate has to publish their full CV or personal contact details. It means the learner-facing course page must state that delivery is by a named delegate (or delegates), give enough professional detail that a reasonable buyer can judge the fit, and make clear how learners can raise concerns if the actual delivery does not match what was described. That level of disclosure protects both the learner and the delegate.
Internally, disclosure discipline also affects how we advertise. Refonte's marketing team is not permitted to imply, in ads or on landing pages, that a named senior figure teaches every session of a cohort when in fact they only appear for guest lectures. This constraint sometimes frustrates marketers who would like to lean harder on a marquee name, but it is the price of running a delegation model honestly.
Step 7: quality assurance during delivery
Quality assurance in a delegated cohort is a shared responsibility, and understanding how it is shared is essential to running a healthy course. The course owner owns the syllabus-level quality bar: whether the learning outcomes are being met, whether the assessments are calibrated correctly, whether the module sequencing still makes sense. The delegated instructor owns the session-level quality: whether the specific class was well-prepared, whether feedback on submissions is timely and constructive, whether learner questions in office hours are being handled well. Refonte owns the operational quality: whether the platform is up, whether the calendaring works, whether disputes are being resolved.
During a live cohort, several quality signals are collected in real time. Learners submit weekly pulse-check surveys, which give a running temperature of the cohort mood. Session recordings are reviewed by the course owner or a Refonte program manager on a spot-check basis, not to surveil the delegate but to catch pedagogical issues early. Submission review turnaround times are tracked automatically, so a delegate who is falling behind on grading gets an early nudge rather than a nasty surprise in the end-of-cohort review.
When a quality issue is identified mid-cohort, the first response is coaching, not escalation. A Refonte program manager will typically speak with the delegate, share the specific signal ("three learners in the pulse survey mentioned that last Tuesday's session felt rushed"), and work with them on an adjustment. Most quality issues are addressable this way. Escalation to a formal review is reserved for patterns that do not respond to coaching or that involve conduct concerns rather than pedagogical calibration. The full framework, including who is on the hook when something goes wrong, is laid out in the article on quality responsibility under delegation.
At the end of each cohort, a structured retrospective is held with the owner, the delegate(s), and the program manager. The retrospective covers what worked, what did not, what should change in the next iteration of the course, and whether the same delegates will run the next cohort. Learners' end-of-cohort feedback is anonymized and shared with the delegate in full, because obfuscating feedback helps no one improve. Delegates who receive consistently high feedback across two or three cohorts become preferred delegates for that course and are given first refusal on future cohorts.
Step 8: safeguarding, data protection, and conduct
A delegation model spreads the surface area of a course across more people, which means the platform has to be more, not less, disciplined about safeguarding and data protection. Every delegate goes through the same training as internal instructors on how to handle learner data, how to recognize and escalate safeguarding concerns, and what the code of conduct requires in specific practical situations.
On data protection specifically: delegates handle learner submissions and, in many cases, personal information (professional context, career goals, sometimes reasonable-accommodations requests). They are bound by the platform's data-processing terms, which are aligned with GDPR and the equivalent regimes in the UK and other jurisdictions. Delegates are not permitted to copy learner data to their own systems beyond what is strictly needed for teaching, are not permitted to retain it after the cohort ends beyond a defined window, and are not permitted to use it for any purpose other than delivering the course. The specifics are in the course provider data-protection duties reference, and every delegate confirms they have read it as part of onboarding.
On conduct: the platform's code of conduct applies equally to owners, delegates, and learners. Boundary violations, harassment, discrimination, and misuse of the instructor's position are all covered, with a clear reporting channel. Refonte investigates every reported concern, and where a delegate is found to have breached the code, the delegation is ended and the delegate is removed from the pool. This is a small number of cases in practice, but the framework has to be robust enough that when it happens, it is handled cleanly.
On safeguarding more broadly: because Refonte's learners are adult professionals in most cohorts, safeguarding concerns look different from those in a school setting. The most common issues are around mental-health disclosures during 1:1 mentoring, workplace-related distress that surfaces in class, and occasionally learners approaching delegates for advice on situations that are outside the delegate's professional competence. Delegates are trained to acknowledge, not to try to solve, and to refer learners to appropriate resources. Refonte maintains a small internal team that supports delegates when a difficult situation arises.
These are not glamorous topics and they are not the reason anyone becomes a delegated instructor. But they are the reason the delegation model does not fall apart the first time something awkward happens, and every experienced delegate has at least one story about being glad the framework existed when it did.
Step 9: what happens when a delegation ends
Every delegation eventually ends, and the graceful ones end predictably. There are four common exit paths.
Cohort completion. The most common case: a cohort finishes on its scheduled date, the retrospective is held, and the delegate either signs on for the next cohort or hands off cleanly to a new delegate. If there is a handoff, the outgoing delegate is expected to spend a couple of hours briefing the incoming delegate on the cohort's rhythm, any known learner-support situations, and any syllabus tweaks that were made mid-course.
Delegate resignation. A delegate may want to step away because their day job has changed, because they want to focus on a different domain, or simply because they have delivered enough cohorts and are ready to do something else. The instructor agreement requires reasonable notice, ideally before the next cohort's marketing has started but at minimum before enrollment closes. Delegates who need to resign mid-cohort are treated compassionately, and the platform will backfill, but this is the case everyone tries to avoid because it disrupts learners.
Course retirement. A course itself may be retired because the underlying technology has moved on, learner demand has shifted, or the course owner has decided not to maintain it. In this case, the delegate's engagement ends with the final cohort, and the course provider termination and learner access rules govern how existing learners retain access to materials they have already paid for.
Termination for cause. In rare cases, a delegate is terminated for breach of contract, breach of the code of conduct, or persistent quality failures that did not respond to coaching. This is handled through a defined process, not summarily, and the delegate has the right to respond before a final decision is made. The details of how learner access is preserved when a delegation ends unexpectedly are covered in the termination-and-learner-access article on the blog.
In all four cases, the delegate's obligations do not end the moment the engagement ends. Confidentiality obligations continue. Non-circumvention obligations, which prevent the delegate from directly soliciting learners they met through the platform for their own competing offering, continue for a defined period. Data-protection obligations continue for as long as the delegate holds any residual learner data (which should be zero within a short window). These continuing obligations are standard for professional-services contracts and are laid out in the umbrella instructor agreement.
Common failure modes and how to avoid them
After running this model across enough courses and enough delegates, a pattern of recurring failure modes has emerged, and it is worth naming them explicitly so that new delegates can avoid them.
The first is scope creep during delivery. A delegate signs on to deliver an existing syllabus, but midway through the cohort, they start rewriting modules on the fly because they disagree with how the owner structured them. This produces a course that is neither what the learners bought nor what the delegate would have designed. The fix is discipline: if you disagree with the syllabus, escalate to the owner, propose a change for the next cohort, and deliver what was agreed in this one.
The second is under-communicating with the owner. Delegates who are used to running their own show sometimes treat the owner as an absent landlord and forget to escalate things the owner would have wanted to know about. The result is that the owner finds out about a problem from a learner complaint rather than from the delegate. The fix is a lightweight weekly check-in during a cohort, even when nothing dramatic has happened.
The third is overpromising in office hours. A delegate, wanting to be helpful, tells a learner "yes, I can also review your take-home project for your real-world job interview." This is out of scope and creates an expectation that other learners will see and want too. The fix is to be generous with the domain conversation and firm about the boundary of the course.
The fourth is under-preparing for live sessions because you think your seniority makes prep unnecessary. It does not. The whole catalogue of these failures is worth reading before your first cohort, and Refonte maintains a summary in the common mistakes article.
Delegation vs. hiring vs. self-teaching: choosing the model
A question that comes up regularly, especially from course owners who are considering whether to delegate at all, is how delegation compares to the two obvious alternatives: hiring a full-time instructor, or just teaching the course themselves. The short answer is that all three are valid and the right choice depends on the volume of teaching and the stability of demand.
Self-teaching is right when the course is new, demand is uncertain, and the owner wants direct feedback from every learner in order to iterate the syllabus. It is wrong when the owner is a working practitioner whose day job cannot absorb the weekly delivery load. Hiring a full-time instructor is right when the course has multiple back-to-back cohorts running year-round with predictable demand. It is wrong when demand is seasonal or when the required skill mix changes cohort to cohort. Delegation is right when demand is real but uneven, when the required teaching skill is specific enough that a full-time hire cannot cover the whole catalogue, or when the owner wants to preserve the option of running multiple parallel cohorts without doubling headcount.
Most mature courses on the platform end up in a mixed pattern: the owner teaches some cohorts personally, delegates the ones they cannot cover, and hires a full-time program lead only when the course reaches enough scale to justify it. The tradeoff analysis is worked through in more detail in the article on delegation versus hiring staff.
For delegates themselves, the parallel question is whether to accept a delegation engagement or to build their own independent teaching practice. The honest answer is that delegation is a good fit if you want to focus on teaching craft and not spend time on marketing, sales, learner support, and platform operations. It is a poor fit if you want full control over pricing, brand, and every operational decision. Both paths are legitimate. Refonte's model gives you the first.
Getting started as a delegated instructor in 2026
If you have read this far and think delegation is a good match for what you want to do, the next step is straightforward. Submit the instructor application, be honest about your domain and your available hours, and be patient with the two-stage approval. Expect the first course-level scoping call to feel more detailed than you thought it needed to be; that detail is what protects you and the learners once delivery starts.
Refonte Learning has spent the last several years refining this model, and while the specifics will keep evolving, the underlying philosophy is stable: teaching craft and platform operations are different jobs and should be done by people who are good at each, with clear contracts, clear disclosure to learners, and clear revenue mechanics. That is what makes delegation work at scale in 2026, and it is what makes it a legitimate professional practice rather than a euphemism for outsourcing.
When you are ready, apply to teach on Refonte Learning and start the conversation. The team on the other end reads every application, and the process from first form to first cohort typically takes six to ten weeks depending on where the next matching cohort sits in the calendar. That six-to-ten-week window is time well spent, because by the time you walk into your first live session, you will already know exactly what you are responsible for, what you are not, and where to turn when the inevitable surprise shows up.
About Refonte Learning
Refonte Learning is an EdTech platform delivering professional training in AI, data engineering, cloud, DevOps, and software engineering through a mix of self-paced content, live cohorts, and 1:1 mentoring. Refonte Learning is operated by Refonte Infini Infiniment Grand, a French SAS (SIREN 949 841 605), with an operational office at 1 Poulton Close, Dover, Kent, United Kingdom, CT17 0HL. The delegation model described in this article is one of several ways practitioners can supply teaching, mentoring, and advisory work to the platform.