Welcome to FloridaProcurements.com (FlaProc), your authoritative resource for navigating Florida’s government contracting landscape, with particular focus on transportation and technology opportunities. FlaProc provides free, expert guidance to help companies identify and secure state contracting opportunities throughout Florida. 

This resource is maintained by Attorney Sean Gellis of Gellis Law, PLLC, one of less than 75 attorneys Board Certified in State and Federal Government and Administrative Practice by The Florida Bar. Mr. Gellis brings unique insight to government contracting, having served as the Chief of Staff of the Florida Department of Management Services (DMS), General Counsel of the Florida Department of Transportation (FDOT), and Deputy General Counsel of the Florida Office of Insurance Regulation – positions that provided direct oversight of technology initiatives and issues of statewide importance. His record in bid protest litigation reflects the sophisticated advocacy and strategic thinking he brings to government contracting matters, particularly in complex transportation and technology procurements. Sean also leads Procurement Insider, a confidential subscription service that provides technology vendors with strategic intelligence and insider analysis of Florida government opportunities. Learn more about transforming your approach to government contracting at www.gellislaw.com/procurement-insider

Brevard’s Early Learning Coalition Issues a Hosted IT RFP: A 50-User, Three-Year Managed Services Opportunity on a 20-Day Clock

Filed in: Bid Watch By: Sean Gellis Date: May 12, 2026

The Early Learning Coalition of Brevard County (ELCB) released RFP #2026-IT-01 on May 5, 2026, seeking a managed services provider to serve as the Coalition’s outsourced IT department for a three-year base term beginning July 1, 2026, with two one-year renewal options. Responses are due Monday, May 25, 2026 at 2:00 PM Eastern (Coalition Time) at ELCB’s Melbourne office.

This is a small-footprint opportunity — roughly 50 users — but the wrapper is more complex than the headcount suggests. The Coalition is a federally-funded 501(c)(3) statutorily designated under Chapter 411.01 and Part V of Chapter 1002, Florida Statutes, which means proposers are buying into the full Uniform Guidance compliance regime layered on top of state-style RFP procedures. Below, the items that should drive your bid/no-bid analysis.

The Opportunity at a Glance

• Solicitation Number: RFP #2026-IT-01
• Issuing Entity: Early Learning Coalition of Brevard County (ELCB)
• Scope: Fully outsourced managed IT services for ~50 full-time staff — Microsoft 365 Business Premium (non-profit licensing), Exchange management, M365 cloud backup with unlimited storage, MDR/ITDR, advanced email threat protection, MFA (Duo), 24/7 cloud MDR SOC/SIEM log ingestion, SonicWall firewall configuration, endpoint patch management, cybersecurity awareness training, help desk (M–F 8:00 AM–6:00 PM), and coordination with the Coalition’s separately-contracted 3CX VOIP provider
• Term: July 1, 2026 – June 30, 2029 (three years), with two possible renewals at the same pricing
• Estimated Spend Context: ELCB administered $34.5M in federal awards and $114.8M in state financial assistance in FY ending June 30, 2026 — this contract is a small slice of overall operations, but it touches the entire operational backbone
• Pricing Model Requested: Fixed fee schedule with cost-per-user/data-usage pricing — Cover Sheet requires separate annual totals for Years 1, 2, and 3
• Page Limit: 18 pages (excluding budgets and required certifications), 11-point font, 1.0 line spacing
• Format: Hard-copy only — one original (blue-ink signatures) plus six copies, plus one electronic copy on flash drive or CD; email and fax submissions will not be considered
• Sole Point of Contact: Sondra Moffit, Finance Director, [email protected]

The Timeline Looks Like Three Weeks. It’s Actually Five Business Days.

The headline “20 days to respond” misses the more constraining number. The last day to submit written inquiries is Noon on Wednesday, May 20, 2026. Final proposals are due Monday, May 25 at 2:00 PM. That leaves vendors three business days between the close of Q&A and the response deadline — and that assumes ELCB posts answers immediately, which the schedule doesn’t guarantee.

The practical sequencing for serious bidders:

1. Today–May 13: Get the mandatory Notice of Intent in (see below).
2. May 13–May 19: Draft your initial response, identify ambiguities, and file written questions.
3. May 20 by Noon: Final inquiry submission.
4. May 21–May 22: Watch elcbrevard.org for posted answers and any addenda.
5. May 22–May 25 morning: Incorporate addenda, finalize pricing, produce seven physical copies plus a flash drive, and deliver to Melbourne.

