Software Development for NC Government Agencies: What Vendors Need to Know
Contracting software development to North Carolina state agencies, county governments, and municipalities involves strict procurement standards. Unlike private commercial projects where a deal closes on an informal handshake, public sector software must satisfy rigorous bidding rules, accessibility statutes, and security governance.
If you are an agency project manager preparing an RFP or exploring government software development services, here are the core procurement, technical, and regulatory requirements software vendors must satisfy in North Carolina.
1. Electronic Vendor Portal (eVP) Registration
All vendors seeking to bid on North Carolina state technology contracts must be registered and in good standing with the North Carolina Electronic Vendor Portal (eVP).
- Why it matters: State purchasing officers use eVP to verify company credentials, corporate registration with the NC Secretary of State, and eligibility to receive state funds under State Term Contracts (STC) or direct agency solicitations.
- Vendor status: Etherea Labs maintains active vendor registration within NC eVP, allowing streamlined contracting with state and municipal departments.
2. Section 508 & WCAG 2.1 AA Accessibility Standards
Public sector software must be fully accessible to all citizens, including people with visual, auditory, motor, or cognitive disabilities.
- In North Carolina, public-facing web applications and portals must comply with WCAG 2.1 Level AA standards and federal Section 508 mandates.
- Engineering teams must implement semantic HTML landmarks, verified color contrast ratios, full keyboard navigation, and screen-reader testing across JAWS and NVDA.
3. Data Privacy and Public Records Compliance
Government data is subject to public disclosure laws as well as strict privacy controls:
- Role-Based Access Control (RBAC): Strict authentication layers ensuring agency personnel only view records within their statutory authority.
- Immutable audit logs: Every database modification, user login, and record export must be timestamped and logged in compliance with state record-retention requirements.
- Encrypted storage: Data at rest must be encrypted using AES-256 standards, with all network transit enforced over TLS 1.3.
4. Clear Deliverables and Transparent SOWs
State purchasing guidelines favor fixed-deliverable or milestone-based contracts with visible acceptance criteria over open-ended hourly retainers.
At Etherea Labs, our government and institutional engagements follow structured deliverables:
- Upfront technical discovery and architecture documentation.
- Source code committed to state-governed Git repositories with zero proprietary vendor lock-in.
- Automated testing pipelines and operational runbooks for internal IT handoff.
- Formal executive documentation available via our Capability Statement.
To review technical capabilities or discuss an upcoming North Carolina public sector procurement, contact our software architects.