Answers for district IT

How do districts track federally funded devices for audit?

Federal grant rules require districts to keep property records that identify each item, its source of funding, its acquisition cost and date, its location and condition, and its ultimate disposition — and to physically verify those records at least every two years. The practical implication is that funding source has to be a field on the asset, recorded at purchase, not reconstructed from purchase orders three years later during an audit. Districts that tag funding at intake pass this easily; districts that don't spend weeks reverse-engineering it.

What the federal property rules actually require

The Uniform Guidance in 2 CFR Part 200 sets the property standards that flow through most federal education funding — ESSER, Title programs, IDEA, and others. The equipment records provision requires records that include a description of the property, a serial number or other identification, the source of funding including the federal award identification number, who holds title, the acquisition date and cost, the percentage of federal participation in the cost, the location, use, and condition of the property, and any ultimate disposition data.

That is a long list, and the part districts most often miss is not the serial number — it is the funding attribution. Which award paid for this specific machine, and what percentage. When a device was bought with a blend of federal and local money, or when a purchase order spanned multiple funding sources, that percentage is the thing nobody can reconstruct later.

The rules also require a physical inventory of the property and reconciliation with the records at least once every two years, plus a control system adequate to safeguard against loss, damage, or theft, with any loss investigated. Note the wording: reconciliation, not just a count. Someone has to compare what was found against what the records claim and explain the differences.

Finally, there are disposition rules. Equipment above a certain per-unit threshold that is no longer needed for the original program has specific disposition requirements, and the district may owe the federal share of its remaining value. Below the threshold the rules are looser, which is why most individual Chromebooks are treated as supplies rather than equipment — but the district's own capitalization policy and any tighter state requirements still apply, and many states are stricter than the federal floor.

Record funding source at the point of purchase

The mechanism that makes all of this tractable is simple: when devices are received, the funding source is attached to the asset records as part of intake, not left implied by the purchase order.

The cleanest approach is to manage funding sources as first-class objects — a named list like "ESSER III," "Title I FY26," "Local capital," "E-Rate Category 2" — and attach one, or a weighted split, to each purchase order. Then every asset received against that PO inherits its funding attribution automatically. This is where the leverage is: nobody types a funding code 800 times, and the attribution is consistent by construction.

Keep the purchase order itself in the system, with vendor, date, cost, and the award identifier. During an audit the request is usually "show me the documentation for these twelve devices," and being able to jump from a serial number to its PO, its cost, and its funding source in one click is the difference between an afternoon and a week.

Capture acquisition cost per unit, not just PO total. The per-unit cost is what determines whether an item crosses the equipment threshold and what the federal share of any disposition is worth. It is trivial to record at receipt and painful to allocate later.

Record warranty at the same time. It is not a federal requirement, but it comes from the same paperwork and you will want it for every other reason.

The biennial physical inventory

The every-two-years physical inventory is the requirement most districts are least prepared for, because it is the one that requires people to walk around buildings.

Do it as a scan sweep. A staff member walks a room or a cart with a scanner — a phone camera works fine — and captures every asset tag present. The system compares what was scanned against what it expected to find in that location, and produces three lists: found where expected, found somewhere unexpected, and expected but not found. That third list is the one that requires investigation, and the federal rules do require investigation of losses.

Scope it sensibly. You do not need to physically locate every student take-home Chromebook simultaneously; a combination of scan sweeps for stationary and stored equipment plus a custody attestation campaign for assigned devices covers the ground. What matters is that you can show a systematic verification with a date and a documented resolution of discrepancies.

Write down the results. The audit finding is rarely "you lost devices" — it is "you cannot demonstrate that you verified." A dated reconciliation report, with the exceptions and what was done about each, is the artifact. Keep it with your grant documentation, not just in the asset system.

Schedule it rather than reacting to it. Districts that run a sweep every spring as a matter of routine are never scrambling, and the annual cadence also keeps the underlying records much cleaner than a biennial scramble does.

What auditors actually ask for

