E-Rate Cost Allocation Worksheet

Cost allocation is a foundational requirement for any E-Rate application that involves bundled services — where a single product, subscription, or contract includes both E-Rate-eligible and ineligible components. The Universal Service Administrative Company (USAC) mandates that applicants identify and request funding only for the eligible portion of bundled services. Failure to properly allocate costs can result in funding denial, recovery of previously disbursed funds, and potential debarment from future E-Rate participation.

For iboss SASE deployments, cost allocation is almost always required because the iboss platform delivers both E-Rate-eligible functions (content filtering and firewall) and functions that are not currently on the E-Rate Eligible Services List (such as ZTNA, CASB, DLP, and RBI). Even within eligible categories, districts must ensure that the costs claimed represent only the eligible components and do not include overhead for ineligible functions.

USAC evaluates cost allocations during the PIA review process and may request additional documentation or revised calculations if the methodology is unclear or appears unreasonable. The cost allocation worksheet provided here is designed to produce a defensible, well-documented allocation that meets USAC's expectations and streamlines the review process. Districts that submit clear, detailed cost allocations with their Form 471 filing consistently experience faster funding commitment timelines.

The iboss SASE platform is licensed as an annual per-user subscription that includes access to the full suite of security capabilities. For E-Rate cost allocation purposes, this unified license must be decomposed into its constituent functional modules, each assigned a proportional value that reflects the relative cost of delivering that capability.

Calbrate works with iboss to maintain a current component-level pricing breakdown that is accepted by USAC reviewers. The standard decomposition identifies the following modules: Secure Web Gateway and Content Filtering (SWG/CF), which includes URL categorization, malware scanning, and SSL inspection; Firewall as a Service (FWaaS), which includes stateful packet inspection, application control, and intrusion prevention; Zero Trust Network Access (ZTNA), which includes identity verification, device posture assessment, and application-level access control; Cloud Access Security Broker (CASB), which includes SaaS discovery, usage monitoring, and policy enforcement; Data Loss Prevention (DLP), which includes content inspection, PII detection, and exfiltration prevention; and Remote Browser Isolation (RBI), which includes cloud-based rendering and safe content delivery.

Each module is assigned a percentage of the total license cost based on iboss's internal cost accounting for development, infrastructure, and support allocation. This component breakdown serves as the foundation for the cost allocation worksheet and should be referenced in the Form 471 narrative as the basis for the claimed eligible amount.

USAC accepts several cost allocation methodologies, provided the chosen approach is reasonable, consistently applied, and adequately documented. The three most commonly used methods for cloud-delivered security platforms are component-based allocation, usage-based allocation, and proportional allocation.

Component-based allocation uses the vendor's itemized pricing to assign specific dollar amounts to each functional module. This is the preferred methodology for iboss deployments because iboss provides a documented component breakdown that directly maps each module to a specific percentage of the total license cost. Component-based allocation is the most straightforward to document and is the least likely to be challenged by USAC reviewers.

Usage-based allocation distributes costs according to the proportion of network traffic or processing resources consumed by each function. This approach can be supported by iboss platform analytics that report traffic volumes processed by SWG, FWaaS, ZTNA, and other modules. However, usage patterns can vary significantly across the school year, requiring districts to calculate averages over a representative period. Proportional allocation simply divides the total cost equally among the number of functional modules. While this method is simple, it is the least precise and may be questioned by USAC if the modules vary significantly in complexity or resource requirements. Calbrate recommends component-based allocation for all iboss E-Rate applications due to its accuracy and defensibility.

The cost allocation worksheet is organized into four sections that build sequentially. Completing all four sections produces a fully documented allocation ready for inclusion in your Form 471 filing.

Section A captures your district profile information: entity name, entity number, FCC Registration Number, number of eligible students, number of staff users, total user count for licensing purposes, and your E-Rate discount percentage. This information is used in subsequent calculations and should match the data in your EPC entity profile exactly.

Section B captures the iboss contract details: total annual license cost, per-user cost, contract term dates, and the component percentage breakdown provided by your Calbrate account team. Each iboss functional module is listed with its percentage of the total license cost, and the worksheet automatically calculates the dollar amount attributable to each module.

Section C is the allocation calculation. You designate each module as E-Rate eligible, Cybersecurity Pilot eligible, or locally funded. The worksheet sums the eligible component costs to produce the total E-Rate-claimable amount, applies your discount percentage, and calculates the expected reimbursement. A separate column calculates the Cybersecurity Pilot-eligible amount for districts that are applying to both programs.

