Content Pipeline

MLflow Published Confidence Prompts

The CFPB is Correcting Flaws to Restore Integrity and Utility to the Consumer Complaint System | Consumer Financial Protection Bureau

https://www.consumerfinance.gov/about-us/newsroom/the-cfpb-is-correcting-flaws-to-restore-integrity-and-utility-to-the-consumer-complaint-system/
Success
Service
Specialism
2026-06-25 14:23:59 · ataylor@vixio.com
Meta Id
3268115
Content ID
3276597
GUID
d2489c883f620193dd548b15a3e46e9a

The consumer complaint portal has long been plagued by issues that severely limit its effectiveness in addressing consumers’ complaints and practical utility of its information.

Pipeline Progress

🔄 Pipeline Journey

⏱ 11s total
Queued 14:23:47
+0s
Metadata 14:23:47
+0s
S3 Content 14:23:47
+0s
Extracted 14:23:47
+7s
LLM Gen 14:23:54
+4s
Stored 14:23:58
TITLE: Consumer Financial Protection Bureau Corrects Consumer Complaint Portal System Integrity and Effectiveness BODY: On June 24, 2026, the Consumer Financial Protection Bureau (CFPB) announced multiple concrete actions to address longstanding flaws in its consumer complaint portal system. The CFPB stated that the portal has been plagued by issues severely limiting its effectiveness in addressing consumer complaints and the practical utility of complaint data. Credit reporting complaints represent the largest share of all complaints submitted to the CFPB. Complaint volume increased dramatically, from more than 150,000 credit or consumer reporting complaints in 2019 to more than five million in 2025—an increase of more than 3,700 percent. The CFPB identified multiple factors driving this surge, including credit repair organizations misusing the complaint process, social media influencers encouraging followers to submit complaints, adoption of artificial intelligence tools, and new businesses seeking to boost credit scores by disputing accurate information. The CFPB stated that without addressing these issues, it cannot rely upon complaint portal data as a reliable reflection of actual market conditions or consumer experiences. The CFPB is implementing six key changes. First, it issued a new Company Portal Manual providing clear guidance on closure categories to standardize data across credit reporting agencies (Equifax, Experian, and TransUnion). Second, the CFPB launched two-factor authentication and plans to implement address validation to enhance identity protections. Third, it is aligning the complaint process to statutory obligations under the Fair Credit Reporting Act (FCRA) by requiring consumers to exhaust dispute rights directly with consumer reporting agencies before submitting complaints to the CFPB. Fourth, the CFPB is collaborating with agencies to provide greater specificity on administrative response categories. Fifth, it is developing educational resources highlighting costs and risks of credit repair services. Finally, the CFPB is building application programming interfaces (APIs) to more efficiently share complaint information with companies and is redefining operational categories, distinguishing complaints awaiting action for more than 30 calendar days as backlog from routine work in progress.
  • Scraped:2026-06-25 14:23:59
  • Created:2026-06-25 14:23:58
  • By:ataylor@vixio.com (61)

Prompt Inspector

eu.anthropic.claude-haiku-4-5- t=0.5 6699 in 458 out

Request

System Prompt 3028c
CRITICAL BEHAVIORAL RULES (these override all other instructions):
- Always generate an update. Never refuse, never ask for more information, and never say you cannot produce output.
- If the source content is in a non-English language, translate and summarise it into English.
- If the source content is sparse, administrative, procedural, or lacks expected regulatory elements, extract and present whatever information is available. This includes personnel appointments, cabinet changes, institutional restructures, and any official government action.
- Never include disclaimers or meta-commentary about source quality, translation limitations, or content gaps.
- If you cannot determine a piece of information, simply omit it rather than noting its absence.
- Content scope is broad: generate updates for all government and official publications including regulatory changes, legislation, consultations, decrees, personnel appointments, institutional announcements, administrative decisions, and any other government or authority action. Do not filter by topic relevance.

You are an AI assistant generating Horizon scanning updates for government, regulatory, and institutional content.

GROUND RULES FOR HORIZON SCANNING UPDATES:

Title Requirements:
- The jurisdiction must appear in the update title
- For PC/FS updates, use title case
- Titles must be declarative statements (not questions)
- Keep titles between 10 and 20 words, using the structure: Jurisdiction + Authority + present-tense verb (e.g. "Turkey's Personal Data Protection Authority Publishes Data Protection Guidance")
- Spell out all entities in titles — never use acronyms (e.g. "Florida Office of Financial Regulation" not "Florida OFR")

Body Text Requirements:
- Keep body text between 200 and 250 words; trim verbose paragraphs or expand thin ones to reach this range, but never fabricate details to meet the word count
- Include as many of the following as the source material supports: jurisdiction, authority, brief description of the development or action, relevant dates (effective dates, announcement dates, enforcement dates)
- Include links to relevant legislation where applicable
- On the first mention of any organisation, regulation, or technical term, give the full name followed by the acronym in parentheses (e.g. "Financial Conduct Authority (FCA)"); use the bare acronym only after this definition
- Always format dates as Month Day, Year (e.g. "May 14, 2026"); never use UK format ("14 May 2026") or numeric formats ("5/14/2026")
- Write in active voice; convert "X was Y by Z" constructions to "Z Y-ed X"
- When attributing a statement, use "said" — never "stated"
- Use "chief executive" — never "chief executive officer" — when referring to the role
- Must be factual only - no speculation or sweeping statements
- When information is unavailable, simply omit it rather than noting its absence

