Disclosure · 122 filers

Artificial Intelligence

122 companies wrote this into a filing in the last 7 days, down from 168. Below: which of them, and what the corpus says they now owe.

Data measured , page built 21 November 2026 at 16:39 UTC.

122filers, current period
168the period before
105controls it touches
61frameworks
2008 2026 701 filings in the busiest month
Artificial Intelligence in 10-K and 10-Q filings, by month. The phrase was already in use in the first month we hold, so this shows how it has moved since rather than when it began.
Companies disclosing it 122 wrote this into a filing with the SEC
What it obligates 105 controls across 61 frameworks whose text speaks to it
Employers hiring for it 131,401 open US roles name it, and the ones below are hiring now

The long view, in 8-K filings

An 8-K is filed within four business days of an event, so this counts filings made because something happened. Every month since 2008. The last point is the current month and is still filling, so it always looks lower than it will be.

 
0350701
2008 peak 701 in February 2026 2026

Who disclosed it

From SEC full-text search over 8-K filings. Every row links to the filing itself.

CompanyFormFiled
Artificial Intelligence Technology Solutions Inc. AITX8-K2026-11-16filing
Health In Tech, Inc. HIT8-K2026-11-18filing
CERENOME, INC. CNSY8-K2026-11-16filing
NIQ Global Intelligence plc NIQ8-K2026-11-19filing
Big Digital Energy, Inc. BGDE8-K2026-11-18filing
Powerfleet, Inc. AIOT8-K2026-11-16filing
Chaince Digital Holdings Inc. CD8-K2026-11-17filing
Sadot Group Inc. SDOT8-K2026-11-18filing
ChronoScale Holdings Corp CHRN8-K2026-11-18filing
Quantum-Si Inc QSI8-K2026-11-18filing
Safe Pro Group Inc. SPAI8-K2026-11-16filing
OLIN Corp OLN8-K2026-11-17filing

The full search on EDGAR

Who is hiring for it

A sample of the open roles naming this phrase. An employer paying a salary against something is the least ambiguous demand signal there is, and every row links to the posting so the claim can be checked rather than believed. The total above is the whole US market; these are the ones we hold the posting for.

RolePosted
Team Lead, Enterprise Service Desk
Abacus Life, Inc. · Atlanta, Georgia, United States; Charlotte, North Carolina, United States; Fort Lauderdale, Florida, United States; Frisco, Texas, United States; Orlando, Flori
2026-11-20
Technician, Site Services (Healthcare)
Abacus Life, Inc. · Sacramento, California, United States
2026-11-20
Strategic Consultant, SMS & Messaging
Airship AI Holdings, Inc. · Remote - U.S.
2026-11-20
Enterprise Account Executive I
Anaplan, Inc. · Bangalore, India
2026-11-20
Enterprise Account Executive
Angi Inc. · Remote - United States
2026-11-20
Enterprise Account Executive
Angi Inc. · Remote - United States - North Carolina
2026-11-20
Enterprise Business Development Manager
Angi Inc. · Remote - United States - North Carolina
2026-11-20
Enterprise Business Development Manager
Angi Inc. · Remote - United States - Massachusetts
2026-11-20
Enterprise Account Executive
Angi Inc. · Remote - United States - Georgia
2026-11-20
Enterprise Account Executive
Angi Inc. · Remote - United States - Texas
2026-11-20
Enterprise Business Development Manager
Angi Inc. · Remote - United States - Texas
2026-11-20
Enterprise Business Development Manager
Angi Inc. · Remote - United States - Georgia
2026-11-20
Enterprise Account Executive
Angi Inc. · Remote - United States - Massachusetts
2026-11-20
Head of Sales - Data and Platform Solutions
AppLovin Corp · New York City, NY
2026-11-20

How it actually arrives

An 8-K's meaning is in its item number, not its text. These are the items the filings containing this phrase were filed under. The first group is something that happened to the company. The second is the phrase turning up in the ordinary course of reporting, most often in an earnings release, which is a very different thing and is usually the larger number.

