Cenovel / Operator guides

E-Rate funding and equipment lifecycle

Record a funding cycle, connect site plans to identifiable equipment, review attribution and movement, and export the evidence currently held in Cenovel.

Reviewed against the application source on 2 October 2026. These guides describe the current development release and its known limits; some behaviour may not yet be in your installed version, so check your release notes.

Start with the record you need to maintain

Use E-Rate to connect a funding cycle, its participating sites and the equipment recorded against it. Cycles describe the program; Sites holds the planned changes; Funded Inventory follows individual assets; Documents holds supporting references. These records answer different questions. A cycle marked active does not prove that its equipment has arrived, and an installed asset does not prove that every funding milestone has been completed.

Before editing, gather the cycle name, confirmed funding year, participating sites, known milestone dates and the records supporting them. For equipment, have the asset tag or serial, catalog model, funding source, funding request number, purchase reference and installation date. Your account needs the relevant page permission; creating or changing plan structure also requires structural authority. Downloading evidence is a separate permission.

Create and revisit a cycle

  1. Open E-Rate, then Cycles, and choose New cycle. Enter its required name and a scope that explains the intended work.
  2. Record the funding year and the start and end dates that describe this cycle. Read the displayed funding-year label carefully: Cenovel distinguishes the funding year from the district fiscal year.
  3. Choose the participating sites, add program notes, and enter only milestone dates supported by your records. Leave dates blank when they have not been confirmed.
  4. Create the cycle and review its saved record. Open Edit cycle to correct it, then reload to confirm that the saved dates, notes and site membership are the intended ones.
  5. Use Open in Sites from the cycle record to review the sites within that cycle. Check the active cycle filter before changing a site plan.

Import a cycle schedule deliberately

Choose whether the file creates a new cycle or replaces the schedule of an existing cycle. To update a cycle, select that existing record; a new-cycle import with a name already in use is refused rather than silently changing it. Review which sites will remain and which will be removed before applying the file.

An import uses the permissions for the changes it makes. Creating a cycle does not grant permission to edit an existing one. Schedule additions, updates and removals require their corresponding permissions. An import that is refused for a missing permission leaves the cycle and schedule unchanged. Administrator EX retains its full access.

If the import is refused, keep the file and review the reported permission or conflict. Reload the current cycle before correcting a stale version. Do not interpret a failed response as a successful schedule update; reopen the cycle and verify the saved membership and dates.

Treat milestones as recorded evidence

The milestone fields include Form 470 posted, Form 471 certified, FCDL received, Form 486 filed, Service delivery deadline, Invoice filed and Invoice deadline. The cycle form will not save an end date before the start date, and Form 471, FCDL and Form 486 dates cannot come before the step before them. Correct the offending field in the existing form; validation should leave your other entries available.

A calendar message saying Deadline not confirmed is an information gap. Record a confirmed invoice deadline when available; the calendar then identifies it as a Recorded deadline. Clearing that field restores the unconfirmed state. Do not replace missing evidence with a convenient estimate or interpret a received-letter date as another date the letter may contain. Cenovel records and displays your information; it does not certify eligibility, filing acceptance or regulatory compliance.

Build site plans without confusing plans with stock

Within Sites, select the cycle and site before working on its plan. Plan categories include Access points, Switches, UPS, Cabling and Other. Decisions are Keep, Replace, Add or Remove. Stages run from Undecided through Planned, Ready and Installing to Accepted. Use these stages to describe the work actually reviewed; they are not a substitute for recording the corresponding physical equipment.

A planned model and quantity describe an intention. Linked units identify the assets used to satisfy it. Review existing deployed equipment and any recorded closet information before adding replacements, so that a typed count is not mistaken for another physical device. Editing plan structure and linking units have distinct server checks. If unit details are unavailable, confirm access to the equipment page before concluding that the plan has no equipment.

A record may refuse removal because plan lines still reference it. Review and resolve those relationships through the plan workflow rather than trying to delete the parent repeatedly. When another person has changed a plan, reload and review the latest state before submitting a correction.

Understand which equipment counts as funded

Funded Inventory includes an asset when its funding source is E-Rate or it has a live received-unit link to a site plan. A year label alone, an intended replacement target, or an unlinked historical unit record does not establish that connection. A linked unit identifies recorded delivery against a plan; it is not independent proof of eligibility or approval.

The verified export correction applies that same qualification, then selects the chosen year from the asset or its historical attribution. If those years disagree, the asset can appear in either relevant year and the disagreement remains visible. Qualifying equipment with neither year appears in No year recorded. The current plan cycle year is not substituted: moving a site plan can change its cycle without changing the original purchase record.

Automatic relocation capture is limited to qualifying equipment and preserves existing attribution. Older automatically captured attribution may have been based only on a year label; inspect its note and supporting records. Historical attribution remains available even when the asset does not currently qualify for Funded Inventory.

Keep asset identity and funding attribution together

In Funded Inventory, review the funded site alongside the current location. Attribution requires a school that still exists and can include the funding year and a note. A difference between funded site and current location is a review signal, not proof of an improper move. Examine the movement and supporting decision before changing attribution. Changing the funded site merely to remove a warning can erase the distinction you needed to investigate.

