Running a coalition site with both a public record and confidential filings

A coalition site has to serve two audiences at the same time. There is the open public record — the mandate, the members, the filings meant for the record, the plain explainers — that journalists, congressional staffers, regulators and the AI assistants they increasingly ask will read. And there is the gated material that only the members and their counsel should ever see: draft strategy, privileged material, member-only working documents. The answer to running both well is not one clever system with a wall of permissions. It is two clearly separated layers: a small, fast, public surface anyone can read, and a properly gated members’ area behind real access control. Get that separation right and you can be openly authoritative in public while coordinating privately, without the two ever crossing.

A coalition site has two audiences, so it needs two layers

Most of the value of a coalition site is in being read. When your issue is searched, whether in a newsroom, a committee office, a regulator’s inbox, or now inside an AI answer, you want your side to be the source that gets found and quoted. That argues for a public layer that is open, credible and machine-readable, with nothing standing between a reader and the substance.

But a multi-party coalition also has to do work that is not for the public: agree messaging before it ships, share analysis between the parties, hold privileged material that is not anyone else’s business. That argues for a private layer with the opposite properties — closed, authenticated, invisible to search.

These are not two settings on one site. They are two different jobs with two different threat models, and the cleanest way to meet both is to build them as two separated layers that share a look but not a lock.

What belongs in the public record

The public side carries everything you want on the record and want found:

• The mandate. What the coalition is, what it is contesting or advancing, and why — stated plainly, up front.
• The members. The organisations behind it, named. A coalition’s credibility rests on who is in it.
• Filings and statements meant for the record. The founding statement, public comments, submissions you want cited — each one an obvious click away.
• Answer-first explainers. Short, direct pieces that answer the exact questions a journalist or staffer would ask, written so a person and a machine can both lift the answer cleanly.

This is the side that has to be fast, credible and readable by an engine, because it is the side an engine reads. It is also the side that should carry as little machinery as possible — the less there is on the public surface, the less there is to attack during a scrutiny moment.

What belongs behind the members’ area

The private side carries everything that is not for the record:

• Draft strategy and messaging, before the parties have agreed what goes public.
• Privileged material, kept where privilege is not put at risk by exposure.
• Internal analysis the coalition relies on but does not want quoted.
• Member-only working documents shared between the parties as the matter develops.

This is about discretion and clean separation, not concealment. A coalition is entitled to coordinate in private before it speaks in public, in the same way any organisation is entitled to a closed room to prepare in. The point of the gated layer is to give the members and their counsel that room — and to make sure nothing in it is discoverable, indexable or citable.

Publishing controls and a sign-off step

On a single-owner site, publishing is one person’s decision. On a multi-party coalition it rarely is. A public statement carries every member’s name, so it usually has to clear members’ counsel, a lead firm, or a steering group before it goes live.

That makes a sign-off step part of the publishing process, not an optional courtesy. The right setup makes approval explicit: a draft is prepared, the parties who need to approve it do so, and only then does it move to the public layer. Nothing reaches the record on one person’s say-so, and nobody is surprised by a statement going out under their name. When several organisations are speaking with one voice, the governance around what goes public matters as much as the words themselves.

Keeping confidential material out of the layer AI reads

The single most important rule is also the simplest to state: confidential material must never land in the publicly retrievable layer that search and AI read.

AI assistants and search engines can only cite what they can fetch. If a document lives behind authentication and is never rendered into a public page, a public link, a sitemap or a feed, there is nothing for a crawler to retrieve and nothing for an assistant to surface. The risk is almost never a dramatic break-in. It is a gated file that quietly leaks into the public layer: a working draft linked from a public page by mistake, an internal note caught by a search index, a preview that exposes more than it should.

Two separated layers make that leak much harder to cause. When the public surface and the members’ area are genuinely distinct — different access rules, no shared back door — a confidential document does not become public because someone toggled the wrong switch. The separation is enforced by how the site is built, not by everyone remembering to be careful.

Clean separation, access control and an auditable trail

Three things hold this together in practice.

Clean separation. The public record and the members’ area are distinct surfaces. The public side has no database or admin login on it for an attacker to reach; the private side keeps working material behind authentication. Neither is a setting on the other.

Access control. The gated area limits what each member and adviser can see to what they are entitled to see. Access is granted deliberately and removed when it should be — when a party leaves, or when the matter moves on.

An auditable trail. When several organisations share responsibility for what goes out, you want a record of who approved and published each item, and who could see what. An auditable trail turns “we think that was signed off” into something you can actually point to — useful while the coalition is live, and useful if the work is ever scrutinised after the fact.

Why two purpose-built layers beat one sprawling system

It is tempting to reach for a single platform that does everything and to manage the public/private line with permissions. On a coalition site, that is usually the wrong trade.

One sprawling system widens the attack surface and blurs the boundary between public and confidential at exactly the point, a hearing, a ruling, a press cycle, when scrutiny is highest and a mistake is most costly. A small, server-rendered public surface, with no database or admin login on the public site, is hard to deface or take down and easy for engines to read. A separately gated members’ area keeps confidential work behind genuine access control. Each layer is built for its one job, which makes both easier to reason about — and easier to defend — than one system asked to be open and closed at the same time.

That is the underlying pattern behind a well-run coalition site: be openly authoritative where it counts, properly private where it must be, and keep an honest record of who published what. The two audiences are served best when the two layers are kept apart.

This is a companion to web design for Washington DC trade associations, coalitions and nonprofits. For how we build and run these sites — the small public surface and the gated members’ area together — see Managed AI-Ready Websites.