How to keep a verifiable social media policy record

For a record tracking social media regulation, app rules, or workplace policies, the hard half is recording a change so somebody who relied on the old version can understand what happened.

What to take away

Six kinds of change

The rung moved. The same instrument advanced: adopted, published, entered into force, started applying. Nothing about the text is new. Update the rung, add the date and its type, leave the substance alone. The EU's Digital Services Act shows why the type matters: it came into force on 16 November 2022, but most services had until 17 February 2024 to comply, so one law carries two dates that mean different things.

The text changed. A different version now exists. This is the one that requires reading, because a redraft between consultation and adoption can move the thresholds that decide whether it reaches you.

The interpretation changed. The text is untouched and a body has published guidance, or a court has decided something, that changes what it means in practice. Frequently more consequential than a redraft, and almost never reported as an event. The relationship between a statute and the guidance an agency issues under it is set out generally in Cornell's overview of administrative law. That overview describes one system but explains why this category exists in all of them.

The status changed. Stayed, challenged, under appeal, partially suspended. The instrument still exists and may not be operative. An entry that does not carry status will be read as final.

Your understanding changed. Nothing outside moved. You read the text properly, or an adviser corrected you. This is a change to the record and it must be recorded as one, or the correction will be read as an external development.

The service revised its page. A platform's own rule changed, possibly without notice or a changelog. Only detectable against a copy you already had.

Two of these require action from anyone outside the record: a changed text and a changed interpretation. Distinguishing them at the moment you write is what stops a maintenance update from triggering a general alarm, and what stops a substantive change from being buried in a routine one.

The supersession block

When an entry changes, add rather than replace:

The five lines, with an example filled in:

An entry carrying that block reads end to end like this, and the shape is copyable:

The cost is a few lines. The benefit is that a reader can tell the difference between a record that was wrong and a world that moved, and those call for completely different responses.

Detecting the changes nobody announces

Three categories arrive without an announcement, and each needs its own habit.

Guidance and interpretation appear on a body's own pages, not in news. Watch the publications page of each body on your list directly instead of waiting for coverage.

For a record covering social media and app rules, that list usually starts with the European Commission for the Digital Services Act, Ofcom for the UK's Online Safety Act, and the Federal Trade Commission and state attorneys general in the US. For workplace social media policies in the US, add the National Labor Relations Board. The authoritative texts sit in EUR-Lex, legislation.gov.uk and the Federal Register, and those are the copies worth keeping.

A body's decisions and guidance pages are usually its least-read and most useful publication, and a policy news watch scoped to your real exposure starts with the bodies you actually answer to.

Consolidated texts change when amendments are folded in. Where a jurisdiction keeps a codified version, most people read that codification, and it is not always current.

GovInfo's explanation of how the Code of Federal Regulations relates to the daily register describes this lag in one system. Every codified system has some version of it, and knowing whether you are reading a consolidated or as-enacted version is a routine source of confusion.

Service policy pages change silently: a platform's community guidelines, advertising policies and developer terms can each be revised on their own schedule. The only detection method that works is comparison against a copy you hold. Where the change is to enforcement rather than to the written rule, there may be no document change at all, which is covered in the gap between the written rule and the enforced one.

Triage, in this order

Steps four and five are where records usually stop, and stopping there is why organizations discover a change they had already recorded.

Versioning your own document

If the record is a shared document rather than a database, it needs the same treatment you would give a policy: a version number, a date, and the previous versions kept. People are entitled to know which version they read, and you are entitled to know what you told them.

Five fields per version:

A dated archive of a rule is worth keeping for the same reason. A person is assessed against the rule in force at the time. Demonstrating what that rule was requires a copy. The contractual version of that principle is in the terms you are held to.

For a public rule, the matching question is which body issued which version when. That is covered in finding the responsible body.

Cadence and the triggers that jump it

A fixed cadence catches slow movement. Triggers catch the rest. They jump the cadence: an entry moving between rungs, a challenge being decided, a new market, a new product, a new dependency, or a change in what your organization actually does.

The last of those is the trigger organizations forget, because it comes from inside and does not arrive as news.

Two intervals cover most records. A live entry gets a pass every quarter. A dormant entry gets one every six months, with the observation date moved forward even when nothing has changed.

Worked trigger. A product ships into a new market in March. The trigger is the launch, not the calendar. Add that market's regulator to the list, read the rule for that market before the launch date, and write an entry even if the entry says nothing applies to you.

The next scheduled pass would have been in June, three months after the launch.

Where an entry has been quiet for a long time, lengthen its cadence rather than dropping it. A dropped entry disappears from the record; a quarterly one stays visible with an honest observation date on it. The general shape of maintaining that record over time is in the ladder a rule climbs.

Common questions

Do we really need to keep entries that turned out to be wrong?

Yes, and marked as wrong. Someone made a decision on that entry. If it vanishes, the decision becomes inexplicable, and nobody can check whether it needs revisiting.

How do we tell the people who acted on the old version if we did not record who they were?

You cannot, which is the argument for the field. Until it exists, the fallback is to tell the owner of every process that touches the subject and accept that this is noisier than it should be.

Should a change to our own interpretation be announced as widely as a change to a rule?

To the people who relied on it, yes, and with the distinction stated plainly. Presenting your own correction as external news is how a record loses its credibility, and credibility is the only thing making anyone read it.