Format your response as:
TITLE: [Your declarative title with jurisdiction]

BODY:
[Your factual summary with all required elements]
Few-Shot Examples 16178c
Horizon Scanning Outline.

Purpose of Analyst writing Horizon Scanning Updates

Distil the key points of the development for clients to quickly see what is changing without reading the whole source.
Provide updates to key events from government and regulatory bodies, including consultations, legislation, decrees, appointments, and institutional changes.
Simplify complex updates and sources so that they’re succinct, concise and clear to read.
Consistently structure and write updates in the same format.

Structure of Horizon Scanning Updates

Always think about:
Who (Authority) is publishing/enforcing the content/regulation? 
Where (Jurisdiction)?
What type of document or announcement is it (e.g., consultation, regulation, decree, appointment, institutional change)? What is changing/being informed?
Who is this update applicable to (credit, e-money institutions, etc.)?
Why is this update noteworthy? What is its significance?
When is the update applicable?


Title
Describe what the update is about.
Include the  jurisdiction (where); subject (authority - who); and a verb (doing word such as issues, publishes, launches, etc.- what). 
All titles should be written in present tense. 
Avoid using acronyms
Approx 10 - 20 words


Example
Turkey’s Personal Data Protection Authority Publishes Data Protection Guidance




Paragraph 1
Open with the date of the update (When)
Name the authority that released the update (Who)
Summarise the release (What)
Example
On June 20, 2025, the Securities and Exchange Board of India (SEBI) launched a consultation on guidelines for responsible usage of artificial intelligence (AI) and machine learning (ML) in Indian securities markets.


Paragraph 2
Summarise key points. 
The change/amendment aiming to achieve (what)
What is its objective, why is it happening? Why is it significant? (why)
Who does it impact or concern? (Who)


The aim is to summarise large source documents so the reader doesn’t need to do it themselves. DO NOT just copy the first few sentences of the document.


Example
SEBI aims to produce guidelines providing high-level principles for market participants to establish reasonable procedures and control systems for the supervision and governance of AI/ML applications and tools. To develop this, SEBI created a working group to:
Study Indian and global best practices.
Prepare the guidelines.
Address the concerns and issues arising from AI/ML usage.
SEBI is consulting on the following principles to develop the guidelines:
Model governance: Market participants should have an internal team with adequate skills and experience to monitor and oversee the use of AI/ML-based models.
Investor protection and disclosure: Market participants using AI/ML that impacts their customers should disclose such usage. Relevant use cases include algorithmic trading, asset management, advisory, and support services. The disclosure must include product features, purpose, risks, limitations, and other relevant information.
Testing framework: Market participants should adequately test and continuously monitor AI/ML-based models to validate their results.
Fairness and bias: AI/ML models should not favour or discriminate against any group of clients.
Data privacy and cybersecurity: As AI/ML systems rely on data processing, market participants should maintain a clear policy for data security.





Paragraph 3 
Acts as a “Call To Action”. Provide forward looking context:
What actions need to be taken?
Who needs to take action?
Next steps to the development.
Include any relevant dates (When)
Response dates - should always be provided for consultations
Effective dates - should be used if we know definitively that the act/reg is coming into effect on a specific date, i.e., it has been passed/adopted.



Example
The comment period ends on February 2, 2026, at 11:59pm and responses can be submitted here. The comment response is expected to be published in April 2026. 



References
Should always be included, and should come from a primary source, i.e., an authority, not a news source.

General Style Notes:
200-250 words
Active voice
Authorities and companies referenced as a single entity (“It”, not “they”)
Titles in title case
Internal Vixio vocabulary guide

















Content Style Guide

Spelling should generally be in UK English, except for North American-facing (US/Canada/Caribbean) content.
A

Acronyms - should be spelt out in first instance with acronym in brackets. For example, Financial Conduct Authority (FCA).

Act - when just referring to “the act”, it does not need a capital a.

Active prose - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE))

Advise/advice - advise (verb) - to offer suggestions (for example, I advised them to sell).
             - advice (noun) - give formal suggestions (for example, I gave them advice).

Advisor NOT adviser

Affect - verb - “have an effect on something, make a difference”


Alternate/Alternative 
           - Alternate (adjective) - means every other
           - Alternative (noun) - strictly one out of two
           - Alternative (adjective) - the other of two things.

Although - not to be interchanged with “while” - means “in spite of” NOT “at the same time”.

AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT

Among/while NOT Amongst/whilst
API - application programming interface

Apostrophes - to be used in possessives, i.e. an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s).

Article/Part/Section - should be capitalised when referring to a specific article - e.g., Article 4 of the Gambling Act.

Assure/ensure - not to be confused - assure means “tell someone something positively to dispel doubts”, ensure means “makes certain something will occur”.
B
Between - should always appear with “and” NOT “to” - for example, between this summer and next summer.

Big tech - two words, breaks convention of other tech words

Bills - U.S. bill names should appear without full points and a space between the letters and numbers (i.e. SB 522 NOT SB522 or S.B. 522).

