First contact

A short first note is enough to start.

Send the decision, the cost of waiting, who has to review it, and what is blocking the call. That is usually enough to tell whether this is a fit.

This page prepares a structured email draft in your own email client. Nothing is submitted through the site. Keep the first note high-level and do not include PHI, patient-level data, medical records, or other regulated personal information in public intake.

What to send

Start with the smallest useful version of the problem.

Decision

Name the move or judgment call that is currently stuck.

Cost of waiting

Say what is getting worse while the review stays unresolved.

Review owner

Name the person, function, or committee that has to weigh in.

Blocker

State what is actually slowing the call right now.

What comes back

A short reply on fit, missing context, and whether it makes sense to talk now.

Fit read

Whether this sounds like a real managed decision-review problem.

Missing context

What still needs to be clarified before an intro call makes sense.

Next step

Whether to move ahead, narrow the question, or wait for better context.

Contact form

Core fields first. Optional context only if it sharpens the decision.

The goal is to get to a clear yes, no, or narrower next step without turning first contact into a long intake memo.

Data boundary Public intake stays out of PHI and patient-level detail.

Most first conversations stay at the decision-review level. Sensitive material moves only after scope, confidentiality terms, and secure handoff are in place.

Read trust and data boundary

Fit check

What makes a note actionable?

Concrete enough A current decision, visible stake, and a named reviewer or committee.

That is usually enough for a useful answer. The issue does not need to be solved yet, but it does need to be specific.

Probably too early Broad topic, unclear owner, or no near-term decision boundary.

If the issue is still exploratory, the right next step is usually to narrow the question before any work opens.

Useful prep Read the sample brief first if the problem is still hard to describe.

That usually gives teams a faster way to define the question, the output, and what would need to be true to move.

What you can expect

You should get a short, specific answer.

Say whether the issue sounds like a real fit
Name the missing context if the question is still too broad
Recommend move ahead, narrow the question, or wait