Questions and Answers.pdf
PDF 163 KB Posted
- Attached to
- Mortgage Prepayment Reports
- Solicitation number
- FHF-26-Q-0046
- Issued by
-
Federal Housing Finance Agency
About this file
This is a Questions and Answers document for Request for Quotation FHF-26-Q-0046 addressing mortgage prepayment reports required by the Federal Housing Finance Agency (FHFA).
The procurement seeks quarterly mortgage prepayment reports based on commercially available data sources, with deliverables matching the format and precision of sample reports provided in Attachment D. The contractor must independently identify and provide preferred commercially available data sources and is responsible for obtaining and maintaining all data. Reports must be based exclusively on Single-Family loan performance data and delivered by the 15th calendar day following each quarter-end (e.g., October 15 for Q3). The contractor must independently calculate prepayment metrics including CPR, SMM, and related analytics using methodologies aligned with industry standards and UMBS Rule. Required deliverables include formatted Excel workbooks matching Attachment D specifications, machine-readable CSV files, and supporting data tables provided separately from formatted reports. The historical look-back period for time-series data is one year. Methodologies for calculating 1-month CPR, 3-month CPR, quartiles, WAC-to-coupon comparisons, and vintage cohort analyses must support industry standards; FHFA will not provide specific formulas. The contract is a recompete with incumbent contractor RiskSpan, Inc. (contract 95314321P0013). The estimated contract value is approximately $300,000 for a base year plus four optional years, with quarterly invoicing anticipated. Minor report changes including new data fields, formatting updates, and language revisions are included in the fixed-price scope; new report requests will be separately negotiated. All reports and data files will be publicly available. Subject matter expert support during normal business hours is included at no additional cost.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment B - Terms and Conditions.pdf | ||
| Attachment D - Vintage Comparison Q4 2025.xlsx | XLSX spreadsheet | |
| Attachment D - WAC_to_Coupon_Comparison.xlsx | XLSX spreadsheet | |
| Request for Quotation.pdf | ||
| Attachment B - Terms and Conditions.pdf | ||
| Attachment C - Pricing Worksheet.xlsx | XLSX spreadsheet | |
| Attachment A - Statement of Work.pdf | ||
| Attachment D - 30-year Prepayment Line and Bar Charts 1-month CPR.xlsx | XLSX spreadsheet | |
| Attachment D - 30-year Prepayment Line and Bar Charts Fastest Quartile Based on 3-month CPR.xlsx | XLSX spreadsheet | |
| Attachment D - Quartiles Q4 2025.xlsx | XLSX spreadsheet | |
| Attachment D - Issuance Q4 2025.xlsx | XLSX spreadsheet |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Request for Quotation - FHF-26-Q-0046 - Mortgage Prepayment Reports Questions and Answers
1. Data Sources / Publicly Available Enterprise Data The SOW states that the required reports shall be based on “commercially available and marketed data available to the Contractor.” May the Contractor use publicly accessible FHFA, Fannie Mae, and Freddie Mac datasets — including FHFA PUDB, Enterprise loan-level performance data, PoolTalk/MBS disclosure files, Freddie Mac MBS disclosure resources, factor files, and Enterprise prepayment data — as source data for the required quarterly reports, provided the Contractor develops the reporting methodology, data normalization, calculations, data dictionary, and report package?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
2. Commercially Available and Marketed Data Requirement Would Contractor-developed reports based on publicly accessible Enterprise/FHFA source datasets satisfy the SOW requirement for “commercially available and marketed data available to the Contractor,” if the Contractor provides documentation of data sources, update cadence, source-to-product lag, methodology, and data dictionary/equivalent documentation?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
3. Preferred or Required External Data Providers Does FHFA require, prefer, or currently use any specific external mortgage, MBS, or prepayment data providers or datasets for this requirement? If so, may FHFA identify those sources or the minimum source-data characteristics needed to replicate the Attachment D reports?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
4. Attachment D Format Expectations The SOW states that the Contractor shall deliver reports in line with the Attachment D samples and that data precision shall match the examples. Can FHFA confirm whether the Attachment D Excel files are intended to define the required report content, structure, and precision, rather than requiring the Contractor to use the exact same workbook formatting? May the Contractor provide an enhanced quarterly report package that includes Excel workbooks aligned to Attachment D, machine-readable CSV files, and Section 508-conformant PDF summary reports?
Answer: The proposed report should match the example reports/Attachment D files. Future reporting enhancements may be considered.
5. CPR, Quartile, and Cohort Methodology Does FHFA have a required methodology for calculating 1-month CPR, 3-month CPR, quartiles/deciles, fastest-quartile groupings, WAC-to-coupon comparisons, issuance groupings, and vintage/cohort comparisons, or may the Contractor propose a documented methodology that produces reports consistent with Attachment D?
Answer: Methodologies should support industry standards/UMBS Rule.
6. Portal Delivery as an Enhancement The SOW allows electronic delivery through email, website download, or similar means accepted by the COR. Would FHFA accept a secure reporting portal as part of the delivery approach if the portal allows authorized FHFA users to access current and historical reports, download supporting machine-readable data, search prior reporting periods, manage user access, and maintain audit/download logs?
Answer: Yes. The vendor must describe the details of the approach.
7. Report Sharing and Access Controls Since the SOW contemplates FHFA use of the reports for official Government purposes, including potential sharing with other government agencies or the public, would FHFA find value in optional controlled-sharing features such as approved-domain access, passcode-protected links, link expiration, administrator approval, and report-version audit logs?
Answer: Yes. The vendor must describe the details of the approach.
8. Data Availability and Sourcing The SOW states that the reports will be based on "commercially available and marketed data that is available to the Contractor". Could you clarify how this data is expected to be sourced? Specifically, will the required metrics be derived entirely from publicly available internet sources, or does FHFA expect the use of proprietary, company-controlled, and internally stored data?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
9. Previous Award Information If this is a follow-on requirement or if there is a previous award associated with this contract, could you please provide the historical contract number, the name of the incumbent vendor, or any relevant award details?
Answer: The incumbent is RiskSpan, Inc. under contract number 95314321P0013.
10. Is there any incumbent/recompete or is this a brand-new project? If yes, could you please provide us with their award number or even if the customer bought similar services in the past.
Answer: The incumbent is RiskSpan, Inc. under contract number 95314321P0013.
11. Is direct servicing data required for the quarterly reports, or are modeled/estimated prepayment datasets acceptable if methodology is documented?
Answer: Actual data is required.
12. For the prepayment analytics, does FHFA expect loan-level servicing/performance data, or aggregated cohort-level reporting outputs?
Answer: The data should support required reporting.
13. Are vendors expected to independently calculate CPR/SMM/prepayment metrics, or will FHFA accept commercially derived/model-based calculations?
Answer: Yes. Vendors are expected to independently calculate the metrics.
14. For the sample reports in Attachment D, are those intended to be exact recurring deliverables with the same structure and layout, or representative examples of the type of reporting desired?
Answer: The proposed report should match the example reports/Attachment D files.
15. Is agency loan identification at the individual loan level required (FNMA vs. FHLMC), or can cohort attribution methodologies be used?
16. What level of historical depth is FHFA expecting for origination data, prepayment history, and vintage analysis?
17. Are there any minimum update cadence or lag-time expectations for the underlying datasets?
Answer: They should be aligned with data availability.
18. Does FHFA expect the contractor to provide only the quarterly reports, charts, and tables, or an interactive reporting portal or dashboard as well?
Answer: Yes. Only the required quarterly reports and associated Attachment D files.
19. Are there preferred machine-readable delivery formats beyond Excel and PDF, such as CSV or API delivery?
Answer: CSV/Excel is the preferred format.
20. For minor report criteria changes, should vendors assume these are included within the base FFP pricing as operational support?
Answer: Yes, minor report criteria changes are included in the FFP pricing.
21. Is there an incumbent vendor currently providing these reports, and if so, are current report methodologies or specifications available for reference?
Answer: Yes, there is an incumbent providing these reports. Please refer to the Statement of Work for additional information regarding the reporting requirements.
22. Does FHFA anticipate any restrictions around the use of estimated mortgage rate methodologies versus directly observed servicing data?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
23. Who is the current incumbent contractor performing these services?
Answer: Riskspan, Inc.
24. What is the estimated contract value or historical value of the current contract, including option periods if available?
Answer: The estimated contract value for a base year plus 4 optional years is approximately $300,000.00.
25. Are the historical quarterly reports or sample deliverables from prior performance publicly available?
Answer: Yes.
26. Does FHFA expect contractors to provide their own licensed commercial mortgage/prepayment datasets, or may publicly available Fannie Mae and Freddie Mac disclosure datasets be utilized to satisfy the reporting requirements?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
27. Is there a preferred or currently utilized delivery format for the machine-readable supporting data tables (e.g., CSV, Excel, API-accessible format)?
Answer: CSV/Excel is preferred.
28. Does FHFA anticipate any restrictions regarding offshore support personnel for development, automation, or analytics activities, provided all contract management and data handling remain compliant with applicable federal requirements?
Answer: Please refer to Attachment B – Terms and Conditions.
29. Are there any minimum historical data coverage expectations for the required reports (e.g., number of years of historical performance data)?
Answer: The proposed report should match the example reports/Attachment D files.
30. What is the budget set aside for this project? Is there an estimated/proposed budget (or ceiling) for this work?
Answer: The estimated contract value for a base year plus 4 optional years is approximately $300,000.00.
31. Is there an incumbent for this work? If so, please specify
Answer: Riskspan, Inc.
32. Attachment B states that contractors typically submit invoices monthly, while the SOW describes quarterly report delivery. Please clarify whether FHFA expects monthly invoicing for the FFP service or quarterly invoicing after each report delivery and acceptance.
Answer: If necessary, vendors may submit invoices more or less frequently than on a monthly basis. For this requirement, quarterly invoices are anticipated.
33. Do the Excel files provided in Attachment D represent the exact required format, layout, column order, number formatting, precision, sheet structure, and content that must be delivered each quarter?
Answer: The proposed report should match the example reports/Attachment D files.
34. Are there any additional reports required beyond those shown in the Attachment D files? If yes, please provide the full list and samples.
Answer: There are no additional reports required beyond those shown in Attachment D.
35. Will FHFA provide the raw loan-level data to the Contractor, or is the Contractor responsible for obtaining and maintaining the data?
Answer: The Contractor is responsible for obtaining and maintaining the data.
36. Fannie Mae and Freddie Mac each publish both Single-Family and Multi-Family loan performance datasets. We assume the required reports in Attachment D are based exclusively on Single-Family loan data. Please confirm this assumption is correct.
Answer: Yes, the required reports are exclusively based on Single-Family loan data.
37. Would it be possible for FHFA to provide a small sample of the raw data files (only a few rows) used to generate each Attachment D report?
Answer: No. The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
38. Will FHFA provide the exact formulas, calculations, and business rules (e.g., CPR computation, quartile/decile definitions, cohort formation, etc.) for each report or section in Attachment D?
Answer: Methodologies should support industry standards/UMBS Rule.
39. If the award occurs in June or July 2026, what would be the due date for the first quarterly report?
Answer: October 15, 2026, for Q3 2026 data.
40. For reports containing historical time-series data (e.g., WAC_to_Coupon_Comparison and prepayment line/bar charts), what is the required historical look-back period?
Answer: The historical look-back period is one year.
41. Are machine-readable data tables (e.g., CSV or raw data tabs) required in addition to the formatted Excel reports?
Answer: The proposed report should match the example reports/Attachment D files.
Yes, machine-readable data tables are required in addition to the formatted Excel reports.
42. Attachment D formulas/calculation methodology
Question: Attachment D provides required report samples and states that the precision of data in delivered reports must match the examples. Please confirm whether FHFA expects the Contractor to generate these reports using the Contractor’s standard commercial mortgage data methodology, including standard definitions for CPR, WAC, WALA, WAM, coupon buckets, vintage cohorts, and quartiles, or whether FHFA requires specific formulas or methodologies for these calculations.
If FHFA requires specific formulas or methodologies, please provide the required definitions for one-month CPR, three-month CPR, WAC / weighted average coupon, WALA / weighted average loan age, WAM / weighted average maturity, quartile ranking methodology, vintage/cohort definition, coupon bucket mapping, and UPB-weighting versus loan-count-weighting.
If no specific formulas are required, please confirm that the Contractor may use its documented commercial data methodology and provide a data dictionary, calculation methodology, and validation checks as part of its technical approach.
Answer: Methodologies should support industry standards/UMBS Rule.
43. Commercial data source preference
Question: Please confirm whether FHFA has any preference or requirement regarding the commercially available data source to be used in generating the Attachment D reports. Specifically, may the Contractor use its own licensed and commercially marketed mortgage loan-level or pool-level dataset, provided that the Contractor documents the data source, data dictionary, update frequency, update lag, methodology, and validation controls used to produce the required reports?
Answer: The vendor should independently identify and provide preferred commercially available data sources used in developing the reports.
44. Authorized users and access requirements
Question: SOW Section 6.0 states that authorized FHFA end users may access and use the product from their official duty stations or remotely via FHFA’s VPN when conducting FHFA business. Please clarify FHFA’s anticipated user access requirements. Specifically:
All submitted reports will be accessible agency-wide and will be published on FHFA’s website for public access.
45. Additional reports and out-of-scope work
Question: SOW Section 2.0 states that “FHFA and the Contractor can bilaterally negotiate to include other reports on an FFP basis as needs arise for related reporting capabilities and information.” Please clarify whether any additional reports, analyses, data cuts, or reporting capabilities requested outside the specific Attachment D reports will be separately negotiated and priced as additional FFP work, or whether FHFA expects such additional reporting to be included within the base quarterly report pricing.
Answer: New report requests will be separately negotiated, but additional analyses/data cuts/minor changes in support of required reports/data files would be included in the base quarterly report pricing.
46. Machine-readable supporting data format
Question: SOW Section 4.1 requires the Contractor to provide supporting data tables/charts in machine-readable format. Should the Contractor provide both formatted report workbooks and separate raw supporting data files?
Answer: Yes, the Contractor should provide both formatted report workbooks and separate raw supporting data files.
47. Definition of minor report changes
Question: SOW Section 4.1 states that FHFA may request minor report criteria changes, such as date range or data/cohort parameters, and that the Contractor shall make “minor report changes” without additional charge. Please clarify the expected scope of
“minor report changes.” For example, would changes to date ranges, formatting, labels, and existing cohort parameters be considered minor? At the same time, would new report types, new calculations, new data sources, or materially different analytics be negotiated separately?
Answer: Updates including new/changing data fields, formatting changes, language updates, etc. to existing reports/tables are included in the “minor report changes” scope.
48. Public release/redistribution limits
Question: SOW Sections 2.0 and 4.2 state that FHFA may use the reports internally and may share them with other government agencies or the public. Please clarify the expected scope of public release or redistribution. Should Contractors assume that all delivered reports and supporting data tables may be publicly released, or only FHFA-created excerpts, summaries, charts, presentations, and publications derived from the reports?
Answer: Required reporting/data files will be publicly available.
49. Data granularity expected
Question: Please clarify the expected granularity of the supporting data tables. Should supporting tables be provided only at the aggregate/cohort level shown in Attachment D, or does FHFA expect loan-level or pool-level supporting data to be delivered as part of the quarterly reporting package?
50. Historical lookback period
Question: Please clarify the required historical lookback period for the quarterly reports. Should Contractors match the time periods shown in Attachment D, provide all available history from their commercial data source, or provide a specific number of years of historical mortgage origination and prepayment performance?
Answer: The historical look-back period is one year. The proposed report should match the example reports/Attachment D files.
51. Report timing and data availability
Question: Quarterly reports are due by the 15th calendar day of each quarter of performance. Please confirm the expected reporting cutoff date and data availability assumption. For example, should the report due October 15 include data through September 30, or should it include the most recent data available from the Contractor’s commercial data source as of the report production date?
Answer: Yes. 15th calendar date after each quarter-end (e.g., October 15th for Q3 reporting).
52. Subject matter expert support expectations
Question: SOW Section 4.2 requires subject matter expert/technical support through email and/or telephone at no additional cost. Please clarify the expected support levels, including business hours, response times, the maximum number of support requests or hours per month, and whether support is limited to report-specific questions, validation issues, and report updates.
Answer: Subject matter expert/technical support services are expected during normal business hours. Please see the Statement of Work for additional details.
53. Section 508 / ACR scope
Question: The RFQ requires an Accessibility Conformance Report for each commercially available ICT item used under the contract. Please confirm whether ACRs are required only for any web portal/SaaS access provided to FHFA, or also for delivered Excel/PDF report files and supporting documentation.
Answer: Please see the Statement of Work, Section 8.0.
54. Acceptance criteria
Question: Please clarify the acceptance criteria for quarterly reports. Will acceptance be based on timely delivery, conformance with Attachment D format and precision, successful opening/accessibility of files, COR review of methodology, or another standard?
Answer: Yes, acceptance is based on the successful delivery of Attachment D – see Statement of Work for additional details.
55. Which company is the incumbent?
Answer: RiskSpan, Inc.
56. Will FHFA redesign the reports? We highly recommend redesigning the reports to align with industry standards, better monitor and compare the performance of the two GSEs, and facilitate easier communication with the industry.
Answer: No.
57. Is the offeror expected to reproduce some or all of the numbers in the reports attached to the RFP package in the response? If so, more details are needed to refine the calculation.
58. Typically, Quartiles are composed of min, 25th percentile, 50 percentile(median), 75th percentile and max. How are Quartile 1, 2,3,4 defined in Attachment D? And when calculating quantiles, are the observations the 3-month CPRs of qualified pools (for example, tba-eligible pools with UPB exceeding a certain threshold)? And how to mark the quantile, by pool count, or by pool current or scheduled balance?
Answer: The proposed report requirements are reflected in the report.
59.
1. How many named FHFA users are expected to require access to the product?
2. How many simultaneous or concurrent users should the Contractor support?
3. Will FHFA require the Contractor to provision and manage individual user accounts, or will FHFA provide a list of authorized users for account setup?
4. Does FHFA require any specific authentication method, such as username/password, single sign-on, multifactor authentication, IP restrictions, VPN-only access, or another access-control method?
5. Should the Contractor assume access is limited to FHFA personnel only, or may authorized users include other government agencies if FHFA shares the reports or product externally?
Answer to Question 59 – (5 part question):
FHFA seeks the delivery of data, not licenses. Therefore, a specific number of users is not relevant, as the data will be made available agency wide and to the public.
File details come from the government source that posted it. Updated .