Loan conditions: spreadsheet or software?

Published 17 October 2026. Updated 17 October 2026.

Every loan file with a conditional decision comes back with a list from the lender. Someone has to turn that list into work: who owes what, by when, and which file runs out of rate lock first. Many small brokerages start this job in a spreadsheet, and many stay there for good reasons. Others rely on the conditions screen in their loan origination system, and a few add a tool that reads the lender's sheet.

This guide compares those three ways to track conditions, says when each one is the right choice, and ends with a checklist that works whichever you pick.

What does condition tracking actually involve?

Before comparing tools, list the work. For each loan file, in each round of conditions, someone does these steps:

1. Receive the lender's condition sheet and file it against the right loan.
2. Read every condition and write it down in your own words, without changing the amount, the date or the document asked for.
3. Tag each condition with its owner: borrower, processor, title or escrow company, or a third party such as an employer.
4. Note the timing group: prior to docs, prior to closing, prior to funding or after closing. See prior to docs vs prior to funding conditions.
5. Find the rate lock expiry and work out the days left.
6. Turn the borrower's items into a clear message. See how to ask borrowers for loan conditions.
7. When a revised sheet arrives, compare it with the last one: what is new, reworded or dropped.
8. Rank the whole pipeline so the loan file with the nearest lock gets looked at first.

Steps 2 and 7 are where time and mistakes pile up, because they are retyping and comparing. Step 8 is where a missed date costs money. Judge each approach on those, not on how tidy it looks.

Option 1: a spreadsheet

A spreadsheet in Excel or Google Sheets is the default for a reason. It costs nothing extra, everyone already knows it, and you decide the columns. A sheet with one row per condition and a days-left formula can run a small pipeline well.

Where it holds up:

• A few open loan files at a time, and a lender sheet that rarely changes.
• One person who owns the sheet and updates it daily.
• A pipeline where most conditions are the same few items.

Where it breaks down:

• Retyping. Every condition is typed by hand, so a transposed digit in a deposit amount or a wrong year on a lock date can sit in the sheet unnoticed.
• Version confusion. Two people save two copies, or the sheet is updated but the borrower message was written from the older version.
• Revised sheets. Nothing compares the new sheet with the old one for you. A late addition is easy to miss when you only skim.
• No source. Unless you add a column for the page and the quote, you cannot tell later where a condition came from.
• Silent formulas. A days-left formula that points at a fixed date, or a sort that leaves one column behind, looks fine and is wrong.

For how to build a sound one, see how to track rate lock expiration dates.

Option 2: the conditions screen in your loan system

Most loan origination systems have somewhere to list conditions and tick them off. That keeps the conditions next to the rest of the file, which matters when other people already work there.

Where it holds up:

• The whole team lives in that system and expects everything to be on the file.
• You want a single record that stays with the loan.
• Conditions are entered once and then edited by whoever clears them.

Where it can fall short, depending on the system and how you use it:

• Unless your system imports conditions from the lender, someone still enters them, so the retyping moves rather than goes away.
• A view that ranks every loan file by days to lock may or may not exist. Check what yours shows.
• Comparing two versions of a lender's sheet may still be a manual job.

Ask your system's vendor what it does. This guide makes no claim about any particular system.

Option 3: a tool that reads the lender's sheet

A third approach skips the typing. You upload the sheet, and the tool returns a checklist and a ranked queue. The risk with any such tool is trust: a checklist that is wrong in a way you do not notice is worse than a slow spreadsheet. So judge it on whether it shows its source, how it treats dates and amounts, and what it leaves for you to decide.

Where it holds up:

• You handle many loan files, or sheets get reissued often.
• Retyping and version comparison are where your time goes.
• You want your loan files ranked by lock without maintaining formulas.

Where it is not the better choice:

• Your volume is low and a spreadsheet is already accurate and current.
• Your sheets are scans or photos, and the tool reads only text-based files.
• You need conditions to appear inside your loan system. A separate tool is a separate place to look.

How do the three compare?

The cells for the first two columns describe what is typical, not what any one product does. Check yours.

A checklist for any of the three

• One owner for the lock date column, and one place where an extension is recorded.
• The page or quote for each condition, so anyone can check it against the sheet.
• Amounts and dates copied from the sheet, then checked a second time by someone or something other than the person who typed them.
• A rule for revised sheets: compare before you message the borrower.
• A visible place for loan files with no lock date found. They should not sit at the bottom by default.
• The borrower message written from the current sheet, not from memory.
• A review of the whole pipeline each morning, soonest lock first.

How ConditionPilot does this step

ConditionPilot is the third option. You upload the lender's condition sheet for each loan file, as a PDF with selectable text, a Word file or a text file. You can add the rate lock confirmation and an earlier version of the sheet for each file. A model reads each sheet and lists every condition with its quote, page, owner and timing. Code then finds each quote and each lock date in the document, works out the days to lock and ranks the loan files in the job, with any file that has no confirmed lock date placed last. A second, stronger AI model reviews every result and lists what is left for you to decide; the drafting model corrects the serious problems the review finds, and code checks every correction. Results are not verified by a person.

You get an Excel workbook with the lock-ranked queue and a checklist sheet, a PDF checklist for every loan file, a Word borrower draft for every loan file, and the full result as JSON, plus a CSV of the items to check when there are any. If you upload an earlier sheet, new, reworded and dropped conditions are marked. A borrower ask that would change an amount or a date is held back from the draft and listed for you to check.

The price is 6 credits a loan file, up to 10 loan files in one job, with no subscription. Each job ranks its own loan files; it does not keep a running queue across jobs. ConditionPilot does not read scanned sheets or photos, does not connect to your loan system and does not email your borrowers. You edit the draft and send it yourself. Sign up to try it.

When a spreadsheet is enough

If you keep a few loan files open at a time, one person owns the sheet, and you add a source column and a daily check, a spreadsheet is a good choice. Move to something else when you notice retyping errors, missed revisions, or no time to do the daily ranking properly.

Questions

Is a spreadsheet enough for a small brokerage?

Often yes, at a handful of open loan files. A spreadsheet starts to strain when several people edit it, when a lender reissues sheets often, or when nobody has time to retype every condition and compare versions.

Should the spreadsheet live in a shared drive?

A shared copy beats several private ones, because version confusion is the usual failure. Name one person who owns the lock date column, so an extension is entered once and everyone sees it.

Does software remove the need to read the sheet?

No. Whatever builds the checklist, someone still reads the lender's sheet for the conditions that matter most on that file. A tool saves the retyping and the sorting, and it should point you back to the page.