WORKFORCE WONKERY · QUICKSTART · POLICY IMPLEMENTATION · WORKING · ABOUT 12 MIN
Turn a New Directive Into Local Practice
Use this when a new WSD, TEGL, WSIN, law, regulation, grant term, or other policy changes how your Local Area should operate. The goal is to move from “we read it” to a documented implementation plan with owners, deadlines, local decisions, procedure changes, training, and evidence of completion.
Before you act
Orientation, not instruction. This AI-assisted playbook does not receive human legal or compliance review. Automated source check completed September 18, 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 new WSD, TEGL, WSIN, law, regulation, grant term, or other policy changes how your Local Area should operate. The goal is to move from “we read it” to a documented implementation plan with owners, deadlines, local decisions, procedure changes, training, and evidence of completion.
You should know what changed, who is affected, what is mandatory versus discretionary, what local documents/processes must change, who owns each action, and how implementation will be verified.
The current controlling federal or California source, grant or agreement terms, and your adopted local policy.
The source document, effective/issue dates, superseded guidance, current local policy/procedure, contracts or provider instructions, system/data impacts, board/CLEO delegations, and staff/partner owners.
Source + authority → what changed → who is affected → required vs discretionary → local decision → procedure/system change → training/communications → implementation date → evidence → follow-up.
1. Identify the source and authority
Start with the actual document. Is it law, regulation, federal guidance, California directive, information notice, grant term, or another source? Determine whether it is binding, interpretive, informational, draft, or temporary—and whether it supersedes prior guidance.
2. Write the change in plain language
State the operational difference in one or two sentences: Before, we did X. Now, the controlling rule requires/allows Y. Avoid copying pages of policy language into an implementation memo without identifying the actual change.
3. Separate required action from local discretion
Create two lists: what the Local Area must do and what it may choose to do. Then identify which local body or role owns the discretionary choice—staff, director, Local Board, CLEO, fiscal/procurement authority, or another entity.
4. Map every local surface the change touches
Check policy manuals, procedures, forms, CalJOBS workflows, provider agreements, procurement language, monitoring tools, board materials, websites, customer notices, partner processes, training materials, and fiscal controls. Policy implementation usually fails at the handoff between the source document and one of these operating surfaces.
5. Assign owners, deadlines, and verification
For each action, name the owner, due date, approval path, dependent task, and evidence that will prove the change is operational. “Email staff” is not implementation if forms, systems, agreements, or supervisory review still use the old rule.
WORKED EXAMPLE
EDD issues a directive changing a statewide eligibility or service requirement. Staff circulate the PDF and assume implementation is complete.
Strong approach: identify the exact change and effective date; compare it with current local policy; determine whether board action is needed; update the procedure, forms, CalJOBS instructions, provider guidance, monitoring checklist, and staff training; assign owners; and retain evidence that each affected surface was updated.
Implementation matrix
| Question | What to capture |
|---|---|
| What changed? | Plain-language before/after statement and source citation |
| Who is affected? | Programs, staff, providers, partners, participants, employers |
| What is required vs discretionary? | Mandatory actions, options, and decision owner |
| What local surfaces change? | Policies, procedures, forms, systems, contracts, monitoring, training |
| How will we know it is done? | Owner, due date, approval, evidence, and post-implementation check |
Reviewer lens
- Did staff use the actual source rather than a summary alone?
- Is the effective date clear?
- Are mandatory and discretionary elements separated?
- Is the correct local decision-maker identified?
- Were all affected procedures, systems, agreements, and monitoring tools reviewed?
- Is there evidence implementation occurred?
What good documentation looks like
Maintain a short implementation record showing source + issue/effective date + plain-language change + affected areas + required/discretionary split + local decisions + action list + owners/dates + approvals + updated documents/systems + training/communications + verification.
Stop and escalate when
- Two authorities appear to conflict.
- The directive changes or appears to change board/CLEO authority.
- A local policy conflicts with the new higher-level requirement.
- Implementation affects procurement, contracts, fiscal exposure, EO/accessibility, or legal rights.
- The effective date has already passed and the Local Area may have operated under an outdated rule.
Use with: the source directive/guidance, the Policy Library, current local policy/procedures, and the appropriate governance/approval documents.
Source checked as of September 18, 2026.
SOURCE + TRUST RECORD
Source checked as of September 18, 2026. Source basis: EDD Active Directives · EDD Policy and Guidance.
Check result: This page is primarily a Workforce Wonkery implementation method, not a prescribed state or federal workflow. The source check supports its core authority principle: identify the controlling issuance, status, issue/effective date, supersession, and mandatory versus discretionary provisions before changing local practice. The sequencing, implementation matrix, ownership model, and verification steps are recommended practice. 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.