The 18-Month Clock Nobody Warned You About

By: Drew Duffy MHA, FACHE, Founder & Managing Director

How the FPOR revision cycle quietly runs Minnesota operators out of time — and how to submit an approvable plan the first time.

If you have preliminary approval from the Office of Cannabis Management, you have already cleared the hardest part of getting into Minnesota's market. Whether you won a lottery for a capped license or qualified directly for an uncapped one, you did something most applicants did not. The trouble is that the next stage has a quiet failure mode most operators do not see coming — and it has nothing to do with whether your business is any good.

The failure mode is time. Specifically, the way the Final Plan of Record review cycle interacts with your 18-month deadline. Two or three ordinary rounds of revision — the kind OCM is issuing routinely right now — can burn six months you assumed you had. Operators do not lose their licenses because they built bad businesses. They lose them because they misjudged the clock.

This post lays out exactly how that clock works, why so many FPOR submissions come back with deficiencies, and what an approvable plan actually looks like. No fear — just the math and the mechanics, so you can plan around them.

How the 18-Month Clock Actually Works

From the date of your preliminary approval email, you have 18 months to complete everything that stands between you and an issued license. That window covers a lot of ground: securing site control, obtaining local zoning certification, building out the facility, submitting your Final Plan of Record, passing a pre-license inspection, and paying the initial license fee. A one-time six-month extension exists, but it is discretionary — you have to demonstrate good-faith progress, and it is not automatic.

Inside that window sits a second clock most operators underestimate. Once you register your site in Accela and attach your FPOR documents, OCM has 90 days to review the submission. It will not schedule your pre-license inspection until those plans are approved. And here is the part that matters: if your submission comes back with deficiencies, you revise and resubmit — and the review clock effectively restarts on the resubmission.

The deadline math operators get wrong

Suppose you wait until month 14 to submit because you are "still tightening things up." OCM takes the full 90 days. Your plan comes back with one round of deficiencies. You revise and resubmit — and another 90-day review window opens. You are now past your deadline, applying for a discretionary extension you may not receive.

The fix is unglamorous: submit no later than month 12, and only after you are genuinely built out and operationally ready. Earlier is fine. Late is fatal.

Why So Many FPORs Come Back Deficient

This is not a hypothetical risk. In July 2025, OCM issued Guidance Memo GM-2025-01 to all preliminarily approved applicants for one reason: it had started reviewing submitted plans and was seeing the same avoidable problems over and over. The agency documented the specific patterns that were causing plans to fall short of the standard for completeness and accuracy.

Read plainly, the memo is a list of the mistakes that trigger a revision cycle. Every one of them is preventable. The most common:

•     Premature submission. OCM is explicit that the FPOR must reflect actual, functioning systems and procedures — not future plans. If your facility is not fully built out and operationally ready, your plan describes a business that does not yet exist, and the review reflects that.

•     Generic or templated content. Answers borrowed from another state's operation, or from a template that was never tailored to your facility, read as generic. Reviewers can tell the difference between a plan written for your site and a plan written for anyone's.

•     Vague SOP references. Naming an SOP by title is not enough. You must either include the relevant text directly, or summarize its contents and cite the title, version number, and approved date. A bare title gives OCM no way to confirm the procedure exists or supports what you describe.

•     Partial answers to multi-part prompts. Many FPOR prompts ask several things at once. Answering two of three questions leaves a gap, and a gap is a deficiency.

•     Vagueness about systems and vendors. When a prompt asks about your point-of-sale software, security provider, or accounting partner, name the actual product and the actual company. "A compliant POS system" is not an answer; the product name is.

Notice what these have in common. None of them is about whether you can run a good cannabis business. They are about whether your written plan proves, in concrete and specific terms, that your systems already work. The gap between "we do this" and "here is exactly how, on which system, on what schedule, verified by whom" is where revision cycles are born.

What an Approvable Answer Looks Like

OCM's own guidance includes examples of answers that meet the standard, and the contrast with a weak answer is instructive. Consider a prompt asking how the business will manage inventory audits and reporting after a theft or security breach. A vague answer gestures at "regular audits and appropriate reporting." An approvable answer reads more like an operating procedure someone could actually follow:

Inventory audits against the point-of-sale system are conducted weekly on Sundays after close for products in the storage area. A full audit of all inventory, including the sales floor, runs monthly on the last day of the month after close. Designated staff check a printed POS report against physical inventory; the on-duty manager verifies records, signs, and dates them. Discrepancies are investigated and reconciled, with the explanation recorded in the statewide monitoring system. If a significant quantity is found missing, local law enforcement and OCM are notified immediately by phone.

That is the texture OCM is looking for across all four required plans — Site, Security and Operations; Inventory Control and Diversion Prevention; Quality Assurance; and Accounting and Tax Compliance. Specific schedules. Named systems. Named roles. A clear chain of who does what, when, and what happens when something goes wrong. Every prompt answered as if a reviewer will hold your written procedure against your physical facility during inspection — because they will.

How to Protect Your Clock

You cannot control OCM's review speed. You can control everything that determines whether you get one clean pass or three painful ones. In order of impact:

•     Do not submit until you are genuinely built out and operational. The single most expensive mistake is submitting early to "get the clock running." It runs the clock — straight into a deficiency notice.

•     Back-plan from month 12, not month 18. Treat month 12 as your target submission date. That leaves room for one full review and one revision cycle inside your window without touching the extension.

•     Answer every prompt as a procedure, not a promise. Concrete schedules, named products, named vendors, named roles, and a defined response to failures. If an answer could describe any operator, rewrite it until it describes only yours.

•     Make your plans match your building. The inspection checks your written procedures against your actual facility. Align them before you submit, not after a deficiency forces the point.

•     Have a second set of trained eyes review before Accela. The failure modes in GM-2025-01 are consistent and recognizable. Someone who knows what a reviewer flags can catch them before your 90 days start ticking — not after.

The operators who clear this stage on the first or second submission will be open and selling while their competitors are still drafting a second revision. In a market with capped license types, that head start is not just convenient — it is competitive position.

The plan does not have to be perfect. It has to be complete, specific, and true to the building you already built. Do that, and the clock stops being a threat.

-Drew

CannaPath Regulatory Solutions is here to help.

We help preliminarily approved Minnesota operators build Final Plans of Record that reflect real, functioning operations — grounded in OCM guidance and Minnesota Rules, chapter 9810 — so your submission clears review the first time instead of eating months of your 18. If you want a second set of trained eyes before your plans hit Accela, we would like to hear from you.

Reach out: hello@cannapath.org

We don't do fear. We do clarity.

This article reflects OCM's published Final Plan of Record requirements, including Guidance Memo GM-2025-01, and is provided for general informational purposes. It is not legal advice. Verify current requirements at mn.gov/ocm before acting.