When to use a grievance
Use a normal transaction or service-request route first when the portal provides one for the problem. A grievance becomes useful when a service remains unresolved, action is delayed, a request is closed without solving the issue, or the response does not address the documented facts.
| Situation | Better first action |
|---|---|
| Forgotten password | Use Password Reset. |
| Account locked | Use Unlock Account. |
| Bank details need changing | Use Bank Account Update. |
| A specific document/service is missing | Use its service-request route where available. |
| An existing request remains unresolved | Consider grievance/escalation with the earlier acknowledgement. |
Prepare the evidence file
- Pension/PPO reference needed to identify the case.
- Existing service-request acknowledgement number.
- Submission and follow-up dates.
- Exact portal remarks or closure response.
- Relevant pension slip, PPO, bank evidence or other supporting record.
- Masked screenshots where useful.
- A single sentence stating the resolution requested.
Keep the evidence narrow. Ten unrelated attachments can hide the one document that proves the problem.
Write a clear grievance
Useful structure:
- Subject: identify the service and problem.
- Issue: state what is wrong in one or two sentences.
- Earlier action: give the request number and important dates.
- Current status: quote or summarise the relevant remark.
- Evidence: identify the attachment that proves the point.
- Resolution requested: ask for one concrete action.
Example: “July pension was credited, but the July pension slip is unavailable. Request SR-XXXX was closed as resolved. Please generate the July slip or state the specific reason it cannot be generated.”
Submission workflow
- Open the official grievance route applicable to the issue.
- Select the closest correct category.
- Use a precise subject line.
- Enter the short chronology and requested resolution.
- Attach only relevant evidence.
- Check that unnecessary sensitive information is not exposed.
- Submit once.
- Save the registration/acknowledgement number and a copy of the complaint text.
Track the grievance
Read detailed remarks, not only a broad label such as “under process” or “closed.” Where the official system offers a reminder or clarification function, use it to add a concise update or requested evidence without opening a duplicate case. Quote the same registration number in related correspondence.
How to judge a closure
- Does the response answer the exact issue raised?
- Does it say what action was taken?
- Can you verify that action in SPARSH, your bank or the relevant document?
- Was the case simply forwarded without a final resolution?
- Does the closure rely on a factual assumption contradicted by your evidence?
A status of “closed” describes the grievance record. It does not by itself prove that a pension payment, document or profile field has changed.
Escalation and appeal
If the grievance remains unresolved, use the appropriate official pension/public grievance route and follow the current instructions displayed there. Government grievance systems can provide registration-based tracking and, for eligible cases, further feedback or appeal mechanisms after closure.
- Quote the earlier grievance number.
- State exactly why the closure did not solve the issue.
- Point to the evidence or fact that was overlooked.
- Repeat the precise corrective action requested.
- Save and track any new appeal/escalation acknowledgement.
Common mistakes
- Opening several identical complaints.
- Writing only “pension problem, please solve” with no dates or references.
- Uploading large bundles of unrelated records.
- Including passwords, OTPs, bank PINs or card details.
- Changing the requested resolution in every follow-up.
- Ignoring a request for clarification.
- Assuming a closed grievance automatically means the underlying service was corrected.
Privacy and fraud safety
A grievance handler does not need your SPARSH password, OTP, bank PIN or card CVV. Use official portals and independently verify current government contact details before sending sensitive records.
Frequently asked questions
Should I file a grievance before using a service request?
Usually use the specific transaction/service-request route first when one exists.
Can I submit the same grievance repeatedly?
Avoid duplicates. Track and clarify the existing registration unless an official instruction requires otherwise.
What makes a grievance effective?
A precise issue, short chronology, earlier acknowledgement, relevant evidence and a clear requested resolution.
What if the grievance is closed but the problem remains?
Save the closure, verify the promised action and use the appropriate official follow-up or appeal mechanism where available.
Should I type my full bank or identity details in the grievance text?
Minimise sensitive data and provide only what the secure official process genuinely requires.
Can an official grievance be tracked?
Government grievance systems commonly provide registration-number based tracking; follow the current official portal.
Is an appeal available for every closed case?
Availability depends on the system and case status. Follow the live official instructions.
Can someone ask for my OTP to resolve a grievance?
No. Never disclose your OTP, password, bank PIN or card CVV.