From recommendation to treatment · Options · proposal · response · treatment

Turn recommended care into a proposal your clinic can follow.

Build patient-linked treatment options, share a proposal, record the response, assign follow-up and move accepted items into treatment. Clinical consent is a separate decision and record.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
06 · ReviewProposal pipeline reviewStage · age · source · valueMeasured
Patient 024 treatment proposal pipeline illustration · demonstration data

01Recommended and alternative treatment options with clinical and commercial context

02Secure proposal sharing with patient review and response states

03Proposal ownership, follow-up dates, aging, source and value reporting

04Accepted-item conversion into treatment, without treating acceptance as clinical consent

Why this workflow matters

THE CLINIC MOMENT

Recommended care can stall without a visible owner and patient decision.

Patient 024 has recommended crown care, but the options, proposal value, patient response and next follow-up sit in separate lists. Consent is still a separate clinical decision. Nobody can see who owns the next step.

BEFORE

Recommended care loses momentum when options, proposal value, patient response, ownership and follow-up are kept in separate lists.

The next owner and source record are unclear.

CONNECTED

Build patient-linked treatment options, share a proposal, record the response, assign follow-up and move accepted items into treatment. Clinical consent is a separate decision and record.

Open the record you need without searching for the patient again.

HOW IT WORKS

Build the options, follow the response and move accepted care into treatment.

Follow the task from its first entry to the next person who needs it.

  1. 01

    Build the options

    Prepare recommended and alternative treatment options with the relevant patient, teeth, clinicians, visits and value.

  2. 02

    Follow the decision

    Share the secure proposal, record review or changes requested, assign an owner and set a follow-up date.

  3. 03

    Move accepted care forward

    Convert accepted items into treatment while keeping procedure-specific clinical consent separate.

ONE WORKFLOW · 6 CHECKPOINTS

Follow a patient-linked proposal from recommendation to treatment.

The clinic can see the response, owner, follow-up and value without treating proposal acceptance as clinical consent.

01 · Options

Build recommended and alternative treatment options.

Patient, teeth, procedures, clinicians, visits and value stay around one proposal rather than a separate estimate document.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
01 · OptionsPatient 024 · treatment optionsRecommended + alternative pathsDraft
Patient 024 treatment proposal pipeline illustration · demonstration data
02 · Issue

Issue a secure proposal for the patient to review.

The patient-facing proposal has its own share path and lifecycle while the underlying treatment context remains with the clinic record.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
02 · IssueSecure treatment proposalPatient 024 · shared linkShared
Patient 024 treatment proposal pipeline illustration · demonstration data
03 · Response

Record opened, reviewed or changes-requested states.

The team can see the response without treating a proposal view or commercial acceptance as clinical consent.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
03 · ResponsePatient responseReviewed · changes requestedReviewed
Patient 024 treatment proposal pipeline illustration · demonstration data
04 · Follow-up

Assign an owner and a follow-up date.

Planning the next contact creates visible work for the coordinator; it does not automatically send a message.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
04 · Follow-upProposal follow-upOwner · due date · next stepAssigned
Patient 024 treatment proposal pipeline illustration · demonstration data
05 · Treatment

Move accepted items into the treatment workflow.

Accepted proposal items can continue into treatment. Procedure-specific clinical consent remains a separate record and conversation.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
05 · TreatmentAccepted crown itemReady for treatment workflowAccepted
Patient 024 treatment proposal pipeline illustration · demonstration data
06 · Review

Review funnel, aging, source and proposal value.

Reporting begins after a patient record exists and reflects recorded proposal, treatment and financial data—not a pre-patient acquisition funnel.

PROPOSAL PIPELINEDemonstration data
024
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected
01Options builtDraft
02Secure proposal issuedShared
03Reviewed by patientReviewed
04Changes requestedAssigned
05Follow-up assignedAccepted
06Accepted items to treatmentMeasured
06 · ReviewProposal pipeline reviewStage · age · source · valueMeasured
Patient 024 treatment proposal pipeline illustration · demonstration data

Patient-linked proposal pipeline

Carry a treatment proposal from draft to completed decision

Start with a patient record and build recommended and alternative treatment options with the relevant teeth, procedures, clinicians, visits and commercial context. Issue the proposal through its secure patient-facing route, then keep its response and next owner visible.

The proposal stages are Draft, Shared, Reviewed, Changes requested, Accepted, Treatment and Closed. Open and review activity can help the team understand where a proposal is; a follow-up date creates visible work for the owner rather than sending an automatic message.

Proposal stages

  1. 01Draft

    Build recommended and alternative treatment options.

  2. 02Shared

    Issue a secure proposal for Patient 024.

  3. 03Reviewed

    Record that the proposal was opened and reviewed.

  4. 04Changes requested

    Keep the requested revision with the proposal.

  5. 05Accepted

    Record the patient response without treating it as clinical consent.

  6. 06Treatment

    Move accepted items into the treatment workflow.

  7. 07Closed

    Close the proposal with its history retained.

Ownership and reporting

See who owns the next decision and what remains in the pipeline

Assign an owner and follow-up date, then review funnel stage, aging, source and proposal value. Patient-source reporting can compare proposal conversion and later revenue only after a patient record exists and its source is recorded.

Reporting reflects the proposal, treatment and financial records entered into Thirty2OS. It is not a pre-patient acquisition funnel and does not replace an enquiry CRM.

A different patient decision

Proposal acceptance does not replace clinical consent

A patient can accept selected treatment options without signing a procedure-specific consent form. The clinic must prepare and discuss clinical consent separately, then review its own consent status before treatment.

Permissions and workflow boundaries

ROLES & PERMISSIONS

Proposal acceptance is not clinical consent.

Clinical users record recommended care. An authorised owner or treatment coordinator can prepare sharing, proposal ownership and follow-up. The relevant permission still applies when accepted items move into treatment.

WHERE IT STOPS

What your team still decides.

This is a patient-linked treatment proposal workflow, not a general lead or prospect CRM. Proposal acceptance and clinical consent are distinct, and follow-up planning does not automatically send a message.

Plan your trial

TRIAL PLAN

Rehearse the complete proposal pipeline.

Try these tasks with fictional patient details and the roles your team uses. Note any setup question or step that needs a different process.

  • Create recommended and alternative options
  • Move a proposal through Draft, Shared and Reviewed
  • Record Changes requested and a follow-up owner
  • Convert accepted items into treatment
  • Review aging, source and value reporting
  • Complete clinical consent separately

QUESTIONS TO ASK

Is this a general patient-acquisition CRM?

No. The proposal pipeline starts after a patient record exists and follows a patient-linked treatment decision.

Is accepting a proposal the same as giving clinical consent?

No. Proposal acceptance is a commercial treatment decision; procedure-specific clinical consent remains separate.

YOUR CLINIC · YOUR EXCEPTION

Bring the handoff that keeps breaking.

Start free to test the workflow yourself, or book a guided demo when you want help mapping the exception.

Start 14-day free trialBook a guided demo