Station Compliance›Field Notes

The public inspection file is the FCC obligation most likely to be handled by nobody in particular. It is not technical, so the engineer does not own it. It is not sales, so the sales manager does not. At a station with four employees it belongs to whoever last remembered it exists.

It is also, consistently, where small stations lose renewal terms. Worth twenty minutes to get straight.

Where it lives

The file is hosted by the FCC and is public at all times. A paper file at the studio has not been the public inspection file for years — if a document is only in a binder, it is not filed.

Commercial stations are governed by 47 CFR § 73.3526. Noncommercial educational stations by § 73.3527. The contents differ in a few places, most notably that NCE stations file donor lists for programming underwriting and commercial stations do not.

The half you do not have to think about

A useful thing nobody tells new licensees: the FCC populates much of the file itself. Authorisations, applications you filed through the Commission's own systems, ownership reports and contour maps generally appear without action on your part, because the Commission already has them.

This is why the file can look reassuringly full while missing precisely the things that matter.

The half that is yours

These are the documents nobody uploads for you. In rough order of how often their absence causes trouble:

Quarterly issues/programs lists — § 73.3526(e)(12). Four a year, due by the tenth day of the following quarter, retained until final action on the next renewal. This is the single most enforced item in the file, and it has its own article.

The political file — § 73.1943. Records of requests for broadcast time by candidates and, for issue advertising, the sponsor and related detail. The political file has a much shorter clock than everything else: entries go up immediately, which in practice means the same business day. This is the item most likely to be violated during an election season by a station that is otherwise diligent, because the pace is set by ad traffic, not by a quarterly calendar.

The EEO Annual Public File Report, for employment units with five or more full-time employees — see the EEO audit article.

Citizen agreements, if any exist, and letters and emails from the public for commercial stations, which have their own retention handling.

The station's authorisation and any applications not filed through the Commission's systems.

The failure modes

Nobody owns it. The most common cause by far. The file is fine until a staffing change, then drifts for two years before anyone looks.

Uploaded, but not where it belongs. The online file has categories. A quarterly list uploaded into the wrong folder is present on the server and missing from the file for practical purposes.

The political file lags. Weekly batching feels reasonable and is not what the rule contemplates. During a contested local race, weekly is very late.

Assumed automatic. A licensee sees a well-populated file, concludes the system is handling it, and never notices that everything in there arrived from the FCC's side.

A twenty-minute audit you can do today

1. Open your own public file as a member of the public would, not through a login. Look at what is actually visible.
2. Count the quarterly lists. One per quarter, for every quarter of the current licence term. Note gaps by date rather than "a few missing."
3. Check the most recent list's upload date against the tenth of that month.
4. If you have five or more full-time staff, confirm an EEO Annual Public File Report exists for each of the last two years.
5. If you sold political time this cycle, spot-check that entries went up promptly rather than in a batch.
6. Write down who owns the file. A name, not a role. This is the step that prevents the whole problem recurring, and it is the one that gets skipped.

What this has to do with the rest of the site

Nothing technically — and everything practically.

The pattern behind a public file gap is the same pattern behind an unpatched STL box with a default password: an obligation nobody owns, that produces no symptom until an outside party looks. The station is not being careless. It is running with fewer people than the rules assume, and the tasks that generate no daily feedback are the ones that fall off.

The defence in both cases is identical and unromantic — write down who owns it, put the dates in a calendar, and check the thing you assume is fine.

If the technical side is what is on your desk this month, the § 11.35(d) reference covers the September 29 program chain deadline.