Brackets - square brackets should be used to denote deletions or additions in quotes.

Buy now, pay later - no hyphens 

Bullet points - see Lists
C
Capitalisation - all important words should have a capital in titles (i.e. just not joining words such as and/of/the/a)

Cardrooms not card rooms

Cases - legal cases should appear in italics, with a v for versus.

Casino-resorts NOT casino resorts or resort-casinos

Chief executive NOT chief executive officer

Colons (:) - used between independent clauses when the second clause explains, illustrates or expands on the first (i.e. to introduce lists, quotes)

Commas - to be used in figures to denote thousands to avoid confusion with years (i.e, $2,000 NOT $2000)

Comparisons - compare with (highlighting differences)
             - compare to (highlighting similarities)

Companies/organisations - singular entities (it NOT they)
should be followed by “which/that” rather than “who”
Ltd, not Limited

Complement - to accompany something/add value
Compliment - give praise (complimentary = free)

Compound adjectives - should be hyphenated (sports-betting operators / first-quarter earnings)

Comprise/comprising - should NOT be followed with “of”, as it means to “consist of”

Conjunctions - should appear with a semi-colon before and a comma afterwards (; however, / ; therefore,)

Continually - if something occurs repeatedly/regularly in the same way

Continuously - if something occurs without interruption or gaps

Contractions - don’t, can’t, won’t, etc. to be avoided in copy (except in marketing material and depending on tone)

Contrast - by contrast - when comparing one thing to another
    - in contrast - simply noting a difference

Counsel/Council - counsel  = advice, guidance; council = an advisory group or meeting
Court of Justice of the European Union (CJEU) rather than ECJ
Cryptocurrency - one word, not hyphenated.
​​Crypto-assets - hyphenated
Cybersecurity  - one word, not hyphenated
CTF - counter-terrorism financing - NOT CFT/countering the financing of terrorism
Currencies - if not using common symbols (£, $, €), then three-letter code should be used before the figure (no spaces) - for example, PLN50,000. Full term lower case (eg euro, baht, pound, dollar)
m for million, bn for billion, trn for trillion.
D
Date format - Month, Day, Year (e.g., March 7, 2019)
For Insights & Analysis summary text: can just say “today”, e.g., “Today a bill was passed for…”
For Insights & Analysis body text: dates should always accompany days of the week in brackets, e.g., “On Wednesday (June 8) a bill was passed...”
For NIBs: always use dates rather than days.

Department for Digital, Culture, Media & Sport - ampersand

Directives - for commonly used directives, style is 4th Anti-Money Laundering Directive (4th AMLD), revised Payment Services Directive (PSD2)
      - try to use widely known titles rather than just numbers to ensure the directives are more easily recognised.

DLT - distributed ledger technology
E
Effect - noun - “cause something to happen”.

Em dash (—) - should be used as a conjunction, not a hyphen or en dash (–).

Ensure/assure - not to be confused - ensure means “makes certain something will occur”, assure means “tell someone something positively to dispel doubts”.

esports NOT eSports or e-sports 
Euros - should be denoted with a “€” (CNTRL+ALT+4) NOT “EUR”.
F
fintech NOT FinTech

Footnotes - avoid where possible, if necessary write them into the text or add links.
G
GGR - “gross gaming revenues” 

Government - does not need a capital g.

Governor - should be written out in full, NOT Gov.

Guidance (singular and plural) - does NOT need to be preceded by “a” (Guide/guides, Guideline/guidelines)
H
Headlines - all words should begin with a capital

Horseracing NOT horse racing

Hyphenation - DO: land-based, fixed-odds, cross-border, invitation-only, fast-tracked (if “a fast-tracked application”), match-fixing, year-on-year, up-to-date, whistle-blowers, six-month period, non-fungible tokens, crypto-assets, e-money

            - DON’T: email, blocklist, whitelist, whitelisted, cybersecurity, cryptocurrency, white paper
I
Impact - should be used as a noun - i.e. the new act will have an impact on…
              - verb means “come into forcible contact with something else”.
              - using “affect” as a verb is more accurate.
J
Judgment - legal decision
Judgement - one’s own opinion

Jargon - avoid using confusing terms or tabloidese, e.g. use players rather than punters.

Job titles - should appear in commas after a name - for example, Neil McArthur, Gambling Commission chief executive.
OR before a name with no commas - for example, Gambling Commission chief executive Neil McArthur
DON’T need capitals unless a figure of importance (i.e., Prime Minister, President)

Italics - whole chunks of text from legislation should be italicised; however, short quotes do not need to be. 

Justice Department - U.S. Department of Justice - to appear with caps (as requested by US team).
K
KYC - know your customer
L
Legislature - does not need a capital l.

Less than - NOT to be confused with “fewer than” when referring to a number of something. i.e. fewer than 100 gambling tables.

Licence - noun (UK), i.e. a driver’s licence
License - verb/noun (US)

Lists - bulleted lists should generally begin with a cap and end with a full stop (make sure they are consistent).
M
MONEYVAL NOT Moneyval

More than - to be used instead of “over”. i.e., more than 20 players rather than over 20 players.
N
Names - should appear before job titles in commas - for example, Neil McArthur, Gambling Commission chief executive.

Names - should be written in full in first instance and then the surname used throughout.

