Skip to content

Power

Campus Protest Maps Turn Disputes Into Permanent Records

A point on a public map looks like neutral documentation. Underneath it sits a classification system that can follow students into discipline, news coverage and police files.

Simone AchebePower — Surveillance

August 14, 2026 · 8 min read

A laptop showing a campus protest map beside printed university notices and handwritten event notes.

On the College Protest Network map, Columbia University becomes a point attached to a record. The underlying event was messier: an encampment established in April 2024, student organizing, university discipline, arrests, negotiations, the occupation of Hamilton Hall and two police entries onto campus. The map needs something cleaner.

A location. A date. An event type. Named actors where the source material supports them.

Notes on intervention by administrators or law enforcement.

That reduction is the product.

The College Protest Network, created by the Armed Conflict Location & Event Data project, known as ACLED, and Princeton University’s Bridging Divides Initiative, assembled information on demonstrations and institutional responses at US colleges. ACLED specializes in event data, meaning reports of political activity converted into standardized records that can be sorted, compared and mapped. Its methods are public, and the project does not generally identify individual student participants. That is better than building personal dossiers.

It does not make the resulting dataset politically neutral.

The point over Columbia is useful because it can move. A journalist can cite it. A university official can compare campuses. A researcher can download or query records.

A police analyst can place protest activity beside other information held by an agency, even if the original map never named a single student. Once a confrontation becomes a row in a dataset, the row can outlive the context that produced it.

The category comes before the conclusion

Public trackers usually describe themselves as documentation projects. That description is accurate but incomplete. Documentation requires decisions about what qualifies as an event, which sources count, where one event ends and another begins, and whether participants belong under the names they use for themselves or labels supplied by an institution, advocacy group or news report.

Those choices do not merely describe political activity. They determine which activity becomes legible to power.

Consider the Columbia record again. A march, an encampment and an occupied building can be separated into distinct events or treated as stages of one campaign. A confrontation may be coded as a protest, a riot or an intervention depending on the tracker’s taxonomy and the available reporting. Police action can appear as a response to disorder, while the earlier administrative decision that brought police onto campus sits in a note or disappears outside the event boundary.

Structured data rewards whatever fits into a field. It punishes ambiguity.

This matters because campus conflicts produce claims faster than investigators can verify them. Administrators issue alerts. Student groups post videos clipped before or after the disputed moment. Police release arrest information.

Advocacy organizations collect complaints. Newsrooms work against deadline. A tracker that waits for a settled account may never publish; one that publishes quickly inherits the weaknesses of its sources.

A methodology can disclose those weaknesses. It cannot prevent downstream users from treating the finished row as fact.

The conversion usually follows a recognizable sequence. A report enters the collection system. A researcher decides that it meets the threshold for inclusion. The event receives a location, actor labels and a category.

Similar records become a count or map layer. The dashboard then presents the collection as something searchable and comparable, with the visual authority of a database rather than the provisional quality of the original report.

The uncertainty has not vanished. It has been moved somewhere less visible.

Different trackers produce different suspects

The campus map is one part of a larger monitoring environment. The Anti-Defamation League’s Campus Antisemitism Report Card evaluates universities through categories that include reported incidents, campus activity, student organizations and administrative responses. Columbia received an F in the report card’s initial 2024 edition. The grade turns a disputed political environment into an institutional score, while the underlying categories encourage readers to see the presence of particular groups or events as evidence about the campus itself.

Canary Mission goes further. It publishes profiles of students, professors and organizations it accuses of promoting hatred of the United States, Israel or Jews. Those pages gather names, photographs, affiliations and social media material into searchable dossiers. The site has drawn sustained criticism over accuracy, opacity and the consequences for people seeking work or crossing borders.

These projects are not interchangeable. ACLED’s event-level research has a different method and purpose from an advocacy report card, and both differ from a site built around named profiles. Treating them as identical would reproduce the flattening under examination.

They do, however, occupy the same information chain. The map establishes that an event happened at a place and time. The report card classifies the institution’s climate and response. The dossier connects political activity to a person.

