From LIHTC Proforma to Application: Reduce Re-Entry Without Losing Review

Name the model that will supply the application

Before populating anything, identify the project, scenario, program, template edition and the point at which the team considers the run ready for application preparation. Resolve whether everyone is reviewing the same saved version.

A draft with an unresolved utility allowance or an unconfirmed loan term may still be useful for feasibility. It is a different starting point from a finalized underwriting run. Keep that distinction explicit rather than letting a successful transfer imply that the assumptions have been approved.

The walkthrough follows a saved Proforma into the California CTCAC 2026 4% workbook. Use it to see how mapped financial values carry from modeling into application preparation. The LIHTC feasibility checklist helps the team organize its assumptions before the handoff.

Populate mapped values, then inspect the sections

In the walkthrough’s linked application, Populate from Proforma carries mapped financial values from the selected saved run. Review those values alongside project identification, narratives and supporting materials in the application package.

Review the unit totals and unit-mix rows, utility allowance schedule, operating expenses, construction and permanent financing, and the budget and basis sections that apply. The important check is that the destination field means the same thing as the source assumption.

Distinguish an unmapped field from an unresolved value

A field can remain incomplete for different reasons. It may require a narrative, a contact, evidence outside the Proforma or a value that the saved run does not yet contain. Those cases deserve different actions.

For an unresolved modeled value, return to the relevant assumption and establish the evidence. For project identification, enter the verified project information. For an attachment, use the program checklist and confirm the required document. Do not put a convenient zero into a field merely because it makes the section look complete.

The automation reduces repeat entry; the sponsor remains responsible for the meaning and completeness of the application. That division is what makes the review practical: spend attention on exceptions and evidence rather than recreating figures already reviewed in the model.

Reconcile the workbook instead of checking only one total

Start with unit counts and the sources-and-uses totals. Then inspect the categories that can be easy to misclassify, such as developer fee, reserves, financing costs and costs outside eligible basis. A balanced grand total does not prove that every component is in the appropriate application row.

Also distinguish tax-credit amounts from equity proceeds, and a funding request from a commitment. Copying the right number into a field with a different financial meaning can be harder to detect than a simple arithmetic error.

EZFeasi’s CTCAC mapping includes budget allocation and reconciliation checks. Review the resulting workbook and its application formulas rather than treating a completed export as confirmation that the allocating agency will accept the assumptions.

Treat a later model change as a new review event

If the unit mix, costs or financing change after population, identify which application sections are affected. Confirm the selected saved run, review what will be replaced and recheck the workbook after the transfer. Do not assume a previously downloaded file has updated itself.

Export is also distinct from filing. California’s 2026 application instructions describe the relevant submission process and requirements. The sponsor and applicable applicant still need to complete the agency process, certifications and supporting materials.

Watch the Proforma-to-Application demonstration, then book a walkthrough with a project you are preparing. We can show the mapped handoff and the remaining review steps together, so the team can judge where it will reduce duplicate work.