WORKFORCE WONKERY · QUICKSTART · AJCC + PARTNERS · WORKING · ABOUT 12 MIN
Manage an AJCC Partner Handoff or MOU/IFA Issue
Use this when the written partner agreement, shared-cost arrangement, or actual customer handoff no longer matches how the AJCC system is working. The goal is to restore access quickly while deciding whether a formal agreement or operating change is needed.
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 the written partner agreement, shared-cost arrangement, or actual customer handoff no longer matches how the AJCC system is working. The goal is to restore access quickly while deciding whether a formal agreement or operating change is needed.
You should know what failed, who owns it, what agreement or rule controls, what can be fixed immediately, and whether the MOU, IFA, referral protocol, or partner commitment needs formal change.
The current controlling federal or California source, grant or agreement terms, and your adopted local policy.
Current MOU/IFA, operator agreement, partner schedule/commitments, referral workflow, shared-cost assumptions, recent examples, customer-impact facts, and any certification or accessibility criteria involved.
Define the gap → identify owner → identify authority/agreement → restore customer access where possible → diagnose root cause → decide operating fix vs formal amendment → verify follow-through.
1. Define exactly what is not working
Is the problem a failed referral, missing partner coverage, weak direct linkage, co-enrollment confusion, shared-space/cost disagreement, accessibility issue, certification concern, or a written commitment that no longer reflects reality? Name the gap before convening everyone.
2. Identify the owner and controlling document
Determine whether the operator, WDB staff, partner program, provider, facilities/fiscal team, or multiple parties own the problem. Then identify the controlling MOU, IFA, operator agreement, partner statute/program rule, local procedure, or certification standard.
3. Protect the customer while the system problem is being fixed
If possible, restore access immediately through a temporary operating solution that does not change a material agreement term. Assign the initiating and receiving owner, define what information can be shared, confirm consent/security, and establish the expected response.
4. Reconcile agreement assumptions to actual operations
For MOU/IFA issues, compare partner presence, square footage, staffing, technology, shared services, cost pools, benefit, access method, and service commitments with the assumptions in the agreement. For referral issues, compare the written workflow with what staff actually do.
5. Decide whether the fix is operational or formal
A broken workflow may need training, ownership, or tracking. A material change to partner commitments, access method, shared-cost allocation, space, governance, or scope may require a formal amendment or approval process.
WORKED EXAMPLE
The MOU says a required partner provides onsite service two days per week, but staffing changed months ago and customers now receive only a phone number. Referrals are rarely confirmed.
Strong response: restore a meaningful access method now, define a completed-handoff workflow and owner, compare the new access arrangement to partner obligations and certification standards, and determine whether the MOU/IFA assumptions or partner contribution require formal amendment.
Required, local, or judgment?
| Question | Who controls it? |
|---|---|
| Required-partner and one-stop access obligations | Federal/state requirement |
| Specific local referral workflow and service standards | MOU/local procedure |
| IFA methodology and partner contributions | Applicable federal/state rules + negotiated local agreement |
| Immediate operating workaround within existing commitments | Staff/operator/partner judgment within authority |
| Material agreement amendment or unresolved dispute | Required signatories/governance + escalation |
Reviewer lens
- Does the written agreement match actual practice?
- Can customers reach the partner in a meaningful way?
- Are referrals completed and confirmed, not just sent?
- Do shared-cost assumptions still match current operations?
- Is the proposed fix within staff/operator authority, or does it change a material agreement term?
What good documentation looks like
Keep the specific gap + affected customers/process + controlling agreement/rule + responsible owner + immediate workaround + root cause + permanent fix + amendment/approval decision + follow-up date/result. For MOU/IFA issues, retain the assumptions and calculations supporting any revised cost or partner commitment.
Stop and escalate when
- The issue affects required-partner obligations or AJCC certification.
- Shared-cost methodology or partner contribution is disputed.
- Physical/programmatic accessibility or customer-rights issues are involved.
- Confidentiality or participant-data sharing is unclear.
- Board/CLEO/signatory action, formal dispute resolution, or legal interpretation may be required.
Go deeper: AJCC Operations + Partner Integration → · Customer Journey →
Use with: the current MOU/IFA, operator agreement, certification criteria, referral procedures, partner schedules, and cost-allocation support.
Source checked as of September 18, 2026.
SOURCE + TRUST RECORD
Source checked as of September 18, 2026. Source basis: WSD18-12 · WIOA Memorandums of Understanding · 20 CFR Part 678 · One-Stop System Joint Provisions · EDD Active Directives.
Check result: The required-partner, MOU, infrastructure-cost, reconciliation, and local-agreement concepts are supported by current federal rules and California’s active MOU directive. WSD18-12 specifically requires partner contributions to be reconciled on a regular basis under the MOU methodology. The page’s handoff troubleshooting, temporary operating workaround, and escalation sequence are recommended practices; material changes to commitments, cost allocation, access, or scope should be tested against the signed MOU/IFA and required approval process. 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.