A Civics Lab project runs through eight steps. Participants work through them more than once. On each pass, they understand the problem more fully, tighten the argument, and read more accurately where power resists them.
Any step can send participants back to an earlier one. New evidence can reopen how they defined the problem. A response from an institution can change what they need to know. A failed action can revise their whole approach.
The eight steps give participants a structure and a sequence to explore an issue, create a project, and work together toward a considered course of action.
Identify the issue and its category. Is it a local civic or consumer matter? A question of institutional accountability? Of rights, or of broader policy? The category shapes what is realistic: the terrain, the tools available, and the scope of action a circle can take on.
Participants begin by naming the problem as they currently understand it: specifically, clearly, and in their own words. Who holds authority over it? What existing accountability mechanism, a public records law, a franchise agreement, a regulatory process, can citizen action reach and put to use?
They then take honest measure of the limits of their own understanding: what they have assumed, what they cannot yet back with evidence, what they still need to find out. For example, participants might discover that the agency they planned to hold responsible does not set the standard in question, which is handed down from a higher level of government. That single fact can send them back to refine their understanding of a problem element and, if needed, redefine the target. This kind of self-assessment recurs throughout a project, as the work teaches participants more.
Participants divide the research into tasks and take them on. Sharing what each person finds does double work: it catches misreadings early, and it lets the circle's stronger readers and thinkers strengthen the whole group's understanding. Out of this comes a documented argument: the specific facts, the relevant rules or commitments, and a clear ask directed at whoever has the power to answer it.
The action requires specific knowledge participants may not yet have: legal, technical, regulatory, historical. That knowledge can come from many sources, a public document, a web search, an expert, an AI session, a neighbor who has been through it before. Locating the source is only half the work. Participants interrogate it: testing what they find, checking it against other sources, asking what it leaves out. What they learn informs their own judgment, and the direction stays with them.
Participants carry out the action as a group, not as individuals who happen to agree. That has practical implications they hold in mind: the work is coordinated so that letters, filings, and public comments are consistent with each other and with the documented case; each member knows what the others are doing; and every action is specific and traceable, so the record stays clear. Letters go to real addresses. Complaints go through official channels. Public comment enters the record.
Every consequential development, a reply, a silence, a partial concession, gives participants new information to work with. They ask what they now know that they did not before, how it changes the case, which earlier work it sends them back to, and what the next move should be. Each pass through this step sharpens the case, the participants' sense of where the real pressure lies, their own delivered impact, and how to strengthen it.
Participants record what happened: the response, or its absence, what worked, what did not, what comes next. This record serves three purposes at once. It is a resource the group returns to. It is an evidentiary trail of the group's process, decisions, actions, and consequences. And it is a contribution to Civics Lab itself, which is a repository and archive of citizen work, and a place designed to help people train themselves for citizenship by learning from what others have done.
Participants publish the project's record on Civics Lab, where it becomes visible and usable to others. What they have built by this point is a working group that has learned to act together, a documented case others can examine, and a worked example of a repeatable process. A project can end in a win, a partial result, or a loss. Publishing it matters in every case, because the value is in showing a process others can follow and adapt, and in adding one more worked example to the growing record of what citizen action can do.
Groups working on hard problems get stuck in familiar places: in criticism that finds fault without offering a way forward, in the search for a perfect answer, in the member who would rather be right than move. The constructive step is a way through. It asks that criticism carry a second obligation: when participants identify a flaw, a limit, or an error, they use what that criticism reveals to build the next position. The critique becomes material for construction.
What participants reach is not the perfect solution. It is the next move they can defend with evidence, doable by this group on this terrain, with a defined target, a defined ask, and a way to tell whether it worked. Circles and hives reach for this tool whenever the work stalls.
Civics Lab's work aligns with democratic government at its best: when elected representatives recognize the considered will of the public and act on it, drawing on open deliberation and access to information not distorted by those with an interest in shaping it. Citizen action of this kind becomes necessary when that alignment breaks down, when the system does not correct itself without pressure from outside.
The gap is always a failure of oversight, a point where the system that should catch a problem, enforce a commitment, or answer to the public does not. What that failure permits varies. Sometimes it lets an abuse go unchecked: a company that charges long-term customers more than new ones, a public official who misuses public resources with no mechanism holding them to account. Sometimes it lets a commitment lapse: a goal an agency adopted and quietly stopped pursuing. Sometimes it leaves a needed action stranded for want of demonstrated public support. Citizen action addresses the oversight failure itself. That can mean checking an abuse, or giving officials and institutions the documented public will to act more forcibly in the public interest, doing what they could not do alone. This too is democracy at work, not just the casting of a vote to put our preferred leaders into office, but the work of guiding and supporting them once they are there.
A project can begin with three questions.
What specifically is not being represented, enforced, served, or decided as a democratic system requires? Name it precisely.
Is it capture? Inertia? Deflection? Weak enforcement? The absence of organized public will? Understanding the failure shapes the action.
Participants look for the points of leverage available to them and build a case for oversight. That can mean a public records request, a regulatory complaint, a shareholder resolution, a franchise agreement, or a public comment period. It can also mean enlisting political support, asking an elected representative to take up the fight, as when a resident asks a city councilor to help challenge a utility's rates. Most cases offer some point of leverage citizen pressure can put to use.
Participants do not need to become experts to act. They need enough understanding to direct the work, not to carry out every technical part of it themselves. Genuine expertise exists and can be reached, through valid sources, through people who know the terrain, and sometimes with help from researchers, organizations, or AI. What matters is the practical, well-grounded understanding a group builds by working a real problem together, the kind of knowledge that comes from testing ideas against evidence and against each other.
A sufficiency report maps what a group knows against what the action requires. It sorts what participants are working with into four kinds.
What participants understand well enough to act on now. The documented facts that support an initial action as it stands.
What they need to understand before acting publicly. The specific gaps that would expose the case to legitimate challenge.
What opponents will say, and how to answer. The counterarguments addressed in advance, and the information environment the action will enter, so participants are ready to engage it.
What participants do not need to know, at least for now. Action itself teaches, and waiting for perfect knowledge is its own kind of paralysis. This is the discipline that keeps a group focused and keeps it from exhausting itself on research.
Every generation of citizen action has used the tools of its moment: the pamphlet, the union hall, the radio address, the televised march. Participants today may use AI in the same spirit, as an assistant and not a substitute, for gathering and synthesizing research, drafting and stress-testing an argument, anticipating objections, and organizing documentation. It is a convenience available to those who want it. The judgment, the decisions, and the direction remain with the people doing the work.
Neighborhood issues, consumer accountability, local environmental quality. Closest to daily life, with the fastest feedback.
Municipal government, public utilities, school boards, local agencies. Issues where elected or appointed bodies are not meeting their stated commitments.
Corporate practices with systemic impact, civil rights, consumer protection at scale. Work that calls for coordination across several circles and hives.
State and federal policy, regulatory structures, long-arc issues that require sustained network engagement and documented patterns of evidence.
Bring a concern, or bring a circle. There is a path that fits where you are.