Numbers   - 1-10 should be written out (except for percentages and measurements); should always be written out at the start of sentences.

Non-fungible tokens - all lowercase (non-fungible tokens)
O
Offence - noun (UK), i.e. commit an offence
Offense - noun (US)

Organisations/companies - singular entities (it NOT they)
should be followed by “which/that” rather than “who”

Oxford comma - (appears before “and” or “or”) - to be used sparingly and only when necessary to avoid any confusion in a sentence (i.e., where more than one “and/or” appears).

Over - should not be used as a replacement for “more than”.
P

Parliament - does not need a capital p.

Part/Section/Article - should be capitalised when referring to a specific part - e.g., Part 4 of the Gambling Act

Passive voice - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE))

Past/passed - past is a noun/adverb/adjective - “in the past”, “past experience”.
           - passed is the past tense of “to pass” - “the law was passed in government”.

Prepaid, not pre-paid

Percentages - numbers should always be written as figures
percent NOT per cent or %
Figures should appear with a full point between them NOT comma (for example, 5.7 percent NOT 5,7 percent)
Possessives - require an apostrophe and should not be confused with plurals - i.e., an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s).

Prepositions - keep an eye out for missing prepositions - according “to”/ in accordance “with”/ in relation “to” / with regard “to”

Principal - main, most important
Principle - a fundamental source or basis of something

Programme (UK)
Program (US, UK - for computer program, Australian English)
Q
Quotes - speaker should be referenced in the past tense (said NOT says)

Quote marks - double quote marks should be used for speech
           - single quote marks should only be used for titles and within quotes.
(See Quote reference sheet for more information on how to use quotes.)
R
regtech NOT RegTech

Repetition - avoid using words that mean the same thing (“and also” / “include, among others” / VLT terminals / ATM machines)

Racetracks not race tracks
S
Seasons - when referencing a specific season of a year should be treated like a proper noun, i.e. should include a capital - Winter 2018.

Section/Article/Part - should be capitalised when referring to a specific section - e.g., Section 4 of the Gambling Act.

Semi-colons (;) - should be used to link two independent clauses that are closely related; or in lists without bullet points. (Do not overuse - often a full stop and new sentence will be better.)

Sports betting NOT sportsbetting

Sports team names 

Storey (pl. storeys) - level of a building (UK English) (story/stories - US English)
T
That defines, which informs

Third person - “you” - avoid where possible.

Titles - all important words should begin with a capital (i.e. just not joining words such as and/of/the/a)

Tenses - content should generally be written in past tense
 - present tense should be used for something that has just happened and will be continuing into the future.
U
United States abbreviated to U.S. (Americas-focused stories on GC) / US in international content when mentioned in passing or across PC

USA PATRIOT Act - should be kept as such, i.e. with caps, as it’s an acronym for “Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act”)

U.S. Department of Justice - Justice Department (with capitals as requested)
V
Vixio GamblingCompliance / Vixio PaymentsCompliance
Vixio (to be used on its own after first instance)
W
Which informs, that defines

While/among NOT Whilst/amongst

While - not to be interchanged with “although” - means “at the same time” NOT “in spite of”.
X
Y
Year quarters - Q1, Q2, H1, H2, etc. 
Z
Acronyms
 AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT

API - application programming interface

DLT - distributed ledger technology
User Prompt 26574c
Horizon Scanning Outline.

Purpose of Analyst writing Horizon Scanning Updates

Distil the key points of the development for clients to quickly see what is changing without reading the whole source.
Provide updates to key events from government and regulatory bodies, including consultations, legislation, decrees, appointments, and institutional changes.
Simplify complex updates and sources so that they’re succinct, concise and clear to read.
Consistently structure and write updates in the same format.

Structure of Horizon Scanning Updates

Always think about:
Who (Authority) is publishing/enforcing the content/regulation? 
Where (Jurisdiction)?
What type of document or announcement is it (e.g., consultation, regulation, decree, appointment, institutional change)? What is changing/being informed?
Who is this update applicable to (credit, e-money institutions, etc.)?
Why is this update noteworthy? What is its significance?
When is the update applicable?


Title
Describe what the update is about.
Include the  jurisdiction (where); subject (authority - who); and a verb (doing word such as issues, publishes, launches, etc.- what). 
All titles should be written in present tense. 
Avoid using acronyms
Approx 10 - 20 words


Example
Turkey’s Personal Data Protection Authority Publishes Data Protection Guidance




Paragraph 1
Open with the date of the update (When)
Name the authority that released the update (Who)
Summarise the release (What)
Example
On June 20, 2025, the Securities and Exchange Board of India (SEBI) launched a consultation on guidelines for responsible usage of artificial intelligence (AI) and machine learning (ML) in Indian securities markets.


Paragraph 2
Summarise key points. 
The change/amendment aiming to achieve (what)
What is its objective, why is it happening? Why is it significant? (why)
Who does it impact or concern? (Who)


The aim is to summarise large source documents so the reader doesn’t need to do it themselves. DO NOT just copy the first few sentences of the document.


