Read the official class correctly
Checkpoint 1, “Read the official class correctly”, has a separate decision checkpoint. This locality-index question is whether the place is called a city or village exactly as Statistics Botswana records it. The settlement card preserves entity name, class, row code, census district, population and reference year and never substitutes a district aggregate for a named place. Its geographic authority is the final 2022 named-locality table; bank access remains a separate unanswered question. Apply associated localities or a whole district being added to the named place to the local decision lens instead of inventing market demand. When the boundary or version cannot be reconciled, the card cannot support a route or availability statement. The responsible index result is to keep the profile out until the exact geography is verified, retaining the official City or Village class.
Do not infer local product access
Checkpoint 2, “Do not infer local product access”, answers a distinct Botswana evidence question. For this settlement entry, first determine whether national product evidence remains separate from branch or digital availability in a place. Keep bank contact channel, date checked and answer about service access attached to the exact named locality, reference year and official class. Support the geographic statement with the two banks’ official Botswana pages, not a broader administrative figure. Use a reader planning travel or document delivery around an assumed branch only as a household decision scenario. If no bank source confirms the channel for that locality, no provider-access statement follows from the locality card. The index should ask the bank directly and budget for the confirmed route only, without relabelling a Village as a City.
Frame a local decision question
Checkpoint 3, “Frame a local decision question”, owns a different verification task. This locality-index question is whether the profile addresses a household borrowing decision rather than tourism or general place description. The settlement card preserves the need, amount, timing, income pattern and feasible no-loan alternative and never substitutes a district aggregate for a named place. Its geographic authority is the borrower’s records and nationally applicable bank evidence; bank access remains a separate unanswered question. Apply local travel, connectivity or timing costs affecting the process to the local decision lens instead of inventing market demand. When the local angle overtakes the personal-loan question, the card cannot support a route or availability statement. The responsible index result is to return the analysis to affordability and comparable written terms, retaining the official City or Village class.
Keep two quotations comparable
Checkpoint 4, “Keep two quotations comparable”, documents an independent comparison step. For this settlement entry, first determine whether residence does not justify comparing different amounts or repayment periods. Keep the same pula scenario, net proceeds, payment calendar, total and charges attached to the exact named locality, reference year and official class. Support the geographic statement with current written proposals from both banks, not a broader administrative figure. Use one application using a shorter or longer term for convenience only as a household decision scenario. If either document omits a required cost field, no provider-access statement follows from the locality card. The index should label the price result incomplete until both are aligned, without relabelling a Village as a City.
Protect identity during remote steps
Checkpoint 5, “Protect identity during remote steps”, sets a specific stop condition. This locality-index question is whether documents are transmitted only after the channel is independently confirmed. The settlement card preserves recipient, purpose, consent, time and receipt for every upload or handover and never substitutes a district aggregate for a named place. Its geographic authority is the bank-owned site and published contacts; bank access remains a separate unanswered question. Apply poor connectivity causing repeated uploads or use of an unverified intermediary to the local decision lens instead of inventing market demand. When someone requests credentials, secrecy or an advance transfer, the card cannot support a route or availability statement. The responsible index result is to stop, preserve the evidence and contact the bank independently, retaining the official City or Village class.
Link locality evidence to a national complaint route
Checkpoint 6, “Link locality evidence to a national complaint route”, records a distinct source boundary. For this settlement entry, first determine whether a place-specific service problem remains traceable to the responsible bank. Keep what happened, where, when, which channel, documents involved and remedy sought attached to the exact named locality, reference year and official class. Support the geographic statement with the bank complaint process and Bank of Botswana consumer guidance, not a broader administrative figure. Use travel or communication gaps making the chronology hard to reconstruct only as a household decision scenario. If the complaint is only verbal or lacks the underlying agreement, no provider-access statement follows from the locality card. The index should submit a documented bank complaint and follow official escalation if needed, without relabelling a Village as a City.