Why a Dispute Resolution Mechanism Matters More Than the Contract Itself
Every tutor contract at Refonte Learning includes clauses on payment, deliverables, IP, and termination. Those clauses matter, but they are only as strong as the process that resolves disagreements about them. A contract that says "tutor will be paid within 30 days" is meaningless if there is no clear path for the tutor to escalate a late payment. A clause on "quality standards" is meaningless if there is no defined route when a learner complains and the tutor disagrees with the assessment.
That is why we treat dispute resolution as a first-class part of the tutor relationship, not a footnote. In 2026, the tutors who thrive on our platform are the ones who read the Refonte tutor contract overview end to end, understand where the friction points typically arise, and know exactly what to do when something goes wrong. This article is the operational companion to that contract: the plumbing behind every clause.
Dispute resolution at Refonte serves three constituencies simultaneously. Tutors need protection against arbitrary termination, disputed payments, and learner complaints they cannot defend. Learners need a credible channel to escalate genuine grievances about instruction quality, missed sessions, or curriculum mismatches. Refonte itself needs a system that scales as the platform grows, that produces consistent outcomes for similar cases, and that generates the data we need to improve tutor selection and training over time.
The mechanism we describe here is not aspirational. It is the process we actually run in 2026, refined over multiple cohorts and program launches. It has three tiers (informal resolution, structured mediation, and formal arbitration), defined timelines at each stage, evidence standards, and an appeals path. Most disputes never leave tier one because the informal channel is designed to resolve them fast. But when a case does escalate, both sides know the rules going in.
One principle underlies everything: procedural fairness beats substantive perfection. We would rather have a dispute process that both parties trust, even if it occasionally produces outcomes one side finds imperfect, than a system that claims to be optimal but leaves either tutors or learners feeling ambushed. That principle shapes every design choice below, from timelines to evidence rules to who sits on review panels.
The Three Tiers of Dispute Resolution
Refonte disputes flow through three tiers, and the vast majority resolve at the first level. Understanding the structure up front helps tutors and learners calibrate expectations.
Tier one: informal resolution. This is direct, documented communication between the parties, facilitated by a Refonte program coordinator when necessary. Timeframe: seven business days from the initial complaint. Most payment questions, scheduling disagreements, and minor learner concerns close here. The coordinator's job is not to judge, but to surface the facts, clarify what the contract says, and help both sides reach a workable outcome. Roughly 78 percent of tutor disputes in 2025 closed at this tier without escalation, and we expect a similar rate in 2026.
Tier two: structured mediation. If tier one fails or if the complaint involves alleged contract breach, a mediation panel convenes. The panel has three members: a senior Refonte program manager, an independent tutor representative drawn from a rotating pool, and a neutral third party (typically a senior educator or industry practitioner unaffiliated with the specific case). Timeframe: 21 business days from escalation. The panel reviews written submissions, may request additional evidence, and issues a written recommendation. The recommendation is binding on Refonte but the tutor retains the right to appeal to tier three.
Tier three: formal arbitration. This is the final internal step and is used rarely. Cases reaching this tier typically involve significant financial claims (over 3,000 EUR), allegations of serious misconduct, or complex IP disputes tied to content ownership rules. Arbitration follows a formal written procedure, both parties may bring representation, and the decision is final within the Refonte process. Timeframe: up to 45 business days. Beyond arbitration, French law and the contract's governing-law clause apply, since Refonte Learning is operated by Refonte Infini Infiniment Grand, a French SAS registered at SIREN 949 841 605.
The tiered structure is deliberate. It filters out disputes that are really just miscommunications (tier one), it applies more rigorous process to cases with real substance (tier two), and it reserves heavyweight procedure for the small subset that genuinely require it (tier three). Every tier has a clear time limit so that no dispute lingers indefinitely, which is one of the most common complaints about grievance systems at competing platforms.
Who Can Initiate a Dispute and What Counts as One
Any party to the tutor engagement can initiate a dispute: the tutor, the learner, or Refonte's own quality assurance team acting on aggregated signals. What counts as a dispute worth escalating is defined narrowly to prevent noise from swamping the system.
Qualifying tutor-initiated disputes include: disputed or delayed payments, disputed session-cancellation charges, alleged contract-clause violations by Refonte or by a learner, disagreement with a negative performance review that affects standing or pay, allegations of harassment or unprofessional conduct from a learner, and IP or content-ownership disputes. Non-qualifying items include general dissatisfaction with cohort assignment, requests for higher pay outside the contract's review cycle, and disagreements about curriculum design (which have their own product-feedback channel).
Qualifying learner-initiated disputes include: allegations of tutor no-show or chronic lateness, session content substantially different from what was advertised, unprofessional or abusive tutor conduct, refund requests grounded in service failure, and grade or assessment disputes where the learner believes the tutor applied criteria inconsistently. Non-qualifying items include general dissatisfaction with course difficulty, personality clashes without specific conduct issues, and disputes about published grading rubrics.
Qualifying Refonte-initiated disputes include: patterns of learner complaints against a specific tutor that cross a threshold, statistically anomalous grading or attendance patterns, breach of the independent contractor status obligations (such as unauthorized subcontracting), and violations of the code of conduct.
All disputes must be filed within 60 days of the triggering event or of the date the party reasonably should have discovered it. Late filings are rejected except in cases involving alleged fraud or safety issues, which have no time bar. The 60-day window is deliberately generous because we would rather process a slightly stale complaint than have parties feel they missed their window.
One subtle but important design choice: disputes are filed against the process or the decision, not against a named individual on the Refonte team. This depersonalises the mechanism and reduces the retaliation concerns that plague other platforms. A tutor filing a payment dispute is contesting a payment decision, not accusing the finance officer who made it. This framing matters because it changes how everyone approaches the conversation.
Evidence Standards and What Tutors Should Document
The outcome of any dispute depends heavily on the evidence available. Refonte applies a preponderance-of-evidence standard at tier one and tier two (the more likely explanation wins) and a clear-and-convincing standard at tier three for cases involving allegations of serious misconduct. This is standard practice in professional dispute resolution and it means documentation quality matters enormously.
Here is what tutors should be documenting from day one, regardless of whether they anticipate a dispute:
- Session logs. Date, time, duration, learners present, and a one-line summary of what was covered. The Refonte platform captures much of this automatically, but a tutor's own log is invaluable if there is ever a question about what happened in a specific session.
- Communication trails. Keep learner communications in the platform's messaging system rather than side channels like personal WhatsApp. If a learner escalates a complaint about tone or content, the messaging record is your best defense.
- Deliverable artifacts. Slide decks, code repositories, feedback documents, and graded assignments should be timestamped and version-controlled. When a learner disputes a grade, the ability to produce the rubric applied at the time and the artifact reviewed is often decisive.
- Contractual notices. Every amendment, extension, or clarification of your contract should be in writing. Verbal assurances from anyone at Refonte, including program managers, are not enforceable if not written. Tutors on the interim tutor contract should be especially careful here because interim engagements have shorter feedback loops.
- Performance data. Screenshot or export your quality metrics dashboard regularly. If a dispute involves your standing on the platform, you want to be able to show your metrics as of the date of the disputed event, not as of today.
Learners face a symmetric documentation burden. Complaints without specifics ("the tutor was rude") are much weaker than complaints with anchors ("in the session on 14 March, at approximately 19:15, the tutor said X, as documented in the session recording"). Session recordings are retained for 90 days as a matter of platform policy, which gives a working window for most disputes.
A note on privacy: session recordings and messaging logs are used strictly for dispute resolution, quality assurance, and legal compliance. They are not shared with other tutors, other learners, or external parties without explicit consent or legal requirement. This is codified in the data-handling clauses of every tutor contract.
The Payment Dispute Path
Payment disputes are the single most common category, so they deserve dedicated treatment. In 2025, payment questions accounted for roughly 41 percent of all tier-one dispute filings, and most were resolved within three business days.
The payment cycle at Refonte runs on a defined calendar. Sessions delivered in month N are invoiced by the fifth of month N+1 and paid by the last business day of month N+1. A payment is considered overdue only after that last business day. Filing a payment dispute before the payment window closes results in the ticket being held rather than actioned, because there is nothing to dispute yet.
When a payment is genuinely overdue, the tutor files a payment inquiry ticket with the invoice number, the disputed amount, and a brief description. The finance team responds within two business days with one of three outcomes: confirmation that payment is in process (with expected date), identification of a data issue that requires tutor correction (such as a mismatched bank identifier or a missing tax form), or acknowledgment of a Refonte-side error with a corrected timeline.
Disputes over amounts (not timing) are more complex. The most common scenarios are: tutor claims a session was delivered but the platform shows it as cancelled, tutor claims a bonus or milestone payment that Refonte disputes, or a chargeback or clawback was applied for a cancellation the tutor argues was learner-caused. Each of these gets a structured review with reference to the platform's session records, the tutor's own logs, and the applicable contract clause. If the tutor's records and the platform's records disagree, the platform record is presumed correct absent contrary evidence, but that presumption is rebuttable.
One specific protection worth calling out: no payment can be withheld pending resolution of a non-payment dispute. If a tutor is in a quality dispute or a conduct dispute, the payments due for uncontested sessions continue on the normal schedule. Withholding payment as leverage in an unrelated dispute is explicitly prohibited by internal policy, and any exception requires sign-off from a program director.
For tutors working across multiple programs, including the AI Engineering program, each program's payments are ring-fenced in the dispute system. A dispute in one program does not freeze payments from another. This modularity matters because tutors who deliver across two or three programs simultaneously would otherwise face cascading risk from a single issue.
The Quality and Performance Dispute Path
Quality disputes are the most emotionally charged category because they touch on professional identity. A tutor who receives a negative quality review is not just disputing a number, they are defending their teaching. Refonte designs this path with that emotional weight in mind.
Every tutor engagement is measured against the metrics defined in tutor quality metrics: learner satisfaction scores, completion rates, technical accuracy of feedback, session attendance, and response times on asynchronous channels. Aggregate scores feed into a tutor rating that affects assignment priority, renewal decisions, and in some cases pay tier.
When a tutor disputes a quality score, the review process has three specific safeguards. First, individual outlier reviews (a single very low score in a stream of high ones) are flagged automatically and can be excluded from aggregate calculations pending review. This prevents one difficult learner from tanking an otherwise strong record. Second, quality reviews are triangulated: no consequential decision is made on a single data source. A pattern of low learner scores must be corroborated by peer review or program-manager observation before it triggers a performance-improvement plan. Third, tutors receive the full breakdown of any negative aggregate score, including the underlying reviews (anonymised) and the metrics that drove the aggregate.
If a tutor believes a specific review is factually inaccurate (the learner claims a session was missed that was in fact delivered) the review can be contested with evidence. If it is a subjective disagreement (the learner found the pace too fast, the tutor believes the pace was appropriate) the review stands but is contextualised in the tutor's file. Subjective feedback is data, not verdict.
A performance-improvement plan (PIP) is the formal intervention when quality issues cross a threshold. A PIP includes specific behavioural targets, a defined timeline (usually 60 to 90 days), and a designated program-manager coach. The PIP is not a dispute in itself, but PIP outcomes can be disputed. Termination following a PIP is only valid if the PIP's targets and process were followed correctly. If a tutor believes a PIP was procedurally defective (targets moved mid-plan, coach unavailable, evidence not shared) that becomes a tier-two dispute.
Some tutors ask why we do not simply let quality disputes go to external arbitration immediately. The answer is that quality is contextual, and external arbitrators lack the domain knowledge to evaluate whether a specific piece of technical feedback in a Kubernetes lab or a PyTorch debugging session was actually correct. Our internal panels include senior practitioners who can evaluate the substance, not just the process.
Learner Complaints Against Tutors
Learner complaints are the mirror image of tutor disputes and follow a parallel but not identical process. The asymmetry reflects the reality that learners are typically less familiar with the platform's contractual mechanics and often need more support to articulate a complaint clearly.
When a learner files a complaint, a program coordinator conducts an intake interview within three business days. The purpose is to understand what happened, what the learner wants as an outcome, and whether the issue is really about the tutor or about something else (program design, technical infrastructure, personal circumstances). Roughly a third of initial learner complaints resolve at intake without ever being formally routed to the tutor, because the actual issue turns out to be elsewhere.
Complaints that do proceed are shared with the tutor within five business days of intake, with the learner's identity revealed unless there is a specific safety concern. Anonymous complaints are not actionable except where they corroborate an existing pattern or involve safety allegations. This is deliberate: professional accountability requires that the accused knows who is accusing them, in almost all cases.
The tutor has ten business days to respond in writing. The response can include evidence, context, and (if appropriate) a proposed remedy. Common remedies at this stage include a make-up session, a written clarification, an adjusted assessment, or a partial refund credited by Refonte (not by the tutor personally, unless the tutor volunteers). Most cases resolve here.
If the tutor's response does not satisfy the learner, or if Refonte's own review of the response identifies concerns, the case escalates to tier two mediation as described above. At tier two, both parties submit written statements, the panel reviews all evidence, and a recommendation issues. Recommendations in learner-versus-tutor cases fall into predictable categories: dismissed as unsubstantiated, sustained with corrective action for the tutor, sustained with financial remedy for the learner, or mixed (partial validity on both sides).
One specific policy worth noting: chronic-complaint learners (learners who file multiple complaints across multiple tutors within a short window) get their own review. A learner who has filed five complaints against four different tutors in one program has a pattern that is unlikely to be entirely explained by tutor failures. This does not invalidate any single complaint, but it changes how the aggregate is weighted, and it may trigger a conversation with the learner about fit with the program.
Content Ownership and IP Disputes
IP disputes are less common but higher stakes when they occur. The default position, spelled out in the contract, is that curriculum and materials developed specifically for Refonte programs are owned by Refonte, while a tutor's underlying methods, generic teaching approaches, and pre-existing content remain their own. The line between these categories is where disputes usually arise.
A typical scenario: a tutor develops an elaborate case study for a Refonte AI cohort, drawing on a general framework they have used in prior consulting work. Six months later, they want to publish an adaptation of that case study in a personal blog or a book. Is that permitted? The answer depends on how much of the specific Refonte-context material remains, whether student work or feedback is referenced, and whether the tutor's contract included specific derivative-works clauses.
The IP dispute path starts with a written notice from either party asserting a claim. The claim must specify the material at issue, the ownership theory, and the relief sought. Refonte's legal review responds within 15 business days with a preliminary position. If the parties disagree with the preliminary position, the case goes directly to tier two mediation, skipping tier one (because tier one informal resolution is not well suited to IP questions that turn on contract interpretation).
Mediation of IP disputes includes a specialist reviewer with intellectual property experience. Outcomes range from confirmation of original ownership, negotiated licensing terms, joint publication with attribution, to (rarely) financial settlement. The mediation panel cannot rewrite contract clauses, but it can interpret them and can recommend forward-looking adjustments to clarify ambiguity.
One pattern worth flagging: tutors who use platforms like GitHub, Notion, or personal websites to publish teaching materials should be careful about the timing of publication. Material created during a Refonte engagement, using Refonte learner feedback or examples, is presumptively Refonte-owned even if published on a personal channel. This does not mean tutors cannot maintain a public teaching portfolio (many do, and Refonte encourages it) but it does mean the boundary between personal and platform work needs to be maintained consciously.
The good news is that in practice, most IP concerns can be resolved with a short conversation and a written note to file. Formal disputes are rare because the incentives are aligned: Refonte benefits from tutors building public reputations, and tutors benefit from Refonte's platform reach. The dispute mechanism exists to handle the edge cases where interests genuinely diverge.
Termination Disputes
Contract termination is the highest-stakes dispute category because it typically ends the working relationship. Both sides have strong interests: the tutor in remaining engaged and preserving reputation, Refonte in maintaining quality and platform standards.
Refonte's contracts distinguish termination for cause (specific breach) from termination for convenience (no reason required, subject to notice period). A termination for convenience is not usually disputable on substance, but the notice period, final payment calculation, and handling of in-flight cohorts are all disputable. If Refonte terminates for convenience with 30 days notice but the tutor argues they had a committed cohort running through 60 days, the dispute is about the cohort commitment and the compensation for it, not about the termination itself.
Termination for cause is different. Cause requires a documented basis: sustained quality failure after a PIP, material breach of the code of conduct, misrepresentation on the tutor application (which is why the independent contractor status piece and background-check processes matter), or specific enumerated breaches such as unauthorized recording of sessions. A cause termination requires evidence, and that evidence is subject to review through the standard dispute mechanism.
A tutor disputing a cause termination has a right to a full tier-two review before the termination becomes final on their public record. During the review period, the tutor is typically suspended from active assignments but remains under contract for pay purposes if the alleged cause does not involve safety or serious misconduct. This protects the tutor's income during what is often a stressful multi-week process.
Reinstatement is possible if a termination dispute is decided in the tutor's favor. Reinstatement includes back pay for the suspension period, a clean record on the internal quality file, and a documented resolution letter that the tutor can share with future counterparties if needed. Full reinstatement is uncommon (most termination disputes either affirm the termination or negotiate a mutual separation) but it happens, and the mechanism exists to make it possible.
Tutors sometimes ask what happens to the reputational and platform-standing consequences of a disputed termination while the dispute is pending. The policy is that internal-facing systems reflect the pending status ("under review"), external-facing communications do not disclose the dispute, and no public statement is made about the tutor's status until the process concludes. This asymmetric protection reflects that reputation, once damaged, is hard to repair.
Timelines, Escalation, and What Happens When Deadlines Slip
Every tier has a defined timeline: seven business days for tier one, 21 for tier two, 45 for tier three. What happens when Refonte itself misses a deadline? This is a fair question and the answer matters.
Missed deadlines by Refonte trigger automatic escalation. If a tier-one coordinator does not close a case within seven business days, the case escalates to a program manager and the seven-day clock restarts under new ownership. If the program manager also misses the deadline, the case escalates to tier two automatically, which changes both the timeline and the panel composition. This ensures that a case cannot languish because a single individual is overloaded or unresponsive.
Missed deadlines by the tutor or learner have different consequences. If a tutor is asked to respond to a learner complaint within ten business days and fails to respond, the case proceeds with only the learner's evidence. This is not a default judgment against the tutor, but it does mean the tutor's position is not represented. Extensions are available on request for legitimate reasons (illness, family emergency, technical issues) but must be requested before the deadline, not after.
Status updates are provided to both parties at defined intervals: weekly during tier one, bi-weekly during tier two, and weekly during tier three. Silence is not part of the process. A party who has not received an update within the expected window can and should ping the case coordinator, and if that does not produce a response within two business days, the case can be escalated on procedural grounds.
Procedural escalation is separate from substantive escalation. A tutor who believes the process is being handled fairly but disagrees with the likely outcome does not escalate procedurally, they present better evidence or arguments. A tutor who believes the process itself is broken (missed deadlines, biased panel composition, refusal to share evidence) escalates procedurally, which triggers an independent process review by a party not involved in the substantive case.
The distinction between procedural and substantive fairness matters because tutors who confuse the two often waste energy. Losing a case does not mean the process was unfair. But a process that skips steps, misses deadlines, or refuses to engage with evidence is procedurally defective regardless of the substantive outcome, and Refonte's own internal accountability depends on treating those two categories separately.
Confidentiality, Retaliation Protection, and What Stays Private
Confidentiality of dispute proceedings is a promise Refonte makes to both parties, and one worth explaining in detail because trust in the mechanism depends on it.
Dispute files are accessible only to: the parties directly involved, the coordinators and panel members assigned to the case, Refonte's legal and compliance teams, and (for aggregate reporting) senior program leadership. The identity of a complainant is shared with the accused party in nearly all cases because procedural fairness requires it, but the details of a dispute are not shared with other tutors, other learners, or external parties without explicit consent or legal requirement.
Retaliation is explicitly prohibited. A tutor who files a payment dispute cannot have their assignment quality changed as a result. A learner who files a complaint against one tutor cannot be reassigned to a worse-fit tutor as punishment. Retaliation allegations are treated as their own category of dispute and are investigated with particular rigor because the credibility of the entire mechanism depends on it.
One nuance: retaliation prohibition does not mean status quo forever. If a learner files a complaint against a tutor and the parties genuinely cannot work together anymore regardless of who was right, reassignment is often the right outcome for both. That is not retaliation, that is practical resolution. The line is drawn by intent and by whether the change is a punishment or a reasonable adjustment.
Public statements about disputes are not made by Refonte. If a tutor or learner chooses to discuss their case publicly (on social media, in reviews, in press) that is their right, but Refonte's own communication remains neutral or silent unless there is a specific legal or safety reason to speak. This asymmetry sometimes frustrates parties who feel wronged, because they want Refonte to publicly vindicate them, but the policy protects everyone in aggregate.
Records of concluded disputes are retained for seven years, consistent with French commercial-law norms applicable to Refonte's parent entity. After that period, records are archived in anonymised form for pattern analysis. Individual identifiable data is deleted according to the platform's data-retention policy.
What This Looks Like Compared to Freelance Marketplaces
Tutors who have worked on generic freelance platforms sometimes ask how Refonte's dispute mechanism differs. The short answer is that generic platforms optimise for volume and speed, while Refonte optimises for outcome quality and long-term relationships. Both approaches have tradeoffs.
Generic platforms typically resolve disputes through algorithmic or rapid-review processes, favoring the party with more platform history or higher ratings, and often defaulting to refunds because refunds are the lowest-friction outcome. This works at volume but produces inconsistent outcomes in complex cases and can leave tutors feeling that ratings drive judgments rather than facts. The dynamics are covered in more depth in analyses of how professional platforms differ from marketplaces, and the tradeoffs are real.
Refonte's mechanism is slower and more procedurally involved. A tier-two case that takes three weeks at Refonte might close in three days on a marketplace. The tradeoff is that Refonte cases produce written decisions with reasoning, applying stated criteria to specific evidence, which both parties can point to. If similar cases in the future produce different outcomes, that inconsistency is visible and can be addressed. If cases produce similar outcomes, the mechanism is generating de facto precedent that helps tutors and learners predict how future disputes will be handled.
The deeper structural difference is that Refonte tutors are contracted contributors to designed programs, not freely floating gig workers. When a dispute arises, the context includes the program design, the cohort structure, the specific learning outcomes committed to, and the tutor's role within that ecosystem. This context is essential to evaluating the substance of most disputes and is largely absent on generic platforms.
None of this is to say marketplace models are wrong for every use case. They are efficient for one-off, low-stakes engagements. But for the programs Refonte runs, where a tutor might work with a cohort for six months and where outcomes matter for learners' careers, the marketplace model does not produce the accountability or quality the situation demands. The dispute mechanism reflects that difference.
Continuous Improvement: How the Mechanism Itself Evolves
A dispute-resolution system is only credible if it improves over time. Refonte tracks metrics on the mechanism itself and publishes annual internal reports that shape the following year's process.
Key metrics include: total dispute volume by category, resolution rate at each tier, average time to resolution, party-satisfaction scores (both winners and losers rate the fairness of the process, not just the outcome), and post-resolution outcomes (do parties who go through disputes continue their engagements with Refonte or churn out?). These metrics do not answer whether individual outcomes were correct, but they do reveal whether the system as a whole is working.
The 2025 report identified three areas for 2026 improvement, all of which are now live. First, tier-one coordinators received additional training in de-escalation, because a portion of tier-one cases were escalating to tier two more from communication friction than substantive disagreement. Second, the tier-two panel roster was expanded to reduce reappearance of the same reviewers, which had produced perception-of-bias concerns even where actual bias was not present. Third, the evidence-submission portal was rebuilt to allow structured uploads with metadata, reducing the volume of "I forgot to include the recording" moments that extend timelines.
Tutors and learners are invited to submit feedback on the mechanism itself, separately from feedback on individual case outcomes. This distinction matters because someone who lost a case might legitimately criticise the process, and someone who won a case might legitimately identify improvements. Aggregating this feedback across hundreds of cases per year gives us the signal to improve.
One change under active consideration for late 2026: opt-in external arbitration for tier-three cases involving significant financial claims. This would allow parties who want an outside reviewer to select one at their own expense, with Refonte agreeing in advance to abide by the outcome. The tradeoffs are cost, timeline, and loss of domain-specific expertise, but the credibility benefits may justify it for the highest-stakes cases.
For tutors considering joining Refonte, whether through the AI Engineering program or one of our other tracks, the dispute mechanism is one of the things worth reading carefully before signing. It is designed to protect both sides, and understanding it up front means you never encounter it as a surprise.
Closing Thoughts: Trust as Infrastructure
Dispute resolution is infrastructure. Like other infrastructure, it is most valuable when it is quietly reliable, and most visible when something breaks. The Refonte tutor community in 2026 includes practitioners who have worked with the platform for multiple years, some of whom have used the dispute mechanism and returned to active engagement afterwards. That pattern (dispute, resolution, continued relationship) is the best evidence the system works.
Refonte Learning treats the tutor relationship as a long-term partnership, not a transaction. The dispute mechanism is a tangible expression of that: it exists to preserve relationships through disagreements, not just to terminate them. Tutors who understand the mechanism, document their work, and engage the process in good faith when needed have a track record of positive outcomes even in cases they lose, because the process itself is designed to be fair even when the outcome is not what one party hoped.
If you are considering a tutor role at Refonte Learning, the resources above (contract overview, quality metrics, IP rules, contractor status) are all worth reading together. The dispute mechanism ties them together operationally. And if you are ready to explore an active teaching engagement, our AI Engineering program is one of several programs currently accepting tutor applications for 2026 cohorts.