Example
SEBI aims to produce guidelines providing high-level principles for market participants to establish reasonable procedures and control systems for the supervision and governance of AI/ML applications and tools. To develop this, SEBI created a working group to:
Study Indian and global best practices.
Prepare the guidelines.
Address the concerns and issues arising from AI/ML usage.
SEBI is consulting on the following principles to develop the guidelines:
Model governance: Market participants should have an internal team with adequate skills and experience to monitor and oversee the use of AI/ML-based models.
Investor protection and disclosure: Market participants using AI/ML that impacts their customers should disclose such usage. Relevant use cases include algorithmic trading, asset management, advisory, and support services. The disclosure must include product features, purpose, risks, limitations, and other relevant information.
Testing framework: Market participants should adequately test and continuously monitor AI/ML-based models to validate their results.
Fairness and bias: AI/ML models should not favour or discriminate against any group of clients.
Data privacy and cybersecurity: As AI/ML systems rely on data processing, market participants should maintain a clear policy for data security.





Paragraph 3 
Acts as a “Call To Action”. Provide forward looking context:
What actions need to be taken?
Who needs to take action?
Next steps to the development.
Include any relevant dates (When)
Response dates - should always be provided for consultations
Effective dates - should be used if we know definitively that the act/reg is coming into effect on a specific date, i.e., it has been passed/adopted.



Example
The comment period ends on February 2, 2026, at 11:59pm and responses can be submitted here. The comment response is expected to be published in April 2026. 



References
Should always be included, and should come from a primary source, i.e., an authority, not a news source.

General Style Notes:
200-250 words
Active voice
Authorities and companies referenced as a single entity (“It”, not “they”)
Titles in title case
Internal Vixio vocabulary guide

















Content Style Guide

Spelling should generally be in UK English, except for North American-facing (US/Canada/Caribbean) content.
A

Acronyms - should be spelt out in first instance with acronym in brackets. For example, Financial Conduct Authority (FCA).

Act - when just referring to “the act”, it does not need a capital a.

Active prose - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE))

Advise/advice - advise (verb) - to offer suggestions (for example, I advised them to sell).
             - advice (noun) - give formal suggestions (for example, I gave them advice).

Advisor NOT adviser

Affect - verb - “have an effect on something, make a difference”


Alternate/Alternative 
           - Alternate (adjective) - means every other
           - Alternative (noun) - strictly one out of two
           - Alternative (adjective) - the other of two things.

Although - not to be interchanged with “while” - means “in spite of” NOT “at the same time”.

AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT

Among/while NOT Amongst/whilst
API - application programming interface

Apostrophes - to be used in possessives, i.e. an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s).

Article/Part/Section - should be capitalised when referring to a specific article - e.g., Article 4 of the Gambling Act.

Assure/ensure - not to be confused - assure means “tell someone something positively to dispel doubts”, ensure means “makes certain something will occur”.
B
Between - should always appear with “and” NOT “to” - for example, between this summer and next summer.

Big tech - two words, breaks convention of other tech words

Bills - U.S. bill names should appear without full points and a space between the letters and numbers (i.e. SB 522 NOT SB522 or S.B. 522).

Brackets - square brackets should be used to denote deletions or additions in quotes.

Buy now, pay later - no hyphens 

Bullet points - see Lists
C
Capitalisation - all important words should have a capital in titles (i.e. just not joining words such as and/of/the/a)

Cardrooms not card rooms

Cases - legal cases should appear in italics, with a v for versus.

Casino-resorts NOT casino resorts or resort-casinos

Chief executive NOT chief executive officer

Colons (:) - used between independent clauses when the second clause explains, illustrates or expands on the first (i.e. to introduce lists, quotes)

Commas - to be used in figures to denote thousands to avoid confusion with years (i.e, $2,000 NOT $2000)

Comparisons - compare with (highlighting differences)
             - compare to (highlighting similarities)

Companies/organisations - singular entities (it NOT they)
should be followed by “which/that” rather than “who”
Ltd, not Limited

Complement - to accompany something/add value
Compliment - give praise (complimentary = free)

Compound adjectives - should be hyphenated (sports-betting operators / first-quarter earnings)

Comprise/comprising - should NOT be followed with “of”, as it means to “consist of”

Conjunctions - should appear with a semi-colon before and a comma afterwards (; however, / ; therefore,)

Continually - if something occurs repeatedly/regularly in the same way

Continuously - if something occurs without interruption or gaps

Contractions - don’t, can’t, won’t, etc. to be avoided in copy (except in marketing material and depending on tone)

Contrast - by contrast - when comparing one thing to another
    - in contrast - simply noting a difference

Counsel/Council - counsel  = advice, guidance; council = an advisory group or meeting
Court of Justice of the European Union (CJEU) rather than ECJ
Cryptocurrency - one word, not hyphenated.
​​Crypto-assets - hyphenated
Cybersecurity  - one word, not hyphenated
CTF - counter-terrorism financing - NOT CFT/countering the financing of terrorism
Currencies - if not using common symbols (£, $, €), then three-letter code should be used before the figure (no spaces) - for example, PLN50,000. Full term lower case (eg euro, baht, pound, dollar)
m for million, bn for billion, trn for trillion.
D
Date format - Month, Day, Year (e.g., March 7, 2019)
For Insights & Analysis summary text: can just say “today”, e.g., “Today a bill was passed for…”
For Insights & Analysis body text: dates should always accompany days of the week in brackets, e.g., “On Wednesday (June 8) a bill was passed...”
For NIBs: always use dates rather than days.

