California’s Pause on VC Diversity Reporting: What It Means and How to Prepare Anyway

If you’re a venture firm or a startup founder in California’s orbit, the state has temporarily paused enforcement of its law that requires VCs to submit demographic data on the founders they back. The law remains on the books, but the deadline and penalties are on hold while officials reassess timing and guidance.

What should you do now? Keep building light‑weight, privacy‑safe collection and reporting processes so you can flip the switch when enforcement resumes. Don’t tie demographic data to investment decisions, document consent, and monitor state updates. This guide explains who’s likely covered, what data to plan for, the trade‑offs of preparing early, and concrete steps to stay compliant-ready without overengineering.

Quick context: What changed and why it matters

• California enacted a venture-focused diversity reporting regime intended to standardize, aggregate, and publish demographic information about startup founders that receive VC funding.
• After pushback and logistical concerns from investors, the state has paused enforcement and extended timelines. During the pause, deadlines and penalties are delayed, but the statute hasn’t been repealed.
• Expect clarifications on scope, definitions, and filing mechanics. Agencies may adjust forms, portals, or FAQs before enforcement restarts.
• Bottom line: treat this as a deferral, not a cancellation. The easiest path is to get "compliance ready" with opt-in, de-identified data collection that you can report quickly when required.

Who should read this

• Venture capital firms with any touchpoint to California (e.g., investing in California-headquartered companies, having a presence or personnel in the state, or actively soliciting deals or LPs there)
• Corporate venture arms and accelerators that make equity investments in early-stage companies
• Emerging managers and micro-funds that back California founders
• Startup founders who receive VC term sheets and are asked to self-report demographics
• Limited partners (LPs) evaluating manager readiness and governance

Are you likely in scope? A decision checklist

Because detailed scope turns on definitions and agency guidance, use this as a directional screen and confirm with counsel:

• Do you make venture-style equity investments in startups? If yes, likely relevant.
• Do you invest in companies headquartered or with substantial operations in California? If yes, higher likelihood of coverage.
• Do you have personnel, an office, or significant deal activity in California? If yes, plan to comply.
• Are you a corporate venture arm investing alongside traditional VCs? If yes, assume inclusion unless clearly excluded by guidance.
• Are you primarily an angel syndicate or crowdfunding portal? Applicability may vary; check definitions and exemptions.
• Are you an out-of-state VC with occasional California deals? You may still be covered based on investment activity; prepare a light process.
• Do you only buy secondary shares without participating in primary rounds? Gray area—seek advice based on how “covered investments” are defined.

If two or more of the above are “yes,” build a lean data collection plan now.

What data to expect (and how to scope it)

California’s regime is designed around founder self-identification. Specific fields may evolve, but you should anticipate optional, self-reported demographics commonly seen in government and workplace surveys, including:

• Race and ethnicity (using standardized categories)
• Gender identity
• Potentially additional categories enumerated by the state (for example, disability status, veteran status, or sexual orientation)—treat these as optional and sensitive
• Founders’ role and ownership at the time of investment
• Company basics (e.g., headquarters location, industry, round type)

Key scoping questions to settle early:

• Who counts as a “founder”? Define a consistent standard (e.g., named founder(s) and any early executives with meaningful equity at first check) and stick to it.
• What’s the measurement point? Many regimes expect data at time of your initial investment. Document this point clearly.
• What if a founder declines to respond? Nonresponse must be allowed; structure your tool to record “prefer not to say.”
• Multiple rounds or follow-ons? Plan to avoid duplicate counting. Track by company and round date.
• Portfolio companies outside California? You may still need to report if your firm’s activity triggers coverage; collect consistently across your book to simplify reporting.

Practical plan: Prepare without overbuilding

Here is a phased, low-regret approach that most firms (from micro-funds to multi-fund platforms) can implement during the pause.

Phase 1: Governance and policy

• Adopt a short written policy: state that demographic data is optional, used for regulatory reporting and aggregated insights only, and never considered in investment decisions.
• Assign an owner: typically Operations, Compliance, or IR. For small funds, a partner plus an ops lead is sufficient.
• Create a data map: list what you’ll collect, from whom, when, and where it’s stored. Include deletion timelines.
• Draft founder communications: a one-page explainer and a short FAQ to accompany your survey link.

Phase 2: Tooling and workflow

• Choose a secure collection method:
  • Minimalist: a privacy-minded survey tool with SSO and data export controls.
  • More robust: the same through your fund admin or a specialized DEI data vendor.
• Use unique links per founder to reduce errors and duplicate entries.
• Keep the dataset separate from deal memos and investment committee docs to avoid decision-making taint.
• Build simple fields aligned with likely categories and include “prefer not to say.”
• Add basic validations (e.g., per-company/per-round dedupe) and a note for later audit.

Phase 3: Privacy by design

• Consent and notice: make it explicit that providing data is voluntary, will be used only in aggregated form for compliance and reporting, and won’t affect funding decisions.
• Minimize access: restrict raw data to one or two designated individuals; share only aggregates internally.
• De-identify wherever feasible: report rates and counts at the cohort level; avoid free-text fields.
• Data retention: set a schedule to retain only as long as necessary for compliance and trend analysis, then purge.
• Security: store in a system that supports encryption at rest and audit logs.

Phase 4: Founder experience

• Send the request after a term sheet or at closing, not at first meeting.
• Use empathetic language:
  • "We’re asking for optional, self-identified demographic information to meet anticipated regulatory reporting and to improve ecosystem transparency. Your response is entirely voluntary and will not impact our investment or partnership."
