Publication workflow
How Gov Influence works
Gov Influence publishes bounded, reviewed records through a reproducible workflow. The example below follows one Boeing LDA filing without turning it into a claim about influence or policy effect.
Reviewed Sep 5, 2026
1. Retrieve a bounded source packet
For the approved Boeing example, the LDA adapter requested BOEING records for Q4 2025 and captured the response on September 3, 2026. Filing eeaaefdd-a9b7-4951-b22a-6f6ee701be9f names BOEING COMPANY as the client and ETHERTON AND ASSOCIATES, INC. as the registrant. The capture preserves the source identifier, direct URL, reporting period, posting time, filing type, names, amount fields, issue codes, and original descriptions.
2. Normalize without changing the source claim
The adapter converts the record to a typed project shape while retaining the original names and wording. Its $30,000 income field remains outside-registrant income; the blank expense field is not converted to zero. Lobbying, legislation, political finance, and federal awards remain separate evidence categories.
3. Review identity and record versions
The complete client name is compared case-insensitively with Boeing's approved exact-alias allowlist. A similarly named credit union in the same search response is excluded. Records are then grouped by client, registrant, year, and quarter; the latest posting is retained, an amendment wins a tied posting time, and filing ID is the final deterministic tie-breaker.
4. Classify and calculate
Only official LDA codes in a reviewed issue allowlist enter a normalized issue profile. The example filing carries DEF, GOV, and INT: DEF may enter Defense and Aerospace Policy, while generic GOV and INT do not enter that normalized issue. Filing-level income is not allocated across codes, and issue-code counts may overlap when a filing contains more than one included code.
5. QA, editorial review, and publication
Schemas validate required provenance; QA reconciles canonical filing counts, quarter groups, amount states, issue distributions, source links, approved relationships, roster size, and publication status. A human review then checks usefulness, wording, limitations, accessibility, and freshness. Only approved, published registry entries appear in the catalog and sitemaps.
6. Refresh or correct through the same path
A later amendment, refreshed source record, or verified correction returns to the curated input and generator. Derived totals are regenerated rather than repaired in page copy. Material corrections are disclosed on the affected existing page and, when the change has broader relevance, through Project updates.