Kapta · 15/09/2026
A map needs a maintenance process as clear as its interface design. Every location and contact should have a source, owner and review date so staff can correct inaccurate information promptly.
Which fields should each map location include?
Define the necessary fields: name, category, location, description, contact and responsible authority. Validate coordinates and address readability. Displayed information should match the location's purpose without attributing unconfirmed services or availability.
How can conflicting information be avoided?
Choose an authoritative source and document how changes reach the app. For an integration, confirm fields, update frequency and failure indicators. For manual maintenance, assign reviews to named staff and retain a change history.
Does showing a location recommend a route?
Not automatically. A useful-location directory and an emergency guidance system have different responsibilities. Content about routes or use of locations should be defined and reviewed by the competent authority; the app presents that information without inventing access conditions.
How can maintenance be tested?
Change a test contact, correct one location and unpublish another. Check the result in the app and website, including the date shown to users. Ask Kapta to include these cases in the project and explain how staff identify an update that failed to reach its destination.
Next step
Explore Kapta institutional services (Portuguese) and describe your project.
