“Report Within 24 Hours” Is Only One Line in the CPSC Clock
Check a forwarded CPSC Section 15(b) timing claim against the statute, Part 1115 and current CPSC guidance before scoping a product-safety reporting project.
Signals to watch
- A forwarded complaint cluster says the CPSC clock started but does not identify when a responsible employee learned each fact
- A message quotes 24 hours without naming Section 15(b), 16 CFR Part 1115 or the CPSC guidance page
- A seller asks for a reporting decision while product identity, incident pattern and prior corrective action remain unknown
A forwarded “report within 24 hours” message is not enough to start or close a CPSC Section 15(b) analysis. The useful record has four dates: when the company obtained each material fact, when responsible staff could be deemed to know it, when a reasonably expeditious investigation began and when the company reported. Keep the product, firm role and possible statutory trigger beside those dates.
Definition: Section 15(b) of the Consumer Product Safety Act requires specified manufacturers, importers, distributors and retailers to inform the U.S. Consumer Product Safety Commission (CPSC) immediately when they obtain information that reasonably supports certain conclusions about a product. Those conclusions include a failure to comply with an applicable rule or standard, a defect that could create a substantial product hazard, and an unreasonable risk of serious injury or death.
Monday, 09:10 — a deadline appears before the product does
A product-safety service practice lead may monitor authorised Telegram groups used by importers, marketplace operators, retailers, testing laboratories and compliance managers. A composite thread might read:
“Three overheating complaints now. US team says CPSC in 24h.”
“Same charger? checking. One photo looks different.”
This is an illustrative composite, not a real customer, incident or legal conclusion. It does not identify the company receiving the information, its role in the distribution chain, the model, incident dates, injury severity, sales volume, compliance rule, defect analysis, earlier complaints or prior CPSC contact.
Seeing it a day late can cost the service lead the chance to preserve the internal knowledge trail before messages, photographs and product variants are mixed together. Seeing it early does not justify declaring a report due. It just allows the lead to ask for the right dated facts while they are still retrievable.
Monday, 09:30 — read the statute before repeating the slogan
15 U.S.C. § 2064(b) names the covered firms and the information-based reporting triggers. It uses “immediately,” not a universal sentence saying that every first complaint starts an identical 24-hour countdown.
Three objects belong in the intake note:
- Firm: manufacturer, importer, distributor or retailer, plus the entity and people who received the information.
- Product: brand, model, stock-keeping unit, production period and controlled identifiers; “charger” is not enough.
- Possible trigger: noncompliance, a possible defect that could create a substantial product hazard, unreasonable risk of serious injury or death, or another expressly covered circumstance.
Do not combine “complaint exists” and “statutory conclusion is reasonably supported” into one event. The complaint is evidence to assess. The statutory object is the conclusion the available information may reasonably support.
Monday, 11:40 — place the 24 hours beside the ten working days
The CPSC’s current business guidance says firms should report immediately and describes immediate as within 24 hours after reportable information has been obtained. It also says a firm may conduct a reasonably expeditious investigation to evaluate whether reporting is required. That investigation ordinarily should not exceed ten working days unless the firm can demonstrate that a longer period is reasonable.
16 CFR Part 1115 supplies the regulatory context for substantial-product-hazard reports, including knowledge and investigation concepts. The two numbers therefore belong in one chronology, not in competing social posts:
| Clock entry | Record the evidence | Do not assume |
|---|---|---|
| Information received | date, recipient, original complaint, model and attachments | every complaint is reportable information |
| Knowledge review | responsible people, circulated facts and product match | knowledge starts only when counsel finishes a memo |
| Investigation | questions opened, owners, tests and elapsed working days | ten working days is an automatic waiting period |
| Report | filing time, scope and receipt | filing proves a hazard or mandates a recall |
The ten-working-day language is not permission to wait ten days after a reporting conclusion is already supported. Equally, the 24-hour guidance should not be detached from the phrase “after reportable information has been obtained.” Qualified product-safety counsel should apply the current law to the actual record.
Tuesday, 08:15 — rebuild the knowledge trail
Start with source-preserving questions, not a conclusion:
- Which legal entity received which message, test result or return record, and when?
- Which employee or agent received it, and who had responsibility for product safety?
- Do the records concern the same model, batch, component and failure mode?
- What injuries, near misses, property damage or severity information are documented?
- Is there a potentially applicable CPSC rule, ban, standard or voluntary corrective action?
- What analysis has already occurred, and what facts remain missing?
- Has any related information already been sent to the CPSC?
Write unknown beside every field that cannot be supported. A photograph that might show another model remains “model not confirmed”; it must not be silently counted as a fourth incident.
The CPSC recall, SaferProducts.gov and NEISS source-routing article helps when fragments confuse public recall records, consumer reports and injury estimates. The Safety Gate screenshot check shows the same discipline for an EU notification. Neither source decides the US firm’s Section 15(b) duty.
What the service lead can route
A sufficiently bounded opportunity is not “urgent CPSC filing confirmed.” It is a request such as: recover the product and knowledge chronology, compare facts with current Section 15(b) and Part 1115 sources, identify missing investigation records, and prepare material for authorised counsel and the responsible firm.
TOP Prospect can preserve original fragments, source, time, duplicate relationships and review notes from groups a user deliberately connects and is allowed to access. The current matching-target interface saves configuration but does not automatically create candidates. It cannot decide a reporting duty, access internal complaint systems, submit to the CPSC, identify people behind group accounts or contact them. The public Signal workflow describes those boundaries.
Key facts
- Section 15(b) applies to specified manufacturers, importers, distributors and retailers.
- The statute uses information that reasonably supports named conclusions; a bare complaint count is not the statutory text.
- CPSC guidance describes immediate reporting as within 24 hours after reportable information has been obtained.
- The same guidance allows a reasonably expeditious investigation that ordinarily should not exceed ten working days without a demonstrated reason.
- Reporting does not itself establish a substantial product hazard or required corrective action.
- The knowledge date, product identity and firm role are fact-specific and remain unknown in a forwarded fragment.
FAQ
Does CPSC Section 15(b) always require a report within exactly 24 hours of the first complaint?
No. CPSC guidance says a firm should report immediately and describes immediate as within 24 hours after reportable information has been obtained, but the legal analysis still depends on the firm, information, knowledge and statutory trigger.
Can a company investigate before reporting?
CPSC guidance says a firm may conduct a reasonably expeditious investigation and ordinarily should not exceed ten working days unless it can demonstrate that a longer period is reasonable.
Does filing a Section 15(b) report admit that a product is defective?
No. The CPSC states that reporting does not automatically mean the Commission will conclude that a substantial product hazard exists or that corrective action is necessary.
What should a service lead obtain before scoping the work?
Obtain the firm role, exact product and identifiers, dated information trail, incident and injury facts, distribution scope, prior analysis and any previous CPSC communication.
Reviewed by TOP Prospect Editorial Team on 19 August 2026 against 15 U.S.C. § 2064, 16 CFR Part 1115 and current CPSC business guidance. This source check is not legal advice; product identity, knowledge, hazard analysis and filing decisions require authorised records and qualified review.
Frequently asked questions
Does CPSC Section 15(b) always require a report within exactly 24 hours of the first complaint?
No. CPSC guidance says a firm should report immediately and describes immediate as within 24 hours after reportable information has been obtained, but the legal analysis still depends on the firm, information, knowledge and statutory trigger.
Can a company investigate before reporting?
CPSC guidance says a firm may conduct a reasonably expeditious investigation and ordinarily should not exceed ten working days unless it can demonstrate that a longer period is reasonable.
Does filing a Section 15(b) report admit that a product is defective?
No. The CPSC states that reporting does not automatically mean the Commission will conclude that a substantial product hazard exists or that corrective action is necessary.
What should a service lead obtain before scoping the work?
Obtain the firm role, exact product and identifiers, dated information trail, incident and injury facts, distribution scope, prior analysis and any previous CPSC communication.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
