Data, access and product boundaries

Radio Workflow supplies operational records through your authorized connection: station details, orders, rates, available airing evidence, programming and research. The platform reads those records without changing Radio Workflow.

Station staff supply the facts that those records cannot establish, including request and sponsor details, employment-unit activity, applicability decisions and supporting documents. The FCC public file supplies dated folder and file metadata for selected checks.

A live source request and a background review are different. Background review uses retained station records and public file checks; it does not silently refresh Radio Workflow as a signed-in user. Source failures and coverage limits need follow-up.

Draft means there is work to review. A generated PDF means a version was prepared and retained. An upload confirmation records the station's statement about the exact file and date it uploaded. An FCC observation records metadata seen during a dated scan. These are separate facts.

A file name is not proof that a document contains all required information. A scan can be incomplete, and absence from a limited read is not proof of a violation. A finished review is not a determination that the station has met every FCC obligation.

The station remains responsible for its public file. Confirm unusual circumstances, actual license terms and special FCC notices using authoritative records. Requirement guidance and routine dates do not replace legal or engineering judgment.

Records and files belong to a workspace. Access checks require the active workspace, an eligible account and permission for the requested action. Generated documents retain their version, file hash and station snapshots. Generating a replacement does not overwrite the earlier PDF.

A document placed in the private vault is not automatically public or submitted to the FCC. File downloads require authorization or a time-limited link. Treat a download link as sensitive while it is valid.

Retention guidance is a prompt to review the applicable rule and station facts. A calculated date is not permission to destroy evidence. Removing a document from active view is different from deleting its retained history. Contact support about retention, correction or account-level deletion requests.

Program-specific donor lists and third-party fundraising records cover one selected stream. Staff enter actual activity and broadcast details, review station eligibility and retain authority evidence. A blank record does not establish that no activity occurred, and a prepared record does not grant fundraising permission.

These NCE PDFs contain the designated public report fields. Private source notes, authority evidence and private notes remain in the preparation record and are omitted from the PDF. Staff must still inspect every public field for unintended private information. Each generated version is retained. Dated donor entries for programs already broadcast can be prepared during the current quarter. Incomplete records remain drafts; quarterly fundraising and whole-quarter no-activity exports stay drafts until the quarter ends.

The leadership workflow prepares a list for one selected station stream from reviewed sponsor, leadership and actual broadcast facts. Copying names from a political record creates an unconfirmed draft with source history. It does not establish the true principal, applicability, broadcast activity or public placement.

Public PDFs contain the designated public fields. Principal research, source references and private notes stay in the preparation record. Staff inspect the public fields, perform the actual external placement and record the exact retained file, destination, date and evidence. Correcting a placement preserves the earlier event.

Each generated version retains its own broadcast facts and retention basis. Later edits do not rewrite that history. A network-originated leadership list may have an alternate public inspection location when the rule permits it; this does not complete foreign-programming disclosure, diligence or a section 325(c) permit workflow.

The political backup exports retained political, disclosure and rate PDFs with an inventory, hashes, exact-file audit references and collection instructions. It includes drafts and private worksheets. The package is a private working copy, not a complete FCC public file or a public-access service.

Save every ZIP part and any separately listed files outside this app while workspace access is available. Files uploaded directly to the FCC, document-vault files and records held elsewhere need separate collection. Review incomplete and unavailable entries, check the files open, and arrange a staff-accessible copy before an outage.

The inventory cutoff controls which retained items are selected. Record status and filing evidence are read when a part is prepared, rather than reconstructed as a historical snapshot. Refresh the backup after changes and keep new activity during an outage. Downloads do not upload to the FCC or confirm public access.

Private cases retain actual inquiries, responses, exact document versions and dated staff reviews for one arrangement and station stream. A request template is preparation, not an executed certification. Recording efforts and determining the programming source are separate decisions; absent or inadequate responses remain visible.

