Automatic Draw Submission in the Sponsored Borrower Portal

Purpose

Automatic Draw Submission lets users upload an entire draw package at once and have Built organize it. Built reads the documents, separates them when several are combined in one file, labels each one, checks them against the documents the lender requires, and fills in draw amounts on the budget.

Before Automatic Draw Submission, every document had to be attached and assigned to a requirement by hand, and every draw amount typed in from the paperwork. The work now shifts from re-typing information to verifying it: every requirement is visible before upload, and every amount Built fills in can be traced back to the exact page it came from.

The manual method is unchanged and remains available. The choice between them is made at the start of the Documentation step of each draw.

Key Features

1. Documentation method choice: At the Documentation step, choose Let Built organize everything for me or I'll upload and assign manually. The choice is saved with the draw and locks as soon as a file is uploaded.

2. Lender requirements shown up front: The Required Documentation sidebar lists the documents that specific lender requires, read live from their configuration. Additional Requirements lists their non-document requirements, marked as Resolved or Not Applicable.

3. Bulk upload with visible processing: A whole package drops into a single drop zone. Each file shows a named-step tracker, so you can see what Built is doing rather than watching a spinner.

4. Automatic splitting and classification: When one PDF holds several documents, Built separates it into individually labelled documents and groups them under the requirement each one satisfies. Opening a document goes straight to its pages.

5. A pre-filled budget with traceable amounts: Extracted amounts are applied to budget line items. Each pre-filled amount carries the file, page, extracted value and reasoning behind it, and every amount stays editable.

6. Feedback on classification results: A thumbs up or thumbs down can be given on how Built classified each document, with a reason and an optional comment. Rate a whole category from the Extracted Documents panel, or open an individual document and rate it from the viewer toolbar — useful when Built split a merged PDF at the wrong pages. Ratings from either place stay in sync, are saved with the draw, and never affect the submission.

Target Users

Borrowers and project accountants who assemble and submit draw requests in the Sponsored Borrower Portal on lender-sponsored Construction Lending (CLA+) deals.

How It Works

Choosing a Documentation Method

Complete the Details step and continue. A screen appears headed "It's time to upload your Draw documentation and backup." with two options:

• Let Built organize everything for me — "Upload your draw package and we'll sort, split, and attach documents to their relevant line items."

• I'll upload and assign manually — "Upload documents and manually attach each file to the required items."

Select one and click Continue. Continue does nothing until a method is selected.

Note:

• Choose before uploading. Once any file is uploaded, the method is locked for that draw and cannot be changed. To use the other method, choose it at the start of the next draw.

Uploading the Package

The Automatic view shows a single drop zone with the lender's requirements alongside it:

• Required Documentation — the documents the lender requires. A check appears beside each one once a matching document is identified. If the lender has none configured, this reads "No document requirements configured for this draw."

• Additional Requirements — the lender's requirements that have no document attached. Set each one to Mark Resolved or Not Applicable. If the lender has none configured, this reads "No additional requirements configured for this draw."

Drag the package into the drop zone, or click browse your files. One file or many can be dropped in a single action.

Supported formats: .bin, .csv, .doc, .docx, .html, .jpeg, .jpg, .json, .mp3, .pdf, .png, .svg, .tiff, .txt, .xls, .xlsm, .xlsx, .xltx, .xml, .zip. Maximum file size 1GB.

Watching Files Process

Each file shows a card headed "Built is organizing your package" with a percentage and five steps:

1. Uploading documents

2. Reading draw package

3. Splitting documents

4. Extracting document information

5. Classifying document types

A file that fails to upload offers Retry upload and Remove file. Completed files are listed under Documents Uploaded, and deleting one there also removes it from processing.

Note:

• The page can be left once files are processing. While a file is still transferring, Save & Close and Cancel are blocked — wait for the transfer to finish. Once a file shows as processing, the work continues unattended and the page can safely be left.

Reviewing the Extracted Documents Panel

When processing finishes, the Extracted Documents panel shows how Built organized the package, under the heading "Built organized your draw package — We organized your documents by category based on your lender's requirements and matched each amount to your budget. Review below or continue."

There is one row per lender requirement. Each row shows a badge:

Two documents are shown per row; the rest sit behind an expand control. Each document shows its page range, such as p. 3-4. Click a document to open it — a document split out of a merged PDF opens at exactly its pages, not at page 1 of the whole upload.

Supplementary Documents. Documents Built recognized but that none of the lender's requirements asked for are grouped in a trailing Supplementary Documents row. They are still attached to the draw and still visible to the lender — the grouping only reflects which requirement they satisfy.

