The SBA’s 7(a) program guidance says application contents vary with the loan size and lender’s processing method, and the lender helps determine the documents needed. A generic checklist is therefore a starting conversation, not proof that a particular application is complete.
Make the request list authoritative
Ask the lender for its current checklist and the secure submission route. Record the date and contact responsible for clarifying requests. If a new requirement arrives by email, add it to the same list instead of maintaining a second informal queue.
For each item, identify the business entity, reporting period, preparer and latest version. A financial statement for the wrong entity or a draft marked as final can be more disruptive than an openly missing document. Flag uncertainty before sending the package.
Separate preparation from submission
Use a review column so staff can distinguish a file that exists from one that has been checked and delivered. Retain the submitted version and a receipt or other available delivery record. Do not overwrite it when an updated document is prepared later.
A simple naming convention helps: entity, document type, period and version date. Keep sensitive records in the approved location with appropriate access. A spreadsheet index should point to the document; it should not unnecessarily repeat bank information, identifiers or personal records.
Close questions with the right person
When figures differ between documents, ask the responsible accountant or lender what explanation is needed. Do not quietly revise a source document to make the package appear consistent. Preserve the original and the explanation so the review can be followed.
The owner’s immediate task is to reconcile the checklist before requesting a decision timetable. Ask which items remain outstanding and what happens after they are accepted. An organized package can reduce avoidable confusion, but it does not guarantee approval, a particular rate or a funding date.
