These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Bank + Lending + Insurance
- Features
- Application preparation
Application preparation
Prepare the requested terms and evidence for an identifiable application revision.
OverviewMy Loan Applications×
Bank + Lending + Insurance · Application preparation
New
My Loan Applications
Loan applications
| Application number | Subject | Borrower | Product | Requested amount | Status | |
|---|---|---|---|---|---|---|
| LA-28009 | Draft la-380 | BRR-8502 | LP-3149 | 450 | Draft | |
| LA-17469 | Submitted la-856 | BRR-6478 | LP-5921 | 420 | Submitted | |
| LA-93408 | Under review la-586 | BRR-8909 | LP-7350 | 200 | Under review | |
| LA-54097 | Approved la-915 | BRR-5610 | LP-7229 | 90 | Approved | |
| LA-68844 | Declined la-145 | BRR-9976 | LP-2075 | 870 | Declined |
6 of 6 records
Draft la-380Loan applications · LA-28009
DraftBorrowerBRR-8502
ProductLP-3149
Requested amount450
Submitted date22 Oct
What you can do
Give the reviewer a complete request
Credit Officer prepares the borrowing request with its purpose, requested amount and term. The application connects the borrower and product to the responsible officer and organization. Supporting files explain the request, while evidence records show which documents have been received and whether they have been verified. Keep the application number visible throughout preparation so later decisions refer to the same case.
An underwriting note can explain why a borrower needs working capital or how an equipment purchase supports the business. It should help Independent Credit Approver understand the request without having to reconstruct it from separate messages. The requested amount remains distinct from the amount ultimately approved. The officer should be able to explain a difference without overwriting the original request.
How the work is organized
- Assigned preparation. Use the application owner and credit officer to identify who gathers information and who answers a review question. The personal worklist brings the officer back to the cases that need their attention.
- Document collection. Attach source files with a title, upload identity and visibility choice. Evidence records identify document types such as a bank statement, collateral appraisal or insurance certificate and retain verification notes.
- Submission revision. Submit a coherent revision for review. If the amount or supporting evidence changes, make the correction visible to the reviewer before asking for a decision. A decision on an earlier revision cannot settle the changed request.
What to agree during setup
Agree what the team needs before submitting each loan purpose. An equipment purchase may need an appraisal, while a working-capital request may rely on financial statements and bank statements. Set the review responsibility for each document type. Agree how the team uses received dates, verification state and expiry information when evidence is replaced or renewed.
Decide which attachments remain Internal and which can be Shared. Shared visibility is a deliberate access choice that must be tested with the intended accounts. Confirm how each user maps to their team membership and assigned application. The personal queue should follow that mapping, and linked borrower records should remain within the same authorized scope.
Check the handoff on an actual case
Prepare a working-capital application with a financial statement and a bank statement. Credit Officer checks that the files belong to the borrower, records the requested amount and submits the revision. Independent Credit Approver opens the request and identifies an unexplained transaction in the statement. The officer adds the explanation and presents the corrected revision for review.
Now repeat the exercise with an expired insurance certificate and a file attached to the wrong parent application. The team should identify both issues before relying on the evidence. Rehearsal ends when the reviewer can locate the exact request, the relevant documents and the responsible officer from the application itself. Record who resolves an incomplete submission and how the corrected revision returns for review.
What your team sees
- My Loan Applications — Return to assigned requests with their current status and submission date.
- Pending Application Evidence — Find documents awaiting verification and inspect reviewer notes.
- Internal Application Attachments — Review files intended for internal handling before a submission moves forward.
Follow the work through
Use application to credit decision for submission and review. For a linked insurance offer, follow bundled application review.
What it keeps track of
Data model- Loan applications
- Loan applications submitted by borrowers, with requested amount and lifecycle status.
- Application evidence
- Supporting documents and evidence collected for an application.
- Record attachments
- Files attached to a loan application with visibility and evidence type.
- Borrowers
- Borrowing entities with legal name, industry, state and relationship details.
- Loan products
- Commercial lending products and their pricing and term parameters.
- Team members
- Organization members who prepare, review and approve lending records.
Who uses it
Permissions- Credit Officer
- Owns preparation and permitted file handling.
- Independent Credit Approver
- Examines the submitted request.
- App Administrator
- Resolves borrower and membership issues; Auditor reads authorized evidence.
Set up Bank + Lending + Insurance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.