Language ownership
Choose English-only or reviewed Spanish scope; assign terminology, tone, legal/business copy, validation messages, help content, and final sign-off.
OSIPTEL reports broad household access through fixed or mobile internet while also showing why geography and actual audience evidence still matter. Build a resilient core task and verify it with representative users rather than turning a national percentage into a performance promise.
A Peru brief should explain how customers understand the offer, complete the task, receive evidence, ask for help, and recover when a provider or connection fails.
Choose English-only or reviewed Spanish scope; assign terminology, tone, legal/business copy, validation messages, help content, and final sign-off.
Use lean pages, saved progress, touch-safe controls, readable status, idempotent actions, and a return path after interrupted connectivity.
State where the service is actually available, what varies by location, who confirms addresses or schedules, and how unsupported requests are handled.
Keep contact, complaint, correction, refund, and support routes visible and connected to the same order or service record.
Name the Peru users, regions or service area, devices, languages, task, accessibility needs, and assisted path.
Attach ANPD, SUNAT, OSIPTEL, Indecopi, provider, and professional material to the exact decision it informs.
Define representative content, contact and location data, transaction states, document rejection, low-bandwidth behavior, and support scenarios.
Reopen the brief when the audience, Spanish scope, provider, tax/invoice path, data, consumer process, or fulfillment changes.
Avoid tourism motifs, broad claims, and machine-translated certainty. The actual customer, operator, provider, service area, language reviewer, and authority evidence determine the build.