--- title: "E-Rate Form 470 changes and RFP amendment review" description: "Keep a dated E-Rate Form 470 and RFP amendment review for your MSP. Separate application identity, attachments, status, and questions before a response." canonical: "https://scalewithsearch.com/articles/erate-form-470-rfp-amendment-review" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # E-Rate Form 470 changes: keep the current RFP in your bid review Keep the posting you first found and the documents you would use today in separate parts of the review. A dated comparison should show what changed, what remains unread, and who confirms the response requirements. USAC permits certain changes to certified Forms 470. Its guidance distinguishes minor corrections from changes that require another waiting period. [USAC Form 470 modification guidance](https://www.usac.org/e-rate/applicant-process/competitive-bidding/ministerial-clerical-errors/). For an MSP, the useful result is a current document set with unresolved differences exposed. A familiar institution name, unchanged application number, or recently retrieved row should not substitute for that reading. The [MSP intelligence overview](/intelligence/it-and-managed-service-providers) introduces amendment tracking. This guide proposes a worksheet for one posting. It does not make a procurement determination or describe a deployed collection system. ## Separate the five identities Give application, entity, funding year, service request, and form version their own labels. They answer different questions in a review. The application number identifies the Form 470 application. The billed entity number identifies the entity on that form. USAC defines both in its [basic Form 470 metadata](https://opendata.usac.org/api/views/jp7a-89nd.json). Keep them together rather than using the institution's displayed name as the sole reference. The funding year identifies the cycle. A service request identifies a request within one application. USAC's detailed metadata defines `service_request_id` at that level. Multiple requested services can share an application number. [Detailed Form 470 metadata](https://opendata.usac.org/api/views/jt8s-3q52.json). Form version is another distinction. USAC defines “original” as the application submitted at certification and “current” as the form processed by USAC. [Basic Form 470 metadata](https://opendata.usac.org/api/views/jp7a-89nd.json). Use the following as a proposed review header. Copy actual identifiers from the official source when reviewing a real posting. Leave missing values empty and identify who must resolve them. | Review label | Purpose in the proposed worksheet | | --- | --- | | Application number | Return to the same application | | Billed entity number | Preserve the applicant reference | | Funding year | Separate this cycle from earlier research | | Service request ID | Keep evidence attached to the intended request | | Form version | Distinguish current and original views | | Review timestamp | Show when your team opened this evidence | Add a plain-language scope label for your staff, such as “fictional library switching request.” Treat that as an internal description. Never let it replace the official identifiers. ## Make an attachment inventory before comparing scope List the documents that your bid review depends on. Begin with the form and issued RFP. Add each published addendum or clarification you find in the current source set. USAC uses “RFP document” broadly for bidding documents that expand the Form 470 description. Applicants issuing an RFP must upload the actual document with the form. [USAC competitive bidding guidance](https://www.usac.org/e-rate/applicant-process/competitive-bidding/). Your inventory should retain the document's displayed name, source location, stated issue date, observed upload date, and the time your team opened it. Distinguish a date printed inside a document from a platform field. The detailed dataset includes a per-service-request attachment count, RFP upload date, and an RFP document link. Its definition describes the link as the original submission copy. [Detailed Form 470 metadata](https://opendata.usac.org/api/views/jt8s-3q52.json). Treat that description as a reason to inspect the current record and attachments. Avoid calling a downloaded file “latest” until the lead confirms the controlling set. Use a neutral working label such as “opened October 28.” A retrieval timestamp tells you when you obtained a file, not when its requirements took effect. ## Use a worksheet that exposes unread evidence The following worksheet is an editorial proposal for bid preparation. It is not a USAC form. Adapt its columns to your procurement process without removing source references. | Worksheet item | Suggested content | Review owner | | --- | --- | --- | | Form observation | Identity header, version, status, dates | Bid coordinator | | Attachment observation | Name, link, issue date, upload date | Bid coordinator | | Compared sections | Scope, quantities, sites, dates, response instructions | Technical and bid leads | | Difference | Earlier wording, later wording, source locations | Assigned reader | | Unresolved issue | Exact question and required clarification | Procurement lead | | Response decision | Current set confirmed, held, or declined, with reason | Bid lead | For each attachment, add a reading state: opened and reviewed, opened but incomplete, or unavailable. A filename in an inventory should not imply that anyone read its contents. When a file is inaccessible, record the source link and observation time. Name the missing review. Continue only the work that does not depend on that document, as directed by the lead. Keep the earlier document beside its replacement in the internal review record. Label it as historical. This preserves the evidence behind an earlier estimate without leaving the older requirements in the current proposal folder. ## Read status and modification fields narrowly USAC's basic metadata describes form status as the current status of the form. It defines `last_modified_datetime` as the last modification time, labeled EST. [Basic Form 470 metadata](https://opendata.usac.org/api/views/jp7a-89nd.json). Record those values as observations. Do not translate a modification timestamp into “scope changed” without reading the difference. Likewise, do not turn a retrieved status into a promise that your team can still submit. In the proposed worksheet, reserve separate space for the source's status and your firm's decision. “Source status observed” and “proposal preparation held” describe different things. Preserve both without merging their meanings. If the two official views appear inconsistent, list the exact fields and the dates you checked them. Avoid choosing whichever value makes the opportunity more attractive. Ask the procurement lead to establish what the team should use. Use the same approach when an attachment count changes. Record the observation, then find the documents. A changed count may prompt investigation, but the number alone does not tell your estimator which requirements changed. ## Understand the material-change boundary USAC allows minor corrections without restarting the waiting period when they do not materially affect competition. Its examples include nickname changes, contact changes, and minor RFP updates. Changes beyond the allowed scope require a restart. [USAC modification guidance](https://www.usac.org/e-rate/applicant-process/competitive-bidding/ministerial-clerical-errors/). Beginning in funding year 2025, applicants can attach updated RFP documents to a certified form without canceling it. Applicants answer an EPC question about the change. When they identify a substantive change, EPC recalculates the 28-day period from that change. [USAC modification guidance](https://www.usac.org/e-rate/applicant-process/competitive-bidding/ministerial-clerical-errors/). Keep that rule separate from your firm's interpretation of a particular addendum. The worksheet can point to a new category, revised quantities, or changed terms. The responsible lead must resolve the actual procurement implications. Avoid a checkbox that says “material change: no” merely because a contact field changed or the displayed date stayed the same. Record the observed difference and the evidence the lead used for its decision. If the change affects the calendar, update the linked [allowable contract date and bid deadline review](/articles/erate-allowable-contract-date-bid-deadline). Do not assume that the allowable contract date and applicant response cutoff move together. ## Walk through a fictional revision Consider a fictional library request for switching equipment. The coordinator first reviews a Form 470 and an RFP labeled “Issue A.” Several days later, the posting includes “Addendum One.” No real applicant is represented. The addendum changes the proposed equipment quantity and replaces a submission instruction. It also asks bidders to acknowledge the addendum. Those details are invented for this exercise. The coordinator creates three difference rows. One points to the two quantity statements. Another compares the submission instructions. The third records the acknowledgment requirement. Each row names the attachment and section. The technical lead reviews the revised quantity against the proposed design. The bid lead checks the response instructions. The procurement lead confirms the controlling document set and any timing question before proposal work resumes. Now add an uncertainty: the Form 470 narrative still shows the earlier submission instruction. Preserve that conflict in the worksheet. Hold the affected submission decision pending clarification through the permitted route. Do not label the addendum immaterial to keep the original proposal schedule. Do not declare a waiting-period restart on the basis of this fictional example. The example demonstrates comparison and escalation, not an official classification. ## Keep clarification within the published process Before contacting the applicant, have the lead read the permitted question method and timing. USAC's provider FAQ directs bidders to the form narrative and attachments for preparation and submission requirements. [USAC provider FAQ, question 14](https://www.usac.org/e-rate/learn/faqs/competitive-bidding-fcc-form-470/). Prepare a narrow question tied to the conflicting source sections. The lead should review the wording and communication route before it leaves the firm. Store the resulting published clarification with the same application review. For example, an internal draft could ask which listed submission instruction applies after an addendum. Avoid adding a sales pitch or an unsupported claim about the applicant's intended schedule. USAC requires an open and fair competition with equal treatment of bidders. [USAC competitive bidding guidance](https://www.usac.org/e-rate/applicant-process/competitive-bidding/). Keep your worksheet focused on public requirements and authorized clarification. Public contact information does not replace the procurement instructions. Check the funding year before reusing a communication method. FCC 26-30 establishes a USAC bidding portal for funding year 2028, with requirements for bid submissions and bidder communications. Confirm that cycle's instructions before sending questions or bids. This guide does not establish that the portal is currently available. [FCC 26-30, bidding portal requirements](https://www.govinfo.gov/content/pkg/FR-2026-05-19/html/2026-10011.htm). ## Confirm the set before any response At the final internal review, ask the bid lead to name the exact form and attachments used. Record their identifiers and the time of the last check. Preserve unresolved questions in the decision record. Ask the technical lead whether each proposal section reflects the checked scope. Ask the commercial owner whether pricing and commitments refer to that same set. A completed document inventory does not establish technical or commercial acceptance. If an attachment arrived after drafting began, identify which sections need another reading. Give those sections to the responsible reviewers. Avoid treating an earlier approval as permission to submit changed terms. The [business memory guide](/articles/business-memory-for-ai-agents-guide) describes retaining sources and decisions in files your firm controls. For a bid review, keep the comparison, clarification, and final decision together. That record should explain why the team acted. ## Preserve a decision when the review stops If your firm declines the opportunity, retain the document set that supported the decision. State whether the reason was scope, capacity, unresolved instructions, or a checked participation requirement. Avoid a generic “not a fit” label when the evidence supports a more precise explanation. If the team later reopens the opportunity, begin with a new observation of the official record. Keep the earlier decision as history. Compare its source set with the documents now available before reusing any draft pricing or technical narrative. Assign the reopened review to a person. An old proposal folder should not silently become the current response package. The new lead needs the unresolved differences and the reasons behind the earlier stop. ## Start with one complete review Use the [E-Rate bid finder](/tools/erate-bid-finder) for discovery, then return to the official posting. Choose one opportunity that fits your approved services. Assign a person to read its current documents before expanding the review queue. The [MSP service overview](/for/it-and-managed-service-providers) provides the wider preparation context. Keep customer operations, public bid research, and outbound proposal decisions separate in your firm's records. Scale With Search can scope a preparation workflow around the document inventory, change comparison, and named review roles. Bring a public example and your existing bid decision process. [Send your brief](/work) ## Sources and limits The linked USAC guidance, both metadata endpoints, and the cited FCC notice were reopened on October 28, 2026. The linked filing tutorial returned an offline message in the text reader. This guide therefore relies on the readable modification guidance for the rule. [USAC filing tutorial](https://www.usac.org/video/sl/how-to-file-an-FCC-form-470/story.html). The worksheet and fictional revision are proposed methods. No live bid, attachment history, or applicant compliance was assessed. Reopen current guidance and documents before a response. The responsible lead retains procurement, eligibility, communication, and submission decisions. Continue the website review: [AI-native IT providers: the first functions to build](/articles/ai-native-managed-service-providers-first-functions); [E-Rate allowable contract dates: distinguish the waiting period from the bid deadline](/articles/erate-allowable-contract-date-bid-deadline); [Managed IT pricing pages: explain what sets the quote](/articles/managed-it-pricing-website-page); [MSP AI rules: data, approvals, and spend](/articles/msp-ai-rules-data-approvals-spend); [MSP case studies: publish evidence without client names](/articles/msp-anonymous-case-study-website); [MSP onboarding pages: explain the first steps](/articles/msp-client-onboarding-website-page); [MSP contact form spam: inspect the receiving path](/articles/msp-contact-form-spam-controls); [MSP cybersecurity website claims: show the scope](/articles/msp-cybersecurity-website-claims); [Google Business Profile for an MSP: check eligibility](/articles/msp-google-business-profile-eligibility); [MSP service area pages: separate on-site and remote](/articles/msp-onsite-service-area-website-pages); [MSP status pages: publish approved incident updates](/articles/msp-public-status-page-website); [MSP buyer guides: make the download useful](/articles/msp-website-buyer-guide-download); [MSP inquiry emails missing: trace the delivery steps](/articles/msp-website-inquiry-email-not-arriving); [MSP website design: separate sales from support](/articles/msp-website-sales-and-support-paths); [Discontinued AV equipment: read Q-SYS service terms before recommending replacement](/articles/qsys-discontinued-equipment-service-terms-review); [Q-SYS compatibility tables: review installed hardware before a software change](/articles/qsys-hardware-software-compatibility-table-review). [IT and managed service providers](/for/it-and-managed-service-providers): website and search resources. ## Related: IT and managed service providers - [Managed IT pricing pages: explain what sets the quote](/articles/managed-it-pricing-website-page) - [MSP AI rules: data, approvals, and spend](/articles/msp-ai-rules-data-approvals-spend) - [MSP case studies: publish evidence without client names](/articles/msp-anonymous-case-study-website) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```