Attribution changes apply the asset’s page edit permission, department ownership and active editor protections in addition to Funded Inventory edit permission. Administrator EX retains cross-department access. A missing asset is rejected.

Scroll the table sideways to read all columns.

Keep asset identity and funding attribution together
Recorded informationWhat to verify
Asset tag and serialThe identifiers belong to this physical unit, not merely another device with the same name.
Funding source and yearThe values describe the intended funding record; an ambiguous year label needs correction.
Installed on, FRN and purchase referenceThese fields are populated from supporting records. An installation date is not a purchase date.
Funded site and current locationThe school whose allocation paid for the unit is recorded separately from where it stands now.

Follow movement and disposal through the asset record

Before moving or disposing of funded equipment, review its funding record and the conditions in your authoritative documents. Preserve the physical identity, original attribution and the reason for the lifecycle action. Some closet relocation paths capture missing attribution from the equipment's existing site; review that automatically recorded information instead of assuming it replaces a funding decision.

Record disposal through the asset's disposal fields and workflow. The evidence pack reads the recorded disposal date and note, along with current status and location. A move, status change or retirement does not by itself establish that an external requirement has been satisfied. Missing dates remain missing evidence; do not backfill them from the date you happen to perform the review.

When a funded unit is swapped out with Replace and sent to disposal, Cenovel asks for the reason and your confirmation that its E-Rate disposal rules are met before it records the disposal.

Export and check an evidence pack

The workbook states that it covers records this account may export. Restricted records and documents are omitted from the workbook and its counts; an empty permitted result is not proof that the district has no records.

The exceptions sheet includes an away-from-funded-site row only when that asset is selected in the funded register for the workbook. A blank or different historical attribution year no longer hides that selected moved asset. Unknown current placement cannot establish that equipment is away.

The workbook also lists Replaced units: each swap recorded with Replace, what happened to the old unit (spare, RMA or disposal) and the unit that took its place. Deleted funded units lists funded records that were deleted. Such a record is never removed for good; its Retained until date and basis say how long it must be kept, and a blank date comes with the reason it cannot be worked out.

  1. Choose a funding year and export the E-Rate evidence workbook with an account allowed to download Funded Inventory. The verified permission correction also requires view and download access to each asset’s owning page; document references require both permissions on Documents.
  2. Review the Summary, funded assets, equipment away from its funded site, equipment marked E-Rate without a year, and supporting document references.
  3. Investigate missing installation dates, FRNs and purchase references. Compare the asset year with its attribution year when the workbook flags a disagreement.
  4. Check the generation time, pack digest and reported audit-chain status. Keep the exported file with the records for the review it supported; its digest helps match that particular export to its audit entry.
  5. Correct the underlying records and export again when needed. Retain the distinction between the earlier export and the corrected one.

Access checks and concurrent changes

The following checks may not be in your installed version. Unit matching follows the same inventory visibility rules as the register. A restricted asset produces the same unknown-asset result as a missing one. Site-plan asset details also respect these rules, while the plan totals remain available through rollout access. Administrator EX retains full access.

Before assigning a tag, Cenovel rechecks the device serial, current department and existing tag when the save can proceed. If another person changes those details while your save is waiting, the assignment is refused. Refresh the preview and review the current record before trying again; an earlier preview is not permission to overwrite a later change.

Funding attribution saves recheck access after locking the asset against concurrent changes. The attribution and its audit record are saved together. A refused save leaves the attribution unchanged. Review the response, reload the record and resolve the reported permission or editing conflict before retrying.

Keep records for the applicable period

USAC distinguishes equipment inventory records from broader program documentation. Its equipment guidance calls for an updated asset register for ten years after purchase. General E-Rate documentation is retained for at least ten years from whichever is later: the funding year’s final day or the funding request’s service delivery deadline.

These dates can differ. Keep an export with its supporting funding records, and check the current USAC guidance and your organization’s requirements before removing evidence. An application deletion or a successful workbook download does not determine when records may be destroyed.

Handle gaps without overstating the result

An empty export for a quiet year can be a valid result. It does not prove that no equipment was funded: the pack reflects the records Cenovel can select, and deleted assets are excluded from its funded-asset query. A broken audit-chain result requires investigation; a working download is not an intact-chain assertion. If inventory or attribution storage is unavailable, retry after service is restored rather than presenting an incomplete screen as a finished review.

Use Documents to retain clear references and descriptions. The evidence workbook includes relevant recorded document metadata and links, not a promise that every linked file is present or authoritative. Keep the source records needed to resolve each gap. Follow the linked official guidance for program requirements; the application records do not certify eligibility or compliance.

Further reading

Limits of this guide

  • This guide describes application behavior and summarizes the linked USAC retention guidance as reviewed on 30 September 2026. It does not determine eligibility, filing acceptance or compliance for any funding request.
  • Evidence exports describe the selected recorded data and document references. They are not an independent verification of the funding file.
  • The year selector cannot yet start an export for only undated equipment, or for a year that appears only in Documents.
  • Some corrections described here, including cycle imports that keep existing status and scope, and the newer access and concurrent-save checks, may not be in your installed version. Check your release notes.

Reviewed against the current source code. Confirm the behavior and available actions on your installed release.