Skip to main content
Skier joke: I ski uphill! Downhill is for amateurs.

SDLA Compliance Resource

Maintain a Useful District Technology Plan Without Inventing a State Deadline

A strategic governance cycle for instructional technology, infrastructure, cybersecurity, accessibility, privacy, staffing, lifecycle costs, and continuity—not a fictitious annual filing requirement.

  • Technology Planning
  • Governance
  • E-Rate
Date(s)No general statewide or E-Rate annual technology-plan submission deadline; review on the locally adopted cycle and before material investments
Applies toLEAs choosing or locally required to maintain a technology plan; grant, bond, procurement, insurance, cybersecurity, or local policy may create separate planning duties

In Plain Language: E-Rate no longer imposes a general technology-plan requirement. Maintain a plan because coordinated technology decisions require one, and separately calendar any plan or approval required by a specific funding source or local policy.

Why this matters

Treating the plan as nonexistent creates fragmented purchases and unowned risk; treating it as a universal annual compliance filing invents work. The right control is a living, locally governed roadmap tied to budgets and service levels.

Primary ownership

Primary owner: technology leader with superintendent/cabinet sponsor. Handoff partners: instruction, special education/accessibility, cybersecurity/privacy, business/procurement, facilities, HR, libraries, communications, and site leaders.

From local obligations to a useful district technology plan: the SDLA ITO workflow

No general state or E-Rate deadline applies, so the plan's value comes from coordinated decisions and from any funding-specific duty. This SDLA ITO (Input, Transformation, Output) graphic shows how the planning obligations, the current technology environment, and instructional needs become the obligations inventory, the approved plan and roadmap, and the progress records.

SDLA ITO: eleven steps from the planning obligations, the current technology environment, and instructional needs, through an authority scan, a current-state assessment, outcome setting, and alignment to budget and governance, to the obligations inventory, the approved plan and roadmap, and the progress records.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers an authority scan, a current-state assessment, outcome setting, and alignment to budget and governance; Output covers the obligations inventory, the approved plan and roadmap, and the progress records. Review on the locally adopted cycle and before material investments.

Open the full-size workflow graphic

Operational workflow

  1. Inventory the actual planning obligations attached to local policy, funding, contracts, insurance, and grants.
  2. Assess instructional needs, access/equity, devices, network, applications/data, interoperability, cybersecurity, privacy, accessibility, support capacity, facilities, and continuity.
  3. Set measurable service outcomes, standards, owners, lifecycle costs, dependencies, and decision gates.
  4. Align projects to LCAP, budget, procurement, staffing, records, and emergency planning.
  5. Review progress and risks at a locally defined cadence; revise after material changes.

Implementation pathway

Authority scan
Current-state assessment
Outcomes/standards
Roadmap/budget
Governance review

Evidence to retain

  • Authority/dependency inventory
  • Current-state and risk assessment
  • Approved plan/roadmap
  • Budget/procurement alignment
  • Progress and revision records

Official guidance and help

Source review completed August 30, 2026. Verify current federal and California requirements, CDE/FCC guidance, local policy, public-meeting procedures, records, and final submitted or adopted state before acting.