If you haven’t started by the time you’re reading this, the schedule is workable but unforgiving.

The Notice of Intent Is a Hard Gate, Not a Courtesy

Section IV.A. is explicit: submission of the Notice of Intent to Submit a Proposal (Exhibit 1) is mandatory, and failure to submit it “will render the proposer’s reply non-responsive and will result in rejection of the respondent’s proposal.” This is a fatal disqualifier, not a procedural nicety.

A few practical points:

• The Notice can be hand-delivered, mailed, or emailed to [email protected].
• The RFP doesn’t print a hard deadline in the Schedule of Events column for the Notice (the date field reads “N/A,” which is itself a drafting issue) — but the 4:00 PM time stamp and the statement that failure to file “may preclude a prospective Proposer from submitting a response” suggests this must be filed well in advance of the May 25 due date.
• File it now. The Notice is also how you get on the addendum distribution list — vendors who don’t file may miss email notifications of changes.

Beyond the disqualification risk, the Notice serves a second strategic function: it triggers ELCB’s notification obligations under Section IV.I if the solicitation is amended. Vendors who skip the Notice are placing themselves at the mercy of the public website for updates, which is a poor risk allocation on a three-week clock.

The Federal Funding Wrapper: 2 CFR Part 200 Is in Play

Because ELCB exceeds the $750,000 federal expenditure threshold for single-audit purposes under 2 CFR §200.501, this procurement carries Uniform Guidance baggage that pure state-funded ELC procurements would not. The certifications package (Attachment D) reflects this — proposers must execute:

• Debarment and Suspension certification (Executive Order 12549, 29 CFR Part 95, 45 CFR Part 74) — and again separately under Attachment F
• Certification Regarding Lobbying under 31 U.S.C. § 1352 (penalties: $10,000–$100,000 per failure)
• Drug-Free Workplace certification (29 CFR Part 98)
• Nondiscrimination and Equal Opportunity assurances (29 CFR Part 37; 45 CFR Part 80)
• Public Entity Crimes certification under § 287.133, Florida Statutes
• Sarbanes-Oxley whistleblower and document-preservation provisions
• Trafficking Victims Protection Act of 2000 § 106(g) compliance

For vendors who routinely respond to state-only Florida RFPs, the federal certifications layer adds approximately 8–12 pages of executed forms to your response. Build that into your page-count planning — the 18-page narrative limit does not include these certifications, but assembling them takes real time and signature coordination.

The federal wrapper also matters for subcontracting. Any subcontract of $25,000 or more in federal monies triggers its own debarment certification flow-down (Attachment F, Instruction 6). MSPs who plan to subcontract SOC services, M365 licensing resale, or SonicWall management need to confirm their downstream partners can execute the same certifications.

The Incumbent Signal Hiding in the 3CX Reference

Section II flags that ELCB’s “current IT service provider manages our 3CX VOIP hosted phone system” under a separate contract running through January 31, 2027, and that “coordination with this contractor will be a critical part of the IT service and support.”

A few inferences worth pressure-testing:

1. The incumbent IT vendor is also the 3CX vendor. That’s the most natural read of the language. If correct, the incumbent has a knowledge advantage on the environment, the user base, the SonicWall configurations, and the M365 tenant — and they’re already in the building until at least January 2027 on the voice contract.
2. The 3CX contract is carved out. This RFP is not for 3CX; it’s for everything around it. That carve-out limits incumbent leverage but creates a coordination handoff risk that the Coalition is asking the new IT vendor to absorb.
3. The “Failure to Perform Prior Contracts” clause (Section IV.M.5) lets ELCB disqualify a Proposer who previously failed to perform satisfactorily, was notified, and failed to cure — or whose contract was terminated for cause by ELCB, any Florida state agency, or any Children’s Services Council. Incumbents with clean records benefit from this clause; vendors with a problematic ELC or Children’s Services Council history should think carefully before responding.

For challengers, the right move is to ask written questions about the incumbent relationship, the documented state of the environment, and the existence of a transition plan or knowledge-transfer commitment from the outgoing provider. Coordination obligations between competing vendors are notorious sources of contract disputes — get the terms documented before you bid, not after.

Drafting Inconsistencies Worth Flagging (and Asking About)

This RFP carries enough internal inconsistencies that responsible proposers should clean them up via written inquiry before May 20:

