Matched contacts
-
Current source-contact matches for the ME/CFS lane.
ME/CFS Referral Handoff
Use one short, crash-aware handoff before the next ME/CFS, primary-care, disability, or family follow-up conversation.
This page is a public-safe handoff aid for people with ME/CFS, caregivers, clinic schedulers, disability-prep helpers, and community moderators who need a cleaner first route before a tracked signup. Start with the public route first, then move to the tracked handoff only when someone wants their own record.
Live Proof Queue
Keep the overdue ME/CFS proof lane attached to the exact packet, handoff page, and crash-safe support route.
This referral handoff now reads the public-safe community-growth snapshot directly so ME/CFS route copy stays aligned with the current proof queue, overdue review state, and reusable partner assets. It is still a public handoff page, not a proof log.
Public mentions
-
Public route and page mentions tracked in the latest community snapshot.
Proof review
-
The next same-session import or reviewed-zero checkpoint for this route.
Activity origin
-
Keep traction claims conservative until production-attributable proof exists.
Recent targets
-
Recent public-safe organizations surfaced for this lane.
Route status
-
This lane still carries fixture/demo activity and needs first production proof.
Loading the current ME/CFS move-first and proof-focus snapshot.
Three-Minute Family Handoff
Capture the four details that make the next ME/CFS or disability-prep visit usable.
1. Stable baseline
Start with the last reliable function anchor.
Use walking, showering, reading, school, work, upright time, or chores so the next team can see what changed from a real baseline.
2. Recent load or trigger
Name the event that likely set up the crash.
Keep it to one activity burst, travel day, poor sleep stretch, infection exposure, stress spike, or support change that happened before the payback started.
3. Crash and recovery pattern
Show what the payback actually looked like.
Include the delay before symptoms hit, the worst symptom cluster, how long recovery took, and whether the person returned to baseline afterward.
4. Next question
End with the narrowest useful ask.
Examples: what follow-up to try next, what support to document, what function loss matters most now, or what the next visit should clarify.
Copy-ready family note:
Baseline before the change: [last stable function]. What changed first: [activity, travel, poor sleep, infection exposure, or stress spike]. Crash pattern: [delay before payback, worst symptoms, and recovery length]. What we need from this handoff: [the next question, support, or documentation need].
Scheduler And Referral Copy
Use conservative wording when a clinic, disability helper, or nonprofit asks for one short explanation.
Clinic scheduler note
For referral intake or pre-visit routing
We are using a patient-owned ME/CFS tracking page to keep crash timing, delayed payback, recovery burden, and daily function in one place before the visit. Public route: https://precisionmito.com/me-cfs-tracking
Moderator or advocate note
For support-group, nonprofit, or family-resource follow-up
If an ME/CFS history keeps getting rebuilt from memory, this page helps keep exertion, crash timing, recovery burden, and function loss on one record before the next handoff: https://precisionmito.com/me-cfs-tracking
Tracked follow-up
Only after someone wants their own record
Tracked ME/CFS signup: https://precisionmito.com/signup.html?next=%2Fmitomap&source=community-growth-me-cfs
Safe claim line
Keep the framing conservative
Patient-owned tracking for crash patterns, function changes, and follow-up prep. This is not an ME/CFS diagnostic tool, PEM validator, or replacement for medical care.
Handoff Ladder
Move from public explainer to tracked signup in a fixed order so clinic, community, and booth follow-up stay proof-safe.
1. Public route first
Lead with the explainer page before attribution.
Use the public ME/CFS tracking page when someone needs one stable link for crash timing, recovery burden, and visit prep without asking them to sign up yet.
2. Short handoff second
Use this page when one shorter summary is easier to share.
Send the referral handoff page to a scheduler, disability helper, moderator, or family helper when the full landing page is more detail than the moment can carry.
3. Tracked signup only on request
Attach attribution only when the person wants their own record.
Move to the tracked signup link only after someone asks to keep their own chronology, prepare for a visit, or preserve the route for later follow-up.
4. Widen when the story stops being narrow
Switch lanes when the thread becomes post-viral, orthostatic, or broadly mixed.
Do not force a narrow ME/CFS label when overlap routing would make the next handoff more accurate and easier for the recipient to use.
Conference scan order:
public page first, referral handoff second, tracked signup only on request, then widen to Long COVID, POTS and dysautonomia, or the overlap hub if the story stops being mainly crash-and-recovery.
Proof Bundle
Keep the referral handoff tied to the exact proof-safe packet set for the ME/CFS lane.
Proof packet route
Use the same source-aware bundle when the handoff becomes real.
Move from the public landing page to this handoff page first. If the person wants their own record after that, switch to the tracked signup and keep any proof logging under community-growth-me-cfs only.
Community and clinic reuse
Keep the booth, scheduler, and partner packet language aligned.
Use the same route order across community groups, clinic scheduling notes, and nonprofit resource follow-up so the ME/CFS story stays narrow until overlap routing is clearly needed.
Proof packet route:
public ME/CFS landing page, this referral handoff page, tracked ME/CFS signup only on request, then the proof packet, route worksheet, and closeout memo if a real tracked follow-up or reviewed-zero check needs to be logged.
Route Choice
Use the narrow ME/CFS route only when it is still the real story.
- Stay on the ME/CFS route for crash timing, delayed payback, pacing breakdown, baseline drift, disability prep, and one patient-owned summary before the next visit.
- Use Crash Decoder when the next handoff needs one fast exertion-to-payback sequence before the full record.
- Switch to Long COVID when infection-linked relapse windows and post-viral framing are doing more explanatory work than a PEM-first story alone.
- Switch to POTS and dysautonomia when upright intolerance, hydration strategy, tachycardia, or standing tolerance are now the clearest route.
- Switch to the overlap hub when no single label is stable enough and the story spans crashes, orthostatic burden, mast-cell-style flares, and practical function loss together.
Companion Copy Pack
Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the lane by hand.
The companion feed keeps the ME/CFS partner-page blurb, moderator ask, email copy, safe-claim line, and asset links aligned with the broader condition campaign kit. Use these blocks when you need a quick community, clinic, or family-facing explanation that still matches the tracked source.
Loading the current ME/CFS companion copy pack.
Proof-Safe Follow-Up
Keep the public route separate from proof logging.
Share the public page first, then this shorter handoff page if clinic, moderator, or booth follow-up needs a faster summary. If the conversation turns into a real tracked follow-up, keep the source attached with the ME/CFS signup link and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-me-cfs.
If someone only wants a lightweight next step, keep them on the public route or Crash Decoder support page. If they need a broader route picker before signup, use the beachhead hub or complex-overlap page instead of attaching ME/CFS attribution too early.
Mito Map is an organization and tracking tool. It does not diagnose ME/CFS, prove post-exertional malaise on its own, or replace medical care.