Department for Digital, Culture, Media & Sport - ampersand

Directives - for commonly used directives, style is 4th Anti-Money Laundering Directive (4th AMLD), revised Payment Services Directive (PSD2)
      - try to use widely known titles rather than just numbers to ensure the directives are more easily recognised.

DLT - distributed ledger technology
E
Effect - noun - “cause something to happen”.

Em dash (—) - should be used as a conjunction, not a hyphen or en dash (–).

Ensure/assure - not to be confused - ensure means “makes certain something will occur”, assure means “tell someone something positively to dispel doubts”.

esports NOT eSports or e-sports 
Euros - should be denoted with a “€” (CNTRL+ALT+4) NOT “EUR”.
F
fintech NOT FinTech

Footnotes - avoid where possible, if necessary write them into the text or add links.
G
GGR - “gross gaming revenues” 

Government - does not need a capital g.

Governor - should be written out in full, NOT Gov.

Guidance (singular and plural) - does NOT need to be preceded by “a” (Guide/guides, Guideline/guidelines)
H
Headlines - all words should begin with a capital

Horseracing NOT horse racing

Hyphenation - DO: land-based, fixed-odds, cross-border, invitation-only, fast-tracked (if “a fast-tracked application”), match-fixing, year-on-year, up-to-date, whistle-blowers, six-month period, non-fungible tokens, crypto-assets, e-money

            - DON’T: email, blocklist, whitelist, whitelisted, cybersecurity, cryptocurrency, white paper
I
Impact - should be used as a noun - i.e. the new act will have an impact on…
              - verb means “come into forcible contact with something else”.
              - using “affect” as a verb is more accurate.
J
Judgment - legal decision
Judgement - one’s own opinion

Jargon - avoid using confusing terms or tabloidese, e.g. use players rather than punters.

Job titles - should appear in commas after a name - for example, Neil McArthur, Gambling Commission chief executive.
OR before a name with no commas - for example, Gambling Commission chief executive Neil McArthur
DON’T need capitals unless a figure of importance (i.e., Prime Minister, President)

Italics - whole chunks of text from legislation should be italicised; however, short quotes do not need to be. 

Justice Department - U.S. Department of Justice - to appear with caps (as requested by US team).
K
KYC - know your customer
L
Legislature - does not need a capital l.

Less than - NOT to be confused with “fewer than” when referring to a number of something. i.e. fewer than 100 gambling tables.

Licence - noun (UK), i.e. a driver’s licence
License - verb/noun (US)

Lists - bulleted lists should generally begin with a cap and end with a full stop (make sure they are consistent).
M
MONEYVAL NOT Moneyval

More than - to be used instead of “over”. i.e., more than 20 players rather than over 20 players.
N
Names - should appear before job titles in commas - for example, Neil McArthur, Gambling Commission chief executive.

Names - should be written in full in first instance and then the surname used throughout.

Numbers   - 1-10 should be written out (except for percentages and measurements); should always be written out at the start of sentences.

Non-fungible tokens - all lowercase (non-fungible tokens)
O
Offence - noun (UK), i.e. commit an offence
Offense - noun (US)

Organisations/companies - singular entities (it NOT they)
should be followed by “which/that” rather than “who”

Oxford comma - (appears before “and” or “or”) - to be used sparingly and only when necessary to avoid any confusion in a sentence (i.e., where more than one “and/or” appears).

Over - should not be used as a replacement for “more than”.
P

Parliament - does not need a capital p.

Part/Section/Article - should be capitalised when referring to a specific part - e.g., Part 4 of the Gambling Act

Passive voice - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE))

Past/passed - past is a noun/adverb/adjective - “in the past”, “past experience”.
           - passed is the past tense of “to pass” - “the law was passed in government”.

Prepaid, not pre-paid

Percentages - numbers should always be written as figures
percent NOT per cent or %
Figures should appear with a full point between them NOT comma (for example, 5.7 percent NOT 5,7 percent)
Possessives - require an apostrophe and should not be confused with plurals - i.e., an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s).

Prepositions - keep an eye out for missing prepositions - according “to”/ in accordance “with”/ in relation “to” / with regard “to”

Principal - main, most important
Principle - a fundamental source or basis of something

Programme (UK)
Program (US, UK - for computer program, Australian English)
Q
Quotes - speaker should be referenced in the past tense (said NOT says)

Quote marks - double quote marks should be used for speech
           - single quote marks should only be used for titles and within quotes.
(See Quote reference sheet for more information on how to use quotes.)
R
regtech NOT RegTech

Repetition - avoid using words that mean the same thing (“and also” / “include, among others” / VLT terminals / ATM machines)

Racetracks not race tracks
S
Seasons - when referencing a specific season of a year should be treated like a proper noun, i.e. should include a capital - Winter 2018.

Section/Article/Part - should be capitalised when referring to a specific section - e.g., Section 4 of the Gambling Act.

Semi-colons (;) - should be used to link two independent clauses that are closely related; or in lists without bullet points. (Do not overuse - often a full stop and new sentence will be better.)

Sports betting NOT sportsbetting

Sports team names 

Storey (pl. storeys) - level of a building (UK English) (story/stories - US English)
T
That defines, which informs

