Guided Advocate

Deeper drafting and route guidance for complicated patient advocacy.

Guided Advocate is the planned Supporter Tool for people who need more than a basic form. It is meant to help organize difficult facts, prepare stronger drafts, and sort the right type of recipient without pretending to replace a doctor, lawyer, agency, or human judgment.

Why it is worth paying for

Guided Advocate has to do work the free tools cannot do well enough alone.

Free tools help a person begin. Guided Advocate is planned for the harder point where the facts are scattered, the route is unclear, the recipient matters, and the wording needs to be stronger without becoming unsafe.

Recipient-specific drafts

A provider message, records correction, board complaint, pharmacy summary, insurance follow-up, and legislator letter should not read the same. Guided Advocate is planned to shape the same facts around the recipient, the lane, and the written answer being requested.

Route clarity for messy situations

Many patients have more than one problem at once. Guided Advocate is meant to separate the medical-record issue, access barrier, complaint route, and policy concern so each document has a responsible destination.

Source status before stronger routing

When official routing is involved, the system should show whether reviewed official guidance supports that route. If the source is not ready, the tool should say so instead of guessing.

Better packets, not longer packets

The value is not dumping more words onto the page. The value is cutting noise, ordering the facts, protecting private details, and making the request harder to ignore.

Time saved for sick users and caregivers

People who are exhausted should not have to rebuild the same story five different ways. Supporter help should reuse the core facts to prepare cleaner versions for different recipients.

User control before anything leaves the screen

The user reviews the wording, removes private details, and chooses whether to copy, print, or save later. No message delivery is part of the first release.

Where the upgrade should feel useful

Supporter access should never feel like a locked door to basic help. It should feel useful when the user has already tried to organize the issue and needs the draft or route cleaned up.

Real use case

A wrong chart note keeps following the patient.

Free: Use the records tool to identify the wrong wording and prepare a basic correction request.

Guided Advocate: Create a cleaner correction packet, separate facts from opinion, and prepare a statement-style draft if the correction is denied.

Real use case

The pharmacy, insurer, and prescriber keep pointing at each other.

Free: Use the medication-access and timeline tools to document the loop.

Guided Advocate: Sort the facts by recipient so each office receives the right summary and the right written request.

Real use case

A hospital or clinic complaint needs to sound firm without sounding reckless.

Free: Use the complaint route helper and letter starter to build a first version.

Guided Advocate: Tighten the complaint into dates, harm, records, requested review, and requested written response.

Real use case

The patient wants to contact a lawmaker without sounding like a personal rant.

Free: Use the public advocacy pages to understand the issue and write a basic message.

Guided Advocate: Turn the story into a policy-focused letter that protects privacy while explaining the real-world harm.

How a session should feel

The experience should be calm, adult, and practical. The user should always know what is happening and why.

  • Pick the issue lane before writing.
  • Name the recipient type before the draft is shaped.
  • Enter only the facts needed for that lane.
  • See the route limits before relying on the draft.
  • Review a concise draft before any longer packet is created.
  • Copy or print without forced storage.
  • Save only later, only with account controls and clear consent.
Release order

Launch narrow first, then expand only after the trust systems hold.

The first Supporter release should prove value through draft quality and route clarity. Higher-risk features wait until accounts, sources, privacy, moderation, and support rules are ready.

First release

Draft improvement, route guidance, privacy review, and packet cleanup for supporter users. The first release should end with copy/print output, not automatic sending, public posting, or stored health drafts by default.

Second release

Reviewed official sources can support more specific board, agency, insurance, privacy, pharmacy, records, and policy routes once source ownership and review dates are visible.

Later release

Saved advocacy packets, caregiver-friendly access, official-contact helper entries, and carefully reviewed delivery options can be considered after privacy and support systems are ready.

Trust limits stay visible.

Serious Supporter tools need serious boundaries. Users should understand the limits before entering sensitive details, paying, saving work, or relying on a route.

  • No diagnosis, prescribing, treatment instructions, or promise of care.
  • No legal conclusions, deadlines, or citations unless supported by reviewed public guidance and careful wording.
  • No invented emails, phone numbers, agencies, forms, doctors, boards, or complaint offices.
  • No public story posting, provider listing, review system, or saved packet without separate approval gates.
  • No confusing Supporter prompt before the free tool has already helped the user create something useful.
Product experience standard

A Supporter tool must feel calm, exact, and useful on the first screen.

Supporter access cannot look like a toy, a generic form, or a vague promise. The experience should guide the user through one issue at a time and produce a cleaner document than they could make alone while exhausted.

Start with the lane

The user chooses the closest issue first: records, medication access, provider message, complaint route, insurance problem, pharmacy barrier, agency route, or policy letter.

Collect only what is needed

The tool should ask for dates, impact, prior contact, missing answer, documents, and the specific written request. It should not push people to overshare private medical history.

Show the source status

If a route depends on a board, agency, law, office, or complaint form, the tool should show whether reviewed official guidance supports that direction.

Draft for the recipient

The output should change based on who is reading it. A provider message should not sound like a legislator letter or board complaint.

Review before use

The user should see privacy warnings, tone checks, missing-fact prompts, and a final review step before copying, printing, saving, or sending anything later.

Keep the first release narrow

The first Supporter release should focus on drafting, routing clarity, and packet cleanup. Message delivery, saved packets, and public sharing wait for separate approval gates.

Quality bar for every Supporter output

The Supporter value should be visible in the final document, not hidden behind marketing language.

  • Does the output name the right recipient type?
  • Does the draft separate facts, impact, records, and requested action?
  • Does it avoid unnecessary private details?
  • Does it avoid promises, threats, diagnosis, legal conclusions, and unsupported claims?
  • Does it give the user a usable shorter version and a fuller packet version?
  • Does the page still make sense on a phone without crowding the user?

Why this protects the mission

Professional tone

The experience should feel like a serious advocacy workspace: calm, readable, direct, and built for people dealing with pain, nausea, brain fog, stress, or caregiver pressure.

Source discipline

Specific laws, agency routes, complaint offices, contacts, and deadlines should never be guessed. If reviewed public guidance is missing, the tool should say the route needs verification.

Plain cost explanation

Supporter access should explain the operating cost honestly: guided drafting, source upkeep, privacy safeguards, security, hosting, and ongoing maintenance.

The Supporter release should prove itself with one strong workflow before expanding.

Start with route sorting, stronger drafts, packet cleanup, and clear limits. Add reviewed official-source support, saved work, contact helper entries, and delivery tools only after security and privacy gates are ready.