In practice, a single audit or a state monitoring visit tends to converge on a few requests. First: a complete list of equipment purchased with the award, with the required data elements. If your asset system can filter by funding source and export, this is a two-minute task; if funding lives only in the finance system, it is a reconciliation project.

Second: a sample. The auditor picks a handful of line items and asks you to physically produce the device, or at minimum to show its current location, condition, and assignment. This is where custody records earn their keep — being able to say "serial ABC123 is checked out to a student at the middle school, here is the checkout date" is a complete answer.

Third: evidence of the physical inventory and reconciliation. Date, method, results, and what happened with the discrepancies.

Fourth: disposition records for anything retired. When a device is disposed of, record when, how, to whom, and what proceeds if any. Devices that simply disappear from the record are the worst possible answer — a device marked disposed with a date and a method is fine; a device that stopped existing in your system is a finding.

A related note on ESSER specifically: the funds have obligation and liquidation deadlines that have now largely passed, but the property records for equipment bought with them persist for the full record-retention period, generally several years after the final expenditure report. Do not purge the funding attribution just because the grant closed.

Practical setup for a district starting from behind

If your current records do not have funding attribution, start with what still matters rather than trying to reconstruct everything. Devices bought with the largest awards, still in service, and above your capitalization threshold are the ones worth backfilling.

Work from purchase orders. Pull the POs for each award, match them to the serial ranges or receiving records, and bulk-tag those assets with the funding source. Most asset systems support a bulk update or an import for exactly this. Where a PO blended funding, record the split percentage rather than picking one source.

For devices you genuinely cannot attribute, say so in your documentation rather than guessing. An honest note that pre-2022 acquisitions lack per-unit funding attribution, alongside a policy change with a date showing when you started capturing it, reads far better in an audit than an attribution someone invented.

Then close the gap going forward with a rule: no receiving without a PO, no PO without a funding source. That single constraint, enforced by the system rather than by memory, is what makes the next audit boring.

Common questions

What does 2 CFR 200 require in equipment records?

A description and serial or other ID, the source of funding including the federal award identification number, who holds title, acquisition date and cost, the percentage of federal participation, the location, use, and condition, and ultimate disposition data. It also requires a physical inventory reconciled to the records at least every two years.

Do individual Chromebooks count as federal 'equipment'?

Usually not at the federal level, since most fall below the per-unit equipment threshold and are treated as supplies. But your district's own capitalization policy and your state's rules may be stricter, and grant-specific conditions can impose tracking regardless. Many districts track them fully anyway because they need the custody records for other reasons.

How often do we have to physically inventory federally funded devices?

At least once every two years, with the results reconciled against the property records. The reconciliation is the part that matters — a count with no comparison to what the records claimed does not satisfy the requirement, and discovered losses must be investigated.

ESSER has ended. Can we stop tracking devices bought with it?

No. Property and record-retention obligations continue past the spending deadline, generally for several years after the final expenditure report, and disposition of the property still has rules attached. Keep the funding attribution on those assets rather than clearing it when the grant closes.

What is the easiest way to attach funding source to thousands of devices?

Attach the funding source to the purchase order and let received assets inherit it. Nobody should be typing a funding code per device — that is where the inconsistency comes from. For a blended PO, record the split percentage, since federal participation percentage is a required data element.

What happens if we cannot find a device during the inventory?

Investigate and document it. The rules require a control system adequate to safeguard property, with losses, damage, and theft investigated. A documented investigation with a conclusion is an acceptable outcome; a device that quietly vanishes from the records is the thing that becomes a finding.

How Chalk approaches this

Chalk tracks purchase orders with managed funding sources, so assets inherit their funding attribution at receipt instead of being tagged one at a time. Scan sweeps produce a found-versus-expected reconciliation for the biennial physical inventory, attestation campaigns cover devices that are out with students, and warranty and disposition data live on the same record. Exports are plain, so handing an auditor a filtered list is straightforward.

See the full feature catalog →

Run this playbook on your own fleet.

Chalk installs to a populated inventory from your SIS and Google Admin in about 30 minutes. Self-host free forever under AGPL-3.0, or let us host it — priced by fleet size, never per seat.