Verified Botswana facts
Coordinate enquiries and submissions so the Botswana borrower knows who received what, under which version and through which authenticated route.
Evidence and limits
Retain the provider identity observation, dated requirement page or written request, consent wording, exact submission copy, destination and acknowledgement for each lane.
Questions before signing
Repeatedly sending slightly different files through unverified channels can create privacy exposure, contradictory answers and confusion about which case is still active.
Decision worksheet
Create the board before sharing documents, permit only one deliberate state change at a time and close every inactive lane with a dated record.
Define one borrowing case before opening lanes
Write the purpose, requested amount in Pula, preferred repayment horizon and non-negotiable household constraints on a private case card. These are the applicant’s comparison inputs, not terms offered by a provider. Use the same card when reading each option so that a different amount or purpose does not masquerade as a better result. Add a stop condition for missing identity, unexplained payment instructions or pressure to bypass normal verification. The card does not predict acceptance. It simply prevents a new conversation from changing the problem before the applicant notices.
Authenticate each provider lane independently
Record the legal name presented, the official channel used to locate it and the date checked. When the named institution is a bank, compare the name with the Bank of Botswana licensed-bank page observed on the cited date. Treat that as a narrow register observation only. It does not authenticate a caller, agent, social-media profile, app or payment destination, and it does not show that a particular loan is available. Reach the institution through contact details independently obtained from a controlled source. If the names or destinations do not reconcile, hold the lane at research and send nothing.
Compare requested documents and unresolved questions
Build a requirement card from the provider’s current written request. List each document, acceptable format, destination and unresolved question. Do not assume that a requirement described by one institution applies to another. Mark sensitive material that is not yet justified by a clear request and remove unrelated pages from any copy. If requirement wording changes, preserve both dated versions and ask which applies to the case. This comparison is about the burden and clarity of the process. It cannot establish eligibility or forecast the provider’s response.
Keep research, enquiry and submission in different states
Looking at a public page is not the same as asking a question, and asking a question is not the same as sending a completed case. Give those activities separate markers. A submitted state requires a saved copy of the completed form or message, its attachments, the authenticated destination and a transmission record. Without that evidence, the state remains enquiry prepared or unknown. This vocabulary prevents a casual conversation from being remembered as a formal application and stops an unfinished draft from being treated as active. It makes no claim about how any external party categorises the contact.
Attach consent wording and a copy list
For every actual submission, record the consent text presented, the applicant’s action, the date and the exact files sent. Create a list that names the copies without reproducing their sensitive contents on the board. Do not infer what happens beyond the written notice or state that information will be used in a particular way. If the wording is absent, unclear or broader than expected, pause and request clarification through the authenticated channel. The board proves what the applicant saw and sent; any unstated handling, onward disclosure or retention remains unknown.
Use a pause signal when lanes begin to conflict
Pause a lane when two providers request incompatible versions of the same fact, when an attachment is out of date, when a destination changes unexpectedly or when the household scenario has changed. A pause is not a rejection and should not be described as one. Record the question that must be answered before movement resumes. Meanwhile, keep other lanes from copying the disputed value merely for consistency. The purpose is to preserve truthful, versioned answers. There is no universal number of conversations that is automatically acceptable; the board supports a deliberate case-by-case decision.
Log each received message without inventing status
Log the sender identity, channel, date, message reference and requested next action. Separate an acknowledgement, a request for another document, a proposal and a final communication according to the wording received. Do not convert silence, a generic notification or an informal assurance into a decision. Do not compare proposals until the same scenario and all compulsory components can be identified in responsible documents. The board should display unknown when the status is unclear. A follow-up request belongs to the provider lane and should use the previously authenticated contact route.
Record withdrawal through an authenticated channel
If the applicant decides not to continue, use the institution’s authenticated channel to communicate that choice and retain the message and any acknowledgement. Do not assume that deleting an app, ignoring a message or discarding a draft closes a submitted case. Record what was requested and what confirmation, if any, was received. The board may show withdrawal requested while closure remains unconfirmed. If a disagreement cannot be resolved directly and falls within the published scope, the Bank of Botswana consumer-protection page can be consulted for the escalation information it states. It does not decide the case.
Archive one final map of the application journey
At the end, export a private map showing each lane, its last verified state, documents shared, unresolved questions and the applicant’s next action. Restrict access to the records and retain only what is needed for the stated purpose and any legitimate recordkeeping obligation the applicant has confirmed. The map is valuable when a later message arrives because the recipient and version can be checked before responding. It should never display a guessed reason, personal outcome or prediction. An orderly archive closes uncertainty honestly instead of turning administrative activity into a promise.