Each layer makes the next one easier to build because public records, campus statements, news stories and social posts can be copied across systems without the subject’s participation.

At Columbia, the point on the map does not need to contain a student’s name to narrow the field. Combine its time and location with arrest records, organization posts, livestreams or disciplinary documents, and an event-level record can become personally identifying. Data linkage, the matching of separate records through shared details, does the work that the original dashboard declined to do.

Privacy promises that address only the first dataset miss this mechanism.

Public does not mean harmless

Campus demonstrations take place in public. Organizers issue statements because they want attention. Some participants film themselves. Institutions therefore fall back on a familiar defense: the information was already available.

Availability is not the same as aggregation. A student standing in a crowd may be visible to everyone nearby for an hour. A structured record makes the event retrievable months later, comparable with activity elsewhere and ready to combine with other files. Search changes the scale of exposure.

Standardization changes the audience.

The likely users also have unequal power. A student may consult a map to understand a national movement. A newsroom may use it to identify patterns. Administrators can use the same material while deciding discipline, access rules or whether to call police.

Law enforcement agencies already monitor open sources, a practice often called open-source intelligence, and a clean event dataset removes part of the collection labor. The dashboard does not have to send a file directly to police to function as surveillance infrastructure.

This is why the word product matters even when access is free. A product is organized for reuse. Nonprofits and university centers may gain grants, institutional standing and partnerships from producing authoritative datasets, while commercial monitoring vendors can build paid analysis around public material. The people described in the records rarely receive notice, correction rights or any share of that value.

The map’s clean interface hides the labor and conflict beneath it. Researchers must review reports, resolve duplicates and update records. Subjects must discover that a classification exists, identify who controls it, gather contrary evidence and request a correction. If a disputed label has already entered coverage or an institutional file, changing the source may not repair the copies.

Permanence arrives by replication.

A better map would be less convenient

A protest tracker can reduce harm, but the changes cut against the features that make dashboards attractive. It can delay publication while facts remain contested, publish source provenance beside each field, display confidence levels prominently, avoid naming student organizations unless necessary and remove records after a defined period. It can document administrative and police decisions with the same precision applied to protesters.

It can also restrict bulk access. An application programming interface, or API, lets another system retrieve records automatically; limiting it slows mass collection and makes the dataset less convenient for researchers, reporters and anyone building a watchlist. That tradeoff is real. A dashboard designed for friction will lose some reach and may cost more to maintain because corrections, appeals and periodic deletion require staff time.

The alternative is to make the burden disappear from the institution’s balance sheet and reappear in students’ lives.

Columbia’s point on the map will remain useful to historians of the 2024 campus movement. It may help establish the sequence of protest and repression across universities. Yet a durable record should preserve the dispute, not merely the classification imposed at collection time. It should show who made each claim, what evidence supported it, what changed later and which details were withheld to prevent a political chronology from becoming a people-search tool.

Otherwise the map records more than protest. It records which version of the protest had enough institutional backing to become data.

Questions people ask

Are campus protest maps public records?

Some are public datasets created by nonprofits, researchers or advocacy organizations, rather than government records. Their contents may still draw from university statements, police information, news coverage and public social posts, which allows the same event to circulate among private and government systems.

Do protest trackers identify individual students?

Some event trackers avoid individual names, while dossier sites explicitly identify people. Even an unnamed event can expose participants when its location, timing and organization labels are combined with arrest records, photographs, livestreams or campus disciplinary material.

Can a disputed entry be corrected?

That depends on the tracker’s policy and whether it offers a visible correction channel. Fixing the original entry may not update screenshots, news stories, downloaded datasets or institutional files that already copied the classification.

What would make a campus protest dashboard safer?

It would minimize organizer information, preserve uncertainty, identify the source behind each claim, limit bulk retrieval and delete sensitive records on a published schedule. Those safeguards make the map slower and less convenient, which is precisely why institutions tend to omit them.

Was this worth your time?
ShareFacebook
surveillanceinternet policycampus protestsstudent organizingpublic dataopen-source intelligence

One update a day

Today's story, in your inbox

One story each morning — no hype, no filler, no algorithm deciding for you.

Read next