WORKFORCE WONKERY · QUICKSTART · POLICY + GOVERNANCE · WORKING · ABOUT 12 MIN
Design or Revise a Local Workforce Policy
Use this when a Local Board needs to create, replace, or revise a policy governing WIOA programs, services, fiscal controls, providers, or system operations. The goal is to convert higher-level requirements and local discretion into a rule staff can actually implement and reviewers can actually test.
Before you act
Orientation, not instruction. This AI-assisted playbook does not receive human legal or compliance review. Automated source check completed September 22, 2026. Consequential claims were compared against the primary authorities identified in the Source + Trust Record below. Local policy, grant or contract terms, and required approvals may add rules or procedures, so check those before acting. Trust standard →
Use this when a Local Board needs to create, replace, or revise a policy governing WIOA programs, services, fiscal controls, providers, or system operations. The goal is to convert higher-level requirements and local discretion into a rule staff can actually implement and reviewers can actually test.
You should have a policy with a clear problem statement, source authority, required-versus-discretionary split, defined standards, decision owner, effective date, implementation plan, and version history.
The current controlling federal or California source, grant or agreement terms, and your adopted local policy.
Federal/state source documents, existing local policy, board/CLEO authority and delegations, operating procedures, stakeholder feedback where useful, monitoring findings, data, and implementation constraints.
Problem → source hierarchy → required vs discretionary → local objective → standard → exceptions → decision authority → implementation → board/CLEO action → version control.
1. Start with the problem the policy must solve
Do not begin by editing old policy language. State why the policy exists: inconsistent decisions, new state guidance, weak controls, outdated limits, access inequity, monitoring findings, changed program design, or another concrete operating need.
2. Build the authority stack
Identify the controlling sources in order: federal statute/regulation, DOL guidance where applicable, California law/directives, grant terms, Local Board/CLEO authority, then local procedure. Local policy should exercise discretion that actually exists; it should not restate a higher-level rule inaccurately or invent a restriction without authority or purpose.
3. Separate mandatory rules from local choices
Mark each major provision as required, locally discretionary, recommended practice, or procedure. This prevents staff preferences from becoming invisible “requirements” and helps future reviewers see why the Board made a particular choice.
4. Write standards that produce consistent decisions
Define who is covered, what is allowed or required, decision criteria, limits, documentation, approval authority, exceptions, appeals/escalation where appropriate, and effective date. Avoid vague phrases such as “reasonable” without explaining who decides and what evidence should support the judgment.
5. Test the policy against real scenarios before adoption
Run several common and edge cases through the draft. Ask frontline staff, fiscal/contract staff, providers, or partners what the language would make them do. If two competent readers reach different answers, the policy may need clearer standards or a defined escalation route.
6. Pair adoption with implementation
Board approval is not the finish line. Identify every procedure, form, agreement, CalJOBS workflow, monitoring tool, staff training, website, provider instruction, and customer-facing document that must change. Set an effective date that gives the system time to align.
WORKED EXAMPLE
A Local Board wants to revise its Individual Training Account policy. Staff begin by changing the dollar cap because that is the most visible issue.
Strong approach: first identify current federal/state ETPL and training requirements; clarify which standards are local choices; examine utilization, access, provider cost, exceptions, customer choice, and monitoring evidence; define the policy objective; test scenarios; then bring the Board a recommendation that makes the local discretion and operational impact explicit.
Policy design table
| Element | What good policy answers |
|---|---|
| Authority | What higher-level rule gives or limits this local authority? |
| Scope | Who, what programs, and what decisions does the policy cover? |
| Standard | What must staff/providers do or test? |
| Discretion | Where is judgment allowed, and who holds it? |
| Exceptions | When may the normal rule be varied, by whom, and with what evidence? |
| Implementation | What procedures, systems, training, agreements, and monitoring tools must change? |
Reviewer lens
- Can every major rule be traced to authority or an explicit local choice?
- Is the Board deciding something it actually controls?
- Would two staff members apply the standard consistently?
- Are exceptions and approval authority defined?
- Does the policy avoid duplicating procedure unnecessarily?
- Is implementation evidence planned?
What good documentation looks like
Preserve problem statement + source authority + redline/current policy + required/discretionary analysis + data/stakeholder input + scenario testing + staff recommendation + board/CLEO action + final policy + effective date + implementation checklist + superseded version.
Stop and escalate when
- The proposed local rule conflicts with federal or California guidance.
- It is unclear whether the Board, CLEO, fiscal authority, or staff holds the decision.
- The policy could create disparate access, EO, due-process, or legal concerns.
- The rule materially changes procurement, contract, or participant financial exposure.
- A “policy” is being used to solve what is really a staff-performance or procedure problem.
Use with: current WIOA statute/regulations, applicable California directives, Local Board/CLEO governance documents, local delegations, and the source material for the specific policy topic.
Source checked as of September 22, 2026.
SOURCE + TRUST RECORD
Source checked as of September 22, 2026. Source basis: EDD Active and Draft Directives · EDD Information Notices · WIOA Laws, Regulations, and State Plan resources.
Check result: This page is primarily a Workforce Wonkery policy-design method. EDD distinguishes final Active Directives, Draft Directives, and Information Notices, so the first policy-design question is what kind of authority the source actually carries. A draft is not final guidance, and an Information Notice should not automatically be treated as equivalent authority to a statute, regulation, grant term, or final directive. The source check supports the central distinction between controlling requirements and local discretion, but the drafting sequence, scenario testing, implementation checklist, version-control approach, and recommended policy structure are editorial operating practices rather than prescribed federal or state procedures. Local governance rules determine who must approve a specific policy. No human legal or compliance review was performed. Official sources and applicable local policy control.
Do not let the Quickstart replace the controlling source or turn a local practice into a rule.
The authority is unclear, an exception is needed, the facts are unusual, or the decision creates material fiscal, legal, civil-rights, data, procurement, or governance risk. Use the escalation guide →
Check the current directive, regulation, grant term, agreement, and adopted local policy before acting.