Stop the Killing at the Border: A Documentation, Diplomacy, and Crossing-Reduction Strategy for BSF Deaths of Bangladeshi Nationals

Diagnosis

The recurring killing of Bangladeshi nationals along the India border by India's Border Security Force (BSF) is the problem, and it is documented domestically by Ain o Salish Kendra (ASK), the human-rights organisation whose records are the standing civil-society ledger of these deaths (per the curated note). This is a medium-horizon, regime-type problem in the security and geopolitics domain: the killings are not isolated incidents but a persistent pattern produced by the interaction of an armed foreign border force, porous frontier zones, and Bangladeshi civilians who cross for cattle, smuggling, livelihood, or simple proximity to the line.

It matters now for three reasons. First, each death is a sovereignty and human-rights injury that the state is obligated to prevent and protest. Second, the killings recur despite repeated diplomatic engagement, which signals that current protest mechanisms are not changing BSF behaviour. Third, the lead responsible body is the Bangladesh Police (BP), supported by Border Guard Bangladesh (BGB), the Department of Immigration and Passports (DIP), and the Security Services Division, meaning the levers are distributed across policing, border control, mobility regulation, and ministerial coordination. The current_state indicator is null in the registry, which is itself a finding: Bangladesh lacks an authoritative, continuously updated official count, leaving ASK's civil-society record as the de facto source. You cannot manage, protest, or negotiate against a number you do not own.

Recommended actions

1. Stand up an official border-death register. Owner: Bangladesh Police (BP), with BGB feeding incident reports. Mechanism: a standing inter-agency register, reconciled against Ain o Salish Kendra's records, that logs every reported death with location, date, victim identity, and circumstances. Observable signal: a single official dataset exists and is updated within days of each incident, and its figures can be reconciled against ASK's independent count.
2. Convert every incident into a documented diplomatic protest with evidence. Owner: Security Services Division, coordinating with the foreign-affairs channel. Mechanism: a fixed protocol that triggers a formal note and a case file (BGB incident report plus the register entry) for each death, raised at the next BGB-BSF border conference and through diplomatic channels. Observable signal: a protest file is filed for every entry in the register, with no unrecorded deaths, and a written Indian response is logged for each.
3. Reduce the irregular crossings that put civilians in front of BSF guns. Owner: Border Guard Bangladesh (BGB), with the Department of Immigration and Passports (DIP) on lawful mobility. Mechanism: targeted patrolling and community awareness in the high-incident frontier upazilas, paired with legal crossing and livelihood alternatives so fewer civilians enter the kill zone. Observable signal: a measured fall in border incidents in the targeted zones and a rise in lawful crossings recorded by DIP.
4. Institutionalise the BGB-BSF conference outcomes. Owner: Border Guard Bangladesh (BGB). Mechanism: insist that each border-level conference produce a written, time-bound commitment on non-lethal force and joint incident review, rather than a general communique. Observable signal: published, dated commitments and a joint review of each fatal incident.

Sequencing (first 12 months)

Start with the register (action 1): it is fast, fully within Bangladesh Police's control, requires no Indian cooperation, and unlocks everything else. Once every death is recorded and reconciled with ASK, the protest protocol (action 2) has an evidentiary backbone, and the diplomatic channel can no longer be brushed off with disputed facts. In parallel, BGB maps the high-incident frontier segments so the crossing-reduction work (action 3) is targeted, not blanket. The conference-outcome discipline (action 4) follows once Bangladesh arrives at the table with a verified file rather than a grievance.

Risks and constraints

The binding constraint is that the trigger sits across the border: the killings are committed by a foreign force Bangladesh cannot command, so the only available levers are documentation, diplomacy, and reducing exposure on the Bangladeshi side. Asymmetry in the relationship limits how hard the protest channel can be pushed without broader diplomatic cost. Domestically, the absence of a single official count (current_state is null) reflects fragmented record-keeping across BP, BGB, and civil society; fixing that is institutional, not budgetary, but it requires sustained inter-agency discipline that past episodes suggest is hard to maintain. Crossing-reduction also collides with entrenched livelihood and smuggling economies in frontier districts, so enforcement alone will fail without lawful alternatives.

Bottom line

Bangladesh cannot stop the BSF from firing, but it can stop being unable to count, prove, and protest each death, and it can reduce the number of its citizens standing in front of those guns. Build the official register first, attach a documented protest to every entry, and pair targeted border policing with lawful mobility, so that diplomacy is backed by evidence rather than grievance.