What the Record Shows

Editorial note

This is not a finding of misconduct against any named officer. It is not an allegation of corruption or criminality. It is an attempt to put one workplace grievance into an evidentiary form that distinguishes four different things that are too easily mixed together:

1. what the preserved record directly shows;
2. what the record supports only in part;
3. what I remember from an oral conversation but cannot independently prove; and
4. what remains unresolved.

Names of individual colleagues and personal identifiers have been removed. Where a message contained Aadhaar, PAN, account, telephone, address or other personal information, this article describes the existence of that material without reproducing it.

The underlying dispute concerns business-development targets, Mela/drive instructions, leave, digital-delivery metrics, reporting through WhatsApp, account-opening and account-closure pressure, and the boundary between legitimate administrative direction and pressure that an employee may reasonably ask to have clarified in writing.

How the grievance reached the Department

On 7 September 2026 I sent a public-interest grievance to Tamil Nadu public-grievance authorities. I did not initially send that grievance directly to Vriddhachalam Sub Division through the Department of Posts internal chain.

The grievance itself recognised that the Department of Posts is a Union Government department. It asked the State authorities to take cognisance of the matter, forward it to the competent Union authorities, obtain a factual report, and communicate the result.

On 8 September, Cuddalore postal administration forwarded the complaint to Vriddhachalam postal administration because the grievance concerned that division, and requested a direct reply to me. From that point onward, the grievance was inside the postal administrative chain through formal forwarding.

On 17 September I also sent a clarification directly to the postal administration. That clarification recorded that the original grievance had reached Vriddhachalam through forwarding, that I was willing to cooperate, and that if attendance, a statement, or documents were required, I preferred the purpose and requirements to be communicated officially.

What the documentary record supports

1. Repeated numerical targets are directly documented

The WhatsApp archive contains repeated numerical instructions over multiple years. These are not reconstructed from memory.

Examples include:

• 7 August 2024: a message described a POSB Mela target of 20 accounts for each GDS staff member and 40 for each departmental staff member. The same message gave PLI/RPLI targets of ₹25,000 for each GDS staff member and ₹50,000 for each departmental staff member.
• 10 October 2024: BPMs and ABPMs were told of an account-opening target of 25 accounts and a PLI/RPLI procurement task of ₹1 lakh sum assured for each individual.
• 9 December 2024: the group was reminded of a POSB drive with 20 accounts for each staff member and a PLI/RPLI drive with ₹50,000 for each staff member.
• 26 May 2025: an “EACH STAFF” target message listed PPF, SSA, POSB and PLI/RPLI numbers, including 40 POSB accounts and ₹50,000 PLI/RPLI.
• 5 May 2026: an instruction for a June PLI/RPLI Mela assigned a ₹1 lakh initial-payment target to a wide list of cadres: GDS packer, ABPM, BPM, MTS, PA and SPM.

These examples support the narrow factual proposition that numerical business targets were repeatedly communicated and, at times, applied broadly across different cadres.

They do not, by themselves, answer the separate legal or administrative question of which targets were formally authorised, how they were intended to be enforced, or what consequences lawfully followed from non-achievement. Those were among the questions raised by the grievance.

2. A connection between leave and target completion appears in the record

A particularly important message is dated 7 December 2024. In substance, staff were advised to take paid leave before a forthcoming Mela because, during the Mela period, the officer said he would feel difficulty granting leave where the target had not been completed and might say leave was not possible.

A later message on 21 December 2024 added counter-context: the same officer stated that he was not saying that nobody could take leave, while also saying that during the Mela period completion of the assigned target was enough.

The fair reading is therefore not “leave was always denied for missing targets.” The documentary record supports something narrower: target completion and leave were explicitly discussed together, while the same record also contains statements that leave was not categorically prohibited.

That distinction matters.

3. Operational compliance and business-transaction minimums were combined in one instruction

On 9 April 2026, a message addressed to BPMs and ABPMs required, among other things:

• 100% DSS usage;
• D+0 delivery above 90%;
• real-time delivery returns;
• digital-mode Speed Post/parcel booking;
• facial attendance;
• daily reporting; and
• minimum monthly numbers for Speed Post bookings, PLI/RPLI transactions and CBS transactions.

The same instruction stated that deviation or regular default could result in “suitable action.”

This is one of the strongest pieces of evidence behind the grievance because operational compliance requirements and minimum business transactions appear in a single instruction followed by an enforcement warning.

It still does not establish what “suitable action” legally meant in every case. It does establish that the wording was circulated.

4. Performance reporting sometimes coexisted with documented technical failure

The archive contains repeated app and network problems.