Filed because something happened Companies
Other material event
Item 8.01
1222
Director or officer departure
Item 5.02
1139
Delisting or listing rule failure
Item 3.01
123
Change of accountant
Item 4.01
69
Financial statements no longer reliable
Item 4.02
18
Bankruptcy or receivership
Item 1.03
16
Material impairment
Item 2.06
9
Material cybersecurity incident
Item 1.05
1
Mentioned in routine reporting Companies
Financial statements and exhibits
Item 9.01
2805
Regulation FD disclosure
Item 7.01
1806
Results of operations, the earnings release
Item 2.02
1487
Entry into a material agreement
Item 1.01
1340
Completion of an acquisition
Item 2.01
356
Shareholder vote
Item 5.07
154

This is why a headline count on its own overstates the case. Where the routine number dominates, the phrase is being tracked as language rather than as events.

Which industries file it

Companies grouped by the industry classification on their own filing. A count, not a survey.

IndustryCompanies
Software and IT services423
Holding and investment offices352
Chemicals and pharmaceuticals255
Banking254
Electronics and electrical equipment179
Instruments and medical devices165
Services and entertainment133
Industrial machinery128
Retail94
Insurance80

What it obligates

Our corpus holds 105 controls across 61 frameworks whose text speaks to this. Not a judgement: these controls say so, and each is one lookup from its source document. Ordered by how much each framework has to say about it, so the one that will cost you the most work is first. Every name opens that framework in the corpus.

FrameworkControls
Australian Information Security Manual verified
Australia
16
ISO/IEC 42006:2025 verified
International
5
WHO Global Strategy on Digital Health 2020-2025 verified
International (WHO Member States)
4
Germany Works Constitution Act (BetrVG) verified
Germany
4
SIG (Shared Assessments) verified
International
3
Texas Data Privacy and Security Act (TDPSA) verified
United States (Texas)
3
China Cybersecurity Law (CSL) verified
People's Republic of China (with overseas liability under Article 77 as amended)
3
ISO 37003:2025 verified
International
3
Australia National Framework for the Assurance of AI in Government (2024) verified
Australia (Commonwealth, states and territories)
3
Brazil AI Framework verified
Brazil
2
Australia AI Ethics Framework verified
Australia
2
GAMP 5 verified
International (pharmaceutical, biotechnology and medical device industry guidance)
2
EN 50126 / EN 50128 / EN 50129 verified
European Union (CENELEC), applied internationally
2
OECD Recommendation on Artificial Intelligence (2024 Update) verified
International (OECD; 51 adherents per the Compendium record of 2026-09-25)
2

What an auditor will ask you to produce

The artefacts named on those controls, most frequently cited first.

How it usually fails

Recorded when each control was verified against its source. This is where programmes that think they are covered turn out not to be.

ISO/IEC 42001:2023 AI Management System Evidence & Implementation Kit

79 controls sit behind ISO/IEC 42001:2023, and this is the documentation set for them: an adopt-ready artifact per control, and the evidence an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

ISO/IEC 42001:2023 NIST SP 800-53 Rev 5245 shared controlsSOC 2201 shared controlsNIST Cybersecurity Framework 2.0180 shared controlsISO 27002:2022160 shared controlsISO 27001:2022157 shared controlsISO/IEC 38500:2024142 shared controlsPCI DSS 4.0138 shared controlsEU AI Act112 shared controlsNIST AI Risk Management Framewor…68 shared controlsCIS Controls v864 shared controls
ISO/IEC 42001:2023 holds 83 controls. They appear again inside 129 other frameworks in our corpus; the 10 strongest are shown. Thickness and size both carry the number of controls shared, so work done once counts in every framework on this diagram.
79If you already run ISO/IEC 42001:2023, that is the 79 controls behind this disclosure, already evidenced.
229And ISO 27001:2022 is not a separate programme. 229 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
160And ISO 27002:2022 is not a separate programme. 160 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
142And ISO/IEC 38500:2024 is not a separate programme. 142 of its controls are the same controls. If it is on next year's plan, that part of it is already done.

Run as two programmes

308 controls

ISO/IEC 42001:2023 and ISO 27001:2022 scoped separately, each with its own evidence, its own owner and its own budget line. This is how almost everybody does it.

Run once, counted twice

229 already done

229 of ISO 27001:2022's controls are controls you evidenced for ISO/IEC 42001:2023. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

2008 2026 701 filings in the busiest month
Artificial Intelligence in 10-K and 10-Q filings, by month. The phrase was already in use in the first month we hold, so this shows how it has moved since rather than when it began.

What this actually means

