Verify MC Automated Registry Filing Tracking
Every morning, WebRun opens Verify MC, lists patients certified in the past week, checks each record for whether the state registry submission has been completed, records the status in a Google Sheet, and posts your compliance team a Slack worklist of certifications still waiting to be filed with the state, oldest first.
How do I track which medical cannabis certifications still need state registry submission?
WebRun opens Verify MC every morning, lists patients certified in the past week, and checks each record for whether its state registry submission is complete. It logs the status to a Google Sheet and posts your compliance team a Slack worklist of filings still outstanding, oldest first, so no approved patient stalls before their card is issued.
- No certified patient stalls unfiled before their card is issued
- Overdue state filings surface the same day they pass your window
- Compliance staff work an ordered list instead of scanning charts
Built for cannabis clinic compliance teams · MMJ certification practices · medical cannabis administrators · telehealth cannabis clinics
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
verifymc.comin a real browser with your saved login - no setup, no API keys. -
1
Verify MC - list recently certified patients
WebRun opens Verify MC to list recently certified patients. - Open Verify MC and list patients certified in the past 7 days
- For each, check whether the state registry submission step is marked complete in the record
- Capture the patient reference, certification date, state, and days since certification
Done when Every recent certification has a submitted or not-submitted status.
-
2
Google Sheets - record submission status
WebRun records each submission status in Google Sheets. - Append or update one row per certification with reference, state, certification date, and submission status
- Highlight rows where the state filing is still outstanding beyond your target window
- Store only the patient reference and state, never names or clinical details
Done when The tracker sheet reflects the live submission status of every recent certification.
-
3
Slack - post the outstanding filings worklist
WebRun posts the outstanding filings worklist to Slack. - Post a worklist to the compliance channel of certifications not yet submitted to the state, ordered oldest first
- Show each by reference, state, and days waiting, and call out any past your filing deadline
- Note that this is an internal tracking list and no submission is filed by the workflow
Done when Compliance staff have today's outstanding state filings worklist in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it submit anything to the state registry itself?
No. WebRun only tracks which certifications have not been filed and posts an internal worklist for your compliance team. Every state registry submission remains a human action, so nothing is filed with a government portal automatically.
How does it know a filing is overdue?
It counts days since the certification date against the filing window you set. Any submission still outstanding past that window is highlighted in the sheet and called out in Slack, so late filings surface before they become a problem.
Does it expose patient details to the compliance channel?
No. The worklist and sheet use a patient reference number and the state only, never names, contact details, or diagnoses, so protected health information stays out of your internal channels.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.