Documents Built could not classify. A file Built could not classify at all gets no row in Extracted Documents. It remains in the Documents Uploaded list, attached to the draw and visible to the lender. Nothing is lost.

Rating Classification Results

Rating is optional. Identified rows carry thumbs-up and thumbs-down controls, and the same control appears in the document viewer toolbar as "Built classified this as {type} · Correct?". Selecting either opens a dialog headed "Help us improve this result" with reason options and an optional comment.

Reasons are single-select — choosing a second replaces the first. The comment box is optional and is labelled "Tell us what didn't work or what you expected instead." on a thumbs down, or "Tell us what worked well." on a thumbs up. Submitting with no reason and no comment is valid.

Clicking the thumb that is already active clears the rating. There is no neutral state. Ratings are saved with the draw and are visible again on return.

Some rows have no thumbs. This happens on the Supplementary Documents row, on rows with no identified documents, and on rows where Built cannot attach a rating to a specific classification. This is expected, not a missing feature.

Rating from the viewer applies to every requirement row that shares that file, so one submission covers a document that satisfied more than one requirement.

Matching Amounts to the Budget

Click Continue. If files changed since the last time Built processed them, a modal appears headed "Finalizing your draw — Matching documents and updating your budget", stepping through:

• Matching documents to budget line items

• Preparing results

• Updating the Budget

If the files have not changed, the existing result is reused and no new processing runs.

Reviewing the Pre-Filled Budget

When matching completes, the Draw & Funding Amounts step opens with amounts already applied, under a banner reading "Built filled the highlighted amounts from your documents. Fields with ✦ came from extracted data — you can override any draw amount, or open the file icon on any line to view its supporting document."

Pre-filled cells are marked so it is clear at a glance which numbers came from the documents. Open the source documents on any line item to see:

• File name

• Page number

• Confidence

• Extracted amount

• Role

• Vendor

• Reasoning

The current draw request is always filled in where a matching line item exists. Reallocation adjustments and retainage are filled in only where the draw is configured for them.

Note:

• Edited amounts are not re-checked. Changing an amount Built filled in saves that edit, and the edit is what gets submitted — but the supporting reasoning is not regenerated. The source documents panel still shows the reasoning behind the original extraction.

Reviewing and Submitting

Retainage, reallocation, stored materials, funding sources, Review and E-Sign all behave exactly as they do in the manual method.

The Review step is headed "Review your draw before submitting — Confirm the details below, then submit to {lender}." It shows the draw summary, the requirements with an Attached, Incomplete or Resolved status, and the line items grid with source documents openable from it.

Click Submit Draw and confirm: "Submit this draw? Once submitted, this draw will be locked for editing and sent to your lender for review."

If any requirement is still unmet, a modal names what is missing — it can be reviewed, or the submission completed anyway. Unmet requirements do not block submission. Once submitted, the draw is locked for editing, exactly as in the manual method.

Availability

Availability is set by Built per lender. If the automatic option is not yet enabled for a lender, the card appears with a Coming Soon badge and cannot be selected.

Note:

• Lender-specific policies are not applied yet. The lender's required documents are shown during upload, so it is clear what is expected. Built does not yet apply the lender's specific policy rules when assessing the contents of the documents, so this release shows no policy findings or flags.

Benefits

• Upload the package as-is instead of attaching files one at a time and assigning each to a requirement by hand.

• See exactly which of the lender's requirements are met before submitting, reducing the chance the draw comes back for correction.

• Review numbers instead of typing them — draw amounts are extracted from the documents and applied to the budget.

• Trace any pre-filled amount back to the file and page it came from, with the reasoning behind it.

• Open a document split out of a merged PDF at exactly its pages, rather than hunting through a long upload.

• Watch named processing steps rather than an opaque spinner, and leave the page once files are processing.

Best Practices

• Choose a method before uploading anything. The choice locks as soon as the first file lands, and there is no way to switch on that draw.

• Upload the whole package in one action. Merged PDFs are the intended input — Built separates them and labels each document inside.

• Open the source documents before accepting an amount. Checking the file and page an amount came from takes seconds and is the fastest way to catch an extraction error.

• Include standing documents every draw. Each draw is assessed on its own. Documents from earlier draws do not carry forward, so a document such as a Change Order Log must be included again.

• Allow a few minutes for processing. A typical package takes around three minutes to read and organize, and the final matching step averages around two and a half — with the slowest packages taking over five. Processing time scales with package size.

• Resolve Additional Requirements manually. These have no document attached, so uploading files will never satisfy them. Mark each one Resolved or Not Applicable.

• Use the thumbs feedback when something is classified wrong. It never affects the submission — documents stay attached and visible to the lender either way — and the reason chosen is what makes the result better next time.