Evidence ledger · signal room

AimTechnologyScope

1 Thesis Under the AIM Act Technology Transitions Program (40 CFR Part 84 Subpart B), any person who manufactures or imports a product or specified component in covered RACHP, foam, or aerosol subsectors that uses or is intended to use a regulated HFC (or HFC blend) must file an annual electronic report with EPA within 90 days after year-end — first due March 31, 2026 for calendar-year 2025 data — via CDX/HAWK using EPA’s Excel reporting form. Failure to report or providing inaccurate information is a violation. Verified Most mid-market OEMs and importers already buy environmental reporting help for TRI/Tier II/GHG, but Technology Transitions product reporting is new, SKU-dense, and poorly productized: ERP/BOM data must be mapped to EPA subsectors, charge sizes, foam masses, and aerosol fills; then assembled into the HAWK workbook and attested.

aimacttechnologytransitionsproductreporting

Who this is for

A precise operating owner, not a generic audience.

Responsible buyer

Operations, finance, and compliance owners responsible for AIM Act Technology Transitions Product Reporting Engine (TransitionDesk).

Cost of the gap

1 Thesis Under the AIM Act Technology Transitions Program (40 CFR Part 84 Subpart B), any person who manufactures or imports a product or specified component in covered RACHP, foam, or aerosol subsectors that uses or is intended to use a regulated HFC (or HFC blend) must file an annual electronic report with EPA within 90 days after year-end — first due March 31, 2026 for calendar-year 2025 data — via CDX/HAWK using EPA’s Excel reporting form. Failure to report or providing inaccurate information is a violation.

Outcome

10 The outcome we sell Paid outcome: Accepted Technology Transitions Annual Filing Package — applicability determination support memo, SKU×subsector×HFC matrix, completed EPA TT Excel workbook, recordkeeping index (3-year), specialist QA certificate, and CDX/HAWK submission confirmation (or revision-response package). Acceptance criteria: All required 84.60 fields populated for in-scope SKUs; totals reconcile to source extracts within agreed tolerance; specialist sign-off; HAWK status Submitted (or Revision Requested closed); confirmation artifact delivered.

Decision rule

Proceed only when the source record, service boundary, responsible reviewer, and release criteria can be named before work begins.

Method

The work moves through visible states.

  1. Scope12 AI-vs-human operations pipeline Customer Uploads SKU/ERP/import packs; designates CDX attestor AI Extracts charges, maps candidate subsectors, drafts matrix Rules Completeness, mass totals, sheet routing, schema checks Operator Chases missing evidence; prepares workbook Specialist Approves mappings; signs QA; releases to file Customer / POA CROMERR attestation in CDX/HAWK
  2. CollectCollect only the source records required for the agreed work.
  3. NormalizeNormalize records and preserve file-level provenance.
  4. ValidateRun deterministic completeness and consistency checks.
  5. ResolveRoute missing, conflicting, or unsupported items to an exception queue.
  6. ReviewHave a qualified human review the release candidate.
  7. ReleaseRelease the final pack with an audit trail and correction path.

Engagement

Buy the reviewed outcome, with boundaries written down.

15 Pricing, pricing legality, and unit economics Primary model: Per-entity annual Technology Transitions Filing Package — not hourly. SKU band Package price Notes ≤200 HFC SKUs $3,500–$5,500 Single entity, one sector 201–1,000 $5,500–$8,500 Most mid-market RACHP 1,001–5,000 $8,500–$14,000 Multi-line OEMs Multi-entity / multi-sector +$1,500–$4,000 / entity Shared SKU library discount Year-round SKU change retainer $400–$1,200 / mo Optional after year 1 Pricing legality: Fixed/per-unit compliance reporting fees are standard. No contingency on “penalties avoided.” Do not sell legal opinions or guarantee EPA non-enforcement. Client remains responsible for attestation accuracy.

Release package

  • 10 The outcome we sell Paid outcome: Accepted Technology Transitions Annual Filing Package
  • applicability determination support memo, SKU×subsector×HFC matrix, completed EPA TT Excel workbook, recordkeeping index (3-year), specialist QA certificate, and CDX/HAWK submission confirmation (or revision-response package).
  • Acceptance criteria: All required 84.60 fields populated for in-scope SKUs; totals reconcile to source extracts within agreed tolerance; specialist sign-off; HAWK status Submitted (or Revision Requested closed); confirmation artifact delivered.
  • Customer promise: “Your Technology Transitions annual report is complete, attested-ready, and filed before the deadline

Proof standard

Operating evidence: No verified cycle-time result is published yet. The first result will be calculated from accepted intake through qualified-human release.

Client evidence: No client identity or case narrative is published. A reference may appear only after written permission and factual review.

Volume evidence: No completed-client count is claimed. Counts will be published only after the delivery ledger and provider records reconcile.

Evidence room

Authority comes from traceable sources, not decorative claims.

Open the full canonical blueprint dossier

  • 40 CFR 84.60Source identified in the canonical blueprint; verify currency before client reliance.
  • EPA TT ReportingSource identified in the canonical blueprint; verify currency before client reliance.
  • 88 FR 73098Source identified in the canonical blueprint; verify currency before client reliance.
  • SICCODESource identified in the canonical blueprint; verify currency before client reliance.
  • RMASource identified in the canonical blueprint; verify currency before client reliance.
  • ERA blogSource identified in the canonical blueprint; verify currency before client reliance.
  • EPA — Technology Transitions ProgramSource identified in the canonical blueprint; verify currency before client reliance.
  • EPA — TT Reporting Webinar Slides (Dec 17, 2025)Source identified in the canonical blueprint; verify currency before client reliance.

Service boundary

Automation prepares. A qualified human releases.

AimTechnologyScope is an operational documentation and processing service operated by Your Deputy, Obuke LLC. It is not a law firm and does not provide legal, tax, medical, financial, or other licensed professional advice. Consumer and personal debt matters are not accepted. The client retains its licensed professionals and decision authority. Automation may organize and check records, but a qualified human must review and release every client deliverable.

  • Unsupported facts remain unresolved, never inferred into a client deliverable.
  • Jurisdiction-specific or licensed questions are routed to the client's professional.
  • Every correction retains the source, reviewer, version, and reason for change.

Questions

Know the limits before intake.

Is this legal or professional advice?

No. This is bounded operational documentation and processing support. Licensed judgment remains with the client and its professionals.

Does automation make the final decision?

No. It can organize records, run declared checks, and prepare an exception queue. A qualified human reviews and releases every deliverable.

Is a client portal or CRM already active?

This public site does not claim an active portal integration. Portal access is provisioned only after the relevant backend is configured and independently verified.

What happens when evidence conflicts?

The item is placed in an exception state with its sources and owner. It is not silently resolved or presented as verified.

Fit diagnostic

Send enough context to scope the next conversation—no sensitive files.

Do not submit protected health information, personal financial data, credentials, or confidential client records through this public page.