Section D generates the documentation output: a formatted cost allocation narrative suitable for pasting into the Form 471 FRN narrative field, a summary table for inclusion in your procurement file, and a certification statement for the E-Rate coordinator's signature.

The following examples illustrate how the cost allocation worksheet produces different results based on district size, discount rate, and deployment configuration. All examples use the standard iboss component breakdown and current pricing as of the 2026 funding year.

Small district example: A rural district with 2,000 students and a 70% E-Rate discount deploys iboss SASE for all students and 300 staff members, totaling 2,300 users. At a per-user annual cost of $28, the total annual license is $64,400. The E-Rate-eligible components (SWG/content filtering and FWaaS) represent approximately 38% of the total license, yielding an eligible amount of $24,472. At the 70% discount rate, the E-Rate reimbursement is $17,130, reducing the district's annual out-of-pocket cost from $64,400 to $47,270.

Medium district example: A suburban district with 8,000 students and a 50% discount deploys iboss for 8,000 students and 1,200 staff (9,200 users). At $24 per user (volume discount), the total annual license is $220,800. E-Rate eligible components total $83,904 (38%), yielding a reimbursement of $41,952 at the 50% discount rate.

Large district example: An urban district with 25,000 students and a 90% discount deploys iboss for 25,000 students and 4,000 staff (29,000 users). At $20 per user (enterprise volume pricing), the total annual license is $580,000. E-Rate-eligible components total $220,400. At the 90% discount rate, E-Rate reimbursement is $198,360. If the district also receives Cybersecurity Pilot funding for the remaining ZTNA, CASB, DLP, and RBI components ($359,600) at the same 90% discount, the combined reimbursement totals $521,998, reducing the district's net cost to approximately $58,002 for comprehensive SASE protection across the entire district.

The Form 471 FRN narrative is the primary location where districts document their cost allocation for USAC reviewers. A well-written narrative reduces the likelihood of PIA inquiries and accelerates the funding commitment timeline. The worksheet generates a narrative template that can be customized and pasted directly into the FRN narrative field on Form 471.

The narrative should include four elements. First, a description of the overall service being procured, identifying the vendor, the platform, and the total scope of the deployment. Second, an identification of the eligible components with their individual costs, referencing the vendor's component pricing documentation. Third, a statement of the allocation methodology, explaining why the chosen approach is reasonable and how the percentages or amounts were derived. Fourth, the calculated eligible amount and the corresponding funding request.

Districts should also prepare a supplementary documentation package that can be uploaded to EPC or provided in response to PIA inquiries. This package should include the completed cost allocation worksheet, the vendor's component pricing letter on company letterhead, the signed contract with itemized pricing, and any supporting analytics or usage data if a usage-based methodology is employed. Having this documentation package assembled before filing Form 471 ensures rapid response to any USAC inquiries and demonstrates the district's commitment to program compliance.

USAC conducts post-commitment audits on a subset of funded applications each year, and cost allocation is one of the most frequently examined areas. Understanding common audit findings helps districts prepare defensible allocations from the outset and avoid the financial and administrative burden of audit recovery proceedings.

The most common audit finding related to cost allocation is insufficient documentation. USAC auditors expect to find a clear paper trail connecting the claimed eligible amount to a documented methodology and supporting data. Allocations that rely on estimates, approximations, or undocumented assumptions are routinely challenged. A second common finding is inconsistency between the cost allocation and the contract terms — for example, when the contract specifies a bundled price but the Form 471 claims an eligible amount that does not reconcile to any documented breakdown.

A third audit trigger is claiming ineligible services as eligible. This occurs when districts misclassify advanced cybersecurity capabilities that are not on the Eligible Services List as Category 2 internal connections. USAC's remedy for this finding is typically full recovery of the overpaid amount plus potential penalties. To mitigate audit risk, districts should use the iboss component breakdown provided by Calbrate, apply the allocation consistently across all funding years, retain all supporting documentation for the required ten-year retention period, and respond promptly and completely to any audit inquiries. Districts that proactively self-correct allocation errors before audit — by filing Form 500 adjustments — generally receive more favorable treatment from USAC.

• Maintain all cost allocation documentation for a minimum of ten years
• Ensure contract pricing aligns exactly with Form 471 claimed amounts
• Use only documented, verifiable allocation methodologies
• Do not claim ineligible services under Category 2 — use the Cybersecurity Pilot instead
• Respond to audit inquiries within the specified deadline to avoid adverse findings
• File Form 500 corrections promptly if you discover allocation errors after commitment