Compliance CTA: Use Terms and Definitions as a control reference when drafting eligibility memoranda, RFIs, appeals, and closeout packages. Cite the current PAPPG terminology, statutes, regulations, forms, templates, and related FEMA resources consistently so the project file uses the same definitions and authorities as FEMA reviewers.

Compliance CTA: Use Acronyms as a control reference when drafting eligibility memoranda, RFIs, appeals, and closeout packages. Cite the current PAPPG terminology, statutes, regulations, forms, templates, and related FEMA resources consistently so the project file uses the same definitions and authorities as FEMA reviewers.

Compliance CTA: For Validation of Applicant-Provided Cost Estimates, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: Assign an owner for Applicability, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: Confirm applicant eligibility for Applicant Briefing before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Applicant Eligibility before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Applicant Eligibility: Private Nonprofit Organizations before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for For-Profit Entities before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Organization Eligibility before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Multiple Facilities before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Facility Eligibility before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Mixed-Use Space before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Mixed-Use Facility before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Multiple Services before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Use by Multiple Entities before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Leased Facilities before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Small Business Administration Loan Requirement before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Private Nonprofit Services before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Applicant Eligibility: State, Local, Tribal Nation, and Territorial Government Entities before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for State and Territorial Governments before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Tribal Nations before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: Confirm applicant eligibility for Local Governments before project formulation. Document legal status, ownership or operating responsibility, eligible public or PNP service, RPA submission, SBA loan requirement where applicable, and any mixed-use or leased-facility limitations. Keep organizing documents, tax-exempt records, service descriptions, leases, and facility-use evidence in the Grants Portal file.

Compliance CTA: For Labor Policies, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Applicant (Force Account) Labor, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Eligibility Criteria for Reimbursement of Employee Labor Costs, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Applicant-Owned and Purchased Equipment, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For State, Tribal Nation, or Territorial Rates, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For FEMA Rates, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Equipment with No Established Rate, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Local Rates, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Telecommunications Equipment Purchase, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Application of Remediation Methods, verify that the incident-specific eligibility criteria, time limitations, public-health or safety threat, legal authority, and documentation requirements are satisfied before claiming costs. Preserve technical determinations, permits, orders, inspection reports, location data, quantities, contracts, and proof that work was limited to eligible emergency protective measures.

Compliance CTA: For Audits, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: For Single Audits, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: For Office of the Inspector General, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: For Government Accountability Office, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: For FEMA Office of Civil Rights, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: For Recovery of Improper Payments, operate a post-award controls calendar. Track scope changes before work deviates, completion deadlines, time-extension justifications, quarterly progress reports, financial status reporting, FFATA, audit requests, civil-rights obligations, fraud reporting, and improper-payment recovery exposure.

Compliance CTA: Assign an owner for Authorities, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: Assign an owner for Policy, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: Assign an owner for Regulations, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: Assign an owner for Public Assistance Web-Based Grants System, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: For Bald and Golden Eagle Protection Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: For Buildings and Structures, identify mitigation during scoping and document how the measure reduces future damage, is cost-effective or otherwise eligible, complies with legal and EHP requirements, and is tied to the damaged facility or capped-project funding rules. Keep BCA, pre/post-repair timing, design assumptions, and construction records in the project file.

Compliance CTA: For Clean Air Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: For Clean Water Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: For Closeout Requirements, lock down the approved scope, fixed-cost basis, election deadlines, funding-use rules, insurance conditions, and closeout documentation before the applicant relies on capped funding flexibility. Track any improved, alternate, or alternative-procedures decision separately from standard restoration eligibility.

Compliance CTA: For Coastal Barrier Resources Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: For Coastal Zone Management Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: Use Code of Federal Regulations as a control reference when drafting eligibility memoranda, RFIs, appeals, and closeout packages. Cite the current PAPPG terminology, statutes, regulations, forms, templates, and related FEMA resources consistently so the project file uses the same definitions and authorities as FEMA reviewers.