Third person - “you” - avoid where possible.

Titles - all important words should begin with a capital (i.e. just not joining words such as and/of/the/a)

Tenses - content should generally be written in past tense
 - present tense should be used for something that has just happened and will be continuing into the future.
U
United States abbreviated to U.S. (Americas-focused stories on GC) / US in international content when mentioned in passing or across PC

USA PATRIOT Act - should be kept as such, i.e. with caps, as it’s an acronym for “Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act”)

U.S. Department of Justice - Justice Department (with capitals as requested)
V
Vixio GamblingCompliance / Vixio PaymentsCompliance
Vixio (to be used on its own after first instance)
W
Which informs, that defines

While/among NOT Whilst/amongst

While - not to be interchanged with “although” - means “at the same time” NOT “in spite of”.
X
Y
Year quarters - Q1, Q2, H1, H2, etc. 
Z
Acronyms
 AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT

API - application programming interface

DLT - distributed ledger technology


---

ARTICLE METADATA (use as ground truth — do not override with guesses):
- Jurisdiction: US Track 1
- Authority: Consumer Financial Protection Bureau
- Domain: Financial Services

Now, given the above instructions and style guide, please generate a horizon scanning
update based on the following webpage content. Generate the update regardless of the
source language, content type, or level of detail available — this includes administrative
decrees, personnel appointments, institutional changes, and any other official content.
Use whatever information is present.

The CFPB is Correcting Flaws to Restore Integrity and Utility to the Consumer Complaint System | Consumer Financial Protection Bureau Skip to main content WASHINGTON, D.C. -- The consumer complaint portal has long been plagued by issues that severely limit its effectiveness in addressing consumers’ complaints and practical utility of its information. Recently, CFPB has taken multiple concrete actions to address these issues and is continuing its work, including with Credit Reporting Agencies, to increase effectiveness of the process, while aligning it with the statutory authorities: Revising its Portal Manual to ensure that CRAs follow a standardized process in addressing complaints Enhancing identity protections Aligning the complaint process to statutory obligations Focusing resources on complaints that warrant a substantive response Educating consumers about how to address errors on their credit reports Increasing the efficiency of the complaint process Read more here: The consumer complaint portal has long been plagued by issues that severely limit its effectiveness in addressing consumers’ complaints and practical utility of its information. Recently, the CFPB has taken multiple concrete actions, including with Credit Reporting Agencies, to address these issues and is continuing its work to increase effectiveness of the process, while aligning it with the statutory authorities. First, users abusing the process stress the systems of the Bureau and companies and impede timely processing of legitimate complaints. This harms consumers and wastes resources. Credit reporting complaint volume increased dramatically in recent years. In 2019, the Bureau received more than 150,000 credit or consumer reporting complaints. In 2025, that number grew to more than five million—an increase of more than 3,700%. Amidst this record complaint volume, the nationwide consumer reporting agencies (NCRAs)—Equifax, Experian, and TransUnion—reported making more updates and deletions to inaccurate tradelines than in prior years. In 2024, the NCRAs closed more than 1.3 million complaints with non-monetary relief. In 2025, that number grew to 2.1 million. The increase is driven by many—sometimes, overlapping—factors: credit repair organizations and credit clinics misusing the Bureau’s complaint process as a tool of their business, social media influencers with questionable expertise encouraging followers to submit complaints, adoption of new technologies (e.g., “AI tools”) that may act as an individual’s agent, and the emergence of new businesses that seek to boost credit scores by disputing accurate information on consumers’ reports. Second, the NCRAs have not been uniformly reporting how they respond to the growing number of consumer complaints. The Bureau has been collaborating with the NCRAs to better understand their complaint handling practices, and to ensure consumers receive timely, complete, and accurate responses to their credit reporting complaints. Credit reporting complaints represent the largest share of all complaints submitted to the Bureau. Without addressing these issues, the CFPB cannot rely upon the consumer complaint portal data as a reliable reflection of actual market conditions or actual consumer experiences. The Bureau is collaborating with NCRAs and other companies to implement the following changes to address these longstanding issues: Increasing clarity of closure definitions to promote consistency Through its outreach to CRAs and other companies, the Bureau learned that companies operationalized the closure definitions differently with some companies using different definitions to categorize a complaint “Closed with non-monetary relief.” What actions are we taking? The Bureau issued a new Company Portal Manual that provides clear information on how companies should use the various substantive and administrative response closure categories and answers to frequently asked questions. That will allow for standardization of data on responses across CRAs. Once the data can be standardized, the Bureau will continue to work with CRAs to ensure data are consistent across them and response rates are appropriately high. Enhancing identity protections Security is top of mind for the Bureau’s complaint system. Likewise, companies need reassurance that they are responding to their customer and safeguarding their privacy. What actions are we taking? The Bureau launched two-factor authentication, requiring users who create online accounts to verify both their email address and mobile phone number. It also added clarifying text and new relationship categories to emphasize that third parties must disclose their involvement in the complaint process. The CFPB plans to implement address validation at the complaint submission step to ensure companies can act on high-quality information. The Bureau is also working on user support materials so adult children of aging parents, spouses of servicemembers, and other authorized representatives know how to submit complaints. Aligning the complaint process to statutory obligations The Fair Credit Reporting Act (FCRA) creates a framework in which individuals dispute inaccurate or incomplete information with consumer reporting agencies directly. Some credit repair clinics and individuals are using the Bureau’s complaint process to circumvent this statutory process. What actions are we taking? The Bureau is aligning its complaint process to its statutory obligations. It added a notice, emphasizing that consumers must first exhaust their dispute rights directly with consumer reporting agencies before coming to the Bureau. The Bureau is working with the NCRAs to understand what information can help them more readily identify and review prior disputes. The Bureau is also exploring adding an additional administrative response option so NCRAs can efficiently return complaints where the consumer has not exhausted their FCRA dispute obligations. These changes will help the NCRAs focus their resources on complaints that warrant review as required by FCRA. Focusing resources on complaints that warrant a substantive response When companies have reason to not respond to a complaint—such as one submitted by an unauthorized third party—the Bureau gives companies the ability to return complaints with an administrative response. Through its outreach, the Bureau learned that companies operationalized use of administrative response options differently. What actions are we talking? The Bureau is collaborating with NCRAs and other companies to provide greater specificity of when to use existing administrative response categories. The Bureau is also exploring additional administrative response categories, such as when a user appears to be abusing the complaint process. The Bureau is exploring additional steps to support its efforts to monitor and safeguard the complaint system from users who attempt to abuse the complaint process. Educating consumers about how to address errors on their credit reports Some credit repair companies make claims that are too good to be true, such as guaranteeing a specific increase in credit scores or removing negative (but accurate) information. Social media financial influencers and new AI tools are also quickly changing the landscape. What actions are we taking? The Bureau continues its work to develop and provide high-quality educational resources and tools for consumers, including materials highlighting the costs and risks of credit repair and how to spot fraud and scams. Increasing the efficiency of the complaint process The Bureau is committed to leveraging technology to deliver faster, more secure services. The complaint process is focused on being a secure, digital-first service for all Americans. What actions are we taking? The Bureau is building technology, like Application Programming Interfaces (APIs), to more efficiently share complaint information with companies. It will also be using software, like an address validation tool, to provide companies with high-quality information and reassurance that they are responding to their customer. Defining operational categories to manage complaints effectively While many complaints are sent to companies for response or referred to other agencies automatically, some complaints require manual review. In discussing complaints, those received seconds or minutes ago but not yet sent, referred, or otherwise closed have been viewed the same as those received weeks or months ago. These complaints collectively have been referred to as the complaint “backlog” and have never been distinguished. What actions are we taking? With record volume, the Bureau took a fresh look at which complaints should constitute a complaint backlog going forward. Most complaints are sent to companies or referred to another agency the same day they are received. For those that require manual review, the Bureau is distinguishing routine work from complaints in the backlog to help ensure that the Bureau can prioritize its work effectively and provide timely responses to consumers. For operational purposes, the backlog will include complaints awaiting action for more than 30 calendar days from the date of submission, whereas the remainder of complaints will be considered routine, work in progress. About us The Consumer Financial Protection Bureau is a 21st century agency that implements and enforces Federal consumer financial law and ensures that markets for consumer financial products are fair, transparent, and competitive. If you want to republish the article or have questions about the content, please contact the press office. Go to press resources page Page last modified Jun. 24, 2026 @ 12:46 PM EDT Subscribe to our RSS feed to get the latest content in your reader. Subscribe to RSS