Evidence links preserve the reviewed document metadata and file hash. Later vault edits, corrections or replacement do not rewrite earlier reviews. Renewal reuse retains the original actual inquiry date and needs an explicit review of unchanged facts. Product timing checks do not decide a legal deadline or authorize broadcasting.

The private evidence index captures a case and its complete event history through a stated revision. Download the manifest and every numbered JSON part, preserve their descriptors, and check the retained hashes. Attachment bytes are not bundled and need separate collection. A later reference observation does not change the original reviewed metadata. Export time is not a review or retention anchor, and the index does not confirm public filing or regulatory sufficiency.

When an AI drafting service is configured and you request an assisted issues/programs draft, selected source titles, short summaries, tags, source facts, station identity and the quarter are sent to that service. It returns proposed text for staff review. The current drafting call has no tools to publish a filing or operate your account.

If that service is unavailable, topic-based grouping can still produce a starting draft. Neither method establishes that a program aired or that a research story was addressed on your station. Staff confirm the program and actual broadcast details before using the entry.

Daily review and automatic preparation of setup drafts are workspace choices. A scheduled review may run later if its worker or sources are unavailable. Review findings and prepared drafts remain visible for people to inspect; the agent does not submit them to the FCC.

Staff can turn findings or actual notices into work items, assign workspace members and retain completion evidence. Website, application-notice and selected-audit guides provide prompts, not automatic website inspection or proof that an event happened. Internal targets are staff scheduling choices. Assignment sends no notification; coordinate the work with the responsible person.

Record the actual wording and broadcasts for one station stream, with local dates, time zones and separately reviewed quarter boundaries. A script is not proof of an announcement. Staff review the programming's primary language against the exact announcement that aired; a supplemental translation cannot establish that match. Missing performance evidence remains follow-up even when staff prepare a truthful public record of known broadcasts.

Staff review all selected public fields before preparation. Generated copies include the preparing person's name and generation time. Private inquiry material, internal notes and receipts are excluded. If the renderer cannot preserve the original language, the complete text remains available for a separately prepared searchable PDF or supported native document that staff review against the selected records. Private preparation JSON is not a public filing artifact.

An exact artifact, its actual placement and later public observations remain separate records. Multiple partial files can cover the quarter together. An unplaced replacement does not erase a valid earlier filing, while corrected public facts or a failed later readback reopen affected work. Metadata alone cannot resolve a reported content mismatch. Corrections and withdrawn content reviews preserve the original bytes and history.

This workflow does not publish to the FCC, monitor on-air equipment, complete section 325(c) permits or activate a deferred rule. Stations supply the actual evidence and review applicable obligations. Conservative retention guidance uses known broadcasts, public availability and holds; the generation date does not authorize release or deletion.

Use your Radio Workflow account to sign in. The password is used for the sign-in exchange rather than stored by this platform. Eligible workspace roles control app access; switching workspaces and signing out end the relevant local session access.

API and MCP keys are workspace-scoped, permission-scoped and revocable. The key owner's current access is checked. Give connected tools only the capabilities they need and revoke unused keys. The published API contract describes the supported operations and their required scopes.

API and MCP writes use the same domain validation as the app. An agent cannot supply its own acting identity, authorize an FCC upload through a local key, or make an unsupported statement true by marking work complete. Consequential changes retain audit evidence about the action and actor.

Choose all app actions or individual permissions when creating a key. Reading document metadata does not itself grant file-download access. MCP connections use a custom Authorization header; check that your client supports this setup. The Integrations page provides the connection URL and the current operation catalogue.

This page describes product behavior. It is not a new contract, a privacy policy, an FCC endorsement or a legal opinion. The company directories link to available product policies and explain where to request terms or privacy information.

Do not assume a regulatory requirement is satisfied because a task is complete here. Compare the underlying evidence and the actual public filing when required. Use the station's qualified adviser for legal interpretation and its engineer for technical measurements.