Back
City of Los Angeles
· City
· California
Cannabis Licensing System
PROPOSALS DUE
October 29, 2026, 10:00 am PDT
9 days left
WHAT THEY WANT
(Summarized from the RFP)
The City of Los Angeles Department of Cannabis Regulation (DCR) is seeking a vendor to design, implement, and support a modern, automated, web-based cannabis licensing and compliance platform. DCR administers all commercial cannabis licensing and regulatory functions for the City, including processing applications, making licensing decisions, and overseeing licensed cannabis businesses. The current environment relies on custom code, lacks integration between DCR's permitting system and the City's financial systems, and creates processing inefficiencies that the new system is intended to resolve.
DOCUMENT SET
43 documents
· 48.8MB
Request for Proposals — full solicitation.pdf · 1.2MB
Addendum 1 — questions and answers.pdf · 210KB
Attachment A — scope of work and deliverables.pdf · 480KB
Attachment B — cost proposal form.xlsx · 64KB
Sample agreement and insurance requirements.pdf · 560KB
Pre-proposal meeting — sign-in sheet and slides.pdf · 1.8MB
More in the folder — every document opens with a free account.
CHANGES SINCE PUBLISHED
7 changes
▶
2026CLS003 Q&A as of 10-15-26.pdf
Q&A
▶
2026CLS003 Q&A as of 10-08-26.pdf
Q&A
▶
2026CLS003 Addendum 3 FINAL 100126.pdf
Scope/requirements
▶
2026CLS003 Q&A as of 10-01-26.pdf
Q&A
▶
2026CLS003 Addendum 2 FINAL 092326.pdf
Q&A
▶
2026CLS003 Exhibit 3 - Narrative Response Form REVISED.docx
Recall
All 7 changes summarized with a free account.
WHAT OTHERS ASKED
148 questions answered
▶
What integration test environments will be provided by the City for Contractor use?
Scope/requirements
▶
Please provide documentation of enforcement workflows.
Scope/requirements
▶
For the API integration, how should the system behave if the API is unavailable or experiences downtime? Is the system expected to handle these scenarios, such as through retries, fallback logic, or error messaging? If so, will specific requirements or instructions be provided for how these situations should be handled?
Scope/requirements
▶
LATAX Integration (Exhibit 7 E006, B010, C013; Exhibit 8 C008). Which data elements does DCR expect to exchange with LATAX (e.g., BTRC number and status, tax account status, delinquency indicators), in which direction, and at what frequency? What interface does LATAX expose, and how is LATAX account status used in licensing decisions today (e.g., at issuance or renewal)?
Scope/requirements
▶
UCS Payment Sync (SOW 4.4; Exhibit 7 E005, E008, E014; Exhibit 8 C007, C014). What is the maximum acceptable time between a payment posting in the Universal Cashiering System (UCS) and its appearance on the license record? Which system originates invoices, assigns invoice identifiers, and communicates partial payments, refunds, and voids? Will UCS interface specifications and a test environment be made available to the selected vendor, and how does DCR reconcile invoices to payments today?
Scope/requirements
▶
Implementation Priorities: When the new system goes live, what would DCR consider the most important early sign of success—faster application processing, better visibility into case status, improved data quality, easier staff workflows, stronger integrations, better applicant experience, or another operational outcome?
Scope/requirements
All 148 answers open with a free account.
ABOUT THIS RFP
RFP number
2026CLS003
Budget
Not Assigned
Published
Entity type
City
State
California
Summarized from the City of Los Angeles portal.
HOW TO SUBMIT
Proposals must be submitted electronically via email to DCR.ADMIN@lacity.org. No physical copies are accepted. Proposers must submit one (1) single PDF file containing the complete response package, plus nine (9) individual native-format files: Exhibits 1, 2, 3, 4, and 6 as MS Word files, and Exhibits 5, 7, 8, and 9 as MS Excel files. The total email size, including all attachments, must not exceed 25 MB. If the file size exceeds the limit, Proposers may send multiple emails, each labeled to indicate order and total count (e.g., 'email 1 of 3'). All emails must be sent from the same address provided in Exhibit 2, and Proposers must include the RFP number (2026CLS003) in the email subject line. Attachments must not be compressed, must not contain viruses or malware, and must be openable. A redacted PDF version with confidential material removed must also be included if the response contains proprietary information. Proposers are solely responsible for ensuring successful receipt before the submission deadline. For confirmation of receipt, Proposers may contact DCR's Administration and Community Engagement Division at (213) 978-0738 during working hours.
NAICS CODES & TAGS
541511
541512
Information Technology Support Services
Website Development
ACROSS 539 RFPS
MORE THAN
RFPs changed their terms while active.
25 days is the median window from publication to due date; day 16 is the median first change for the 113 that changed. 539 RFPs published and due: July 23 - Sept. 30, 2026.
Bid on five RFPs, and the odds are better than two in three that at least one changes its terms before the deadline. Larger firms have staff tracking this. Start free and you’ll have it at your fingertips too.
Free to open
free account required
A free account opens this RFP in full, starting with the rest of the description above — and 5 RFPs a week, no card.
Changes since published
7 changes filed since it went out, each one summarized, so a date or a requirement never shifts without you knowing.
What others asked
148 questions the government entity answered in writing — the answers bind.
The documents
The set as published, in one folder or as direct links to the document.
Matched to you
The RFPs that fit the NAICS codes and tags you save; open up to 5 a week in full.