Compliance CTA: For Codes and Standards, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Consensus-Based Codes, Specifications, and Standards, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Locally Adopted Codes and Standards, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Codes and Standards Eligibility Criteria, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Path of Travel, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Ineligible Upgrades, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Accessibility for Individuals with Disabilities, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Permit Requirements, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Additional Resources, do not treat upgrades as eligible until the code or standard test is met. Document the applicable written standard, adoption and enforcement history, uniform application, reasonableness, applicability to the required restoration, permit requirements, accessibility/path-of-travel triggers, and any consensus-based code requirements used to support added scope.

Compliance CTA: For Compliance Reviews, align the scope, cost, insurance, EHP, hazard mitigation, and eligibility record before obligation. Use the review stage to resolve inconsistencies, unsupported quantities, omitted reductions, and compliance conditions; then document how funds are requested, managed, and drawn consistent with FEMA and recipient requirements.

Compliance CTA: For Comprehensive Environmental Response, Compensation and Liability Act, start EHP screening during scoping, not after construction. Identify ground disturbance, floodplain/wetland, historic, threatened species, coastal, water, air, hazardous materials, and other resource impacts; obtain required reviews or permits; follow FEMA conditions; and retain correspondence and approvals before work proceeds where required.

Compliance CTA: For Cost Development, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Project Thresholds, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Expedited Projects for Emergency Work, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Costs for Projects with All Work Completed, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Estimating Emergency Work Projects with Work to be Completed, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Estimating Permanent Work Projects with Work to be Completed, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: Establish the declaration file for Damage Assessments early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Assign an owner for Damage Caused During Performance of Emergency Work, confirm the governing PAPPG requirements on the cited page, and build a project-file checklist that links the topic to eligible applicant, facility, work, cost, documentation, deadlines, EHP, insurance, procurement, DOB, monitoring, and closeout controls. Resolve exceptions before obligation, drawdown, or final reconciliation.

Compliance CTA: For Debris Removal (Category A), prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: For Hazardous Limbs, Trees, and Stumps, prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: For Waterways, prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: For Privately-Owned Vehicles and Vessels on Public Property, prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: For Disposal, prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: For Monitoring Contracted Debris Removal Operations, complete a 2 C.F.R. Part 200 procurement compliance check before claiming costs. Retain procurement method rationale, competition records, cost or price analysis, required contract clauses, conflicts disclosures, disadvantaged business outreach when required, monitoring records, and justification for any exigency, emergency, noncompetitive, time-and-materials, or pre-positioned contract use.

Compliance CTA: For Private Property Debris Removal, prove an eligible immediate threat, eligible location, legal authority, and debris quantity/cost basis. Retain debris monitoring records, load tickets, disposal/tipping documentation, PPDR public-interest determinations when applicable, photos, GPS or site identifiers, contractor records, recycling revenue offsets, and DOB checks.

Compliance CTA: Establish the declaration file for Declaration Determinations . early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Incident Type early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Designated Areas early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Incident Period early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Types of Assistance early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Federal Cost Share early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Declaration-Related Appeals early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Application for Federal Assistance early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Recipient Administrative Requirements early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Payment Management System early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for FEMA-State/Tribal Nation Agreement early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Hazard Mitigation Plan early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Public Assistance Administrative Plan early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Recipient-Led Public Assistance early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Declaration Evaluation early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Tribal Nations early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for State and Territorial Governments early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: Establish the declaration file for Declaration Request early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.

Compliance CTA: For Differences Between Standard and Alternative Procedures, lock down the approved scope, fixed-cost basis, election deadlines, funding-use rules, insurance conditions, and closeout documentation before the applicant relies on capped funding flexibility. Track any improved, alternate, or alternative-procedures decision separately from standard restoration eligibility.

Compliance CTA: For Direct Federal Assistance, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Disposition for Small Projects, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Disposition of Equipment and Supplies, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Disposition of Purchased Equipment, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.

Compliance CTA: For Disposition of Purchased Supplies, demonstrate that claimed costs are necessary, reasonable, allocable, and adequately supported. Compare actual costs, estimates, procurement results, historical data, unit prices, FEMA or applicant estimates, insurance reductions, and completed-work documentation. Segregate ineligible, duplicate, excessive, or unsupported costs before obligation and drawdown.