Describing your business correctly, before a reviewer describes it for you

The first substantive decision in an application is not what to disclose. It is what to say the business is, and it is made so early and so casually that most applicants do not notice making it.

Get it wrong and everything downstream is slightly misaligned: the questions asked are the wrong questions, the evidence supplied answers something else, and the correction costs a round trip in the middle of a review.

Why the description does so much work

A review assesses a model. Which questions matter, which documents are expected and which risks are being weighed all follow from what kind of operation the reviewer thinks they are looking at.

A business that dispenses medicines is assessed on dispensing. One that prescribes is assessed on prescribing. One that does neither and connects patients to people who do is assessed on what it is responsible for and what it is not. Those are three different reviews, and the difference is not cosmetic.

Six questions that sort almost every business

Answer these plainly, in writing, before anything is filed.

Do you prescribe? Do clinicians employed or contracted by your entity make prescribing decisions for patients, or does that happen inside somebody else's organisation?

Do you dispense? Does your entity hold pharmacy licensure and physically supply medicines, or does a partner do that?

Do you sell? Does the patient pay you, and does your entity own the commercial relationship, the pricing and the subscription?

Whose website is it? The certified thing is a website. If patients transact on your domain, it is yours regardless of who fulfils behind it.

What is in the catalogue? Approved medicines, compounded preparations, controlled substances, supplements, devices, laboratory tests, or a mixture. A mixture is normal and it means several sets of rules apply at once.

Who is the patient's counterparty? When something goes wrong, who does the patient believe they are dealing with, and is that the same entity the application names?

The structures that get described badly

The professional corporation and the operating company. Clinicians employed by one entity, the brand and the platform owned by another. Extremely common, entirely ordinary, and frequently described as though the operating company prescribes. State the relationship rather than leaving it to be inferred, which is the same discipline a complete file applies to corporate structure generally.

The brand that thinks it is a pharmacy. Because the medicine arrives in packaging carrying its logo. It is not, and describing itself as one produces questions about licensure it does not hold and cannot produce.

The pharmacy that also sells direct. Two models in one entity, and both need describing rather than one standing in for the other.

The platform that thinks it is neutral. Covered below, because it is the category with the largest gap between how the business sees itself and how a patient does.

Getting the catalogue description right

The catalogue drives more of the review than the entity does, and it is described loosely more often than anything else.

Say, per product, whether it is an approved medicine prescribed generically, a compounded preparation, a controlled substance in some or all formulations, a supplement, a device or a test. Businesses routinely discover during this exercise that they cannot answer for two or three items, which is a finding in itself and is much better found now.

The eligibility consequences follow directly: compounded products bring a claims-focused review, controlled substances bring a documentation-focused one, and a mixed catalogue brings both.

Where the description meets the website

The description in the application has to match what the website tells patients, because the reviewer reads both. A site saying "our doctors" while the application describes a contracted professional entity is not lying anywhere. It has told two stories, and resolving the difference is time.

The cheap fix is to write the description first, then read the website against it, and change whichever one is wrong. Usually it is the website, because the website was written to reassure rather than to describe.

The description drifts as the business grows

The other failure is a description that was accurate when it was written. A clinic adds a second brand, a brand starts white labelling its intake, a platform hires clinicians, a company that referred patients begins employing them.

Each of those changes what the business is, and none of them arrives with a prompt to update the file. The description in a submission from eighteen months ago describes a company that no longer exists, and the gap is discoverable from the website.

Put a date on the description and re-read it whenever the corporate structure, the catalogue or the fulfilment arrangement changes. That is the same quarterly habit that keeps the rest of the file current after approval, and this is the page of it most worth re-reading.

What to do with an honest ambiguity

Some businesses genuinely sit between categories: a platform that also employs clinicians, a pharmacy that operates a consumer brand, a clinic that white labels its intake to partners.

Describe the ambiguity rather than resolving it in your own favour. A file that says "we do these two things, here is how each works, here is which entity does which" is a file with an explanation in it. A file that picks the simpler description and hopes has planted a discrepancy the reviewer will find in the corporate filings.

The one-page description worth writing

Before anything else, write one page. What the business is, which entities do what, who prescribes, who dispenses, who sells, what is in the catalogue, and what the patient's relationship is with each party.

Then read the website, the corporate filings and your partner agreements against it. Every place they disagree is a question you would otherwise receive, which is the whole of the preparation argument and the reason the fast reviews are the ones with nothing left to ask.