Preparing for a Federal Program Monitoring Review

When to begin: Maintain readiness continuously; mobilize immediately when the selection notice arrives
Organizing unit: Current program instrument item and its associated evidence request
Submission system: California Monitoring Tool (CMT)

Start with the assigned scope

The goal is not to assemble the largest possible document library. It is to demonstrate, clearly and efficiently, that each assigned requirement operates across the LEA. Begin with the selection notice, current-year instruments, assigned programs and sites, review format, CDE review lead, and dates shown in CMT.

Prepare by requirement, not by department. One instrument item may depend on program, fiscal, human resources, data, governance, and school-site evidence. Organize the work around what must be proven.

At notification: establish control of the review

Read the selection notice and record the programs, schools, review format, review dates, and required meetings.
Download or record the exact current-year instruments assigned to the LEA.
Name one executive sponsor, one FPM coordinator, program owners, fiscal support, site contacts, and a backup for every critical role.
Confirm the assigned CDE FPM Review Lead and the approved communication path.
Verify CMT access early. A California Department of Education account alone does not grant access to an active review.
Confirm which users may upload, link, comment, and certify evidence requests.
Create one master evidence matrix and one controlled calendar for the entire review.

Build an evidence matrix

Use one row for every evidence request or testable instrument component. A workable matrix records:

Requirement control

Program and instrument item
Plain-language requirement
Legal authority
Evidence request number
Responsible owner and backup

Evidence control

Document or system source
Applicable year, population, and site
File name and CMT link status
Gap, corrective action, and due date
Internal validation and certification status

Use a complete evidence chain

Evidence layer	What it should demonstrate	Possible examples
Authority and design	The LEA has an accurate, current requirement and an assigned process.	Board policy, administrative regulation, approved plan, procedure, role assignment
Implementation	The required process actually occurred.	Dated notices, agendas and attachments, service records, completed forms, system extracts
Participation and service	The right students, families, staff, or advisory groups were included.	Rosters, invitations, sign-ins, consultation records, participation logs
Fiscal traceability	Funds were planned, approved, spent, and monitored for allowable purposes.	Ledgers, time documentation, allocation methods, purchase support, reconciliations
Monitoring and correction	The LEA checks its own implementation and responds when practice differs from policy.	Review logs, site monitoring, exception reports, corrective-action records, follow-up evidence

Remove information that is irrelevant to the review. When personally identifiable or sensitive records are necessary, follow CDE’s secure submission instructions and the LEA’s privacy controls.

A practical preparation sequence

Scope: Translate the selection notice and instruments into a complete assignment list.
Crosswalk: Map every item to its owner, local process, sites, data source, and evidence.
Collect: Retrieve authoritative records from the applicable review period.
Test: Ask whether a reviewer can trace the requirement from policy through implementation and monitoring.
Correct early: Repair genuine current-practice gaps and document what changed; do not manufacture or backdate evidence.
Upload and link: Place files in CMT and connect each file to the correct evidence request.
Validate and certify: Conduct a second-person review before an authorized CMT user certifies the request.
Prepare people: Help interview participants understand the requirement and locate authentic evidence without scripting their answers.
Monitor: Check CMT comments and requests regularly; comments are not necessarily delivered by email.

The CMT submission workflow

Uploading is not submitting. In CMT, the LEA uploads a document, links it to the appropriate evidence request, and then certifies that evidence request. Reviewers cannot see the documents until the evidence request is certified.

Upload the controlled file to the Documents area.
Link it to each evidence request for which it is relevant.
Review the file, label, date, scope, redaction, and link.
Certify the evidence request through an authorized agency administrator or coordinator.
Monitor CMT for reviewer comments, returned items, and additional requests.

Prepare sites and interview participants

Tell participants why the review is occurring, what program requirements are in scope, and how the process will run.
Confirm that staff can describe their actual responsibilities and show where records are maintained.
Include site administrators and relevant advisory groups when CDE identifies them for interviews.
Test technology, rooms, schedules, access permissions, and backup contacts before the review.
Do not coach participants to give a preferred answer. Consistent, authentic practice is stronger than a rehearsed response.

Common readiness failures

Evidence problems

An old policy is presented as current practice
A policy is supplied without proof of implementation
The document covers the wrong year, site, program, or student group
Counts or lists cannot be traced to a source system
Board minutes omit the plan, attachment, notice, or consultation record they reference

Workflow problems

Documents are uploaded but not linked or certified
Files are named inconsistently or duplicated without explanation
One employee holds all institutional knowledge and has no backup
CMT comments are missed because staff expect email alerts
The LEA corrects only the sampled school instead of the systemwide condition

For smaller LEAs

A small team can still create reliable separation of duties. Use the county office and CDE review lead for process clarification, cross-train at least one backup, keep the evidence matrix in a shared controlled location, and document services performed by contractors or consortia. Outsourcing a service does not outsource the LEA’s responsibility to demonstrate compliance.

When a finding is issued

Read the cited instrument item, legal authority, reviewer explanation, and stated resolution requirement together.
Determine whether the condition exists elsewhere in the LEA and identify the root cause.
Correct the procedure, implementation, and internal monitoring—not only the document submitted during review.
Submit concise evidence showing that the correction has actually been implemented.
Upload, link, and certify the resolution evidence by the deadline shown in the current Notification of Findings and CMT.
If additional time is genuinely needed, coordinate a Resolution Agreement with CDE before the operative deadline.

Deadline caution: CDE’s current Compliance Monitoring page describes a 60-calendar-day response period and a maximum of 240 calendar days from the last review day under a Resolution Agreement. Older CDE FAQ and CMT pages still show 45 and 225 days. Use the dates assigned to the current review and confirm discrepancies with the FPM Review Lead.

Final pre-review check

Every assigned instrument item has an owner and status.
Every certified request contains evidence for the correct period and scope.
Every file is readable, appropriately redacted, clearly named, uploaded, and linked.
Fiscal and program evidence reconcile where they describe the same activity.
Sites and interview participants know the schedule and can explain actual practice.
The coordinator is monitoring CMT comments and has a response protocol.
Leadership knows which unresolved gaps require immediate correction.