How to Prepare a Deal Submission

A deal submission is not an application. It is the minimum set of facts that lets a reviewer form a real opinion — quickly enough that you are not waiting on a maybe, and completely enough that the opinion is worth having. Everything below is built around one goal: give the first read what it needs, in the form it needs, so the answer comes back fast and honest.

What a first read is actually looking for

Before listing what to gather, it helps to understand what a first read is doing with it. A preliminary review is not trying to approve the loan on the spot. It is trying to answer three questions: Is this a real, business-purpose investment deal? Do the numbers hang together — does the cost fit the value with room to spare? And is there a credible way this ends — a sale or a refinance the plan can actually reach? Every item in a good submission maps to one of those questions. When a submission answers all three, a reviewer can respond with a direction. When it answers one or two, the response is a request for the rest, and the clock resets.

That is why "more documents" is not the goal. The goal is the right documents — the specific facts that let the three questions be answered. A tidy, complete submission of five things beats a disorganized pile of twenty.

The five things to gather

Across nearly every business-purpose transaction, five categories carry the first read: the purchase basis, the scope and budget, the value support, the exit, and proof that you can transact. The sections below take each in turn — what to bring, and why a reviewer needs it.

"Underwriters do not reward volume. They reward a submission where every number can be traced to something real."

1. The address and purchase basis

Start with the property address and the real basis of the deal — the purchase price under contract, or, on a refinance, the current payoff and how long you have owned it. The address is not a formality: it lets a reviewer pull the market, the comparable sales, and the property's own history, which is often the fastest way to sanity-check everything else in the file. The basis matters because it is the foundation every ratio is built on. A purchase price supported by a signed contract or a letter of intent is a fact; an "asking price" or an estimate is not, and a reviewer will treat it accordingly.

If the property is under contract, say so and be ready to share the contract. If it is not yet under contract, that is fine for a preliminary read — but be clear about it, because a deal you control and a deal you are hoping to win are two different risk profiles, and a reviewer should not have to guess which one they are looking at.

2. The scope and budget

If the deal involves renovation or construction, the scope and budget are the heart of the submission. A reviewer needs to see the work you plan to do and what you expect it to cost — ideally as a line-item budget organized by trade, not a single lump sum. The reason is simple: a lump-sum "rehab: $60,000" cannot be underwritten, because there is no way to test whether it is realistic. A line-item budget can be checked against the scope, the property, and the market, and it signals that you have actually planned the project rather than guessed at it.

For heavier or ground-up projects, the budget should include a contingency line, because a budget with no contingency has not accounted for the surprises every renovation produces. If you want a structured way to build the number, a rehab budget worksheet organizes the scope into the categories a reviewer expects to see. A budget you can defend line by line does more to move a deal than almost anything else in the file.

3. ARV or value support

Whatever the deal assumes the property will be worth — the after-repair value on a flip, the stabilized value on a rental, the as-is value on a bridge — that number needs support. Value support usually means comparable sales: recently sold properties, close in location, size, and condition, that justify the value the deal is built on. This is the number underwriting scrutinizes hardest, because at higher leverage there is little cushion to absorb a value that comes in soft.

The most common submission mistake here is an aspirational value — a resale or stabilized figure the market will not actually support. A reviewer will test your value against real comps regardless, so bringing your own supporting comps up front does two things: it speeds the read, and it shows you have priced the deal honestly. If you are unsure how a defensible value is built and why it carries so much weight, understanding ARV and how it is supported walks through exactly what makes a value figure hold up. On a qualifying joint-venture purchase-and-rehab, this number is the whole gate — the structure only works when total project cost is within 70% of a defensible after-repair value.

4. The exit and timeline

Every deal needs a credible ending, and a submission should name it. The exit is how the capital is repaid: a sale, a refinance into a term loan, or, on a hold, the stabilized cash flow that carries the property. Alongside the exit, give a realistic timeline — how long the work takes, when the property is ready, and when the exit event is expected to happen. A reviewer is not looking for a guarantee; they are looking for a plan that is internally consistent, where the timeline supports the exit and the exit supports the numbers.

Vague exits are a red flag. "I'll sell it or refinance, whatever works" tells a reviewer the plan has not been thought through. Pick the primary exit, make it specific, and keep the other as a genuine backup. If the exit is a refinance, be ready to show the property will qualify; if it is a sale, ground the price in the same comps that support your value. A clear exit turns a property into a deal.

5. Proof of funds and entity

Finally, a reviewer wants to know you can actually transact — that you have the reserves a project needs and the entity in place to close. Proof of funds is documentation that you hold the liquidity the deal assumes, whether for a down payment, closing costs, reserves, or contingency. Even structures that fund the full stack generally expect reserves, because an operator with contingency available is a materially better risk than one operating with no margin. A clear, current statement of available funds removes a question a reviewer would otherwise have to ask. For what qualifies and how it is typically presented, see the proof-of-funds guidance.

Alongside it, be ready with the entity — most business-purpose deals close in an LLC or similar structure, and having the entity formed, in good standing, and documented avoids a scramble at closing. You do not need every entity document for a preliminary read, but knowing the entity exists and is clean lets a reviewer see a path to close rather than a question mark.

Putting it together

A strong submission is short and complete: the address and basis, the scope and budget, the value support, the exit and timeline, and proof you can transact. Presented cleanly, those five categories let a reviewer answer the three first-read questions in one pass and come back with a real direction — a fit, a redirect to a better path, or the specific missing piece. That is the entire point of preparing before you submit: you trade a week of back-and-forth for a fast, honest read. The flip side — what an incomplete file costs you in stalled time — is exactly what why transactions get delayed walks through.

When the pieces are in hand, the Submit a Deal flow is built to take exactly this information — no full application required to begin. RECR reviews the property, the project, and the exit before selecting a capital path, so a complete submission is the difference between a same-week read and a stalled inquiry. Gather the five, then send them.

Frequently asked questions