• Attachment G, Fatal Criteria #1, states that the application must have been received by “2:00 p.m. on April 21, 2020 (EST)” — clearly leftover template language from a prior cycle. The actual deadline per Section III is May 25, 2026. Ask ELCB to confirm in writing via addendum.
• Schedule of Events table in Section III contains a block of Section 3.5.2/3.6 scope language pasted into the “Last day to submit written inquiries” row. The actual deadline is identifiable (May 20, 2026 at Noon), but a clean reissuance via addendum protects everyone.
• Section 3.1.5.2 appears immediately after Section 3.1.4.1 — the numbering jumps from 3.1.4 to 3.1.5.2 with no 3.1.5 or 3.1.5.1.
• Schedule of Events lists no specific date for the Notice of Intent (“N/A”) despite the Notice being mandatory and gating.
• Section 3.7 (Services Not Included) is the correct numbering in one place and Section 3.6 in another, with the same content.
• The “Connectivity Information” / “Firewalls” subheadings appear with no content beneath them before Section 3.1 begins — suggesting more was intended to be specified about the firewall environment than appears in the document.

These are the kinds of items that, left unaddressed, become protest fodder later. A vendor who files clean written inquiries forcing addendum corrections is doing themselves and the Coalition a favor.

Submission Mechanics: The Old-School Format Requirements Are Real

A few format requirements that have killed otherwise-strong proposals in similar procurements:

• Hard-copy delivery is mandatory. Email and fax are explicitly rejected. Build courier or hand-delivery into your timeline — for Tallahassee-based vendors, that’s a same-day or overnight logistics commitment to Melbourne.
• One original with blue-ink signatures plus six paper copies plus one electronic copy on a flash drive or CD as PDFs viewable in Adobe Acrobat Reader. The “Original” must be clearly marked.
• 18-page narrative cap, 11-point font, 1.0 line spacing, 8.5″ x 11″, tabbed sections. Budget pages and certifications are excluded from the count.
• Outer envelope must be labeled: “RFP 2026-IT-01 — Proposal for Hosted Information Technology and Support Services.”
• All addenda must be incorporated — failure to incorporate any addendum renders the proposal non-responsive (Section IV.M.9). If ELCB issues addenda between May 20 and May 25, you need to acknowledge them in your final response.

Protest Posture Under § 120.57(3)

This is a 287 procurement subject to Chapter 120 protest procedures. The relevant mechanics:

• Notice of protest: Within 72 hours of electronic posting of the notice of intended award, excluding weekends and state holidays.
• Formal written protest: Within 10 days after the notice of protest is filed.
• Bond requirement: A bond payable to the Coalition equal to 1% of the Coalition’s estimate of the total Contract amount, per § 287.042(2)(c), F.S. Cashier’s check or money order accepted in lieu.
• Cone of silence: From RFP release through 72 hours after posting of intended award (excluding weekends and state holidays), proposers may not contact ELCB employees or Board Members except in writing to the sole Point of Contact. Violations may be grounds for rejection.

The 1% bond figure is worth thinking about up front. For a three-year contract that’s likely in the $200,000–$450,000 range based on typical 50-user MSP pricing, you’re looking at a $2,000–$4,500 bond per year of contract value. Not prohibitive, but build it into your protest-readiness analysis.

Strategic Takeaways

For incumbents (or vendors with the inside track): Your advantage is real but defensible. Document your transition plan, your knowledge transfer obligations to and from the 3CX vendor, and your continuity-of-staff commitments. Section IV.B.3 explicitly asks about continuity of staff — this is your section.

For challengers: File written inquiries by May 20. Force ELCB to clean up the drafting inconsistencies by addendum. Ask specifically about (1) the identity of the incumbent and any coordination obligations between the new IT vendor and the existing 3CX provider, (2) the current state of the SonicWall environment and licensing status, (3) whether ELCB will provide a current network diagram and asset inventory pre-bid, and (4) whether the “fixed fee with cost-per-user pricing” model means a true unit-price contract or a flat fee with a separate per-seat add-on rate.

For everyone: File the Notice of Intent today. Build the seven-copy production timeline backward from a May 22 ship date to Melbourne. Confirm your federal certifications are current and that your subcontractors can flow down the Attachment F debarment certification.

This is a manageable opportunity for an MSP with non-profit and federally-funded client experience. It is a difficult opportunity for an MSP who has never assembled a Uniform Guidance certifications package and is reading 2 CFR Part 200 for the first time on a three-week clock.