Reporting
The 2007 Army Blogging Rules: What They Actually Required of Soldiers
In spring 2007 the US Army updated the regulation governing operational security, and the update was widely reported as effectively ending soldier blogging. The reporting and the regulation did not match particularly well, and the resulting argument is a useful case in how institutional documents get translated into headlines.
What the regulation said
The instrument was Army Regulation 530-1, Operations Security, revised by a directive issued on 19 April 2007. It updated the regulation that governs operational security rather than introducing a new rule about publishing. Its relevant provision required that material a soldier intended to publish about military matters be reviewed for operational security before release, with the review conducted by the soldier’s chain of command. Wired, which obtained the new version and reported it on 2 May 2007, set the change against the previous edition: where the earlier rules had asked Army personnel to consult an immediate supervisor before posting anything that might contain sensitive information, the revision required an operational-security review prior to publishing, and was read in practice as requiring a commander to be consulted before every blog update. It did not prohibit blogging, and it did not create the review requirement from nothing: review obligations for public release of official information already existed.
What the update did was extend the framework explicitly to personal websites, blogs and email, media that had not existed in a meaningful way when the earlier guidance was written.
Why it read as a ban
Three features made the practical effect far larger than the text implied.
The review burden fell on units, not on the Army. A brigade in Iraq had no staff element whose job was reviewing a soldier’s blog post before dinner. Where the requirement was applied literally, the realistic answer for a busy commander was to decline to review, which functions as a prohibition without being one.
The consequences were asymmetric. A soldier who published without review was in violation. A commander who declined to review incurred no cost. Any rule with that shape produces suppression regardless of its wording.
Interpretation varied enormously. Some units required review of every post, some of none, some issued blanket instructions to stop. The regulation permitted all three readings, so soldiers a few kilometres apart were operating under materially different rules.
The underlying concern was real
It is worth stating plainly, because the argument at the time tended to treat the security concern as a pretext. It was not.
Operational security is defeated by aggregation instead of by disclosure of secrets. Individually harmless details: a unit’s location, the timing of patrols, the layout of a base, the effect of a particular attack, the presence of a specific capability, combine into a picture useful to an adversary. A soldier posting daily from a forward operating base can supply that aggregate without ever writing anything classified, and without any intent to.
Photographs were a particular problem, and remain one. Image metadata, visible terrain features and recognisable structures locate a position more precisely than text usually does.
What the Army lost
The countervailing argument, made forcefully at the time by serving personnel and by journalists who read them, was that soldier writing had value the institution could not replicate.
It provided a first-hand account from the level where policy meets reality, which is where official communications are least informative. It supplied the technical scrutiny that had already changed outcomes in public disputes about equipment and about reporting. And it connected units to families and to a civilian public with very little direct contact with military service.
Suppressing it did not remove the information from the internet; it removed the voices most likely to be accurate and most invested in getting it right.
How it settled
The practical resolution over subsequent years was a shift from prior review toward training and guidance: teach soldiers what not to publish, publish the criteria, and rely on judgement rather than on a review pipeline that could not scale. Later social-media guidance across the services follows that model.
The specific 2007 provision matters less now than the pattern it illustrates. A rule requiring per-item approval, in an environment where the approver has no capacity and no incentive to approve, becomes a prohibition in practice while remaining a review requirement on paper, and the gap between those two descriptions is where most of the argument happens.
The reporting lesson
Coverage at the time split into “Army bans blogs” and “Army does no such thing”, and both were defensible readings of different things: the first of the effect, the second of the text. The more accurate account required saying that the regulation permitted review and that the incentive structure made refusal the default — which is two sentences longer and considerably less quotable.
That is a recurring problem with reporting on institutional rules, and it is worth holding in mind whenever a document and its consequences are described as though they were the same object.
Questions and answers
What did the regulation actually require?
Review of material before publication where it concerned operations, and it was aimed at operational security instead of at opinion. The practical difficulty was that it applied a review process designed for official publications to something being written in the evening from a tent, by people whose chain of command had no procedure for it.
Was the concern about operational security legitimate?
Yes, and that is the least disputed part. Unit locations, movement patterns, casualty details before notification, equipment vulnerabilities and the effect of specific weapons are all genuinely sensitive, and none of it requires malice to disclose: a photograph with a recognisable feature in the background does it. The dispute was about the mechanism, not the risk.
Why is this episode still cited?
Because it is the first case of an institution having to regulate publication by its own members at a scale it had never faced, and the questions it raised have not gone away. Every subsequent argument about serving personnel and social media is a version of it, with the volume raised and the review process no more practical than it was.