On 9 April 2026, a DSS utilisation report listed Sevveri B.O. at 0%. I replied in the group that the DSS app had not worked the previous day and that the issue had been escalated to the DSM. Other employees can also be seen reporting errors and being advised to retry, switch to Wi-Fi, or wait for escalation.

This does not prove that every poor metric resulted from a technical failure. It does support the grievance’s narrower concern: when performance numbers are reviewed, there must be a way to distinguish staff non-compliance from system failure.

5. Work-related WhatsApp instructions occurred outside ordinary daytime hours

The preserved export contains operational messages in the evening and at night, including instructions concerning leave procedure, targets, day-end work, account drives and device-related requirements.

The grievance did not claim that every after-hours message was automatically unlawful. It asked what status WhatsApp instructions had, what response was expected outside engagement hours, and what safeguards applied when communication extended beyond the normal duty period.

6. The archive contains compulsory-sounding attendance instructions

On 12 April 2024, staff connected with a list of offices were instructed to come to the office at 4 PM. The message stated that there was no permission/exemption and that everyone had to attend; SPMs were told to inform BO staff.

That supports asking how such attendance is classified, especially for GDS staff with defined engagement hours, and whether travel/allowance or compensatory rules apply.

It does not, without the governing orders and individual duty records, establish that the meeting itself was unlawful.

7. Sensitive personnel information was circulated in the workplace group

The WhatsApp archive contains instances where employee or substitute details were posted in the group, including combinations of name, date of birth, address, email, phone number, Aadhaar, PAN and account information.

Those values are deliberately not reproduced here.

The grievance therefore asked what rules govern the collection and circulation of personal data in workplace WhatsApp groups and whether less exposed channels should be used. The existence of the data in the group is documented. Whether each disclosure breached a specific rule requires a separate legal and administrative analysis.

Account closures: what the record shows, and what it does not

This issue needs particular care because it can affect customers as well as staff.

The record contains closure-related pressure. For example:

• in March 2025, a message linked completion of assigned targets with a later decision about allowing account closures;
• on 20 August 2025, staff were instructed to complete targets and, during a severe review period, were told not to close accounts for the next 15 days;
• in June 2026, the group discussed a large negative net-opening position — more closures than openings — and additional account-opening targets were assigned to correct that negative position.

Those records support the proposition that account-closure numbers were administratively discussed in relation to account-opening performance.

But the evidence I currently possess does not establish a specific written instruction that Sevveri B.O. must refuse a customer’s closure unless that customer opened an equivalent RD account.

I remember having described, colloquially, a practice in which Sevveri had not closed an account unless an RD equivalent was placed against it. If a customer transaction is ever questioned, the only responsible approach is to reconstruct the individual transaction and identify exactly which written instruction, if any, was relied upon. A general instruction to reduce closures must not be retrospectively rewritten into a more specific order that the documentary record does not contain.

That limitation is part of the evidence, not an inconvenience to be edited out.

Counter-evidence also belongs in the record

A neutral account cannot publish only the material that supports my grievance.

The archive also contains evidence that:

• leave was at times described as being granted without questioning, subject to correct leave-letter procedure;
• technical problems were sometimes acknowledged and escalated;
• officials themselves referred to pressure or review from higher offices, including RO/PMG/SP-level review;
• many messages used requests, encouragement and praise rather than threats;
• operational campaigns were often framed as departmental or regional initiatives rather than as purely personal decisions by a local officer.

These facts do not erase the questions raised by the stronger messages. They change the interpretation from a simple story of one officer imposing arbitrary demands into a more complicated administrative chain in which local officers may themselves be implementing instructions and performance expectations from above.

That is precisely why the grievance asked for the written authority and methodology behind the targets rather than simply attributing motive to an individual.

The meeting on 17 September 2026

The following section is different from the preceding documentary sections.

It is a reconstruction from memory, written after the event. I believe the context is roughly 90% accurate, but the wording is not verbatim. I do not possess an audio recording of the conversation, and where I describe tone, that is my perception rather than an independently verifiable fact.

The calls

At approximately 1:45 PM, I received a call from a Mail Overseer asking me, on behalf of the Inspector Posts, to come to the Sub-Division Office. No reason was disclosed during that first call.

A later call said that the Mail Overseer and Inspector had official work at Tittagudi S.O. and that I should wait there until they arrived.

I reached Tittagudi at approximately 3:45 PM after lunch.

The printed emails and four written questions

At the meeting, the Inspector had hard copies of the grievance emails. I was asked to provide written answers to four questions. I do not presently possess a copy of the handwritten question-and-answer sheet, so the following is contextual reconstruction only.

