Development Loan Requirements

Developers ask for the requirements list, and the honest answer is that development lending does not run on one. There is no universal minimum score, no fixed leverage ceiling, no standard experience threshold; anyone publishing those numbers is describing a single program, not the market. What exists instead is a consistent set of questions every serious capital source asks. This page explains them in principle. The specific parameters for your project (leverage, pricing, terms, recourse) are confirmed during project review.

Sponsorship and track record

The first file reviewed is the sponsor's, not the project's. Capital sources want to understand who is behind the entity: completed projects comparable to the one proposed, the roles actually performed on them, and how past projects performed against their budgets and schedules. They also weigh financial capacity: liquidity to cover the equity requirement and absorb surprises, and a net worth appropriate to the guaranties being signed.

Track record is read as a team. A sponsor stepping into a first ground-up project can strengthen the file with an experienced general contractor, a seasoned project manager, or a co-sponsor, and should expect the structure to reflect where the experience actually sits. Credit history matters, but narrative matters with it: disclosed, explained difficulties are workable in ways that discovered ones are not.

The borrowing entity

Development loans are made to entities, almost always a single-purpose entity formed for the project. Expect requirements around formation and good standing, organizational documents that clearly authorize the borrowing, and a complete organizational chart showing every member of the ownership chain, including the individuals who ultimately control it. Where the stack includes mezzanine debt or preferred equity, entity structure becomes part of the financing design itself, since those layers attach at different points in the chain.

This is business-purpose financing. The entity borrows for investment and development purposes; owner-occupied consumer lending sits outside this platform entirely.

The project

The project has to be real in the specific sense underwriting means it: a controlled site, entitlements in hand or on a dated and credible path, plans developed far enough to price, and a permit strategy that matches the schedule. Location and market questions follow: the depth of demand at the project's price point, comparable sales or rents for the finished product, and the realistic pace of absorption or lease-up.

Physical condition belongs here too: site conditions, soils, environmental exposure, and any demolition or remediation the budget must carry. A project can be excellent and still underwrite poorly because its site work was priced on hope.

The budget and the sources-and-uses

The budget is the document underwriting trusts or does not. It should be complete (land or land basis, hard costs, soft costs, financing costs, carry, and a contingency line sized to the project's actual risk), and it should be current, reflecting real bids rather than last year's pricing. The schedule must agree with it: a budget and a construction timeline that tell two different stories invite a slower review.

The sources-and-uses statement is its companion: every dollar the project needs, and where each dollar comes from. Capital sources verify that the equity shown actually exists (bank statements, land basis documentation, commitments from any subordinate capital) and that the stack is complete before construction starts. The most common gap in submitted files is arithmetic: uses that quietly exceed sources.

The exit plan

Every request is underwritten against its repayment. For-sale projects need pricing and absorption assumptions supported by comparable sales, not by the pro forma's needs. Rental projects need a stabilization plan and a realistic takeout: a refinance or sale the finished, leased project can support under conservative assumptions. Expect the exit conversation to include the fallback: what happens if sales run slower, if rates move, if lease-up takes longer. Files with a credible second exit read as stronger files, because they are.

Third-party reports

Underwriting relies on independent verification: an appraisal with the value scenarios the structure needs (as-is, as-completed, as-stabilized), environmental review where the site or its history calls for it, and construction-level review of the budget, plans, and contractor (often called a plan-and-cost review) on ground-up and completion files. Title, survey, and insurance requirements round out the set. Reports are ordered during processing; the sponsor's job is to make them unsurprising.

Insurance, title, and the closing file

A set of requirements arrives late in the process and delays more closings than it should, purely because nobody started early. Builder's risk and liability insurance must be in place with the coverages and endorsements the structure requires, and construction insurance markets do not always move at closing speed. Title must be clean or curable, with existing liens, easements, and exceptions understood rather than discovered. Surveys, entity certificates, and payoff or status letters on any existing debt round out the closing file. None of these is intellectually difficult; all of them take calendar time, and the sponsors who order them early close on schedule.

What requirements are not

Two clarifications keep expectations honest. First, meeting every requirement is not an approval. Underwriting weighs the whole file, and financing is never certain until it closes. Second, missing one element is rarely a rejection by itself. Files succeed as arguments: this team, this budget, this market, this exit. Strength in one area genuinely offsets thinness in another, which is why the review is a conversation rather than a form.

It follows that the useful preparation is not perfecting a checklist but understanding your file's actual argument: where it is strong, where it is thin, and what compensates. Sponsors who can state their own file's weakness before a capital source finds it control the conversation about it.

From requirements to paperwork

Requirements describe what must be true; documents prove it. The document checklists page organizes the paperwork by category, and the document checklist generator produces a list matched to your property type, stage, and request, the fastest way to see your file the way a capital source will.