How long does LegitScript certification take?
Plan on weeks rather than days, currently 4 to 12 weeks. The clock starts when your submission is complete rather than when you send it. An application with missing detail therefore runs longer than the published range suggests.
What determines how long it takes?
- whether the submission is complete on the first attempt
- how many states you serve, and whether your licensing covers them
- how many providers are involved
- whether the pharmacy arrangement is already documented
- whether your site matches what you are submitting
Where do applications stall?
Most delay comes from three mismatches. The site advertises states you are not licensed in. The pharmacy is not named clearly. The brand on the storefront does not obviously belong to the entity that applied.
Each mismatch becomes a question from the reviewer, and each question costs a round trip. Three round trips turn a fast application into a slow one.
How do you run certification alongside the build?
Certification is the longest item and almost nothing else depends on it finishing to start. The site, the brand, the provider network and the pharmacy terms can all be built while the review runs.
| Stage | Runs alongside certification |
|---|---|
| Brand and site build | Yes |
| Provider network and licensing | Yes, and it feeds the application |
| Pharmacy terms | Yes, and it feeds the application |
| Payment account approval | No. It waits on certification |
| First patient billed | No. It waits on the payment account |
What does this mean for your launch date?
Your launch date is set by the last item in that chain, which is payment approval. Starting certification first is the only way to move it, and starting it last is the most common reason a program misses its own deadline.
What can you build while the application runs?
Most of the program, which is why the waiting period is less wasteful than it first looks.
Things that do not depend on approval
- The brand, the site pages and the program copy.
- The intake and consent flow, provided it is built to the standards you are applying under.
- The pharmacy relationship, including the medication list and wholesale terms.
- Provider coverage planning, so the states you sell into are covered on day one.
- Staff briefing, so the front desk can answer questions before launch rather than after.
Things that wait for approval
- Taking a payment for a prescription.
- Advertising on platforms that require the credential.
- Anything that promises a patient a delivery date.
The split is simple. Build what you can, and do not promise what you cannot yet deliver.
How do you set a launch date you can trust?
| Step | Who moves it | Can it run in parallel? |
|---|---|---|
| Documentation assembly | You | Yes |
| Application review | The certifying body | Yes, with everything else |
| Payment underwriting | Your processor | Yes, once certification clears |
| Pharmacy onboarding | Your pharmacy | Yes |
| Site and intake build | You or your platform | Yes |
Four of the five run at once. The reason launches slip is almost never that the work took longer than expected. It is that the application started after the work instead of alongside it.
What should you do if the date is already tight?
Ask two questions before you spend anything. Does the certifying body offer an expedited review, and does your processor accept anything faster than certification?
Where an expedited option exists it costs more and shortens the wait. Take that trade when a launch date is fixed. The cost of delaying a program you have already paid to build is usually larger than the fee.