> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/_archive/social-registry/features/dynamic-registry.md). # Dynamic Registry Many government departments maintain registries built through surveys and data collection, but these are rarely updated, resulting in significant inclusion and exclusion errors in welfare delivery. OpenG2P’s **Dynamic Registry** transforms this process by ensuring beneficiary data is always current and accurate. With a suite of powerful update mechanisms, the Dynamic Registry enables: * Seamless integration and automatic data synchronisation from other departments, registries, and sources via **APIs** * Beneficiaries to easily update their information through intuitive **self-service portals** and mobile apps * Reliable **offline data collection** and updates in low-connectivity areas using field agents and mobile devices, with automatic uploads when connectivity is restored * **Agent-assisted** online registration and updates for those needing in-person support * Direct data updates by administrators, complete with a secure audit trail for full transparency This comprehensive approach dramatically reduces errors and ensures your welfare programs reach the right people, every time. With OpenG2P’s Dynamic Registry, you gain a future-ready, flexible, and robust solution to keep your beneficiary data accurate and actionable—empowering more effective and inclusive social protection programs {% hint style="info" %} References [SOCIAL PROTECTION POLICY PAPER - 2 - Dynamic Social Registries in Social Protection](https://www.undp.org/sites/g/files/zskgke326/files/2022-11/Social%20Protection%20Policy%20Paper%202.pdf) [Turkey's Integrated Social Assistance System](https://documents1.worldbank.org/curated/en/515231530005107572/pdf/Turkey-SA-summary.pdf) {% endhint %} ## Update mechanisms Several mechanims are available to keep the registry up-to-date as listed in the table below.
MechanismDescription
APIsAPIs provide automatic updates and real-time data synchronization between systems.
Login-based direct data entryAuthorised users can log into the SR module to manually insert or change information. You have direct control over the data and can make changes quickly using this mechanism.
Registration portalBeneficiaries who have registered can log in to the portal to receive services from service providers, such as organisations or entities. They can manually add and update their details on the portal.
ODK
  • ODK (Open Data Kit) can be accessed via Android devices, Agents, and other devices. ODK is a tool that allows for data collection from mobile devices. The ODK Collect app allows enumerators or field workers to collect data offline. The registrant details are uploaded to ODK Central as the agent moves to a place with internet connectivity.
  • The ODK Importer is a module built by OpenG2P. It is specifically designed to customise, set up the necessary field depending on the ODK form, and import the beneficiary's pertinent ODK form into OpenG2P Systems using the Social Registry module.
CSVUsers can upload a CSV (Comma-Separated Values) file with the most recent data to update the Social Registry. This approach is helpful for users with the data in a spreadsheet format or bulk updates.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.openg2p.org/products/registry/registry/_archive/social-registry/features/dynamic-registry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.