Features
Part of Recording the right date type keeps a policy news timeline useful for years
Policy news and timelines checklist: a tracking method
A policy news and timelines checklist for social app rules, with ten checks for dated records, source review, follow-up triggers, and workplace use.
This policy news and timelines checklist is a run list for one session tracking rules and policy changes that can affect social media, apps, or workplace use of those services. Not a reading list and not a research method: it is a bounded pass over your policy record that helps you avoid drifting into interesting things that are not yours.
Print it, or keep it beside the record. A checklist removes the decision about what to do next.
What to take away
- Open the record before opening any source. Working from the record forward keeps the pass bounded.
- Four stop conditions matter more than the run liststop at the primary document, when the question becomes legal rather than factual, when the source is a secondary account of a foreign rule, and when the scope expands mid-pass.
- A pass that finds nothing is a successful pass and has to be recorded as one.
Before you start
Three lines at the top of the page, written before anything else:
- The date of this pass, and who is running it.
- The date of the previous pass.
- Anything flagged for follow-up last time.
If the previous pass was longer ago than your stated cadence, note that too. A record with an honest gap is worth much more than one that implies continuous coverage it did not have.
Before the pass, make sure your exposure list names the bodies, laws, and services relevant to your organization. For a U.S. social-app watch, that list can include the Federal Trade Commission (FTC) and, when consumer-protection issues are relevant, the Federal Trade Commission Act; check FTC publications, the Federal Register, and the Code of Federal Regulations for relevant notices and rules. If your organization relies on Instagram or TikTok, include each service's policy and change pages. These are examples, not a substitute for scoping your actual exposure.
The ten checks
- Read your own open items first.Anything marked unresolved, contested, or awaiting a date. These are where change is most likely and where you already know what you are looking for.
- Check each named body's own publication page.Registers, decisions pages, guidance pages. In the order of your exposure list, not in the order they occur to you.
- Check the policy and changelog pages of any service you depend on.These change without announcement more often than public rules do.
- Take a dated copy of anything you rely on that has changed.Before you write the note, not after.
- Update the rungof any entry that moved, and add the date type. Adoption, publication, entry into force and application are different dates, and an entry that does not say which one it holds is a trap.
- Ask the separate question of whether it reaches you.In force and applies to us are two fields. Fill in both, even when the answer to the second is unknown.
- Write the one-line summary in your own words.Copying the regulator's headline reproduces the compression that caused the confusion.
- Note anything you looked for and did not find, with where you looked.
- Set the next triggerfor every entry you touched: a date, an event, or both.
- Record that the pass happened, even if nothing changed. Especially if nothing changed.
Stop conditions people override
Stop at the primary document. Once you have the official text, stop reading commentary about it. Commentary is for discovery. Continuing to read it after you have the document is how someone else's interpretation ends up in your record wearing your name.
When to stop reading
Do you have the primary document?
Stop reading commentary
Keep reading for discovery
Stop when the question becomes legal rather than factual. "What does this document say" is a research question. "Does this apply to us, and what must we do" is frequently a legal one. The honest entry at that boundary is a note that says counsel is needed, with the specific question written out. Handing an adviser a precise question is also considerably cheaper than handing them a topic.
Stop when the source is a secondary account of a foreign rule. Two translations away from the text, in a system whose terminology does not map cleanly onto yours, is the point at which confident notes are usually wrong.
Stop expanding the scope mid-pass. Interesting things you find that are outside your exposure list go on a separate list to be considered at the next scoping review. Widening scope during a pass is how a two-hour session becomes a lost day and then stops happening at all.
What each field should hold
Good content
- What happened
- One sentence, your words, naming the body that acted
- Rung
- Proposed, adopted, published, in force, applying, enforced
- Date and type
- The date plus which kind of date it is
- Source
- Document, body, retrieval date, URL
- Reaches us
- Yes, no, or unresolved, with the reason
- Status
- Final, under challenge, stayed, superseded
- Owner and trigger
- A name and what would make you look again
Bad content
- What happened
- The headline, pasted
- Rung
- "New rules"
- Date and type
- A bare date
- Source
- A link with no title
- Reaches us
- Blank
- Status
- Assumed final
- Owner and trigger
- A review date with no owner
The two fields most often left blank are the last two, and they are the ones that decide whether the record is alive.
Good versus bad field content
Good content
- What happened
- One sentence, your words
- Rung
- Proposed, adopted, published, in force
- Date and type
- Date plus which kind
- Source
- Document, body, date, URL
- Reaches us
- Yes, no, or unresolved, with reason
- Status
- Final, under challenge, stayed
- Owner and trigger
- A name and what to look for
Bad content
- What happened
- The headline, pasted
- Rung
- New rules
- Date and type
- A bare date
- Source
- A link with no title
- Reaches us
- Blank
- Status
- Assumed final
- Owner and trigger
- A review date with no owner
Running it as a group
With more than one person, split by body, not by topic. One person watching a regulator learns its publication rhythm and house vocabulary. That is real efficiency.
Three people each watching a slice of a topic across five bodies learn none of it and duplicate each other. Splitting by body mirrors scoping a policy news watch before you drown in sources.
Keep the write-up with one person. Multiple voices in one record produce entries that are inconsistent about exactly the things this checklist is trying to standardize.
After the pass
Two outputs. One is the updated record. The other is a short note to whoever needs to act, containing only the entries where the answer to "does anything we do become non-compliant, and by when" changed. Sending the whole record to a general distribution list trains people not to read it.
Two outputs after the pass
- Update the record
- Write a short note to whoever acts
- Include only entries where compliance changed
- Do not send the whole record to a general list
- Service rule: tell account holders, not compliance
- Public rule: find which body owns it
Where the change is a service's own rule rather than a public one, the people who need to know are usually different. The practical consequences show up as account actions rather than as compliance work.
For a service's own rule, record the affected service and the account or workflow that may be affected. For a public rule, record the responsible body and the instrument you are tracking before deciding what action may be needed.
Bookmark two institutional explainers for the pass itself. The National Archives publishes an account of what the Federal Register is and what appears in it. GovInfo publishes an explanation of how the Code of Federal Regulations is organized, including how it relates to the daily register.
Those two describe one country's machinery. Find equivalent pages for every system you are exposed to and add them to this list.
Common questions
How long should a pass take?
An hour to two hours for a scoped list, once the address book exists. If it routinely takes longer, the scope is too wide or the record is holding entries that no longer matter to you.
What if nothing has changed for months?
Record the passes anyway and consider lengthening the cadence. A quarterly pass that happens is better than a weekly one that stops. Keep the triggers, since those are what catch the thing that arrives between passes.
Should the checklist itself be reviewed?
Once a year, and after any surprise. If something reached you that no step on this list would have caught, the fix belongs here rather than in a general resolution to pay more attention. That is also the honest way to record how a change to your own record should be handled.
