Field brief / Colombia
This is not a market-entry promise or a substitute for local advice. It is a set of questions that reveals which Colombia-specific facts must change the scope, interface, test plan, or handoff.
Decision register
The point is not to collect trivia. Every row should end in a requirement, an explicit exception, or an assigned verification task.
| Area | Question to answer | Evidence before release |
|---|---|---|
| Audience | Who in Colombia uses, approves, supports, or pays for the system? | Named roles and one tested priority journey. |
| Language | Which surfaces require Colombian Spanish, and who approves wording? | Language owner, terminology list, and native review where required. |
| Geography | Do address, department, municipality, coverage, or travel assumptions affect the workflow? | Representative inputs and service-area rules tested. |
| Data | What is collected, why, where it travels, who can access it, and when is it deleted? | Data map, notices, vendor list, retention, response, and incident owners. |
| Commerce | Who sells, invoices, collects, settles, refunds, and reconciles? | Approved provider route, invoice model, failure states, and reconciliation test. |
| Access | What devices, connection conditions, permissions, and support routes matter? | Mobile, accessibility, recovery, performance, and support checks. |
| Acceptance | Who says it is done, and what will they inspect? | Live acceptance record, known limitations, access handoff, and rollback path. |
When Colombian pesos are displayed, confirm whether COP is informational, contractual, charged, or settled. The client and its advisers own the final commercial and tax model; the software implements the approved behavior.
Useful output
Build the record
Faith Forge Labs can turn that context into a scoped technical route without pretending every country question has already been answered.