This page provides configuration details for PGR master data templates
DIGIT Public Grievance Redressal system abbreviated as PGR is a mechanism commonly used to receive and act on complaints or grievances reported by residents of a city/ ULB enabling prompt actions on any issue raised by them and to avail services more effectively.
DIGIT PGR offers a variety of features to make complaint lodging and redressal easy for residents and employees of a ULB. A list of standard features is given below.
Web and mobile interface to lodge, track, reopen, and update feedback on the complaint made by the citizen.
Web and mobile interface to comment, forward, and close the complaint by the ULB employees.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Browse details on configuring master data template
A grievance is a formal complaint submitted to a ULB. Something wrong or something believed to cause distress in services provided by the ULB is considered as grounds for complaint. Grievances that are closely associated with ULB’s functions classified into different buckets, that different sections of ULB deal with are known as grievance types.
1
SLS
Street Lights
स्ट्रीट लाइट
2
GBG
Garbage
कचरा
3
DRN
Drains
नाली
The data given in the table is sample data.
1
Grievance Type Code*
Alphanumeric
64
Yes
Unique code is given to the grievance type. This code is used to uniquely identify the complaint type and as a reference in the child record. E.g. SLS given above in data table to identify Street Lights complaint type
2
Grievance Type* (In English)
Text
256
Yes
This is the text or string stating grievance type in English
3
Grievance Type* (In Local Language)
Text
256
Yes
This the text or string stating the grievance type in local language like Hindi, Telugu etc. whatever is applicable
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all different types of grievances on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see a common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure completeness and quality of data.
This checklist covers the activities which are specific to the entity.
1
Grievance type code should not have any special characters other than ‘-', and '_’
SLS - [Allowed]
SLS1 - [Allowed]
SL#1 - [Not Allowed]
2
Grievance type should be text and should not contain special characters other than ‘-', '_', SPACE
Street Light - [Allowed]
Street_Light# -[Not allowed]
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Browse details on configuring master data template
The grievance sub-type defines the second level of classification of grievances which are related to ULB’s functions and adds detail to a grievance type.
The data table below represents the structure of the template and given here to explain the template in detail.
1
SLS01
No Street Light
कोई स्ट्रीट लाइट नहीं है
SLS
TP
48
2
SLS02
Street Light Not Working
स्ट्रीट लाइट काम नहीं कर रही है
SLS
TP
48
3
WNS01
Illegal Discharge of Sewage
सीवेज का अवैध निपटान
WNS
PHS
48
The data given in the table is sample data.
1
Grievance Subtype Code
Alphanumeric
64
Yes
Unique code is given to the grievance subtype and is used to uniquely identify the complaint subtype. E.g. SLS01 given above in data table to identify Street Lights complaint subtype
2
Grievance Subtype (In English)
Text
256
Yes
This is the text or string stating grievance subtype in English
3
Grievance Subtype (In Local Language)
Text
256
Yes
This the text or string stating the grievance subtype in local language like Hindi, Telugu etc. whatever is applicable
4
Grievance Type Code
Reference
64
Yes
5
Department Code
Reference
64
Yes
6
SLA (In Hours)
Decimal
(5,2)
Yes
This field defined the service level agreements in hours. This the time within which a complaint raised to be resolved
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all different subtypes of grievances on the basis of ULB’s functions and grievance types.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every checklist point/ activity mentioned in the checklist.
The checklist is a set of activities to be performed after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see the common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure complete and quality data.
This checklist covers the activities which are specific to the entity.
1
Grievance Subtype code should not have any special characters other than ‘-', and '_’
SLS01 - [Allowed]
SLSA - [Allowed]
SLS#1 - [Not Allowed]
2
Grievance Subtype should be text and should not contain special characters other than ‘-', '_', SPACE
No Street Light - [Allowed]
No Street Light# -[Not allowed]
Reference to parent grievance type code from the entity
Unique department code from the entity
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.