HUD Plans Catalyst-to-Plus Transition as Lender Comments Open Through December 7

HUD is preparing a new online doorway for FHA multifamily and healthcare lenders, but the transition is not an instruction to stop using FHA Catalyst today. An October 8 Federal Register notice describes the Portal + Loan Underwriting System, known as PLUS, and seeks public comments by December 7, 2026 on the information collection supporting it.

The notice says PLUS will allow lenders to request FHA project numbers and view the real-time status of applications. Additional lender-portal functions are planned for later phases. HUD expects PLUS eventually to replace the multifamily lender-portal functions now in FHA Catalyst, likely in 2027. That timing is an expectation in the notice, not a fixed shutdown date for every Catalyst function.

For owners, developers, housing finance agencies and their lending partners, the immediate value is understanding which parts of an application workflow HUD is discussing and what remains unchanged. A new status screen can improve visibility, but it does not itself approve a mortgage, reserve financing or eliminate underwriting requirements. The proposal is an information-collection revision under the Paperwork Reduction Act, not a new commitment to insure an individual development.

WHAT HUD SAYS PLUS WILL DO

FHA Catalyst: Multifamily Applications is the existing web-based portal through which FHA multifamily lenders upload and submit applications for FHA multifamily mortgage insurance. HUD's description assigns PLUS two initial functions: requesting FHA project numbers and viewing real-time application status. The notice separates those functions from the later lender-portal capabilities that HUD intends to build.

That distinction gives a project team a more useful question than whether everything is moving to a new system. The team needs to know which transaction belongs in which application at the time it is performed. Project-number requests, mortgage-insurance application submissions and access requests are separate activities in HUD's burden table. They should not be treated as one undifferentiated upload task.

The notice includes FHA multifamily and healthcare lenders in its description of PLUS. Its respondent categories include FHA-approved mortgagees identified as MAP lenders, housing finance agencies and government-sponsored enterprises. It is not a general resident portal, an application for rental assistance, or an online waiting list for affordable apartments.

Owners and developers who work through a lender may experience the change indirectly. They may be asked for project information earlier, receive a different status report, or need to reconcile identifiers across systems. Those are possible workflow implications, not additional requirements announced in the notice. The lender should explain its current process rather than asking the owner to infer operating instructions from a public-comment document.

A COMMENT NOTICE IS NOT A MIGRATION ORDER

The Federal Register document is a 60-day notice of proposed information collection. HUD is seeking approval from the Office of Management and Budget for a revision to an existing collection, identified by OMB Control Number 2502-0620. The document is numbered 2026-20679 and appears at 91 FR 64387-64388.

Those details matter when people search for the record or prepare a comment. A news summary can explain why the transition is relevant, but a submission should identify the actual collection being discussed. The notice names the collection FHA Catalyst: Multifamily Applications, and Portal + Loan Underwriting System (PLUS).

The December 7 deadline is a public-comment deadline. It is not the date by which every development must obtain a project number, the date Catalyst shuts down, or a financing application deadline. Confusing those meanings could cause a project team to accelerate the wrong task or communicate an invented compliance obligation to a borrower.

Similarly, the phrase likely in 2027 should be preserved rather than hardened into a launch promise. HUD says subsequent phases will add functions and that PLUS will later replace current multifamily lender-portal functions. A system rollout can require later operating instructions. Until those instructions are issued, project teams should use the channels HUD and their lenders currently require.

THE BURDEN ESTIMATES SHOW THE PROPOSED WORKFLOW

HUD estimates 833 annual project-number requests through PLUS, at a quarter hour per response. The table assigns those requests 208 annual burden hours and $9,360 in annual cost. It separately estimates 739 application submissions through FHA Catalyst at a half hour per response, totaling 370 hours and $16,650.

A third row covers 47 Catalyst access requests through an access-request form. At a quarter hour per response, HUD estimates 12 annual hours and $540. The overall estimate is 590 annual burden hours and $26,550 in annual cost. The figures are HUD's estimates for the information collection, not an application fee schedule or the total cost of developing an FHA-insured property.

The table uses a $45 hourly cost assumption. A lender considering a comment can ask whether the estimated minutes capture its actual work: assembling information, entering it, checking it, resolving errors and completing the submission. That is a question about the accuracy of the collection burden, not an invitation to substitute a different project's underwriting budget for the table.

The separate rows also show why teams should avoid claiming that Catalyst has already disappeared. The proposed collection still anticipates Catalyst application submissions and access requests while PLUS handles project-number requests. The document describes coexistence and a phased replacement, not a single completed transfer of every function.

WHAT A USEFUL COMMENT CAN ADDRESS

HUD asks whether the collection is necessary for the agency's work and whether the information will have practical utility. A useful response can identify a specific field, process or reporting need and explain how it helps or fails to help the application process. General praise or frustration may communicate a view, but it provides less detail for evaluating the collection itself.

The agency also asks about the accuracy of its burden estimate. Lenders with relevant experience can distinguish time spent preparing an application from time attributable to the information-collection process HUD is estimating. A documented example of repeated entry or an error-correction step can be more useful than an unsupported statement that a task takes too long.

Other questions concern improving the quality, utility and clarity of the information collected and minimizing respondent burden through automation or other technology. Suggestions could address clear field definitions, confirmation messages, the handling of duplicate project data or the ability to identify an incomplete request. Those are examples of comment topics, not promises that PLUS will contain any particular feature.

A comment should be accurate about the writer's experience and avoid disclosing borrower, resident or transaction information that does not belong in a public record. The Federal Register page says comments are public and may be posted after agency review. Before submitting, an organization should use its own approval process and confirm the final text and any attachment are suitable for that audience.

PREPARE THE PROJECT RECORD WITHOUT INVENTING NEW RULES

An owner does not need to wait for a final migration date to improve its internal project record. The team can identify the current project name, legal ownership entity, site information, lender contact and existing identifiers. It can also agree on who is responsible for receiving a project number and communicating status updates. These are preparation practices, not new duties imposed by this notice.

A status label should be reported with its source and date. If a lender says an application is visible in a system, the owner should ask what that status means for the next required step. Visibility is not the same as a complete submission, a favorable underwriting decision, a firm commitment or a closing. The project schedule should continue to distinguish those milestones.

Maintain the underlying documents rather than relying on a screen as the only project record. A portal may show progress while the team still needs correspondence, submission confirmations and the version of a document the lender actually provided. This is especially important when a project spans a system transition and different participants keep different copies.

The notice does not announce a waiver of existing standards or a change to every FHA multifamily program. It describes how information is collected and how parts of the lender portal are expected to evolve. Program eligibility, underwriting and other transaction requirements must be evaluated under their own governing materials.

WATCH THE RIGHT NEXT STEPS

The practical near-term milestone is the December 7, 2026 comment deadline. Monday is the calendar day for that date. Organizations that want to comment should work backward far enough to review evidence, obtain approval and use the submission instructions in the official notice. Preparing a comment is separate from the work needed to keep a current financing application moving.

HUD's later operating communications will matter for actual migration tasks. Lenders and borrowers should look for the functions being activated, the users affected, any access instructions and any explicit cutoff or transition dates. The October 8 notice alone should not be stretched into details it does not provide.

The change is worth watching because project numbers and application status are basic coordination tools. A clearer shared record can reduce confusion about where an application stands. But the sound response today is modest and specific: understand the proposed collection, comment if the organization has useful evidence, preserve the current application record, and wait for actual transition instructions before changing a live submission route.