Verified local facts
The stage-without-promise runway permits movement only on attributable evidence and keeps receipt, assessment, decision, signature and disbursement visibly separate.
Evidence reviewed
Help a Mauritius household separate review from approval using attributable evidence and a stop condition.
Decision checklist
The stage-without-promise runway permits movement only on attributable evidence and keeps receipt, assessment, decision, signature and disbursement visibly separate; review marker 118 applies this device only to “separate review from approval Mauritius” and the evidence boundaries named on this page.
Park at preparation
Complete the criterion matrix, identity wallet, income chronology and commitment register for the exact product. Preparation means the package is internally ready, not that the provider has seen or accepted it. Record missing items and stop conditions. Do not use a public calculator or eligibility phrase as permission to move to a later runway position.
Move to submitted
Use the authenticated route and record item list, consent, recipient and time. A browser message or sent email proves only what it actually states. Keep a copy of the submission record without duplicating sensitive files unnecessarily. If destination changes, return to verification. Submission starts provider handling but says nothing about completeness or outcome.
Mark receipt separately
Acknowledge only a reference or message attributable to the provider. Receipt is not a completeness check, assessment or approval. If no receipt arrives, follow up through the verified route rather than sending repeated packages. Record the household's follow-up date as its own control, not an institution promise. Keep the fallback active.
Mark assessment only when stated
An under-review message indicates the provider's stated stage and nothing more. Do not derive progress from MCIB participation, a data access request or silence. The institution may seek information or decide under its own process. Record message owner and date, and keep household circumstances current. A changed income or commitment still affects the household decision.
Handle information requests as new disclosures
Verify sender, purpose and relevance before responding. Add requested evidence to the record, record consent and obtain receipt. Do not interpret a request as favourable momentum or likely approval. If the request conflicts with the product or seems excessive, ask a bounded clarification. Data-access rights remain a separate personal-information process.
Separate decision from offer
Record approve, decline or another provider-owned result exactly. An approval may carry conditions and proposed terms; it does not prove affordability or final contract. A decline does not explain a personal data record unless the responsible party says so. Do not invent reasons. Send any offered schedule back through cost, charge, term and household-capacity review.
Separate signature from disbursement
Review contracting entity, net proceeds, rate basis, charges, schedule and conditions before voluntary signature. Signature itself does not prove money has been released. Record disbursement only from actual account or payee evidence. Keep project deadlines and fallback visible. A delay or changed amount creates a new decision rather than an automatic continuation. Add a runway fuel gauge based on household resilience rather than provider timing. Record how long the underlying purchase, repair or other purpose can wait, which deposits or commitments could be lost, and what lawful fallback remains if no acceptable offer arrives. The gauge does not estimate processing days. It shows when the household must revisit the project instead of treating silence as progress. At each confirmed stage, perform a change scan across income, commitments, requested amount, purpose and deadline. A material change reopens the relevant evidence and affordability work even if the provider has not requested it. Keep a communications tower beside the runway log. Only messages obtained through a verified institution route can move the marker; a phone statement is recorded with caller details and independently confirmed where the action is consequential. Requests for unusual payment, credentials or an urgent transfer are isolated as security incidents and never treated as conditions of ordinary advancement. When an offer appears, park it at the review stand. Compare contracting entity, net proceeds, rate basis, charges, repayment dates, conditions and expiry with the household's current budget and purpose. An earlier indicative statement cannot fill a missing term. The applicant may pause or leave even after a favourable message and before voluntary commitment. The runway closes only when the household records the actual end state and archives the messages supporting it. That end state may be withdrawal, decline, expired proposal, signed agreement or evidenced disbursement; the labels are not interchangeable, and none retrospectively turns earlier uncertainty into a promised outcome.
Close the runway log
List every stage reached, supporting message, disclosure, unresolved condition and next action. The log names no standard processing time and predicts no approval. It cannot tell what an MCIB participant holds or replace a data request. The household may leave the runway at any stage before commitment. A new offer version reopens review positions rather than inheriting an old pass. Add a runway incident board for stalled, contradictory or suspicious messages. Each incident records the stage claimed, authenticated sender check, affected disclosure, household deadline and fallback. Do not advance the marker until the contradiction is resolved by the responsible provider. A suspected impersonation is handled outside the same contact route. The board prevents urgency from making an unverified message look like progress and keeps the household project from depending indefinitely on a status that no competent owner has confirmed.