Keep the E-Rate funding-request file whole — the posted request, the bidding clock, every bid logged against the criteria as published, the discount traced to a dated extract — while a named person certifies.
A request for services is posted, and the waiting period is run from the certification date, not the posting date.
02
A material amendment lands mid-window, and it is flagged as one that restarts the waiting period.
Reason
03
A bid arrives by email to one engineer, and it enters the same file as every other bid received.
04
A bid is read against the evaluation criteria as the applicant published them, and against nothing added since.
05
A price is held in its own column, separable, so the primary-factor test can be evidenced rather than asserted.
Decide
06
A bid is disqualified, and the file is checked for the reason recorded against it.
07
A cost is split between eligible and ineligible components, and the basis for the split is captured with it.
Out
08
A CIPA certification falls due, and the policy, the public notice and the minute of the hearing are looked for.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent builds the comparison; the person authorised to order eligible services makes the selection and certifies it under oath.
Example workflow
One funding request, posted to certified
AgentHuman
1Request for services postedPosting record, certification date and the evaluation criteria as published
2Bids loggedEvery bid received, its response to each published criterion, and its price in a column of its own
3File assembledBid log, clocks, cost-split basis, CIPA evidence and confidence
4Controls appliedWaiting-period checks, criteria-drift checks, the procurement rules the district names and confidence threshold
No human action required
Stages 1 to 4 run unaided, and none of them ranks a bid — the agent is logging, and the signer lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the authorised signer to review.
Low confidence
Adds a procurement-counsel read first.
Signer review
The file is held with the criteria as published, the bids as received and the confidence.
Review · Correct · Send to counsel
Reviewed — the signer certifies▼
6Procurement record updatedOnly where write access and approval policy allow it
7Outcome evaluatedBid-capture completeness, clock accuracy, cost-split basis and findings raised in review
Corrections
Every signer correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Scoring or ranking a bid — that is making the decision the signer certifies they made.
Selecting the vendor, or naming the most cost-effective offering.
Certifying anything, or signing the funding request.
Deciding a cost is eligible where the rules leave it open.
Automation boundaryAgent acts unaided
✓Log every bid received against the criteria as published.
✓Run the waiting period, and flag an amendment that restarts it.
✓Hold price in its own column and check each bid for completeness.
✓Show what the file is missing under the rules the district names, and hold it for the signer.
Wrong after the oath and the money is already paid; recovery and False Claims Act exposure follow.
Determining the discount percentage or the eligibility count behind it.
Deciding that a disqualification was properly made.
Judging whether state or local procurement law was satisfied.
Changes to criteria, clock or certification-control configuration.
Example output
One funding request, annotated
Everything the agent logs is attached to the bid or the criterion it came from.
Bid-log output · single funding requestIllustrative example
Funding request
Logged finding
Waiting period
Criterion applied
Confidence
Certification status
Internal connections
A bid arrived by email and was logged after the evaluation matrix had been closed
Restart required
47 CFR 54.503
89%
Uncertified — bid unlogged
As receivedTaken from the posted request and the bids as received — the discount percentage comes from the nutrition office, and our nutrition agent owns that count, not this one.
Record usedPosting recordBid as receivedPublished criteria
Why this flagA material amendment restarts the window, and this bid landed inside the old count — the clock is the finding.
ActionReviewCorrectSend to counsel
What the score decidesBelow the configured threshold the file picks up a counsel read before the signer sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every funding requestFrom the posted request
03Logging
Log against the published criteria
Draw on the posted request, the bids as received and the clocks. Wisconsin Bell, Inc. v. United States ex rel. Heath, decided unanimously on 21 February 2025, holds that E-Rate reimbursement requests are claims under the False Claims Act.
01Approved path
The oath is on the selection
Routine bid capture and clock arithmetic arrive already done.
02Human review
Point people at what an auditor will ask for
Unlogged bids, criteria drift and an unexplained disqualification are marked. A 2026 FCC order will make the bid evaluation and vendor selection documents a filing from funding year 2028; a technology plan is not one, and has not been required since funding year 2015.
04Build an evidence trail
The bid, the criterion it was read against and the person who certified stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
E-Rate systemsUSAC EPC portal Posting and funding records
Procurement recordsBid inbox and bid log Board agendas and minutes
District systemsStudent information systems Nutrition eligibility extracts
Agent
E-Rate bidding and certification
Reads the file Logs the bids Holds for the signer
Finance and contractsERP and purchasing Contract and document stores
A district-level bid-capture figure can read sound while a single funding-request type holds most of the unlogged bids and missing bases. Nestack reports the gap rate by funding-request type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Category two internal connections
9.8%
3.7×
Review
Multi-year contract renewals
7.7%
2.9×
Review
Consortium funding requests
4.4%
1.7×
Watch
Recurring internet access
1.6%
0.6×
Normal
Bar: gap-rate lift vs. the recurring-internet-access baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A missing bid ends as a test
A cycle closes when the unlogged bid is a regression case. That suite is what the next request assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Gap rate rises in one funding-request type.
02Diagnose
The vendor who won on a criterion nobody wrote down is read back through the posting and the bid log until the cause narrows to one.
03Improve
The change ships numbered, and the requests that forced it ride with it.
04Verify
Nothing releases while one touched bid case is still red.
05Learn
It is kept for good, and the criterion rules are amended in the same commit.
Learn → DetectThe return edge. Detection next time meets a suite one case longer than this one.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, bidding workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Bidding workflow discovery and refusal boundary.
02EPC and procurement-record assessment.
03Criteria, clock and cost-allocation rule mapping.
04Bid and posting ingestion.
05Clock arithmetic and criteria binding.
06Confidence scoring and finding routing.
07Authorised-signer review workflow.
08EPC and procurement-system integration.
09Bid and window cases.
10Guardrails and certification controls.
11Bid-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne district, one funding yearProductionProduction EPC and procurement systemsAdvancedMultiple entities / consortia
Introduced at Pilot
Bid logging to your published criteria✓✓✓
Authorised-signer review✓✓✓
Bid-capture baseline✓✓✓
Introduced at Production
Reporting by funding request—✓✓
Review workflow in your systems—✓✓
Approved record write-back—✓✓
Procurement-record integration—✓✓
Introduced at Advanced
Multi-state procurement rules——✓
Multi-stage board approvals——✓
High funding-request volume——✓
Multi-entity certification controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, funding-request volume, review controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your posted requests and where the bids land→Bid and posting ingestion, and criteria bindingWeek 1
02Representative files from a past funding year→Bid-capture baseline, clock normalisation and rule bindingWeek 2
03Your published criteria and cost-allocation basis→Criteria, clock and cost-allocation rule mappingWeek 1
04Access to relevant APIs, feeds or exports→EPC, procurement and eligibility-source review, then integration setupWeek 2
05Files you would not want subpoenaed→Window cases and failure-mode testingWeek 4
06What no certification may cover→Confidence scoring, finding routing, guardrails and certification controlsWeek 3
07The named person authorised to certify→Signer review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each band here is the weeks its own phase truly costs, so the fifth one honestly carries a pair.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Bidding workflow discovery, criteria mapping and the refusal boundaryW2Record integration and the bid-capture baselineW3Clock arithmetic, cost-split basis and review controlsW4Evaluation suite, window cases and failure-mode testingW5EPC and procurement integration, a pilot request and targeted correctionsW6One funding year run under the authorised signer, then Agent Care handover
Reading the bandEach bar sits only on the weeks its work is named in. The fifth-week overlap is real, not padding.
At the end of W6Validation closes on live requests, and Agent Care picks up the watch.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Education AI agent
Build an E-Rate agent around the person who signs.
Show us your posted requests, your published criteria and who holds the authority to certify. If your bid evaluation still lives on one desktop, then know that the FCC calls it a document you are already required to maintain and produce.
