Why a Code of Conduct Matters More in 2026 Than It Did Five Years Ago
Online teaching has changed shape. In 2020, most instructors ran a webcam and a slide deck. In 2026, a working instructor at Refonte Learning is often orchestrating a live Kubernetes cluster for a class, reviewing student pull requests, mentoring adults through a career switch, and occasionally advising a corporate cohort with confidential data on the screen. The surface area for professional conduct has multiplied, and so has the risk of getting it wrong.
A code of conduct is not decorative. It is the operating contract between an instructor, the platform, and the learner. When something goes wrong (a harassment complaint, a plagiarism accusation, a leaked dataset, a payment dispute, a safeguarding disclosure from a young adult learner), the code is what everyone falls back on. If it is vague, the platform ends up making arbitrary calls. If it is specific, decisions become defensible and consistent.
This article is a child of our pillar on how Refonte vets everyone who earns on the platform. Vetting is what happens before you teach; the code of conduct is what governs you once you do. The two are inseparable. A rigorous intake process is meaningless if there is no ongoing standard, and an aspirational conduct policy is meaningless if anyone can slip through onboarding.
What follows is not a legalistic paste of our full policy document. It is a plain-language walkthrough of what an instructor on Refonte Learning actually agrees to in 2026, why each clause exists, what enforcement looks like in practice, and where the honest tradeoffs live. If you are considering applying to teach, if you are already teaching and want a refresher, or if you are a learner trying to understand what protections you have, this piece is written for you.
We wrote it in the same spirit we run the platform: practical, opinionated, and specific. Generic conduct policies (be respectful, do not discriminate, follow the law) are true but useless. The interesting work is in the edges. What counts as a conflict of interest when an instructor also freelances in the same domain? Where is the line between using AI to accelerate lesson prep and using AI to replace the human judgment learners are paying for? What obligations does an instructor have when a learner discloses something serious in a private DM? These are the questions the 2026 code answers, and the ones we will walk through in the sections below.
By the end you should have a clear picture of what conduct means at Refonte, why the rules are shaped the way they are, and how they connect to the broader trust architecture of the platform.
The Five Foundational Commitments Every Instructor Signs
Every instructor who joins Refonte Learning signs a conduct agreement built on five foundational commitments. These are not slogans. They are the frame every other rule hangs from, and every enforcement decision references at least one of them.
The first commitment is honest representation. An instructor agrees that the biography, credentials, employment history, and skills claimed on their profile are accurate and verifiable. This ties directly into our vetting pipeline (see identity verification at Refonte explained for the mechanics), but the ongoing obligation is stronger than the intake check. If your circumstances change (you leave the employer listed on your profile, you let a certification lapse, you have not shipped production Kubernetes in three years despite claiming current expertise), you are obligated to update the profile within a reasonable window. Frozen or stale profiles are a slow-motion form of misrepresentation.
The second commitment is learner welfare over commercial interest. If a learner would be better served by a different Refonte program, a different instructor, or even a resource outside the platform, the instructor is expected to say so. This sounds obvious until you are the one whose income depends on retention. The commitment is deliberately worded to bind instructors even when it costs them a sale, because the alternative (instructors upselling learners into programs they do not need) is the single fastest way an EdTech platform loses trust.
The third commitment is confidentiality and data hygiene. Instructors handle a surprising volume of sensitive information: learner employment histories, corporate cohort project details, sometimes proprietary code shared for review. The code of conduct binds instructors to treat all of this as confidential by default, to never share learner work publicly without written permission, and to follow the platform's data handling rules (no personal cloud drives for learner data, no screen recordings without disclosure, no reuse of learner code in other courses).
The fourth commitment is safeguarding. This applies even though the majority of Refonte learners are adults, because adult learners still disclose sensitive circumstances (mental health struggles, harassment at work, immigration precarity, financial distress). Every instructor is trained on the 5 Rs of safeguarding framework: Recognise, Respond, Report, Record, Refer. The obligation is not to solve the problem yourself. The obligation is to respond appropriately and escalate correctly.
The fifth commitment is cooperation with review. If Refonte receives a complaint or opens an internal review, the instructor agrees to participate honestly, to preserve relevant records (chat logs, session recordings, code review comments), and not to retaliate against learners or colleagues who raised concerns. This clause is what makes the rest enforceable. Without it, every serious investigation would stall the moment the subject decided to stonewall.
Together these five commitments form the spine of the code. Every specific rule in the sections that follow is a load-bearing application of one or more of them.
Conduct in Live Sessions: Preparation, Presence, and Boundaries
Live teaching is where conduct becomes most visible. A pre-recorded module can be reviewed and revised; a live session is a real-time performance in front of paying learners, and the standards are higher because the risk is higher.
Preparation is the first non-negotiable. An instructor who shows up to a live session without a run sheet, without having tested the environment (Jupyter kernel loaded, Kubernetes cluster warm, dbt models seeded, whatever the stack requires), and without having reviewed the previous session's outcomes is in breach of conduct. Not because unpreparedness is illegal, but because learners paid for expertise delivered thoughtfully, and winging it is a form of misrepresentation. The internal rule of thumb we use: for every hour of live teaching, expect ninety minutes to two hours of preparation, more if the material is new.
Presence is the second. Instructors must be fully attentive during sessions. No side work, no unrelated Slack conversations, no answering emails during a lull. Learners can tell when an instructor has drifted. The code specifies that instructors must be on camera unless a documented reason applies (low bandwidth region, disability accommodation, a specific pedagogical choice communicated in advance) and that they must actively engage with learners by name, not just broadcast at them.
Punctuality is the third. Sessions start on time and end on time. If an instructor is going to be late, they notify the cohort at least fifteen minutes in advance where possible, and never simply no-show. Chronic lateness or unannounced absences are one of the fastest paths to removal from the platform, alongside more dramatic violations.
The hardest area is boundaries with learners. Adult learners sometimes form strong attachments to instructors, particularly in career-change contexts where an instructor becomes something like a mentor. The code draws a firm line: no romantic or sexual relationships with current learners under any circumstances, no financial entanglements (no borrowing, no lending, no investment invitations), no offering paid side services outside the platform to learners you met through it, and no private communication channels that are not visible to Refonte's compliance systems.
That last point deserves elaboration. Instructors sometimes want to move a learner conversation to WhatsApp or personal email out of convenience. The code forbids this not out of paranoia but because it removes the record. If a dispute arises later (a harassment claim, a payment dispute, an accusation of plagiarism), Refonte cannot mediate a conversation it cannot see. All learner communication happens on platform-hosted channels, full stop.
Instructors should also model professional language and tone. Frustration is human, and learners can be difficult. But sarcasm at a learner's expense, public humiliation over a wrong answer, or dismissive language about beginner questions are all breaches. Teaching is a service, and the service standard applies even on a Friday afternoon after the fourth repeated question.
Content Integrity: Authorship, Attribution, and the AI Question
Content is the product. Instructors create lessons, exercises, projects, and assessments. In 2026, the ethics of content authorship have become genuinely complicated because generative AI can produce competent-looking teaching material in minutes.
The code of conduct addresses this head-on with a principle we call authorial responsibility. It does not matter whether you drafted a lesson from a blank page, adapted it from an old employer's internal training, or used ChatGPT, Claude, or a fine-tuned model to accelerate the process. What matters is that you, the named instructor, take full responsibility for accuracy, pedagogy, and originality. You must be able to defend every claim, correct every mistake, and answer every question the material provokes.
In practice, this creates specific rules. First, direct copy-paste from an AI tool without review is a violation, because AI models hallucinate. We have seen drafts that confidently cite Python standard library functions that do not exist, misattribute quotes to famous engineers, and describe Kubernetes primitives in ways that made sense in version 1.18 but are wrong in current releases. If you use AI, you fact-check.
Second, if a lesson is substantively derived from AI output, it must still reflect your judgment about what to teach and in what order. A lesson that is just a lightly edited AI dump is a breach even if every fact checks out, because pedagogy is more than facts. We wrote about the underlying dynamic in AI-generated code and technical debt; the same dynamic applies to AI-generated lesson content. Speed today, expensive cleanup tomorrow.
Third, attribution is required. If you adapt a diagram from a public source, cite it. If you borrow a problem set structure from a textbook, name the textbook. If you use a dataset from Kaggle or an open source project, link to it and check the license. Plagiarism (passing someone else's material off as your own) is grounds for immediate removal, and it does not matter whether the source was human or machine.
Fourth, there are areas where AI assistance is broadly welcome. Rewriting your explanation of a concept for clarity, generating varied practice problems from a template, translating your English lesson notes into another language for accessibility, drafting quiz distractors, brainstorming analogies: these are legitimate productivity uses. The rule is not "do not use AI." The rule is "the instructor named on the lesson is the accountable author, regardless of tools used."
Assessment integrity is a related area. Instructors must design assessments that measure real learning, not memorization of an answer key that circulates on Discord. They must respond promptly to reports of leaked assessments, rotate problems when necessary, and report suspected cheating to platform staff rather than accusing learners directly. False accusations of cheating cause real harm, and the code requires evidence and process before any action.
Finally, instructors own the copyright to material they create for Refonte, but they grant the platform a license to host, distribute, and reuse it within the platform's programs. The code prohibits instructors from reselling identical material to competitors during their tenure and for a defined post-departure window; it also prohibits Refonte from stripping instructor attribution from lessons that remain in the catalog.
Conflicts of Interest and Outside Work
Most Refonte instructors have day jobs or freelance practices. That is a feature, not a bug: current practitioners make better teachers than career educators who have not shipped in a decade. But it creates a persistent risk of conflicts of interest, and the code addresses this with more nuance than most platforms bother with.
The first rule is disclosure. Instructors must disclose their primary employer and any significant freelance clients in domains overlapping with their teaching. If you teach cloud security and consult for a cloud security vendor, we need to know, and learners need to know when it becomes relevant (for example, when you recommend a tool that happens to be your client's product).
The second rule is no undisclosed promotion. You may not recommend a product, service, book, or program in which you have an undisclosed financial interest. If your recommendation is genuine and you have a stake, disclose the stake. If you cannot disclose (an NDA prevents it), do not recommend. This applies to affiliate links, referral bonuses, revenue share arrangements, and equity positions.
The third rule is no poaching. Instructors may not solicit Refonte learners for private tutoring, consulting engagements, or non-Refonte courses. This is where instructors sometimes push back, arguing that they should be free to serve their audience. The code's position is that the audience was aggregated by Refonte's marketing, curriculum, and reputation, and diverting it privately is a breach of the earning relationship. If an instructor wants to teach independently as well, they may, but they may not source those learners through Refonte channels.
The fourth rule is transparency about competing offerings. If you also teach on another platform, that is generally fine. What is not fine is recycling identical Refonte cohort material verbatim on a competing platform (an authorship-integrity issue) or badmouthing Refonte to learners in ways that undermine the program they are enrolled in.
The fifth area is investments and advisory roles. Instructors who take advisory roles at startups whose products are discussed in Refonte curricula must disclose those roles. If the conflict is material, the platform may ask the instructor to hand off the specific lesson to a peer or add a visible disclosure to the module.
What happens when a conflict is disclosed? Usually nothing dramatic. Most disclosures are noted and closed. The purpose of the rule is not to prevent instructors from having lives outside Refonte; it is to prevent learners from receiving advice shaped by hidden incentives. When learners see a disclosure banner on a module ("the instructor holds an advisory role at Vendor X, discussed in this lesson"), they can weigh the information appropriately. That is the whole point.
One edge case worth naming: instructors who move between full-time roles frequently. If your employment situation changes materially every few months, we ask you to update your profile at each change rather than waiting for an annual review. This connects to our ongoing employment verification process, which is not a one-shot check at onboarding.
Safeguarding, Wellbeing, and Escalation Paths
Refonte's learner base is predominantly adult professionals, but "predominantly adult" is not "exclusively adult," and even fully adult populations experience safeguarding-relevant events. The code of conduct treats safeguarding as a core competency of every instructor, not an edge case.
Instructors complete a safeguarding module during onboarding that walks through the 5 Rs of safeguarding: Recognise (spot the signs of distress or risk), Respond (react appropriately without overreacting or dismissing), Report (escalate to the platform's designated safeguarding lead), Record (write down what was said and when, using platform tools not personal notes), and Refer (point the learner to appropriate external resources).
A concrete example. A learner in a career-switch cohort messages her instructor to say she is going to miss the next session because her partner has become physically threatening and she is looking for somewhere to stay. What does the code require the instructor to do? Not to problem-solve directly. Not to promise confidentiality that cannot be kept. The correct response is empathetic acknowledgment, a clear statement that the instructor will connect her with someone at Refonte trained to help, an immediate escalation to the safeguarding lead, and a written record of the exchange in the platform's system. External referrals (domestic violence helplines in the learner's country) are provided by the safeguarding lead, not improvised by the instructor.
The rationale for this structure is that instructors are subject matter experts, not counsellors. Trying to be a counsellor when you are not trained is well-intentioned but often harmful. Escalating quickly to trained staff is not passing the buck; it is the correct professional response.
Mental health disclosures are common. Learners in intensive career-change programs sometimes hit a wall around week six or seven, when the initial excitement wears off and the difficulty of the material bites. Instructors are expected to notice signs (sudden drop in engagement, missed assessments after strong early work, comments about not sleeping or feeling like an imposter) and to check in privately with a light touch. The code does not require instructors to diagnose or treat; it requires them to be human, to normalize the struggle, and to signpost the platform's learner support resources.
Harassment between learners is another scenario. If an instructor witnesses or receives a report of harassment (racist comments in a Slack channel, sexual comments to a peer during a breakout room, aggressive DMs), the code requires immediate action: pause the behavior, secure the affected learner, and report to Refonte's trust and safety team. Instructors do not adjudicate harassment claims themselves. They preserve evidence and escalate.
Instructor wellbeing is also part of the code, though it is often forgotten in these documents. Instructors who are burned out teach badly, respond irritably to learners, and make more mistakes. The code recognizes this and asks instructors to set sustainable schedules, decline cohorts they cannot properly serve, and use the platform's instructor support channels when they are struggling. An instructor who quietly overcommits and then delivers poor sessions is in breach of conduct, even though the immediate cause is overwork rather than malice.
The overall philosophy is that safeguarding is not just about protecting learners from external threats. It is about maintaining a psychologically safe learning environment where difficult material can be attempted, mistakes can be made publicly, and vulnerability can be voiced without penalty. That environment is built or destroyed session by session, and the code makes each instructor an active builder of it.
Financial Conduct: Payments, Refunds, and Learner Disputes
Money is where conduct policies get tested. Instructors earn from Refonte through a mix of hourly teaching rates, cohort revenue shares, project-based payments, and sometimes referral bonuses. Learners pay significant fees for programs. When either side feels the financial terms are being bent, trust collapses fast.
The code addresses this through several specific rules. First, no cash side deals. Instructors may not accept payment directly from learners for anything related to Refonte programs. If a learner offers to pay extra for private sessions, the answer is either "book a paid tutoring block through the platform" or "no." Direct payments bypass tax reporting, bypass Refonte's revenue share, bypass the record-keeping that protects both parties in a dispute, and often violate the tax and labor laws of the instructor's country. This connects to background checks for online teaching jobs and the broader compliance frame the platform operates within.
Second, honest hour reporting. Instructors who bill by the hour report actual hours worked, rounded honestly. Padding hours (reporting three hours for two hours of prep, adding phantom minutes to session times) is a straightforward breach and one of the more common causes of removal. The platform has automated checks that flag suspicious patterns (large numbers of hours reported at odd times, hours reported on days when there was no scheduled activity, hours that exceed reasonable ratios to session length) and any discrepancy triggers a review.
Third, refund cooperation. When a learner requests a refund, the instructor may be asked for context: did the learner attend, did they complete assessments, was the experience delivered as promised? The code requires instructors to provide honest input, even when a refund would reduce their revenue share. Attempting to influence a refund decision by misrepresenting learner engagement is a serious breach.
Fourth, transparent pricing communication. Instructors sometimes discuss pricing with learners considering upgrades or additional programs. The rule is simple: quote the actual platform price. Do not invent discounts you cannot honor, do not describe programs you do not know the current price of, and if you are unsure, point the learner to the official page or to a Refonte enrollment advisor.
Fifth, payment disputes with the platform. Instructors occasionally disagree with a payment calculation. The code requires disputes to go through the platform's finance review process, not through public complaints or through withholding services. An instructor who threatens to stop teaching a cohort mid-program over a payment dispute is in breach; the correct path is to complete current commitments and pursue the dispute through proper channels.
There is a related area worth flagging: how instructors handle their own tax reporting. Refonte issues appropriate documentation depending on the instructor's jurisdiction, but tax compliance is ultimately the instructor's responsibility. The code requires instructors to keep their tax residency information current on their profile and to notify the platform of changes. Instructors who move countries mid-year sometimes forget this, and it creates headaches for everyone.
Finally, referral and affiliate arrangements. Instructors may earn referral bonuses for bringing new instructors to the platform. They may not earn referral bonuses for bringing learners (this would create pressure to recruit learners into programs regardless of fit). The distinction is important and gets asked about often.
Enforcement: What Actually Happens When the Code Is Breached
A code of conduct is only as strong as its enforcement. Refonte's enforcement approach is graduated, evidence-based, and documented, with escalation paths that match the severity of the breach.
Minor breaches (a late session without notification, a lesson that failed to cite a source, a curt exchange with a learner) typically start with a private conversation between the instructor and their program lead. The instructor is told what went wrong, why it matters, and what to change. Most first-time minor issues end here, and the instructor learns from it.
Repeated minor breaches, or a single moderate breach, trigger a formal notice. This is written, it goes on the instructor's internal record, and it includes specific expectations for change and a review timeline. Instructors under a formal notice may have their cohort load reduced or may be asked to complete additional training modules.
Serious breaches (harassment of a learner, financial misconduct, safeguarding failures, plagiarism, misrepresentation of credentials) trigger a suspension while the platform investigates. During suspension the instructor's sessions are covered by peers, their access to learner data is revoked pending review, and they cannot enroll in new cohorts. The investigation follows a defined procedure: gather evidence, interview the instructor and any affected parties, review platform logs, reach a decision, and communicate the outcome in writing with reasons.
The most serious breaches result in permanent removal from the platform. We have written specifically about what gets you removed from Refonte, and the same principles apply to instructors. Categories of behavior that lead to immediate and permanent removal include: sexual misconduct toward a learner, credential fraud discovered after onboarding, financial fraud against the platform or against learners, serious safeguarding failures, and retaliation against learners or colleagues who raised concerns.
Removal is not the end of enforcement in every case. Where behavior may have violated laws (criminal harassment, financial fraud, distribution of unlawful material), Refonte reports to appropriate authorities. Where behavior violates professional codes of conduct in the instructor's home jurisdiction (for example, financial services regulations), we may notify relevant regulators.
Due process matters. The code guarantees instructors under investigation the right to see the specific allegations, to respond in writing, to provide their own evidence, and to appeal an initial decision. Appeals are heard by a reviewer who was not involved in the original decision. This is not just fairness for its own sake; it is what makes enforcement decisions defensible when they are challenged, whether internally, in the press, or in court.
Transparency about outcomes is deliberately limited. We do not publish the names of removed instructors, both because it invites defamation liability and because it turns removal into a public shaming ritual that discourages people from raising concerns in the first place. Aggregate statistics are shared with the instructor community periodically so that the population understands what is happening: how many formal notices were issued in a quarter, how many suspensions, how many removals, and the broad categories involved.
Enforcement is also proactive, not just reactive. The platform runs periodic audits of session recordings, code review comments, and learner feedback patterns. Automated systems flag concerning patterns (large drops in cohort engagement, clusters of low ratings, unusual payment patterns) for human review. Most flags resolve as noise; some catch problems early.
Onboarding and Ongoing Training: The Code Is a Living Document
A code of conduct that is signed once and forgotten is theatre. The Refonte code is a living document, revisited during onboarding and refreshed throughout an instructor's tenure.
Onboarding starts before the first session. New instructors complete a structured program that includes: reading the full conduct policy, watching short training modules on safeguarding and content integrity, passing a scenario-based assessment (given this situation, what do you do?), and having a one-on-one call with a program lead. The scenario assessment is not a rubber stamp. Instructors who answer key questions poorly are asked to revisit specific modules and retest.
Instructors who are new to online teaching entirely, as opposed to experienced teachers moving platforms, get additional support. If you have never taught a live technical session before, the code holds you to the same standards as a veteran, but the onboarding gives you more scaffolding: shadowing existing instructors, co-teaching your first cohort with a mentor, receiving structured feedback on early sessions. Our guide to online tutoring jobs for beginners covers what to expect if you are earlier in your teaching career.
Ongoing training happens quarterly. Every instructor completes a short refresher on at least one conduct area per quarter (safeguarding, content integrity, financial conduct, and so on), rotating through the topics annually. When the code is updated (usually once or twice a year to reflect new circumstances or lessons learned from real cases), all instructors receive the updated document, a summary of what changed and why, and a required acknowledgment.
Ad hoc training happens when the platform notices a pattern. If a wave of complaints surfaces about, say, how instructors handle late submissions, we produce a short training piece on the specific issue and require relevant instructors to complete it. This is more effective than pretending the general code covers every specific circumstance in useful detail.
Instructors are also expected to keep their subject matter current. The code does not prescribe a specific continuing education requirement, but it does hold instructors accountable for teaching accurate, current material. A cloud instructor who has not touched a major cloud provider's console in two years is a problem. A data engineering instructor still teaching pre-modern data stack patterns as best practice is a problem. Peer review sessions, where instructors sit in on each other's classes and provide feedback, are part of how we surface these issues.
Feedback loops from learners feed back into training. When learner feedback consistently identifies a gap ("the instructor was expert but hard to follow"), the platform provides pedagogical coaching, not just a warning. When feedback identifies a strength ("the instructor handled a difficult classroom moment brilliantly"), that instructor may be asked to contribute to peer training.
The philosophy is simple: conduct is a skill, not a static compliance checkbox. Skills atrophy without practice and improve with feedback. The onboarding and ongoing training system is what keeps the code from ossifying into a document nobody reads.
How the Code Connects to Vetting, Verification, and Broader Platform Trust
This article is a child of our pillar on how Refonte vets everyone who earns on the platform, and the connection is worth making explicit. Vetting is upstream. Conduct is downstream. Both are needed, and each makes the other more effective.
Vetting establishes that an instructor is who they claim to be, has the credentials they claim, and has no known history that should disqualify them. It is a snapshot in time, refreshed periodically. If you want the mechanics, our post on identity verification at Refonte explained covers exactly how we confirm identity, and the broader vetting picture is in the pillar itself.
The code of conduct picks up where vetting leaves off. Vetting cannot predict future behavior. A well-credentialed instructor with a clean background check can still be careless with learner data, plagiarize a lesson, or fail a safeguarding scenario. The code is what governs behavior once someone is inside, and enforcement is what removes them when the behavior fails the standard.
These two systems together create the platform's trust architecture. Learners need to trust that instructors are real experts, and that they behave professionally once teaching. Instructors need to trust that colleagues have been through the same rigor, so that the professional reputation of teaching on Refonte is worth something. Corporate clients need to trust that cohorts they enroll their teams in will meet a consistent standard.
There is one more layer worth naming: the platform holds itself to conduct standards too. If an instructor raises a concern about how Refonte staff handled a situation, the code guarantees it will be investigated with the same seriousness as a concern about an instructor. Trust cannot be one-directional.
If you are considering teaching with us, the best next step is straightforward. Read this piece, read the vetting pillar, read what gets you removed from Refonte to be honest with yourself about whether the standards are ones you can meet, and then apply. When you become an instructor on Refonte Learning, you are agreeing to a specific and demanding professional contract. That is a feature, not a warning. The demanding standards are what make teaching on the platform meaningful, and what make the credential of being a Refonte instructor worth carrying.
Refonte Learning is operated by Refonte Infini Infiniment Grand, a French SAS (SIREN 949 841 605, verifiable at data.inpi.fr), with an operational office at 1 Poulton Close, Dover, Kent, United Kingdom, CT17 0HL. The code of conduct summarized here is the practical distillation of a longer legal document, which every instructor signs at onboarding and reaffirms annually. Questions about how any specific clause applies to your circumstances are always welcome; the whole point of a living code is that it responds to real cases.
Closing: What Good Conduct Actually Looks Like Day to Day
If you strip away the policy language, what does a well-conducted instructor look like on a normal Tuesday in 2026?
They open the session with the environment already tested and the run sheet in front of them. They greet learners by name. They handle a wrong answer with grace, using it as a teaching moment rather than a mistake to correct. They notice a learner who has been quieter than usual and check in privately after the session. When a learner asks a question they do not know the answer to, they say so, promise to follow up, and actually follow up within the promised window.
They use AI to speed up lesson prep but they read every word before it reaches a learner. They cite the Kubernetes documentation when they show a manifest, because they know the docs are the source of truth and want learners to know it too. When a learner shares proprietary code from their employer for review, they treat it as confidential, review it privately, and delete the copy after the session.
They turn in honest hours. They flag when they are overcommitted rather than delivering poor sessions silently. They tell their program lead when they have started freelancing for a company whose product features in one of their lessons. When a learner discloses something serious in a DM, they respond warmly, escalate correctly, and record the exchange. When they disagree with a platform decision, they say so through proper channels and keep teaching well while the disagreement is worked out.
They do not chase learners into private tutoring outside the platform. They do not badmouth Refonte to their cohort when things frustrate them. They do not cut corners on preparation because a session feels routine. They keep their own skills current, because they know that teaching stale material is a slow betrayal of learners paying good money to catch up to the current state of the field.
None of that is heroic. It is professional. That is exactly the point. The code of conduct is not designed to produce heroes. It is designed to make professional teaching the default, so that learners can trust the experience and instructors can trust each other. When it works, the code is nearly invisible in day-to-day teaching, surfacing only in the specific moments where a decision needs a framework.
When it does not work, we notice. Learners tell us in feedback. Peer instructors flag concerns. Automated systems surface patterns. Reviews happen, decisions are made, and the code updates to reflect what we learned. That cycle is the machine that keeps online teaching honest at scale, and it is why the code matters as much in 2026 as any curriculum decision the platform makes.
If you want to teach under this standard, we would like to hear from you. Read the linked resources, think honestly about whether the commitments described here fit how you want to work, and then become an instructor on Refonte Learning. The code is demanding on purpose. It is also, in our experience, what makes teaching here worth doing.