Response (Summary)

TITLE: Consumer Financial Protection Bureau Corrects Consumer Complaint Portal System Integrity and Effectiveness

BODY:

On June 24, 2026, the Consumer Financial Protection Bureau (CFPB) announced multiple concrete actions to address longstanding flaws in its consumer complaint portal system. The CFPB stated that the portal has been plagued by issues severely limiting its effectiveness in addressing consumer complaints and the practical utility of complaint data.

Credit reporting complaints represent the largest share of all complaints submitted to the CFPB. Complaint volume increased dramatically, from more than 150,000 credit or consumer reporting complaints in 2019 to more than five million in 2025—an increase of more than 3,700 percent. The CFPB identified multiple factors driving this surge, including credit repair organizations misusing the complaint process, social media influencers encouraging followers to submit complaints, adoption of artificial intelligence tools, and new businesses seeking to boost credit scores by disputing accurate information. The CFPB stated that without addressing these issues, it cannot rely upon complaint portal data as a reliable reflection of actual market conditions or consumer experiences.

The CFPB is implementing six key changes. First, it issued a new Company Portal Manual providing clear guidance on closure categories to standardize data across credit reporting agencies (Equifax, Experian, and TransUnion). Second, the CFPB launched two-factor authentication and plans to implement address validation to enhance identity protections. Third, it is aligning the complaint process to statutory obligations under the Fair Credit Reporting Act (FCRA) by requiring consumers to exhaust dispute rights directly with consumer reporting agencies before submitting complaints to the CFPB. Fourth, the CFPB is collaborating with agencies to provide greater specificity on administrative response categories. Fifth, it is developing educational resources highlighting costs and risks of credit repair services. Finally, the CFPB is building application programming interfaces (APIs) to more efficiently share complaint information with companies and is redefining operational categories, distinguishing complaints awaiting action for more than 30 calendar days as backlog from routine work in progress.