| ID | ENV-1 |
|---|---|
This use case provides step by step guidelines on how to implement the Extended Producer Responsibility (EPR) system of waste from electrical and electronic equipments (also known as e-waste). EPR is an environmental policy approach that regulates a producer’s responsibility for a product throughout the product’s life cycle. Improper disposal of e-waste poses numerous threats to the environment, economy, and health and well-being of citizens. Under the EPR approach, a producer takes the responsibility for financing collection, recycling and end-of-life disposal of e-waste equipment/product streams - batteries, small consumer electronics, accumulators, packaging and other EPR product categories - in order to mitigate the environmental impacts of their products throughout the entire product life cycle. It thereby aims to increase the separate collection of end-of-life products and to enable their more circular treatment.
Implementing EPR can create various environmental, economical and social benefits. Example of EPR benefits include - improved waste collection and treatment, higher rates of waste reuse and recycling, incentivizing greener products, helping to finance waste collection and processing, and generally promoting a sustainable management of waste and circular economy. Governments in low- and middle-income countries are increasingly interested in implementing an EPR system in various forms through a system where they: define the products covered, the producers affected, the obligations imposed on producers - targets and fees, disseminate information on EPR and e-waste to stakeholders and citizens, and have a process to ensure effective monitoring and enforcement of the EPR.
Ministry of Environment or any Ministerial body in charge of environmental, recycling, waste, ICT and/or circular economy related regulations and policies.
Inspectorate, Competition and Consumer Protection Authority or any governmental body that ensures the protection and promotion of basic consumer rights as well as safeguarding healthy competition among enterprises.
Utilities Regulatory Authority or any governmental body with the mandate to license, monitor and enforce license obligations in the ICT sector.
Revenues Authority or any government revenue collection agency in charge with enforcing, assessing, collecting, and accounting for the various taxes imposed in a country.
Producers/business operators that manufacture, import, distribute, resell and/or assemble electrical and electronic equipments (e-waste products).
11.6: Reduce the adverse per capita environmental impact of cities, including by paying special attention to air quality and municipal and other waste management.
12.4: Achieve the environmentally sound management of chemicals and all wastes throughout their life cycle, in accordance with agreed international frameworks, and significantly reduce their release to air, water and soil in order to minimize their adverse impacts on human health and the environment.
12.5: Substantially reduce waste generation through prevention, reduction, recycling and reuse.
12.6: Encourage companies, especially large and transnational companies, to adopt sustainable practices and to integrate sustainability information into their reporting cycle.
The Ministry of Environment or relevant Ministry, should coordinate with relevant authorities i.e. the Inspectorate, Competition and Consumer Protection Authority, Utilities Regulatory Authority, the Revenues Authority etc., to develop and establish a legal EPR Framework and Implementation Plan that outlines the responsibilities and role of all relevant authorities. The EPR framework should include key clauses on scope of obligated products, stakeholder roles and responsibilities, financing mechanism, targets, penalties, authorization procedure, reporting, monitoring and enforcement mechanisms. To formulate this document, the Ministry can map policies and learnings from other countries, evaluate e-waste quantities and flows within their country, analyze waste management infrastructure and skills, as well as existing policies and legislation at national and sub-national level.
As a next step, the draft Framework can be shared with a core group of diverse stakeholders including other government authorities, civil society actors, and private sector actors that are electrical and electronic equipment producers (importers, distributors, manufacturers and resellers) - to review and comment on the draft document via workshop format sessions. A co-creation session with this group around the registration and EPR fee payment procedure would be very useful to acquire input from producers, and promote a user-friendly EPR designed process.
Once the EPR regulations and processes have been finalized, information on the EPR scheme can be disseminated via - media campaigns facilitated by relevant government authorities, and through local private sector federations/associations.
Workflows
Client education for educating and/or informing producers (e.g. an importer, manufacturer, distributor or reseller) on the EPR legal framework, requirements, fee as well as sustainable e-waste management and collection systems they are recommended to implement.
Client communication to facilitate information dissemination of the EPR Framework and electrical and electronic product license and registration process via government and business registration and licensing websites, mobile / media channel(s)
Country wide campaign to increase awareness amongst local population about how and where to drop off old electrical and electronic equipment and the status of e-waste collection and management in the country.
Identification and Registration where target producers register with the relevant Regulatory Authority of the EPR system, apply for operational licensing and register the electricals and electronics they intend to introduce (new or used) into the market. Producers are then allocated a certificate of approval with an EPR registration certificate and operational license number for identification purposes.
Content management for the backend EPR Regulatory and Revenue Authorities to populate, track and monitor e-waster producers (electronic manufactures, e-waste importers, e-waste management and recycling companies), and their registered products.
Building Blocks
Producer registration is the process of collecting information of a new business - i.e., a business' name, purpose, tax data, etc – required by the chamber of commerce and/or relevant government authority as part of the business registration process. In this use case, producers (e.g. an importer, manufacturer, distributor or reseller) of electrical and electronic equipment have to register with the relevant Inspectorate, Competition and Consumer Protection Authority, as a business entity planning to operate in the electrical and electronics sector. A certificate of domestic company registration will be provided to the producer following their provision of the required registration information. The business registration certificate is a prerequisite in order for the producer to then apply for the operational license required to put electrical or electronic equipments on the market.
Workflows
Data Collection and Reporting for capturing the business registration information of producers wishing to operate in the electronics and electrical sector.
Identification and Registration for locating, authenticating and tracking business operators registered in the EPR system.
Client Case Management for automating the process in creating, collecting and organizing the registered producers' records in one place. This will allow the convenient access and a comprehensive view of each registered producer in order to initiate and manage compliance. Moreover, support improved and timely registration services, and back office efficiencies.
Building Blocks
Licensing is the process to acquire authorization from a government agency to operate in a sector that has specific requirements that need to be met. In this use case, licensing is fee-based and is the process for business operators, manufacturers, importers, distributors or assemblers of e-waste products, to apply for operational permission to introduce e-waste products into the local market. The local government's Regulatory Authority makes the decision on whether or not to issue an EPR license. This license is required for all producers to acquire prior to registering the specific type of e-waste product(s) they plan to introduce into the market. Licensing application to include i.e. licensing application fee payment receipt, completed application form, certificate of domestic company registration, environmental impact assessment, audit certificates etc). Certain countries also require site visits of a producers warehouse/factory prior to approving the issuance of a license.
Workflows
Data Collection and Reporting for capturing and evaluating licensing application data submitted by producers of e-waste products.
Identification to easily be able to identify and track registered business operators applying for a license within the EPR system.
Client Case Management to help automate and manage the licensing application and approval process, schedule site visit appointments of e-waste factories/warehouses, and distinguish between new and renewal licensing applications. Moreover, support in vetting/ensuring the applicants meet the eligibility requirements, and have submitted all required documentations.
Client Communication to update producers on additional documentations required and/or application status updates/outcome.
Financial Services for facilitating one off licensing application fee payment by the producer and allocation of a fee payment receipt.
Building Blocks
Registration is the process of documenting and maintaining records of registered electrical and electronic products (new or used) being manufactured, distributed, imported and sold on the market. All licensed producers will be required to register the respective type of e-waste goods they wish to introduce to the market - in order to obtain a registration number/code for each type of product. As part of the product registration process: producers submit a completed product registration application form with agreement to comply to the EPR, the product user manual, installation manual, and document indicating product life span. The producer completes this registration process by paying the product registration application fee and receiving a receipt confirming payment. Some producers may be requested to submit a product sample. Based on whether a producer imports their e-waste products, additional data might be requested (i.e. import permit, product country of origin etc). Once all requirements are met, the producer receives a registration number/product code.
Workflows
Data Collection and Reporting for capturing the registration data of e-waste product(s) that will be on the market.
Identification and Registration for locating and tracking e-waste products being introduced into the market in all phases of their life cycle.
Client Case Management for automating the process in creating, collecting and organizing the registered e-waste products' records in place. This will allow the convenient access and a comprehensive view of each type/category of registered e-waste products in order to calculate EPR fees and manage compliance.
Financial Services for facilitating one-off product registration application fee payment by the producer and allocation of a fee payment receipt.
Building Blocks
Data verification and validation should be coordinated with all relevant governement authorities and regulatory bodies. For the EPR system, in certain countries, the registration data collated of the e-waste producer and their products by the respective business registration and licensing authorities, is then generally checked by the Ministry of Environment, and against other government databases (eg. ID, tax, chamber of commerce, etc.) in order to fill in any missing gaps, verify and validate collected information, including authentication of all records. *Data checking approaches also vary: sometimes batch-sharing via CD, sometimes full interoperability.
Workflows
Client Case Management for storing and reviewing identification, registration, and licensing records.
Data Analysis and Business Intelligence for cross-referencing and verifying records across multiple registry sources, and reconciling gaps / overlaps.
Building Blocks
For this use case there are three specific payments: (1) producer licensing fee, (2) product registration fee, and (3) EPR fee.
The producer licensing fee and the product registration fee are to be paid as part of each application process/phase, to the respective government agency in charge of allocating EPR licensing and EPR products registration. A payment receipt is to be provided to each producer for each payment made.
The concept of the EPR policy scheme is that an EPR fee is to be paid for each type of electrical and electronic equipments introduced into the market every year. The fee will be used at the end of the product lifecycle to cover the collection, treatment, recycling and awareness raising when it becomes e-waste. The EPR regulatory framework must clearly spell out which entity will collect the EPR fee, how much the fee is, what the methodology is being used to determine the fee, and how payment should be processed. For instance with e-waste products being imported, the EPR fee can be collected at the point/port of entry by Customs Revenue Authority or the Utilities Regulatory Authority. The EPR fee can be collected with the import tax fee etc. To facilitate this, producers could be required to declare cargo (online: e-single window) and make the payment through an online portal.
The fee to be paid could be proportional to the amount of electrical and electronic equipment introduced into the market. Below are examples of methods that can be used to arrive at the fee:
Product EPR fee paid by the producer = Total costs for waste stream divided by/ Mass of product type put on the market.
Market share calculation for a producer:
Market share = The weight of products put on the market by an individual producer per product type divided by/ The total weight of products put on the market by all producers for that specific product type
Obligation calculation for a producer:
Obligation for a producer = Total reported tonnage by product type multiplied by* Individual producer's market share
Total costs per e-waste product stream:
Total costs = Overhead costs per product type multiplied by* % Market share + Operational costs (per tonne) multiplied by* Tonnes collected
Product EPR fee paid by the producer = An EPR cost is calculated and associated for every possible type of e-waste product. Thus, the EPR fee a producer has to pay is the quantity of a product they plan to introduce into the market multiplied by the EPR cost associated with the product type.
Workflows
Financial Services for processing EPR fee payments by producers.
Client Case Management for identifying, authenticating and monitoring/verifying that the e-waste producers have made the EPR payment and the transaction has been fully processed and received.
Building Blocks
This step involves ensuring information of e-waste producers are kept up to date - specifically relating to registration and licensing. Also ensuring that there is a process in place to address any complaints, grievances and appeals raised by the producers. This process should be led by the government authority's EPR compliance officers/team.
Workflows
Data Collection and Reporting for capturing changes in producer's information (e-waste products, licensing etc).
Client Case Management for identifying and recording producer interaction with EPR compliance officers and capturing reported cases on grievances / appeals etc., and for determining decisions/actions to proceed with by reviewing individual producer client case.
Building Blocks
The government authority leading the EPR implementation should also allocate a team in charge of regulating EPR compliance and enforcing penalties. A monitoring team consistently tracking all e-waste operators active in the market, registered with a license within the EPR system and payments of the EPR fee. A live database should be put in place to categorize and track e-waste products in the market and EPR fee payments from the producers. Late payments can be tracked and an automated system put in place to send out late fee penalties to the producers.
Workflows
Financial Services for processing late EPR fee payments by producers.
Client Case Management for identifying, authenticating and monitoring/verifying that the e-waste producers have made the EPR fee payment and the transaction has been fully processed and received.
Building Blocks
Identification and Verification
Garam Bel, Circular Economy Coordinator, International Telecommunication Union (ITU)
Wesley Brown, GovStack Product Owner, Digital Impact Alliance
Taylor Downs, CEO and Founder, Open Function
Jaume Dubois, Digital ID Lead, GovStack
Longin Dusengeyezu, Database and Applications Lead, Rwanda Institute for Conservation Agriculture (RICA)
Theophile Dusengimana, Environment and Climate Change Policy Specialist, Rwanda Ministry of Environment
Hani Eskandar, Head of Digital Services, International Telecommunication Union (ITU)
Sarah Farooqi, The Exchange Product Owner, Digital Impact Alliance
Sainabou Jallow, Business Analyst, Digital Impact Alliance
Concord Kananura, GovStack Africa Regional Coordinator, International Telecommunication Union (ITU)
Dismas Karuranga, Pollution Control Specialist, Rwanda Ministry of Environment
Nico Lück, GovStack Advisor, GIZ
Margus Mägi, GovStack Project Lead for Estonia, Governement of Estonia
Yolanda Martínez, Overall Lead for GovStack, International Telecommunication Union (ITU)
Antoinette Mbabazi, Head of Registration& Licensing Department, Rwanda Institute for Conservation Agriculture (RICA)
Olivier Mbera, Country Manager, Enviroserve Rwanda
Robert Mugisha, Director of Registration& Licensing Unit, Rwanda Institute for Conservation Agriculture (RICA)
Eric Murera, Environment Expert, Private Sector Federation (PSF) Rwanda
Dr. P. S. Ramkumar, GovStack, International Telecommunication Union (ITU)
Ayush Shukla, Technical Officer, International Telecommunication Union (ITU)
Patrick Umuhoza, Multilateral Cooperation Officer, Rwanda Environment Management Authority
Olivier Urukundo, Engineering Risk Analysis Specialist, Rwanda Institute for Conservation Agriculture (RICA)
Eng. Gaston Uwayo, TMEA ICT Technical Assistant, Rwanda Standards Board
Damascene Uwizeyemungu, IT Officer, Rwanda Utilities Regulatory Agency
Meelis Zujev, Project Manager, Govstack Sandbox, Gofore
Name
Extended Producer Responsibility (EPR)
Sector
Environment and Climate
Version
1.0
Status
Published
Within the core GovStack Initiative, "reference use cases" are used to provide context and limit scope of the various GovStack Building Blocks. These use cases are considered to be part of GovStack and are versioned and released alongside the Building Block Specifications when a given GovStack release occurs.
Work on use cases is organized by the GovStack Product Committee and is tracked by the Product project on the GovStack Jira instance.
| ID | HLTC-1 |
|---|---|
This use case profiles the digital integration steps to provide high-quality and integrated Postpartum and Infant Care services for a mother and child spanning the mother's prenatal and postnatal periods - during the pregnancy, childbirth and after birth. Governments in low- and middle-income countries are increasingly implementing mother and child care programmes to provide primary healthcare services, prenatal care and educate new mothers about post-delivery care (e.g. breastfeeding, nutrition, immunization, personal hygiene).
Postpartum maternal and infant mortality is still high across multiple low and middle income countries. This use case will support and guide countries in their efforts to reduce maternal and perinatal mortality and morbidity, through digitizing the process of postpartum care and services.
Ministry of Health and Welfare or national government body in charge of providing nationwide healthcare services and/or postpartum services and care.
Community healthcare workers trained in essential newborn care, and providing postpartum care for both mother and their newborns.
Expectant mothers and their new born babies as the key beneficiaries of this service.
3.1: By 2030, reduce the global maternal mortality ratio to less than 70 per 100,000 live births.
3.2: By 2030, end preventable deaths of newborns and children under 5 years of age, with all countries aiming to reduce neonatal mortality to at least as low as 12 per 1,000 live births and under‑5 mortality to at least as low as 25 per 1,000 live births.
Staff from the Ministry of Health or the relevant government agency leads a campaign to spread awareness about a new mother and childcare community health programme with the purpose of facilitating postpartum healthcare services. A comprehensive information and education campaign is developed around prenatal and postnatal healthcare services available through the programme. These educational materials/content can be made available in local languages online. The materials could include information on programme enrollment process and incentives, primary care recommendations/guidelines, pre-and post delivery healthcare support services being offered, participating facilities/clinics, beneficiaries rights and responsibilities, etc.
Outreach communication should be intensive during the kick-off phase of the new programme, but also requires targeted communications to encourage expectant mothers' enrollment in the mother and child care community programme. The campaign can be conveyed via mobile messaging and/or aired on national radio/television as well as through field visit campaigns to local villages, hospitals/clinics - performed by well trained community healthcare workers.
Workflows
Client Communication to facilitate the spreading of programme awareness for target audience and encouraging enrollment via mobile / media channel(s)
Client Education for educating potential target beneficiaries around the approach and objective(s), benefit(s), incentives, role of Community Healthcare Workers, partner(s), etc. of the programme
Content Management for the backend Community Healthcare Workers staff to populate relevant educational and promotional content that local clinics, hospitals, facilities etc, can disseminate and use during on-the-ground outreach campaigns
Building Blocks
Registration is the process of collecting information of target beneficiaries for identification purpose, assessment of their needs and conditions, and to enroll them in a programme. Depending on specific country context, registration can work in very different ways. Registration should support the creation of an electronic medical record and tracking capabilities for each enrolled beneficiary. This can ensure timely and effective monitoring of healthcare data.
For example, some countries use a centralized information technology based application to deliver maternal and child health care services through name-based tracking. During registration, the following information is collected: the mother's name, phone number and ID, as well as the information of their child's name, address and birth certificate. The data (the birth certificate and mother’s ID) provided is then automatically validated in the government’s citizen records system. Once their information is validated, it results in the following: 1. an online account per beneficiary - created for records associated with the mother and child care community programme; 2. a barcode unique to each beneficiary; 3. a Community Healthcare Worker assigned to their case to support the beneficiary in accessing all health services under this programme.
Workflows
Data Collection and Reporting for capturing responses or general observation during registration process
Identification and Registration for registering the mother and child in the system
Client Case Management for the target beneficiary (mother/child's main caregiver) to give permission to a Healthcare Worker to access and use their electronic healthcare record to coordinate the mother and child's healthcare services being provided under the programme
Building Blocks
Data within the Mother and Child Tracking System (MCTS) is generally checked by the Ministry of Health managers, against other government databases (eg. ID, citizen's records, civil registry municipality etc.) in order to fill in any missing gaps, verify and validate collected information, including authentication of all records. *Data checking approaches also vary: sometimes batch-sharing via CD, sometimes full interoperability.
Workflows
Client Case Management for storing and reviewing identification records and authentication information of target beneficiaries
Data Analysis and Business Intelligence for cross-referencing and verifying records across multiple registry sources, and reconciling gaps / overlaps
Building Block Workflows
Eligibility determination is the process of assessing whether an eligibility criteria is met inorder to benefit from certain services. In most countries, the maternal and child health programme is part of the general health services provided by the government, however the eligibility structure can vary across countries. All expecting mothers and caregivers of infant children are generally considered to be eligible beneficiaries. The targets for this programme depends on a country by country basis. In certain countries, the target beneficiaries all women in their reproductive age groups, i.e., 15 - 49 years of age, and infants/ new born population. ***Certain government's give eligibility priorities to low-income pregnant individuals to help them get the health and social services they may need and covers a variety of services for pregnant individuals and their infants.
Community Healthcare workers determine eligibility by reviewing all submitted registration details. Once eligibility has been determined, a notification (via sms, email etc) is sent to the beneficiary.
Workflows
Client Case Management for effectively managing all eligible and enrolled beneficiaries in the programme and monitoring the healthcare services being provided to them
Communication to inform target beneficiaries that they meet the eligibility criteria and can start the enrollment process
Data Analysis and Business Intelligence potentially for mapping and analyzing the different beneficiaries - socioeconomic / demographic information
Building Blocks
Enrollment is the action of being enrolled and accepted as a beneficiary to receive certain benefits and/or access to a service provision. In certain countries, once eligibility is confirmed, the target beneficiary is considered as enrolled in the programme. During the enrollment, further data can be collected (depending on programme design) e.g. pregnancy and general health details, phone number, bank account details, biometrics, etc. Moreover, depending on the system setup by country, each beneficiary is then issued an online account and/or unique barcode to keep track/record of each beneficiary participating in the programme and utilizing the primary healthcare services being provided. **All programme specific data is often stored in a tailored software application that supports beneficiary management functions (e.g. enrollment, payments, case management, M&E etc.).
Workflows
Data Collection and Reporting for capturing additional programmatic information on the beneficiaries during enrolment
Financial Services for staging beneficiary account details for enrollment incentive payment processing
Identification and Registration for identifying beneficiaries and confirming enrolment
Client Case Management for storing program specific data for tracking
Building Blocks
Certain mother and child community health programs have a financial incentive in place in order to incentivize eligible beneficiaries to enroll and fully participate in the programme and the pre and post natal health services being provided. Furthermore in some cases, Community Health Workers also receive an incentive distribution for convincing/facilitating the process for expectant mothers to enroll in the programme. In most cases, incentive distributions are paid through mobile G2C or B2C incentive payments. Payments are subsequently paid according to the programme schedule e.g. one time incentive payment.
Workflows
Financial Services for processing incentive payments that are G2C or B2C mobile payments, for withdrawal by beneficiary from designated mobile money/ pay-point(s) thereafter
Client Case Management for identifying and authenticating individual that is making a withdrawal, or to recall / verify deposit account information prior to payment transaction
Building Blocks
As part of this programme, Community Healthcare Workers or healthcare professionals, play a very active and hands-on role in the programme. They are generally the professionals on the ground, reaching out to target beneficiaries and convincing them to enroll in the programme.
This step involves ongoing interaction with beneficiaries via Community Health Workers and local hospitals/clinics/facilities to: ensure information on beneficiaries stays up to date, monitor usage of the primary healthcare services, and address grievances, and general primary care needs. Note that this step also requires clarity, clear decisions, and protocols regarding up-to-date data management and sharing between different health clinics and hospitals that provide pre-and post natal healthcare services.
Workflows
Data Collection and Reporting for capturing changes in beneficiary information
Client Case Management for identifying and recording beneficiary interaction with Community Health Workers, local hospitals/clinics and capturing reported cases on grievances etc., and for determining risks / conditionality by reviewing individual beneficiary client case
Work Planning and Coordination to potentially suggest and connect with other hospitals, clinics and relevant healthcare services to target beneficiaries
Building Blocks
National healthcare managers and officers make decisions and management choices (e.g. where to conduct add-on training on pre-natal and post-natal care, enrollment facilities in clincs/hospitals, or communities, where to prioritize budget, etc.) on up-to-date data on the programme/s (e.g. what primary healthcare services are being provided and by whom, where and when, what areas are performing better, etc). Note that countries that do this effectively ensure programme data is connected / integrated/ uptodate on MCTS and other relevant databases.
Workflows
Client Case Management for ongoing monitoring and tracking of both mother and child's health wellbeing and performance, ensure easy assessment of holistic view and reporting
Identification and Registration (with aid of geographic information services tool for potential use) in tracking / locating clinics and hospitals being used through the programme
Data Analysis and Business Intelligence / Decision Support / Data Collection and Reporting to analyze, update, and report programme output / performance information
Building Block Workflows
Ensuring data is up to date to trigger: Programme exit for those who are no longer eligible e.g. when a beneficiary dies, migrates, child exceeds eligible infant age or no longer qualifies for other reasons. This is achieved via a combination of re-enrollement campaigns anytime a mother is expecting, automated data updates, and data-sharing with other government databases e.g. civil registration for brith and death. Programme entry for newly eligible beneficiaries, via new data collection or analysis etc. Other changes to entitlements (e.g.child no longer considered an infant). Note that this step also requires clarity, clear decisions, and protocols regarding whose data (or subset of such) is to be updated by which programme personnel or role and at what time.
Workflows
Data Collection and Reporting for routine update of information on the beneficiary client base, and integration of other databases and systems for automated data update on client cases overtime
Client Case Management for ongoing review of beneficiary case information
Data Analysis and Business Intelligence / Decision Support to support identification of individuals for exit or entry based on analyzing change in programme-specific / socioeconomic data
Building Block Workflows
Wesley Brown, GovStack Product Owner, Digital Impact Alliance
Steve Conrad, Associate Director of Technology, Digital Impact Alliance
Sarah Farooqi, The Exchange Product Owner, Digital Impact Alliance
Sainabou Jallow, Business Analyst, Digital Impact Alliance
Dr. P. S. Ramkumar, GovStack, International Telecommunication Union (ITU)
Max Carlson, GovStack
Raul Kaidro, GovStack
| ID | URB-1 |
|---|---|
This use case profiles the implementation process of a construction permit. A service that automates the entire construction permit approval process - from enabling online application submissions of building construction plans, to initiating verification and final approval by the local government authorities. This process is how local governments can decide whether to approve or decline construction permit applications by evaluating submitted building plans, and assessing their compliance with standard building codes and local regulations. A construction permit is an important requirement for countries to ensure buildings and structures are safe, with sound engineering, foundations and construction techniques.
Municipalities and counties/towns have traditionally managed construction permits "over the counter" and through paper or PDF applications. This time-consuming, complex and error-prone tasks has raised issues in some countries - around the accountability and transparency, as well as inefficiencies in achieving timely construction permitting processes, and sustainable urban planning development. As a result, a number of governments in low-and-middle income countries are implementing an online construction permit. A digital service with a hassle-free online procedure and user-friendly tools to achieve a more streamlined end to end approval process that ensures transparency, accountability, and time-bound services.
Ministry or national government body in charge of urban development, housing, and/or town planning.
Local building government authorities - building officials, inspectors and design auditors - across municipalities in charge of reviewing and/or issuing construction permits.
Technical team responsible for the rollout of the construction permit portal/platform initiative in the state - system integrator, building architect, software engineer, QA engineer, help desk staff, DevOps engineer etc.
Citizens and professionals (engineers, architects, construction supervisors) seeking permission to construct, renovate or alter a building.
11.3: By 2030, enhance inclusive and sustainable urbanization and capacity for participatory, integrated and sustainable human settlement planning and management in all countries.
11.6: Reduce the adverse per capita environmental impact of cities, including by paying special attention to air quality and municipal and other waste management.
Staff from the Ministry of Urban Planning or another leading agency / organization in charge of regulating all aspects of a country's construction permit issuance processes (building codes and laws), leads the campaign to disseminate information about the construction permit. Roll out of this service can be disseminated on the Ministry's and all the municipalities' websites and social media platforms. Marketing and promotional communication materials (i.e., brochures, pamphlets, flyers etc) can also be made available at the local municipalities/urban planning centers.
To achieve clarity, consistency and transparency on the new online process and requirements for obtaining a construction permit, target communication to the key stakeholders involved (issuing government authorities, citizens, architects, engineers) should be prioritized. The state team can lead rollout plans and ensure the necessary infrastructure for local municipalities staff training and deployment are made available at each building plan department in the country. Moreover, to ensure that implementation of the construction permit approval method is uniform throughout the country and that the rules are not interpreted differently, a user manual on the new construction permit should be provided to each local government building plan staff.
Awareness campaigns can be organized across municipalities informing citizens about the new construction permit application procedure with information on how they can upload their application (building plans and construction documents), pay fees and track their application online, schedule an inspection (if required), and download and print their permit order once issued.
Workflows
Client communication to facilitate information dissemination on the new digitized construction permit via government and municipalities' building construction permit websites, social media, and national media channel(s).
e-Marketplace as a web-based application to promote and disseminate information of all government services offered to citizens, and guidance on how to access them.
Content management for the development of a user manual and training guide on the digitized service for building plan officials and/or users wishing to submit a construction permit application.
Staff communication and education for informing construction permit issuing staff authorities about the construction permit. Organize training sessions for staff on how to review applications, check fee payment status, and process and issue permits - all online.
Identification and Registration for providing an administration account for all qualified government building plan staff with authority to issue construction permits.
Data Collection and Reporting for capturing the new construction permit and regulation changes, and to report this data to all relevant stakeholders.
Building Blocks
Registration is the process of collecting information of users wishing to access a digital service. Depending on specific country context and the platform being utilized to host the construction permit, registration process could defer. This service can be hosted using a single window approach to facilitate the end-to-end construction permit application procedure and clearances from multiple agencies or departments.
In certain countries, there is a statewide online construction permit platform in place, and the target users - citizens, architects, engineers etc., are required to register (provide full name, email, phone number, occupation etc.) on the platform in order to generate personalized login credentials. Then subsequently with these login credentials, the user can then create, save and/or submit a construction permit application on the online portal. **If a country already has a national digital registry system in place with a unique identification number for every citizen, then the registration step that allocates a unique username and password to access the permitting platform might not be necessary. In some countries, a citizen can use their national electronic identification data to access all online public services. This system will pull in all applicants' data to facilitate their registration process.
Workflows
Data Collection and Reporting for capturing, managing and evaluating registration application data submitted, and in some cases - allocating personalized login credentials per user.
Identification to easily be able to identify and track registered users.
Client Case Management to help automate and manage the registration process, and respond to any inquiries or issues around registering on the platform.
Building Blocks
A permit application is the process of applying for the issuance of a legal document to conduct a specific activity that requires the approval from a governmental authority. In this use case, a construction permit is an official approval issued by a local government agency that reviews construction permit applications to ensure the building plan complies with local standards for land use, zoning, and construction. Once approval has been received, the applicant can start the construction project.
Depending on the country context, the application process can require applicants to first login to the permitting platform using their unique identification data from the registration step (i.e., username and password or national identification data). Then fill out a standardized online application form, upload the documents required to process the application and asses the building design (i.e., building plan - drawings, specifications, photographs of existing situation, photomontage of proposal, land title, ownership certificate, etc) and pay the application fee that must be submitted with the application. Once their application is submitted, applicants should be able to view and track their application, schedule any follow-up appointments required for document scrutiny and/or site inspection visits by a public official. Emails and SMS notifications can be sent to the applicants to request follow-up action items and provide updates during the application process. ** An application cancellation request could be made available for applicants to cancel their permit request at any stage.
Workflows
Client Case Management to help automate and manage the permit application submission process. Support in vetting applications - ensuring the applicants meet the eligibility requirements and have submitted all required documentations. Also schedule any necessary follow-up site visits by the building plan inspection authority.
Data Collection and Reporting for capturing and evaluating permit application data submitted by the user applicant.
Identification to easily be able to identify and track registered applicant applying for a construction permit.
Financial Services for processing the permit application fee and generating payment confirmation receipt.
Building Blocks
Data within the online construction permit is generally checked* by the Central Level Ministry in charge of urban planning and the local permit issuing municipality departments, against other government databases (e.g., ID, tax, land titles, utilities, etc.) in order to fill in any missing gaps, verify and validate collected information, including authentication of all records. *Data checking approaches also vary: sometimes batch-sharing via CD, sometimes full interoperability. This step may be done for both the registration (step 2), and application process (step 3) - whereby before any application is reviewed, each applicant's submitted data will be scrutinized and vetted. **To address data privacy issues, in some countries, data sharing permission should have already been requested and granted from the applicant, to conduct the data checking process against other government databases.
Workflows
Client Case Management for storing and reviewing registration, and construction permit application records.
Data Analysis and Business Intelligence for cross-referencing and verifying records across multiple registry sources and reconciling gaps / overlaps.
Building Blocks
The construction permit can have APIs in place that can scrutinize submitted construction permit applications to support in the decision-making process. This entails the detailed review of application form data and all uploaded documentations (i.e., building plan design, land ownership, deed etc). Applicants should receive general updates on the status of their application such as a notification when their application is being processed with a tentative decision date, or additional information and documents required.
NOTE: Depending on the country, construction permit approval takes different forms e.g. some countries have a document submission checklist embedded and if one of the required documents is not submitted or the submitted documents are unclear or structural design images blurry, then the application is left as pending and a local building plan officer receives a notification for a more manual review and followup. The applicant will receive a notification (via email, SMS, on the permitting platform) stating what is missing or required. The building plan officer can request the hard copy permit application submissions, when appropriate. The application can then be revised and resubmitted.
In most countries that have implemented the construction permit, a building authority still scrutinizes all applications received and consults with other authorities: i.e., a design auditor may conduct an audit to provide feedback regarding the extent to which the design conforms to planning demands and technical requirements. If opinions from other authorities and design auditors are favorable, and the building authority is satisfied that the building design meets the compliance and technical building plan requirements (fire safety, accessibility, space standards etc), then a construction permit is granted. If the building design and construction documents do not meet the compliance and technical building plan requirements, the applicant will be issued a notice stating why their construction project does not comply. These applicants could be asked to submit further information or a revised application meeting the compliance requirements, in order for their application to be reconsidered. **All submitted applications should be archived to ensure a secure longterm storage of this data.
Workflows
Client Case Management for reviewing submitted applications and communicating any application status updates or additional information needed to the applicant.
Data Analysis and Business Intelligence / Decision Support for approving or rejecting applications - based on compliance with building regulations, submission of required documents, and existing criteria (e.g. via checklist, or category-based).
Building Blocks
Multiple fee types can be required in the construction permit approval process (e.g., filing fee, permit fee, surcharge fee, fixed fee per building use etc). A document can be made available summarizing the construction permit fees and calculation method.
If an electronic payment process is enabled, then applicants can pay these fees via a digital financial service embedded in the platform. In certain countries, these fees are calculated based on the size, type and valuation of construction. Following the submission of their online permit application, the applicant can be taken to a payment portal with information on the calculation of their permit fee which is payable online i.e., via a third-party integration (NOC, Payment gateway, Digital signature) or local government online payment system. The applicant must pay all outstanding fees for their permit to be issued. Once the payment is processed, a payment confirmation screen is displayed. Applicants should also receive (i.e., via email, mobile etc) a standard payment receipt.
Workflows
Financial Services for processing all fees associated with the construction permit approval process and generating payment confirmation receipts.
Client Case Management for calculating fees, and monitoring/verifying that all required payment transactions, per applicant, has been fully processed and received. Also ensuring that applicants receive payment confirmation and receipt.
Content Management for the development of documentation summarizing construction permit fees and calculation method.
Building Blocks
Permit issuing generally takes place once the submitted construction permit application has been reviewed and approved, and in some country cases - an extra step includes conducting an in-person building site inspection prior to permit issuance. Examples of construction permit standards that must be met could include structural safety, fire safety, the control of toxic substances, ventilation, sanitation, fall-protection and general safety measures that will be implemented during the design, installation and inspection of building construction works.
Once the building authority also ensures that all outstanding fees have been paid by the applicant, a notification is sent to the applicant informing them that their construction permit has been granted and issued. The permit can be allocated in different forms – a digital format that is downloadable via the permitting platform and/or issuance of a physical permit document with an official stamp. Permit issuance is communicated to different parties - informing relevant individuals/stakeholders of the issuance. A digital security label could be embedded in all government issues construction permits and an online system utilized to validate the authenticity of all permits during any building construction processes.
*** In certain countries, following permit issuance, construction work can start right away. However, a construction permit can expire if construction work is not started within a certain period or is not completed within a certain time from the date the permit was granted. An application to extend the period to start or to complete the construction work can be submitted to the building authority. Beyond a certain limit, a new construction permit must be applied for.
Workflows
Data Collection and Reporting for capturing and tracking all approved permit issuances and permit holders and informing all relevant authorities of approval decision.
Client Case Management to check that the applicant has paid all outstanding fees. To communicate approval decision to the applicant and coordinate permit pickup should allocation of a physical copy be a requirement.
Building Blocks
This step involves ensuring that there is a virtual help desk and/or physical support centers in place to address any queries pertaining to registration on the platform and the construction permit approval decision. Incorporating a complaint management software will efficiently and transparently ensure that all grievances, complaints and appeals raised by the applicants, are tracked and addressed. In certain countries, this process is led by the construction permit help desk support unit at the state level, to address problem diagnosis needs pertaining to the platform. The local building officials can also be trained to address any queries that cannot be addressed through an automated process.
Workflows
Data Collection and Reporting for capturing reoccurring complaints, queries and feedback received from the construction permit service users and permit holders. And integration of other databases and systems for automated data update on client cases overtime.
Client Case Management for identifying and capturing reported cases on grievances / appeals etc., and for determining decisions/actions to proceed with by reviewing individual applicant's client case.
Building Blocks
Monitoring and evaluation is crucial to ensure transparency, accountability and quality public service delivery. To facilitate this process, the government authority leading the implementation of the construction permit can allocate a coordination team (i.e., inspection unit) in charge of ensuring construction work is carried out in compliance with the approved building plans, the construction permit and building regulations. This team could have in place a system with key stages to inspect all construction works or carry out random site inspections to supervise construction works. The inspector authority can provide a report for each examination - available in a digital format and accessible via the permitting platform. If construction works take place without a construction permit or do not comply with the approved design, they can be suspended until the relevant local authority takes a decision regarding demolition or continuation. A fine may also be charged.
In certain countries, once the construction work has been completed, the building authorities are to be notified. Several documents may be required to demonstrate completion, such as, the building design with the actual works carried out, reports of site inspections etc. In addition, submission of an attestation stating that the construction work has been carried out in accordance with the approved design and if any changes were made, that they comply with the building regulatory requirements. In other country cases, a final site inspection is required - the purpose is to verify whether construction works actually carried out comply with the building regulations and the approved building design.
Workflows
Financial Services for processing fine payments of construction works not complying with the approved building design.
Client Case Management for monitoring building construction compliance by all permit holders. Also scheduling all site inspection visits, tracking site inspection reports, and communicating with permit holders.
Building Blocks
Identification and Verification
Dominika Bieńkowska, IT Project Manager, SolDevelo
Wesley Brown, GovStack Product Owner, Digital Impact Alliance
Steve Conrad, Associate Director of Technology, Digital Impact Alliance
Hani Eskandar, Head of Digital Service Division, International Telecommunication Union (ITU)
Sarah Farooqi, The Exchange Product Owner, Digital Impact Alliance
Ibrahim Habib, Director, Djibouti Ministry of Housing, Urbanism and Environment
Abdallah Ibrahim, Secretary General, Djibouti Ministry of digital economy & Innovation
Sainabou Jallow, Business Analyst, Digital Impact Alliance
Concorde Kananura, GovStack Regional Coordinator, Africa, International Telecommunication Union (ITU)
Mohamad Kaourah, Deputy Director, Djibouti Ministry of Housing, Urbanism and Environment
Arnold Kibuuka, Project Officer, International Telecommunication Union (ITU)
Nico Lück, GovStack Advisor, GIZ
Margus Mägi, GovStack Project Lead for Estonia, Government of Estonia
Yolanda Martínez, Overall Lead for GovStack, International Telecommunication Union (ITU)
Stephen Oyala Odhiambo, Digital Government Advisor, GIZ
Farina Carolina Owusu, Junior Advisor Global Program Digital Transformation with GovStack, GIZ
Hossam Ragheb, GovStack Regional Coordinator, International Telecommunication Union (ITU)
Dr. P. S. Ramkumar, GovStack, International Telecommunication Union (ITU)
Christin Schulz, Governance Advisor and Component Leader, GIZ
Pia Seiffarth, Junior Advisor Global Program Digital Transformation, GIZ
Ayush Shukla, Technical Officer, International Telecommunication Union (ITU)
Siri Nanz Snow, Country Engagement Lead for the GovStack Initiative, GIZ
Valeria Tafoya, Technology Consultant, International Telecommunication Union (ITU)
Meelis Zujev, Project Manager, Govstack Sandbox, Gofore
Raul Kaidro, GovStack
| ID | INST-1 |
|---|
This use case profiles specifically the digital integration steps within the delivery journey of a generalized unconditional social cash transfer service. Unconditional cash transfers are cash payments provided to financially disadvantaged or vulnerable people or households without requiring anything in return (i.e. without conditionality). This is different from a conditional payment where the benefit needs to be applied on the basis of achieving a certain result (e.g. higher school attendance, or prenatal care visit), or to be expended specifically on a type of resource (e.g. housing, or agricultural equipment). Governments in low- and middle-income countries increasingly use these benefit schemes in attempt to reduce poverty or other vulnerabilities, such as those related to health.
Ministry or national government body in charge of social welfare, community development and/or implementing social assistance and cash transfer programmes.
Local social welfare officers in charge of identifying potential beneficiaries that meet eligibility criteria, and facilitating allocation of cash transfers to eligible beneficiaries.
Vulnerable population/households - beneficiaries, that comply with pre-defined conditionalities and meet the eligibility criteria.
: Implement nationally appropriate social protection systems and measures for all, including floors, and by 2030 achieve substantial coverage of the poor and the vulnerable
: Develop effective, accountable and transparent institutions at all levels
Staff from the Ministry of Social Welfare or another leading agency / organization organizes an information campaign to inform about a social assistance programme aimed at potential target population / beneficiary group(s) and implemented via predefined approaches and partners. The campaign is conveyed via mobile messaging and/or aired on national radio/television, while a more capillary village to village campaign is performed by district / local social welfare officers. Outreach communication is intensive during the kick-off phase of the new programme, but also requires ongoing touchpoints and additional information sharing, e.g. on grievance procedures, rights and responsibilities, behavioural change communication, etc.
Workflows
Client communication to facilitate the spreading of programme awareness for target audience and encouraging enrolment via mobile / media channel(s)
Client education for educating potential target beneficiaries around the approach and objective(s), benefit(s), constraint(s), partner(s), etc. of the programme
Content management for the backend Social Welfare staff to populate relevant educational and promotional content that local officers can use during on-the-ground outreach campaigns
Identification and Registration (with aid of geographic information services tool **** for potential use) in mapping and locating households and individuals for outreach target
Building Blocks
Registration is the process of collecting information on potential beneficiaries for assessment of their needs and conditions. Depending on specific country context, registration works in very different ways – either through mass-census survey, or on-demand at local offices (either approach potentially building on interoperability existing data sources). While the practicalities of data collection differ across the two, with very different implications for data quality, currency and completeness, the underlying digital processes are broadly the same: Mass census survey registration is sometimes carried out in-house, other times by statistics agency or trained enumerators. A percentage* of households across the country are interviewed on a periodic basis to collect socio-economic data (especially if to target population in poverty), geo-location data, and key documentation. On-demand registration is primarily carried out in-house via capacity at local levels of implementation (e.g. social welfare offices or municipalities) and involves people pro-actively applying when in need. In either case data (both at individual and household-levels) is entered into a registry that serves one social assistance programme alone or several: the Social Registry** (SRIS). This is sometimes done directly at the moment of interview via computer assisted interview methods (CAPI), other times subsequently post-enumeration.
* Percentage varies greatly across countries; 10-95% range depending on prior policy choices, etc.
** The Social Registry collects, organizes, stores, processes, transforms, creates, and distributes information necessary to support intake and registration of potential beneficiaries (gateway function). It is part of a broader Social Assistance Information System, further discussed below and in subsequent steps.
Workflows
Data Collection and Reporting for capturing interview responses or observation during registration process
Identification and Registration for enrolled identified beneficiaries in the system and enabling possible permissions for interaction with the SRIS, and (with aid of geographic information services tool) to potentially locate and track households during the interview process
Client Case Management for creating beneficiary user records
Building Blocks
Data within the SRIS Social Registry Information System (SRIS) is generally checked* by central level Social Welfare Ministry managers, against other government databases (eg. ID, tax, land cadastre, etc.) in order to fill in any missing gaps, verify and validate collected information, including authentication of all records. *Data checking approaches also vary: sometimes batch-sharing via CD, sometimes full interoperability
Workflows
Client Case Management for storing and reviewing identification records and eligibility information of potential beneficiaries
Data Analysis and Business Intelligence for cross-referencing and verifying records across multiple registry sources, and reconciling gaps / overlaps
Building Block Workflows
NOTE: Depending on the country and programme, eligibility determination takes different forms e.g. categorical by age without income screening , poverty-targeted, etc. often via “Proxy Means Test” calculation to screen and rank households by ‘inferred’ income. "Clean" data from a Social Registry that have undergone the data verification and validation step is used to screen eligible beneficiaries and establish the recommended benefit and services ‘package’. The amount of transfer often varies depending on household composition, and beneficiaries may qualify for other add-on services based on analyzed socioeconomic / demographic information being used for other welfare or social programmes.
Workflows
Client Case Management for determining and assigning benefit packages and benefit levels to specific user groups
Data Analysis and Business Intelligence / Decision Support potentially for identifying different benefit levels / types in correlation to target groups’ socioeconomic / demographic information, based on existing eligibility criteria (e.g. via proxy means test, means test or category-based)
Building Blocks
Eligible beneficiaries are re-contacted and asked to enroll onto the programme. During enrolment, further data can be collected (depending on programme design) e.g. bank account details, biometrics, etc.. Further information is exchanged and, in certain program design or context, beneficiaries are issued with a programme card (depending on system setup by country). Programme specific data is often entered into a separate Beneficiary Registry associated with a Beneficiary Operations Management System (BOMS)*, not the Social Registry used during Step 1. Registration. Non-eligible households are also contacted and informed, depending on program and context.
Much of the literature on the topic refers to this as the programme’s Management Information System (MIS). In practice, this is a tailored software application that supports beneficiary management functions (e.g. enrolment, payments, case management, M&E etc.).
Workflows
Data Collection and Reporting for capturing additional programmatic information on the beneficiaries during enrolment
Financial Services for staging beneficiary account details for cash transfer processing
Identification and Registration for identifying beneficiaries and confirming enrolment
Client Case Management for storing program specific data for tracking
Building Blocks
If a social cash transfer programme has enabled electronic payment processes (e.g. via banks, mobile money, etc.), payments are subsequently paid cyclically according to the programme schedule e.g. often bi-monthly. In the context where a digital financial service system is not employed, each beneficiary would be requested to travel to the nearest designated pay-point* and collect money by programme-specific authentication. In either case, the money is transferred to the selected payment provider as per generated payroll and is subsequently verified against the individual’s identification of program enrollment. Other possible add-on intervention activities at this step: behaviour change communication; triggering of add-on benefits (or widening of beneficiary pool) in emergency context using GIS data, etc.
These vary depending on design / implementation choices: banks, armoured vehicles, post offices, schools, etc.
Workflows
Financial Services for processing beneficiary payment directly to their account, or for generating payroll to deposit payment amounts for withdrawal by beneficiary from designated banking institution(s) / pay-point(s) thereafter
Client Case Management for identifying and authenticating individual that is making a withdrawal, or to recall / verify deposit account information prior to payment transaction
Building Blocks
Depending on the programme and on the country’s broader social protection policies, this step involves ongoing interaction with beneficiaries via local social welfare officers to help: Ensure information on beneficiaries stays up to date Address complaints, grievances, and appeals Address multi-dimensional risks via connecting beneficiaries to other programmes and services e.g. child protection, etc. Carry out assessment of co-responsibilities / conditionalities, if any (this is achieved in some countries via data integration into e.g. school management system from Education ministry on attendance, or HIS from Health ministry on check-up, etc.) Note that this step also requires clarity, clear decisions, and protocols regarding whose data (or subset of such) is to be updated by which programme personnel or role and at what time.
Workflows
Data Collection and Reporting for capturing changes in beneficiary information
Client Case Management for identifying and recording beneficiary interaction with local officers and capturing reported cases on grievances / appeals etc., and for determining risks / conditionality by reviewing individual beneficiary client case
Work Planning and Coordination to potentially suggest and connect with departments / agencies offering other social benefits and services to eligible beneficiaries
Building Blocks
Central level managers and local social welfare officers base decisions and management choices (e.g. where to conduct add-on training, re-registration camps, where to prioritise budget, etc.) on up-to-date data on the programme/s (e.g. who receives what, when, what areas are performing better, etc). Note that countries that do this effectively ensure programme BOMS data is connected / integrated via an Integrated Beneficiary Registry* and develop effective reporting functions, including GIS enabled spatial reporting. *This is a Registry that integrates data across existing Beneficiary registries and their associated BOMS to give an overview of who is receiving what across programmes.
Workflows
Client Case Management for ongoing monitoring and tracking of client performance, and integration to other registries for holistic view and reporting
Identification and Registration (with aid of geographic information services tool for potential use) in tracking / locating areas in relation to level of activities and adherence, or client household location
Data Analysis and Business Intelligence / Decision Support / Data Collection and Reporting to analyze, update, and report programme output / performance information
Building Blocks
Ensuring data is up to date to trigger: Programme exit for those who are no longer eligible e.g. when a beneficiary dies, migrates, exceeds eligible age or no longer qualifies for other reasons. This is achieved via a combination of recertification campaigns, automated data updates, and data-sharing with other government databases e.g. civil registration for death. Programme entry for newly eligible beneficiaries, via new data collection or analysis etc. Other changes to entitlements (e.g. benefit type of transfer size) due to changes in household composition, incomes, etc. Note that this step also requires clarity, clear decisions, and protocols regarding whose data (or subset of such) is to be updated by which programme personnel or role and at what time.
Workflows
Data Collection and Reporting for routine update of information on the beneficiary client base, and integration of other databases and systems for automated data update on client cases overtime
Client Case Management for ongoing review of beneficiary case information
Data Analysis and Business Intelligence / Decision Support to support identification of individuals for exit or entry based on analyzing change in programme-specific / socioeconomic data
Building Blocks
Wesley Brown, GovStack Product Owner, Digital Impact Alliance
Steve Conrad, Associate Director of Technology, Digital Impact Alliance
Jaume Dubois, Digital ID Lead, GovStack
Sarah Farooqi, The Exchange Product Owner, Digital Impact Alliance
Sainabou Jallow, Business Analyst, Digital Impact Alliance
Dr. P. S. Ramkumar, GovStack, International Telecommunication Union (ITU)
Max Carlson, GovStack
Uwe Washer, GovStack
Raul Kaidro, GovStack
Saurav Bhatta, GovStack
Name
Postpartum and Infant Care
Sector
Health
Version
1.0
Status
Published
Name
Construction Permit
Sector
Sustainable Infrastructure
Version
1.0
Status
Published
Name | Unconditional Social Cash Transfer |
Sector | Institution |
Version | 1.0 |
Status | Published |
| ID | <Abbev-Sector - Index> |
|---|---|
Prose description of the overall use case. This can, and likely should comprise multiple paragraphs and can be used and a high-level perspective on the individual use case steps.
A list of the stakeholders that have some engagement with this use case, including how they are involved
The specific SDG targets this use case contributes towards
The format for this section is: <Url to SDG Target with text of specific target ID>: Text of the SDG Target
11.6: Reduce the adverse per capita environmental impact of cities, including by paying special attention to air quality and municipal and other waste management.
List of the GovStack Building Blocks involved in this use case, including link to Building Block specification
Future building block inclusion
List of Building Blocks that may be involved in this use case once the Building Block specification is complete/updated
List of links to documents used to create the use case
Prose description of the use case step
Workflows
List of the workflows involved in this step, include a description of how the workflow involved
Format: Workflow Name text description
Identification and Registration for locating and tracking users registered in the system.
Example Implementation
<Link to example implementation>
Building Blocks
List of Building Blocks involved in this use case step, including link to building block specification
<List of contributors, optionally including organization and email address>
Name
<Use Case Name>
Sector
<SDG Sector>
Version
<Document Version>
Status
<Draft, Proposed, Approved, Published>