# Study Guide: Case Study: From PPO Analysis to Verified Reimbursement Increase
## How To Use This Guide
Use this as pre-recording prep for Joey, not article copy.
The recording goal is to capture how Joey would tell a proof story without
turning it into a testimonial, a sales claim, or a guaranteed-result promise.
The final article should come from Joey-approved case facts, anonymized details,
verified numbers, and spoken explanation after recording.
This case study should teach one standard:
- A PPO reimbursement increase is not proven when a carrier sends a new fee
schedule. It is proven when actual EOBs show the expected allowed amounts on
real claims.
During recording, keep pulling Joey back to these practical questions:
- What was the owner's original frustration?
- What did the practice think was wrong?
- What data did Unlock request first?
- What did the analysis show that the owner could not see from the fee schedule
alone?
- What recommendation or decision came out of the analysis?
- What had to happen operationally before claims could pay correctly?
- What EOB evidence proved the result?
- What result can be safely claimed without overpromising?
- What must stay anonymous, generalized, or source-needed?
- What should another owner copy from the process, not from the outcome?
Do not draft final article prose from this guide. Use it to prompt Joey's case
facts, proof standards, caveats, examples, and service boundaries.
## Article Thesis
The case study should show the path from PPO concern to verified reimbursement,
not just the moment a new fee schedule arrived.
The article should move the reader away from:
- "The carrier sent better fees, so the practice got a raise."
- "A signed fee schedule is the finish line."
- "A headline percent increase proves the business result."
- "One impressive CDT code tells the whole story."
- "Negotiation alone caused higher collections."
- "Every practice can expect the same outcome."
- "A testimonial quote is enough proof."
- "Implementation is just admin cleanup after the win."
And toward the better operating standard:
- Document the starting condition.
- Analyze the practice's own top CDT codes, payer mix, participation paths, fee
schedules, contracts, effective dates, and EOBs.
- Define the recommendation and decision.
- Track implementation through effective dates, fee loading, provider records,
claim routing, and first affected claims.
- Compare expected allowed amounts with actual EOB allowed amounts.
- Resolve discrepancies before calling the increase verified.
- Report the result using a fair metric, ideally weighted by procedure mix.
Owner-facing rule to test with Joey:
- The increase only matters if it reaches collections.
Better final-article claim shape:
- Avoid "we increased reimbursement by X" until Joey approves real case facts,
dates, weighted mix, and EOB proof.
- Prefer "this case shows how Unlock verifies whether an intended reimbursement
increase actually appears on claims."
## What To Understand Before Recording
The reader is an established private-practice owner. They are probably busy,
financially frustrated, and skeptical of broad promises about higher PPO fees.
They may already have fee schedules, carrier emails, or vendor reports, but they
do not know whether those documents translated into correct payment.
Likely reader state:
- The practice looks busy, but profit or owner compensation feels squeezed.
- The owner suspects PPO write-offs, stale fees, network routing, or payer mix
are part of the problem.
- The office manager may know which claims "feel wrong," but the owner needs a
documented proof trail.
- The practice may have received a negotiated fee schedule but has not verified
it against EOBs.
- The owner may not know which direct, shared, leased, affiliate, or TPA path
controlled the allowed amount.
- The practice may have provider, location, TIN, NPI, effective-date, or PMS
setup issues affecting claims.
- The owner wants a concrete story, but not one that exposes client identity or
confidential fee schedules.
Terms Joey should be ready to define simply:
- PPO analysis
- Case study
- Anonymized case
- Composite case
- Starting condition
- Top CDT code mix
- Weighted reimbursement
- Office fee
- Contracted fee schedule
- Allowed amount
- Write-off
- Direct contract
- Shared network
- Leased network
- TPA
- Participation map
- Effective date
- Fee schedule loading
- Provider record
- Claim routing
- EOB verification
- Expected allowed amount
- Actual EOB allowed amount
- Discrepancy
- Corrected payment
- Verified reimbursement increase
- Annualized impact
Important distinction:
- A signed fee schedule is a document.
- A loaded fee schedule is a system state.
- An EOB-verified fee schedule is proof that actual claims are paying under the
expected terms.
The most important teaching move:
- Make the proof trail the hero. The case is not "look how big the result was."
The case is "look how the result was proven."
## Research Briefing
Study sources reviewed for this guide:
- `content/core/core-036-case-study-ppo-analysis-verified-reimbursement-increase.md`
- `content/prompts/core-036-case-study-ppo-analysis-verified-reimbursement-increase.md`
- `content/research-packs/core-036-case-study-ppo-analysis-verified-reimbursement-increase.md`
- `content/seo-packs/core-036-case-study-ppo-analysis-verified-reimbursement-increase-seo-pack.md`
- `content/core/core-034-verify-negotiated-ppo-fees-on-eobs.md`
- `content/core/core-035-annual-dental-ppo-review-checklist.md`
- `research/raw/topical-authority-map.md`
- `research/raw/competitor-media-audit.md`
- `research/raw/deep-research-report-11.md`
- `research/raw/buyer-intent-keywords.md`
- `research/raw/keyword-gap-analysis.md`
- `research/raw/citation-magnet-questions.md`
- `research/raw/chatgpt-user-profile.md`
Strong findings to carry into recording:
- Core-036 belongs in Wave 6 proof content. It should demonstrate execution,
not repeat generic negotiation messaging.
- The topical authority map says case studies need documented starting
conditions, decisions, implementation, and verified results rather than a
quote alone.
- The research pack gives the central angle: a reimbursement increase is proven
on EOBs, not by receipt of a new fee schedule.
- The competitor media audit identifies Unlock's strongest open position as
participation execution. Competitors already talk about negotiation; Unlock
should show whether the strategy reached actual claims.
- A strong positioning line from the media audit: "A signed fee schedule is only
a promise. The EOB shows whether the strategy was implemented."
- The SEO pack says this should stay a single proof page until Unlock has
approved anonymized cases with unique data.
- The SEO pack identifies the direct answer target: what proves a dental PPO
reimbursement increase actually happened?
- ADA-related deep research supports EOB interpretation, network leasing,
contract negotiation, claim adjudication, eligibility, and checking EOBs
after changes as relevant source areas.
- The ChatGPT user profile says the owner is proof-oriented and distrusts broad
claims like "higher reimbursement." That makes transparent proof standards
more persuasive than salesy outcome language.
- Buyer-intent research shows owners ask who can audit fee schedules, negotiate
better rates, increase reimbursements, review PPO offers, and show annual
revenue impact. This case should answer those questions with process proof.
- Keyword gap research points to opportunities around dental PPO reimbursement
rates, fee schedule analysis, write-off calculators, contract review, and
low-fee diagnostics. This case can connect to those assets without becoming a
generic guide.
- Citation-magnet research says answers about expected negotiation results are
weak because the industry mixes percent fee increases, code-level increases,
annual collections uplift, and production growth as if they were the same.
Workflow Joey should be prepared to explain:
1. Identify the practice's starting concern: low reimbursement, write-offs,
unclear network paths, stale fees, or unverified negotiated fees.
2. Gather the evidence: fee schedules, top CDT codes, payer mix, participation
map, contracts, effective dates, provider records, EOBs, and PMS setup.
3. Establish the baseline: current allowed amounts and current actual EOB
payments for the selected code basket.
4. Analyze the root issue: underpriced codes, network layering, stale fee
schedules, routing problems, effective-date confusion, provider mismatch, or
payer processing.
5. Recommend the action: renegotiate, clean up participation, correct fee
loading, verify an already negotiated increase, or escalate discrepancies.
6. Implement the change: confirm effective date, load updated fees, check
provider/location records, submit claims correctly, and watch first affected
claims.
7. Verify the result: compare expected allowed amounts with actual EOB allowed
amounts and document discrepancies.
8. Resolve mismatches: contact payer, confirm correction, and re-check the next
EOB.
9. Report the outcome with a fair metric: weighted reimbursement change,
corrected allowed amount, reduced write-off, annualized impact, or narrower
verified proof point.
10. Explain what another owner should copy: the evidence standard and workflow,
not the exact result.
Case fact table to build during or after recording:
| Field | Why it matters | Study note |
|---|---|---|
| Case type | Defines whether this is real, anonymized, or composite. | Needs Joey approval and permission boundaries. |
| Practice descriptor | Gives enough context for learning. | Avoid identifying geography, carrier mix, size, dates, or numbers if sensitive. |
| Starting problem | Anchors the case in the owner's real frustration. | Use Joey's words where possible. |
| Documents reviewed | Shows this was analysis, not guesswork. | Fee schedules, EOBs, contracts, reports, payer correspondence. |
| Baseline period | Prevents cherry-picked comparison. | Source-needed until dates are approved. |
| Top CDT code basket | Makes the result practice-specific. | Weighted mix preferred. |
| Participation path | Explains which contract/network could control payment. | Direct/shared/leased/TPA details may need anonymization. |
| Recommendation | Shows the owner decision. | Renegotiate, clean up, verify, or follow up. |
| Effective date | Separates paper approval from claim impact. | Needs exact or anonymized date. |
| First affected claim date | Shows when proof could begin. | Do not imply immediate payment. |
| Expected allowed amount | Defines what the EOB should show. | Avoid publishing confidential fee details without approval. |
| Actual EOB allowed amount | Provides proof. | Must be redacted or summarized. |
| Discrepancy | Shows real execution risk. | Useful if Joey has a safe example. |
| Resolution | Shows follow-through. | Payer correction claims need evidence. |
| Result metric | Defines success. | Weighted reimbursement, write-off reduction, corrected payment, or annualized impact. |
| What not to claim | Prevents overstatement. | Especially if one code or one claim looks impressive. |
Proof evidence to request from Joey:
- Redacted before/after fee schedule details or summarized top-code table.
- Procedure volume or weighted code mix.
- Analysis date.
- Carrier response date.
- Effective date.
- Fee schedule load date.
- First affected claim date.
- First verified EOB date.
- Discrepancy resolution date, if any.
- Redacted EOB line or EOB-style worksheet.
- Written permission or approved anonymization rules.
## Competitive And SERP Briefing
Primary answer target:
- "What proves a dental PPO reimbursement increase actually happened?"
Related search and AI-answer targets:
- how to verify a dental PPO fee increase
- dental PPO reimbursement increase verification
- signed fee schedule vs EOB verified reimbursement
- negotiated PPO fees not paid correctly
- dental EOB audit after PPO negotiation
- how to prove PPO fee negotiation worked
- dental PPO fee schedule verification
- why did my new PPO fees not show up on claims
- PPO analysis case study dental practice
- dental PPO reimbursement case study
SERP differentiation:
- Do not write a generic testimonial page.
- Do not lead with "we negotiate better PPO fees." Competitors already occupy
that message.
- Do not make this a thin success story with an unsupported headline result.
- Do not publish a result claim without tying it to baseline, date range, code
mix, expected allowed amount, actual EOB allowance, and verification method.
- Do make this the clearest proof-standard article in the cluster.
- Do show how analysis, implementation, and EOB verification connect.
- Do link the case to the EOB verification guide, annual PPO review checklist,
weighted fee schedule comparison, profitability analysis, and participation
map.
Competitive/media signal:
- PPO Advisors, PPO Profits, and Unitas are visible through podcasts, partner
placements, and office-manager communities.
- Competitor themes include fee negotiation, direct contracts, leased networks,
participation, optimization, and revenue-cycle consequences.
- Unlock's opportunity is the operational gap after the negotiation
conversation: did the correct contract and fee schedule actually control the
claim?
- The best media angle for this case is "the 90 days after PPO renegotiation,"
not another broad "fees are too low" story.
Citation-magnet opportunity:
- Create a reusable proof checklist for reimbursement increases.
- Define verified reimbursement increase in a direct answer block.
- Publish a safe EOB verification worksheet.
- Explain why weighted procedure mix is more honest than one impressive code.
- Show the difference between signed, loaded, and EOB-verified fee schedules.
- Include an anonymization note that models responsible case-study publishing.
Article blocks likely needed after Joey voice capture:
- Direct answer: what counts as a verified reimbursement increase.
- Case anonymization note.
- Starting problem.
- Documents reviewed.
- Analysis findings.
- Recommendation and owner decision.
- Implementation timeline.
- EOB verification process.
- Before/after proof table.
- Result metric and what it does not prove.
- Owner takeaway.
- What another practice should copy.
- Claims and caveats box.
- Links to EOB verification and annual review assets.
Positioning lines to test with Joey:
- "The fee increase is not real until the EOB proves it."
- "A signed fee schedule is only a promise. A paid claim shows whether the
strategy made it into the system."
- "The win is not the carrier email. The win is the correct allowed amount on
the claim."
- "Do not celebrate the new schedule until the first claims prove it."
- "This is a proof story, not a promise that every practice gets the same
result."
Use with caution:
- Any percent increase.
- Any dollar increase.
- Any annualized impact.
- Any carrier or network name.
- Any before/after fee schedule table.
- Any claim that negotiation alone caused the outcome.
- Any implication that Unlock can guarantee the same result.
## Examples And Scenarios To Study
Use these as recording prompts. They are not final article examples unless Joey
validates or replaces them with approved case facts.
### Scenario 1: The New Fee Schedule Arrived But Claims Still Paid Old Fees
Study setup:
The practice receives a better fee schedule and assumes the increase is done.
First affected EOBs still show the old allowed amounts.
Questions for Joey:
- How does the office know which claims should have been affected?
- Which dates matter most?
- What evidence should be sent back to the payer?
- Was the issue fee loading, provider record, location, claim date, network
path, or payer processing?
- How did the practice confirm the correction?
Study answer:
This is the cleanest proof-standard story. The signed schedule started the
verification work; the EOB revealed whether implementation was finished.
### Scenario 2: One CDT Code Improved But The Weighted Result Was Smaller
Study setup:
One high-value code increased meaningfully, but the practice's actual procedure
mix made the weighted reimbursement improvement more modest.
Questions for Joey:
- Which codes belong in the top-code basket?
- How does Joey avoid cherry-picking one dramatic procedure?
- What result metric would be honest?
- Should the final article show percent increase, dollar change, or an
illustrative weighted table?
Study answer:
The case should teach fair measurement. A headline code can explain the issue,
but weighted mix should carry the result.
### Scenario 3: The Practice Had A Network Routing Problem
Study setup:
The practice believed a direct or negotiated path controlled payment, but EOBs
suggested a shared, leased, affiliate, or TPA path was setting the allowed
amount.
Questions for Joey:
- What EOB clues suggest the wrong path?
- What documents help trace the participation route?
- What does Unlock compare before contacting the payer?
- What should stay carrier-anonymous in the final article?
Study answer:
This scenario supports Unlock's participation-execution positioning. The
analysis has to identify the path behind the payment, not just compare two fee
schedules.
### Scenario 4: The PMS Fee Schedule Was Wrong
Study setup:
The payer may be paying correctly, but the practice-management software uses
stale or incorrect fee tables for estimates, posting, or internal reports.
Questions for Joey:
- How does the team separate payer payment error from PMS setup error?
- What should the office manager compare: PMS fee, expected allowed amount, or
EOB allowance?
- What damage can wrong internal fee schedules create even if claims pay
correctly?
Study answer:
Correct reimbursement proof should distinguish payer adjudication from internal
software setup. Both matter, but they are not the same problem.
### Scenario 5: Provider-Level Mismatch
Study setup:
One provider's claims pay correctly while another provider's claims pay under
the wrong fee or network path.
Questions for Joey:
- What provider, NPI, TIN, location, or credentialing details would be checked?
- How many claims need review before escalating?
- What does the practice document to prove the mismatch?
Study answer:
The case can show why verification cannot stop at "the plan is active." Payment
can vary by provider record or setup details.
### Scenario 6: Effective Date Confusion
Study setup:
The carrier response names an effective date, but claims around that date do
not process as expected.
Questions for Joey:
- Which date controls: service date, claim submission date, received date,
processing date, or system load date?
- What does Joey avoid saying without contract or payer confirmation?
- How does the office track the first claim that should prove the change?
Study answer:
This scenario should stay caveated. It is useful for showing why dates must be
tracked, but payer-specific date logic needs source review.
### Scenario 7: The Case Had No Huge Result, But It Prevented A Bad Assumption
Study setup:
The analysis showed that a claimed or expected increase was narrower than the
practice thought. Unlock helped the owner avoid overstating the financial
impact.
Questions for Joey:
- Would this still be a useful case study?
- How do you explain value when the work prevents a bad decision rather than
creates a dramatic increase?
- What did the owner learn?
Study answer:
This may be a stronger trust-building story than a big number. It proves
Unlock's standard is evidence, not hype.
### Scenario 8: Office Manager Verification Workflow
Study setup:
After the new fee schedule goes live, the office manager reviews the first 10
affected claims against expected allowed amounts.
Questions for Joey:
- Which fields should the worksheet include?
- How many claims are enough for early confidence?
- Which mismatches require payer follow-up?
- What can be delegated to the office manager, and what needs owner or Unlock
review?
Study answer:
This scenario can become a derivative checklist and service bridge. It also
keeps the case practical for the team member who implements the change.
Study table: proof stages
| Stage | What the owner may believe | What Joey should clarify |
|---|---|---|
| Analysis complete | "We know the problem." | Analysis identifies the likely path, but action and verification still matter. |
| Carrier response received | "The increase is approved." | Approval is not the same as correct claim payment. |
| Fee schedule signed | "The result is locked in." | Contract terms, effective date, provider setup, and system loading still matter. |
| Fees loaded in PMS | "Claims will pay correctly." | PMS loading can help estimates, but payer adjudication must still be checked. |
| First claim submitted | "Now we will know." | The EOB, not the submitted claim, proves the allowed amount. |
| First EOB received | "We are done." | One EOB may be enough to catch a problem, but broader verification may require more claims. |
| Corrected payment received | "The increase is verified." | Define exactly what was verified: code, provider, plan, date range, and sample. |
## Claims And Caveats
Treat these as study notes and source-needed guardrails.
Claims to avoid or qualify:
| Claim | Recording posture | Safer study note |
|---|---|---|
| "Unlock increased reimbursement by X%." | Source-needed. | Use only if tied to approved case facts, weighted mix, dates, and EOB proof. |
| "The practice collected X more per year." | Source-needed. | Annualized impact needs denominator, period, mix, and assumptions. |
| "The carrier paid incorrectly." | Qualify. | Say the EOB did not match the expected allowed amount until payer review confirms cause. |
| "Negotiation caused the result." | Qualify. | The result may come from negotiation, routing cleanup, fee loading, provider setup, or discrepancy resolution. |
| "A new fee schedule means higher collections." | Avoid. | The schedule must be implemented and verified on EOBs. |
| "One EOB proves every claim will pay correctly." | Avoid. | One EOB can confirm one claim; broader confidence needs a defined sample. |
| "Every practice can get similar results." | Avoid. | Outcomes depend on starting fees, contracts, payer behavior, market, code mix, and implementation. |
| "Direct contracts always override shared networks." | Avoid. | Contract language, carrier setup, provider/location records, and payer implementation can vary. |
| "Payers must correct retroactively." | Source-needed. | Retroactivity and correction rules depend on payer, contract, dates, and law. |
| "Office managers can verify this without help." | Qualify. | They can track fields, but interpretation and escalation may need expert review. |
| "This case is real and identifiable." | Permission-needed. | Use anonymized or composite labeling unless explicit permission exists. |
Safer claims after Joey/source review:
- A reimbursement increase should be verified against actual EOBs.
- A signed fee schedule and an EOB-verified allowed amount are different proof
stages.
- A fair case study should document the starting problem, documents reviewed,
recommendation, implementation steps, verification evidence, and result
definition.
- Weighted procedure mix is usually more honest than highlighting one
impressive code.
- Practices should avoid publishing identifiable client details, actual fee
schedules, payer contracts, or unredacted EOBs.
- When EOBs do not match expected allowed amounts, the office should document
the discrepancy and follow up with the payer or responsible party.
Legal, contract, and compliance caveats:
- Do not give legal advice.
- Do not imply Unlock replaces attorney review for contract language,
termination, state law, ERISA, noncovered services, balance billing, or
dispute rights.
- Do not publish actual client fee schedules, payer contracts, screenshots, or
EOBs without approval and redaction.
- Do not encourage dentists to exchange fee schedules, reimbursement amounts,
contract terms, or negotiation positions with peers.
- Do not name a carrier, network, practice, city, provider, or date if it could
identify the client or expose confidential terms.
- Do not promise a payer will honor a disputed fee schedule or correct prior
claims.
- Do not make carrier-specific claims without current source review.
Operational caveats:
- The wrong fee may come from payer adjudication, network routing, provider
setup, location setup, effective-date confusion, stale PMS fee schedules, or
claim-processing rules.
- The practice's PMS may be wrong even if the payer is paying correctly.
- The payer may be paying according to a contract path the practice has not
mapped.
- Provider-level or location-level setup can make claims pay differently within
the same practice.
- A result measured on one code may not represent the whole practice.
- A result measured on one short period may not represent durable collections.
- An annualized impact is an estimate unless actual collections are measured
over the full period.
- A case study should not imply that all low-fee PPO problems can be solved by
negotiation.
Public source caveats:
- Source-needed: exact ADA support language for EOB interpretation and contract
negotiation.
- Source-needed: current payer or carrier rules if any named example is used.
- Source-needed: legal/antitrust caution language before discussing fee
schedules, payer contracts, or peer comparison.
- Source-needed: any market statistic about dentists dropping networks,
insurance pressure, or overhead.
- Source-needed: any claim about typical number of EOBs needed for confidence.
- Source-needed: any state-law, ERISA, noncovered-service, prompt-pay, or
retroactive-correction statement.
## Open Research Questions
Ask Joey before final drafting:
- Is there a real case we can use, or should this be an anonymized composite?
- Do we have explicit client permission?
- What case facts must be changed or removed?
- Can carrier names, network names, states, dates, practice size, or procedure
mix be included?
- What was the owner's original frustration?
- What had the owner already tried?
- What made the practice suspect the issue was bigger than one low fee?
- What did Unlock ask the practice to send first?
- Which documents were most important: fee schedules, EOBs, contracts, payer
correspondence, PMS reports, or participation map?
- What did the analysis reveal?
- Was the issue underpriced codes, stale fee schedules, network layering,
routing, effective dates, provider records, PMS setup, or payer processing?
- What recommendation did Unlock make?
- What decision did the owner approve?
- What had to happen before the new reimbursement could appear on claims?
- What dates matter in this case?
- What was the baseline period?
- What was the first period where new reimbursement should have appeared?
- Which CDT codes should be shown, if any?
- What code mix or weighting method would be honest?
- What before/after numbers can be safely used?
- What should not be used because it would overstate the result?
- Do we have a redacted EOB or EOB-style worksheet?
- Did any EOB initially pay incorrectly?
- If there was a discrepancy, who contacted the payer and what was corrected?
- How was corrected payment confirmed?
- What result metric should this case use?
- Should the case say higher allowed amounts, reduced write-offs, corrected
routing, corrected fee schedule loading, improved weighted reimbursement, or
something narrower?
- How many EOBs does Joey want before calling a result verified?
- How does Joey explain signed versus loaded versus EOB-verified fees?
- What should the office manager track after an effective date?
- What should another practice copy from this case?
- What should another practice not assume applies to them?
- Which service boundary should the article close with?
Research still needed before publication:
- Joey-approved case facts.
- Permission or approved anonymization/composite note.
- Redacted before/after top-code table.
- Weighted procedure mix or approved fairness method.
- Redacted EOB example or EOB-style worksheet.
- Approved timeline dates or anonymized sequence.
- Source-reviewed ADA/EOB/network-leasing/contract references.
- Legal/antitrust review for fee schedule and case-study confidentiality.
- Claims review before any percentage, dollar, annual impact, or guaranteed
outcome language.
- Service-boundary approval for how Unlock describes analysis, negotiation,
implementation, payer follow-up, and EOB verification.
## Connections To Tools And Offers
This article should connect naturally to Unlock's participation execution
position. The reader should finish understanding that Unlock helps prove whether
the intended PPO strategy actually reached claims.
Relevant internal concepts and tools:
- EOB Verification Tracker.
- Effective-Date and EOB Verification Tracker.
- First 10 Claims After Fee Schedule Change checklist.
- Before/After Top-Code Comparison.
- Weighted Fee Schedule Comparison.
- PPO Participation Map.
- PPO Fee Schedule Review Prep Generator.
- PPO Plan Profitability Scorecard.
- Annual PPO Review Checklist.
- Dental PPO Implementation and Monitoring Guide.
- Dental PPO Network Change Desk.
Natural internal article connections:
- How to Verify Negotiated PPO Fees on EOBs.
- Annual Dental PPO Review Checklist.
- Weighted PPO Fee Schedule Comparison Using Procedure Volume.
- Dental PPO Profitability Analysis.
- Dental PPO Plan Profitability Scorecard.
- How to Analyze a Dental PPO Fee Schedule Using Your Top Procedure Codes.
- How to Build a Complete Dental PPO Participation Map.
- PPO Layering and Contract Stacking.
- Direct Contracts and Shared-Network Opt-Outs.
- How to Track PPO Contract and Fee Schedule Effective Dates.
- How to Load and Maintain PPO Fee Schedules in Practice Management Software.
Offer connection:
- Unlock can help an owner move from vague PPO frustration to a documented
reimbursement proof trail.
- Unlock can help gather and interpret fee schedules, EOBs, payer
correspondence, contracts, effective dates, participation paths, and top-code
data.
- Unlock can help define the difference between paper increases and verified
payment behavior.
- Unlock can help reduce burden on the office manager by turning EOB review
into a focused verification workflow.
- Unlock can help identify whether the issue is negotiation, implementation,
network routing, fee loading, provider setup, or follow-up.
- Unlock can help decide what result metric is fair before the owner makes a
business decision from the case.
Service boundary to keep clear:
- Do not promise a specific reimbursement increase.
- Do not promise every practice has negotiable upside.
- Do not promise payer correction, retroactive payment, or legal result.
- Do not describe confidential carrier or contract tactics unless approved.
- Position Unlock as PPO analysis and execution support, not a guarantee of
outcome.
Derivative asset prompts:
- Proof checklist: What verifies a dental PPO reimbursement increase?
- Worksheet: Expected allowed amount versus actual EOB allowed amount.
- Office manager checklist: First 10 claims after a new fee schedule.
- Visual: Signed fee schedule vs loaded fee schedule vs EOB-verified
reimbursement.
- Table: Before/after top-code proof with weighted mix.
- Timeline: Analysis, carrier response, effective date, first claim, first EOB,
correction, verification.
- Short video hook: "The fee increase is not real until the EOB proves it."
- Short video hook: "Your PPO increase may still be sitting on paper."
- Carousel: Problem, analysis, decision, implementation, EOB proof, result,
owner takeaway.
- Email angle: "Did your negotiated PPO fees ever reach the EOB?"
- Lead magnet: EOB Verification Worksheet for PPO Fee Changes.
## Suggested Study Path
1. Read the core article stub.
Focus on the intent: this is a proof and case-study article. The current core
file is only a voice-capture scaffold.
2. Read the recording prompt.
Notice the proof standard: signed fee schedule, loaded fee schedule, and
EOB-verified reimbursement are not the same.
3. Choose the case posture.
Before recording the story, decide whether Joey is describing a real approved
case, a de-identified case, or an anonymized composite.
4. Define the result before naming it.
Decide whether the case proves higher allowed amounts, reduced write-offs,
corrected routing, corrected fee schedule loading, improved weighted
reimbursement, or a narrower EOB-verified proof point.
5. Study the baseline.
Prepare the starting condition: owner frustration, documents reviewed, top CDT
codes, current allowed amounts, payer mix, participation path, and actual EOBs.
6. Study the analysis finding.
Be ready to explain what Unlock found that the owner could not see from the fee
schedule alone.
7. Study the implementation gap.
Prepare to talk through effective dates, fee loading, provider records, claim
routing, PMS setup, and first affected claims.
8. Study EOB verification.
Practice explaining expected allowed amount versus actual EOB allowed amount in
plain language.
9. Study discrepancy handling.
If the case includes a mismatch, explain what was documented, who followed up,
what changed, and how corrected payment was confirmed.
10. Study fair measurement.
Do not let one impressive code become the whole case. Use a weighted mix or
clearly label the result as a limited proof point.
11. Keep caveats visible.
When tempted to say a percent increase, dollar increase, annual impact, payer
behavior, carrier rule, or guaranteed result, mark it source-needed until Joey
and source review approve it.
12. Record for proof, not polish.
The final article can be shaped later. The recording needs Joey's operating
logic: what to check, what to verify, what can go wrong after the "win," and
what an owner should believe only after the EOB proves it.