Define the request before the form
Checkpoint 1, “Define the request before the form”, has a separate decision checkpoint. The submission file must establish whether the application reflects the smallest amount that meets a stated personal need. Its preparation checklist contains purpose, requested pula amount, preferred term, budget ceiling and no-debt fallback, with truthful versions, consent purpose and recipient recorded before transmission. Confirm the requested route using the borrower’s own plan before bank contact; never send a credential merely because a message appears urgent. The applicant rehearses the need being reduced or delayed without harmful consequences so document collection does not conceal affordability pressure. Stop the file when the form encourages a larger amount than the documented need. A safe procedural response is to submit the smaller case or do not apply, without assuming acceptance.
Verify the bank and product route
Checkpoint 2, “Verify the bank and product route”, answers a distinct Botswana evidence question. Before submission, verify whether the legal entity and official product page match. Organise register entry, bank domain, product name, contact channel and access date in the application folder, retaining authentic versions and the bank’s reason for requesting each item. Reach Bank of Botswana and the relevant provider page independently to confirm the destination. Rehearse the file process during an advert redirecting to an unrelated domain, including time and privacy costs. If the recipient identity or payment account differs, halt transmission and investigate. The applicant may then contact the bank independently and resolve the mismatch; a complete file still does not guarantee approval.
Prepare truthful identity and address evidence
Checkpoint 3, “Prepare truthful identity and address evidence”, owns a different verification task. The submission file must establish whether all personal details are current and consistent across documents. Its preparation checklist contains identity reference, address proof, names, dates and explanation for any difference, with truthful versions, consent purpose and recipient recorded before transmission. Confirm the requested route using the bank’s current document request; never send a credential merely because a message appears urgent. The applicant rehearses an expired document or recently changed address so document collection does not conceal affordability pressure. Stop the file when someone suggests editing a document to satisfy a requirement. A safe procedural response is to explain the discrepancy and request formal instructions, without assuming acceptance.
Document income and employment accurately
Checkpoint 4, “Document income and employment accurately”, documents an independent comparison step. Before submission, verify whether the bank receives verifiable recurring income information without inflated figures. Organise income source, frequency, recent evidence, employment status and genuine variations in the application folder, retaining authentic versions and the bank’s reason for requesting each item. Reach original records requested through the official channel independently to confirm the destination. Rehearse the file process during overtime, commission or seasonal income falling away, including time and privacy costs. If the proposed repayment depends on income that cannot be evidenced, halt transmission and investigate. The applicant may then use a conservative figure or reduce the request; a complete file still does not guarantee approval.
List existing commitments
Checkpoint 5, “List existing commitments”, sets a specific stop condition. The submission file must establish whether the application and household budget include all current credit and essential obligations. Its preparation checklist contains balances, instalments, due dates, arrears, dependants and recurring necessities, with truthful versions, consent purpose and recipient recorded before transmission. Confirm the requested route using statements and the borrower’s payment records; never send a credential merely because a message appears urgent. The applicant rehearses another application or obligation starting before the new loan so document collection does not conceal affordability pressure. Stop the file when information given to different banks conflicts. A safe procedural response is to correct the record before continuing, without assuming acceptance.
Control document transmission
Checkpoint 6, “Control document transmission”, records a distinct source boundary. Before submission, verify whether each file goes to a confirmed bank channel for a stated purpose. Organise document name, recipient, time, consent and receipt in the application folder, retaining authentic versions and the bank’s reason for requesting each item. Reach the official website or bank-confirmed contact independently to confirm the destination. Rehearse the file process during repeated upload requests and weak connectivity, including time and privacy costs. If PINs, passwords, verification codes or unexplained transfers are requested, halt transmission and investigate. The applicant may then end the exchange and call the bank through a trusted number; a complete file still does not guarantee approval.
Review the decision and agreement
Checkpoint 7, “Review the decision and agreement”, serves a separate reader decision. The submission file must establish whether approval, if offered, still matches the requested scenario and budget. Its preparation checklist contains final amount, net proceeds, term, instalments, total, charges, conditions and cancellation or settlement points, with truthful versions, consent purpose and recipient recorded before transmission. Confirm the requested route using the written quotation, schedule and agreement; never send a credential merely because a message appears urgent. The applicant rehearses a bank changing the amount or duration during assessment so document collection does not conceal affordability pressure. Stop the file when the signed document differs from the version reviewed. A safe procedural response is to ask for correction, reconsider or decline, without assuming acceptance.