Right-Sized Public Tech field kit

Grant or subrecipient monitoring

A working session for building one defensible trail from subaward setup through monitoring, follow-up, and closeout.

For K-12 program, grants, finance, procurement, and compliance staff

Factual resources last verified August 26, 2026

Use this kit when

The workload is real, but the review path is not.

  • Subrecipient evidence lives across email, shared drives, spreadsheets, and finance systems.
  • Program and finance teams cannot see the same open findings and corrective actions.
  • Reporting is collected, but risk decisions and follow-up are difficult to reconstruct.

Minimum review packet

Bring evidence, owners, and open questions.

Packet item 1

Award and program requirements, including the current Assistance Listing and agency terms

Packet item 2

Subaward record and required subaward information

Packet item 3

Documented pre-award or annual risk evaluation

Packet item 4

Financial and performance reports for the period

Packet item 5

Monitoring notes, audit results, site-visit records, findings, and corrective actions

Packet item 6

Payment, suspension, closeout, and record-access rules confirmed by the responsible local officials

Working sequence

A 45-minute review.

  1. Confirm the relationship and rules

    Determine whether the organization is a subrecipient or contractor and identify the current award, program, agency, state, and local requirements. Do not rely on a generic checklist for that determination.

  2. Record the risk basis

    Document the factors used to set the monitoring approach and who approved the result.

  3. Map each requirement to evidence

    For every required report or control, name the owner, due date, evidence, review method, and follow-up path.

  4. Work the exceptions

    Separate missing, late, inconsistent, and unacceptable evidence. Assign a corrective action, owner, due date, and escalation rule.

  5. Close with a decision record

    Record whether monitoring is complete, additional action is required, or a locally authorized remedy must be considered.

Leave with

A decision record, not another discussion.

  • Current requirements and evidence map
  • Risk-based monitoring plan
  • Open findings and corrective actions with owners and dates
  • Documented follow-up and escalation decisions
  • Closeout readiness and unresolved questions

Local verification required

  • Federal, state, program, award, and local requirements may differ. Verify the current rule set with the awarding agency and responsible local officials.
  • This kit does not determine whether an entity is a subrecipient or contractor and does not provide a legal conclusion.
  • Collect only the data required for the monitoring purpose. Apply approved retention, access, and destruction rules.

Primary sources

What this kit relies on.

Data Security: K-12 and Higher Education

U.S. Department of Education Student Privacy Policy Office. Current resource hub. Last verified August 26, 2026.

Safeguarding student records, data security, data flows, retention, destruction, and online-service considerations.

Commercial disclosure

Related JSTK option: GrantDesk

Proposed bounded pilot, not a finished product

JS Technology Solutions publishes this field guide and offers GrantDesk. Review the neutral workflow above before considering the product.

When it may fit

  • One program has a clear monitoring workflow, evidence set, and decision owner.
  • The team needs intake, reminders, evidence review, findings, and follow-up in one traceable lane.
  • A pilot can avoid protected student data or use an approved minimum data set.

When it does not fit

  • The team needs a full enterprise grants platform across many unrelated programs now.
  • The main gap is an unresolved legal, program, or subrecipient classification decision.
  • No internal owner can review findings and make the actual compliance decisions.
Visit GrantDesk

Cut the next scope.

Turn this review into a bounded working brief.

Open the Scope Cutter