Why now
122 public companies wrote this into an 8-K in the last seven days, 27% fewer than the seven before. That is not sentiment or a survey. It is a count of companies choosing to put a phrase into a document they are legally accountable for.
Who already cares
131,401 open US roles name this work today, which suggests increased attention to it beyond what any filing says. A job advertisement clears a budget holder and a filing clears legal, so the two answer to different people. We have not measured which moves first, only that both are moving.
What comes into scope
Once the phrase is on the record it maps to obligations within ISO/IEC 42001:2023, NIST AI Risk Management Framework (AI RMF 1.0), EU AI Act. 214 controls behind those, and the difference between asserting them and evidencing them is the whole of the work.
Who is quietly ahead
Anyone already running ISO/IEC 42001:2023 has done 229 of the controls that carry ISO 27001:2022 too. Same evidence, second standard. Most organisations run those as two programmes with two budgets because nobody told them the mapping existed.
Who is exposed
164 companies disclosed this for the first time in the last ninety days, out of 2894 in total. A first mention is a company deciding it can no longer not say it. Whoever has not yet is either genuinely unaffected or has not looked, and nothing here distinguishes the two.

What this obligates

The instruments in our corpus that govern this disclosure, and how many controls sit behind each. This is not a filing count. It is what applies once a company has written the phrase down.

5 frameworks, 214 controls between them.

ISO/IEC 42001:2023 NIST SP 800-53 Rev 5245 shared controlsSOC 2201 shared controlsNIST Cybersecurity Framework 2.0180 shared controlsISO 27002:2022160 shared controlsISO 27001:2022157 shared controlsISO/IEC 38500:2024142 shared controlsPCI DSS 4.0138 shared controlsEU AI Act112 shared controlsNIST AI Risk Management Framewor…68 shared controlsCIS Controls v864 shared controls
ISO/IEC 42001:2023 holds 83 controls. They appear again inside 129 other frameworks in our corpus; the 10 strongest are shown. Thickness and size both carry the number of controls shared, so work done once counts in every framework on this diagram.

What closing it also moves

The same controls appear in other frameworks through mappings held in our corpus. Work done here is already progress there. This is the part that is not in EDGAR and not in any public dataset: it comes from mappings built and verified by hand, control by control.

ISO 27001:2022229
ISO 27002:2022160
ISO/IEC 38500:2024142
ISO 22301:201945
ISO 22000:201836
ISO 9001:201535
ISO 27701:201933
ISO 37301:202131

Counted as controls reached through cross-framework mappings. It measures overlap of work, not compliance with the named framework.

Run as two programmes

308 controls

ISO/IEC 42001:2023 and ISO 27001:2022 scoped separately, each with its own evidence, its own owner and its own budget line. This is how almost everybody does it.

Run once, counted twice

229 already done

229 of ISO 27001:2022's controls are controls you evidenced for ISO/IEC 42001:2023. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

79If you already run ISO/IEC 42001:2023, that is the 79 controls behind this disclosure, already evidenced.
229And ISO 27001:2022 is not a separate programme. 229 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
160And ISO 27002:2022 is not a separate programme. 160 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
142And ISO/IEC 38500:2024 is not a separate programme. 142 of its controls are the same controls. If it is on next year's plan, that part of it is already done.

If that number surprised you, the same measurement across every topic we track:
What changed this week →

This is what it looks like when the same failure is named by standards bodies who never spoke to each other:
How compliance programmes fail →

And the companies that have already written this into a filing:
Artificial Intelligence filers →

Tell me when Artificial Intelligence files something new

One email when a public company newly discloses this, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

Where this comes from

The left half is public record: SEC full-text search over 8-K filings, counted across a 7 day window against the equivalent window before it. You can check every row.

The right half is ours: 723 frameworks and 20,473 controls, 531 of those frameworks verified against their source documents, with the auditor evidence and common failure modes recorded control by control. Controls appear here because their own text names this term.

Cite this

The Art of Service Signals. Artificial Intelligence corporate disclosure activity: 122 filers against 168 in the prior period, in 8-K filings over seven days against the seven before. Accessed 22 November 2026. https://signals.theartofservice.com/t/artificial-intelligence/

Free to use with attribution, no permission needed. The chart downloads as an SVG with the source printed on it. If you cite it we would like to know, but you do not need to ask.

Today's edition · How programmes fail · The obligation index