Question 1 — authorship. I understood the first question to ask who had sent the email and whose email it was. My answer ultimately acknowledged that I had sent it and included my details as a Department of Posts employee.

Question 2 — channel and public grievance route. I understood the second question to ask why I had not sent the matter through the proper departmental channel and why I had approached a public grievance route. I answered, in substance, that being employed by the Central Government did not remove my status as an Indian citizen, while also acknowledging that I had not known the specific departmental channel expected for this type of grievance and that I would use the appropriate channel in future.

The Inspector also asked orally why I had not simply written a letter and forwarded it internally, and suggested that I could write in Tamil. I chose to write in English.

Question 3 — meaning of “future”. I understood the third question to clarify why I had written that I would use proper channels in future when the current grievance had already been sent. My answer was that the present grievance had already gone out; “future” referred to future representations.

Question 4 — acknowledgement and knowledge. I understood the final question as seeking a clear acknowledgement that the email had been sent by me and with my knowledge. I gave that acknowledgement as a matter of professional responsibility.

None of those answers, as I remember them, was intended as a withdrawal of the factual concerns in the grievance.

Oral remarks I cannot independently prove

During the discussion, the Inspector explained, in substance, that targets were assigned from higher levels, including the Circle administration, and that implementing them was part of his duty.

I also remember him saying, in substance, that if I could not manage the work or requirements, I should find another job.

I do not have an independent recording or written proof of that sentence. I therefore publish it only as my contemporaneous recollection, not as an established fact or a formal threat.

I also perceived some comments about my use of AI tools as mocking or dismissive. Again, tone is interpretive. The objective fact is simpler: AI tools were used to help me organise, research and draft the grievance; I authorised and sent it myself. AI assistance does not change the underlying question of whether the cited workplace messages exist and what they say.

What the original grievance did and did not allege

The grievance asked for clarification on matters including:

• the written authority and methodology for numerical targets;
• whether leave, permission, transfer, discipline or performance assessment could be linked to non-achievement;
• the formal status of WhatsApp instructions;
• safeguards where technical failures affect measured performance;
• the treatment of meetings or work outside engagement hours; and
• the circulation of sensitive personnel information.

It did not ask the receiving authorities to assume criminality, corruption or personal malice. It asked for a factual report and written clarification.

That distinction remains important now that the complaint has moved into the departmental chain.

What I can responsibly say today

Based on the material preserved so far, I can responsibly say that repeated numerical targets, leave/target language, transaction minimums accompanied by a warning of “suitable action,” after-hours instructions, performance monitoring during technical problems, account-closure pressure, and circulation of sensitive personnel information are all present in the documentary record.

I cannot responsibly say, on the present record, that every target was unauthorised, that every officer acted improperly, that the 17 September oral remarks were recorded or independently corroborated, or that a specific written order required Sevveri to exchange an RD opening for an account closure.

The purpose of publishing this is not to turn uncertainty into accusation. It is to prevent the opposite problem: allowing uncertainty about some details to erase the parts that are directly documented.

Evidence classification

Issue	Present classification
Repeated numerical business targets	Documented
Targets applied across multiple cadres	Documented
Leave discussed in relation to target completion	Documented, with counter-context
Operational compliance + minimum business transactions + “suitable action”	Documented
Technical failures during performance monitoring	Documented
After-hours WhatsApp work instructions	Documented
Compulsory-sounding attendance instructions	Documented; legal/administrative effect unresolved
Sensitive personnel data in workplace group	Documented; legal effect unresolved
Pressure concerning account closures	Documented
Specific RD-for-closure instruction at Sevveri	Not established by current written evidence
17 September “find another job” remark	Author’s uncorroborated recollection
Mocking intent concerning AI use	Author’s interpretation of tone
Retaliation for filing the grievance	Not established on present evidence

A note on an unrelated Telegram incident

A separate Telegram message from a workplace contact contained a shortened link that resolved to a third-party domain and generated an explicit-content preview. I have preserved that incident separately.

I am not presenting it here as evidence of retaliation, harassment or a connection to the grievance because no such connection has been established. Including it in the main evidentiary argument would make the argument weaker, not stronger.

Preservation and revision

The underlying WhatsApp export is being preserved unchanged. Call logs, emails and any future departmental correspondence should likewise be preserved in original form. If I obtain the handwritten four-question statement, an official reply, a written order establishing the authority for the targets, or evidence that contradicts this account, this article should be revised rather than silently overwritten.

This is therefore an unresolved record, not a verdict.

The question I want the documentary process to answer is narrower than the emotion of the day: what was formally authorised, what was merely communicated through workplace pressure, and what protections exist when an employee asks for that distinction to be made in writing?