• Keep it fast: <3 minutes to complete.
• Offer a point of contact for questions or deletion requests.

Phase 5: Monitoring and dry runs

• Track official updates from the relevant California agency and any implementation FAQs.
• Do a mock export and “report”: verify you can produce the expected aggregates quickly.
• Keep a change log: if categories or forms change, note the date and rationale.

Pros and cons of preparing now

Pros

• Avoid a last-minute scramble when enforcement restarts
• Build trust with LPs who expect credible DEI governance
• Identify data quality issues early (e.g., duplicate founders, missing rounds)
• Minimal marginal cost if you implement lean processes

Cons

• Potential rework if the state significantly changes forms or categories
• Operational overhead for small teams
• Sensitivity concerns from founders if messaging is clumsy

How to de-risk the cons: keep the process narrow, optional, and adaptable; do not finalize your schema in stone; treat the first cycles as pilots.

How this compares to other regimes

• Public-company board diversity disclosures: Some U.S. exchanges and state laws have pushed for board-level transparency; the venture regime focuses specifically on private startup founders and VC activity.
• Workplace EEO reporting: Employers report workforce demographics; here, the reporting is centered on funded founders, not employees.
• Global context: European and UK rules increasingly target corporate governance and workforce diversity metrics, not founder-level venture data. If you invest globally, align your taxonomy loosely to widely used categories, but keep local compliance streams distinct.

The takeaway: California’s regime is relatively unique in spotlighting the demographics of founders receiving venture capital. That makes the mechanics and privacy framing especially important.

Special cases and gray areas

• Corporate venture capital (CVC): If your CVC makes direct startup investments, assume you’ll need to collect founder data akin to traditional VCs.
• Accelerators and venture studios: If you invest for equity, your activity may be in scope. If you provide only services without equity, you may fall outside—but double-check.
• Angel syndicates and SPVs: Applicability depends on structure and whether the manager is treated like a venture investor under the statute.
• Out-of-state funds: Occasional California investments can still trigger obligations; build a lightweight process for all new deals to avoid guesswork.
• Secondary transactions: Pure secondary purchases may be treated differently than primary financings; seek guidance based on definitions and agency FAQs.

For founders: What to expect and how to respond

• Participation is voluntary: You can decline to share or answer only some questions.
• Your funding should not depend on your answers: Reputable firms firewall this data from investment decisions.
• Ask how your data is handled: Who sees it? How long is it stored? Will it be shared outside the firm? Is it de-identified?
• Keep your own record: If you choose to respond, save a copy; it helps avoid duplicate surveys later.
• You can request deletion: Firms should honor reasonable deletion requests unless retention is required by law.

LPs: Questions to ask your managers during the pause

• Do you have a written policy governing founder demographic data and its separation from investment decisions?
• What is your collection plan and vendor stack? How do you protect privacy and minimize access?
• Can you produce an audit trail and aggregated portfolio view within 10 business days?
• How will you adapt if the state changes categories or reporting templates?
• How are you communicating with founders to maintain trust?

Common pitfalls to avoid

• Collecting data pre‑term sheet: It can feel coercive; wait until commitment.
• Embedding demographic fields in deal memos or IC decks: Keep them out of decision files.
• Over-collection: Stick to anticipated categories and avoid excessive detail.
• Treating nonresponse as a data point about commitment: Do not interpret or pressure; neutrality is key.
• Ignoring privacy law basics: Even optional data deserves consent, minimization, and secure storage.

Key takeaways

• Enforcement is paused, not repealed. Expect reporting to resume with updated guidance.
• Build a lean, optional, privacy-by-design collection process now; it pays off later.
• Keep demographic data out of investment decisions and restrict access internally.
• Communicate clearly with founders; make it fast, respectful, and voluntary.
• Monitor state updates and be ready to adapt categories and templates.

FAQ

Q: Is California’s venture diversity reporting law canceled?
A: No. The state has temporarily suspended enforcement and extended timelines. The statute remains in effect unless lawmakers repeal it.

Q: Should we stop collecting data until the state finalizes guidance?
A: No. Continue preparing with a light, optional, privacy-safe process. That way you can comply quickly when enforcement resumes.

Q: We already collected founder data. Is it safe to keep?
A: Yes, if you obtained consent, limit access, and have a retention schedule. Consider migrating to a secure system and documenting your controls.

Q: Do angel investors or syndicates have to comply?
A: It depends on structure and whether the activity fits the law’s definitions. Many pure angels will fall outside, but managers running pooled vehicles may be covered. Confirm with counsel.

Q: Can we avoid this by investing only via SPVs or secondaries?
A: Not necessarily. Applicability turns on definitions and activity in California. Rely on legal advice rather than structure alone.

Q: Will founder-level data become public?
A: The intent is typically to publish aggregated statistics, not individual identities. Still, treat raw data as highly sensitive and protect it accordingly.

Q: What if a founder refuses to respond?
A: That’s acceptable. Your system should record nonresponse without pressure. Never make funding contingent on answers.

Q: We’re a non-U.S. fund with a handful of California deals. Do we need a full program?
A: Likely not; build a narrow process for those deals—standardized survey, consent language, secure storage—and be able to export aggregates on request.

Source & original reading: https://www.wired.com/story/california-temporarily-lets-vcs-off-the-hook-for-dei-reporting/