Schema record
@proseid v2026.07.26 US

CPSC Section 15(b) reporting determination

Determines whether a manufacturer, importer, distributor, or retailer must report product-safety information to CPSC within 24 hours and records the investigation, initial report, and supporting product information.

Compatible with
FormGuided assessmentDeterminationCompliance checklistAPI
Use Schema in a Flow
Publication
Protocol
Proseid_v1.0
Version
v2026.07.26
Applies in
United States
Fields
19
Flow price
$0.20
Publisher fee
None
Standard base $0.20 · exact total is frozen when a Flow is created
Legal history

Time periods

cpsc_15b_20262026-01-01 → continues indefinitely
Current
Controlling sources
Consumer Product Safety Act 15 U.S.C. § 2064(b)
Source ↗
16 CFR Part 1115 §§ 1115.12–1115.14
Source ↗

Schema fields

19 fields
Reason the Section 15(b) report was late
String
—
Opt
The initial report was submitted within 24 hours after reportable information was obtained
Boolean
—
Opt
Business
String
—
Req
Evidence that CPSC is already adequately informed
String
—
Opt
Information supports noncompliance with a voluntary standard relied on by CPSC
Boolean
—
Req
Information supports noncompliance with a CPSC-enforced rule, regulation, standard, or ban
Boolean
—
Req
A focused reportability investigation is still underway
Boolean
—
Req
Tests, complaints, technical records, and corrective-action material are preserved
Boolean
—
Opt
A defect could create a substantial risk of injury to the public
Boolean
—
Req
The product may create an unreasonable risk of serious injury or death
Boolean
—
Req
The business has actual knowledge that CPSC is already adequately informed
Boolean
—
Req
Business role for the product
Select
Choices: Manufacturer, Importer, Distributor, Retailer, Other
Req
The product is within CPSC's jurisdiction
Boolean
—
Req
Calculated reporting position
Select
Choices: Outside section 15b business test, No reportable information identified, Document existing cpsc notice, Cpsc already informed recorded, Complete investigation promptly, Report to cpsc within 24 hours, Document late section 15b report, Complete report supporting record, Section 15b record current
Opt
The initial Section 15(b) report has been submitted
Boolean
—
Opt
Working days spent investigating reportability
Number
—
Opt
Product, model, and date-code identification
String
—
Req
Date the business obtained the potentially reportable information
Date
—
Req
The defect, risk, injuries, complaints, and distribution history are recorded
Boolean
—
Opt

Example payload

JSON 
{
  "responses": {
    "report_delay_reason": "",
    "submitted_within_24_hours_of_reportable_information": false,
    "business_name": "",
    "adequate_information_evidence": "",
    "relied_upon_voluntary_standard_noncompliance": false,
    "cpsc_rule_regulation_standard_or_ban_noncompliance": false,
    "investigation_ongoing": false,
    "supporting_material_preserved": false,
    "defect_could_create_substantial_product_hazard": false,
    "unreasonable_risk_of_serious_injury_or_death": false,
    "actual_knowledge_cpsc_already_adequately_informed": false,
    "supply_chain_role": "",
    "product_within_cpsc_jurisdiction": false,
    "section_15b_report_submitted": false,
    "investigation_working_days": null,
    "product_identification": "",
    "date_reportable_information_obtained": "",
    "hazard_injury_and_distribution_information_complete": false
  },
  "effective_at": "2026-07-26"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL 
curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json
200 OK
{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}
422 Invalid
{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "report_delay_reason",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}
A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions
Loading published versions…

Trust ledger

Crowd → credentialed
P
Provenance
Community publisher (unverified)
@proseid · latest v2026.07.26
Community signal
0
0 votes

No votes yet.

Attestations · by version
0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments
to join the discussion.
Continue exploring
Browse all records →
v2026.07.26

FDA food-facility registration determination

@proseid · 17 fields

 v2026.06.19

EU right-of-withdrawal record

@proseid · 25 fields

 v2026.07.24

EU whistleblowing internal-report deadlines

@proseid · 48 fields

 v1.0.0

OSHA fatality or severe-injury reporting determination

@proseid · 19 fields