The Federal Forty-Day Limit Covers Four Duties, Not Just Rendering a Decision

Where the forty days comes from

A manufacturer-sponsored dispute settlement program attached to a written warranty does not set its own pace. Under Office of the Law Revision Counsel, 15 U.S.C. 2310, subsection (a)(2) instructs the Federal Trade Commission to prescribe rules setting "minimum requirements for any informal dispute settlement procedure which is incorporated into the terms of a written warranty." Subsection (a)(3) supplies the consequence: where a warranty incorporates a qualifying procedure, a consumer "may not commence a civil action (other than a class action) ... unless he initially resorts to such procedure."

The rules the Commission wrote are eCFR, 16 CFR Part 703 — Informal Dispute Settlement Procedures. Part 703 calls the program a "Mechanism," defined in section 703.1(e) as "an informal dispute settlement procedure which is incorporated into the terms of a written warranty to which any provision of Title I of the Act applies."

The number most often repeated about that framework is forty days. The number is real, but the sentence it sits in does not say what a bare "forty days to a decision" summary suggests. Two clauses reverse direction at the end of the sentence, and a third deadline is measured in a unit the regulation never defines.

The forty-day sentence, read to its end

Section 703.5(d) opens this way: "If the dispute has not been settled, the Mechanism shall, as expeditiously as possible but at least within 40 days of notification of the dispute, except as provided in paragraph (e) of this section:". Two features of that opening carry most of the weight.

The first is the starting point. The forty days runs from notification of the dispute — not from the first repair visit, not from the purchase date. The second is the closing clause. Cutting the sentence at "40 days" and dropping "except as provided in paragraph (e) of this section" produces the opposite of what the provision says, because paragraph (e) is where the forty days becomes movable.

What follows the colon is a list of four duties, all of them inside the same forty days. Paragraph (d)(1) requires the Mechanism to "render a fair decision," and the parenthetical inside it adds that "a decision shall state a specified reasonable time for performance." Paragraph (d)(2) requires disclosure of "its decision and the reasons therefor" to the warrantor. Paragraph (d)(3) requires the Mechanism, where the decision would require action by the warrantor, to "determine whether, and to what extent, warrantor will abide by its decision." Paragraph (d)(4) requires disclosure to the consumer of the decision, the reasons, "warrantor's intended actions," and the information described in paragraph (g).

Paragraph (g) is itself three disclosures: that legal remedies "including use of small claims court, may be pursued"; that the decision "is admissible in evidence as provided in section 110(a)(3) of the Act, 15 U.S.C. 2310(a)(3)"; and that the consumer "may obtain, at reasonable cost, copies of all Mechanism records relating to the consumer's dispute."

The four duties that 16 CFR 703.5(d) places inside the forty-day limit A diagram showing notification as day zero, the four duties listed in section 703.5(d), and the two delay grounds in section 703.5(e), the second of which applies only where the consumer has made no attempt to seek redress directly from the warrantor. Diagram 1 — what the forty days actually attaches to Notification of the dispute to the Mechanism treated here as day 0 16 CFR 703.5(d) — "at least within 40 days of notification of the dispute, except as provided in paragraph (e) of this section" (1) Render a fair decision; it "shall state a specified reasonable time for performance" (2) Disclose to the warrantor the decision and the reasons for it (3) Determine whether, and to what extent, the warrantor will abide by that decision (4) Disclose to the consumer the decision, the reasons, intended actions, and the (g) information Paragraph (e) — the only two grounds for going past the forty days (e)(1) delay "due solely to failure of a consumer to provide promptly" name, address, brand name and model number, and the nature of the defect or other complaint (e)(2) "For a 7 day period in those cases where the consumer has made no attempt to seek redress directly from the warrantor."

Diagram 1 — built from the text of 16 CFR 703.5(d) and 703.5(e).

The seven-day stop, and the clause that can end the wait early

Paragraph (e) states that the Mechanism "may delay the performance of its duties under paragraph (d) of this section beyond the 40 day time limit" on two grounds. The first, (e)(1), covers a delay "due solely to failure of a consumer to provide promptly his or her name and address, brand name and model number of the product involved, and a statement as to the nature of the defect or other complaint." That ground carries no fixed number of days. The second, (e)(2), is bounded: "For a 7 day period in those cases where the consumer has made no attempt to seek redress directly from the warrantor." Seven days, not seven working days, and available only where no direct approach to the warrantor was made.

Section 703.5(i) then governs when the resort requirement of 15 U.S.C. 2310(a)(3) is satisfied, and it moves in both directions inside a single provision. The first sentence: the requirement "shall be satisfied 40 days after notification to the Mechanism of the dispute or when the Mechanism completes all of its duties under paragraph (d) of this section, whichever occurs sooner." That trailing phrase is the part most often lost in summary. Where a Mechanism finishes all four duties on day 26, the resort requirement is satisfied on day 26, not day 40.

The second sentence of (i) runs the other way: "Except that, if the Mechanism delays performance of its paragraph (d) of this section duties as allowed by paragraph (e) of this section, the requirement that the consumer initially resort to the Mechanism shall not be satisfied until the period of delay allowed by paragraph (e) of this section has ended." So a seven-day (e)(2) delay does not merely move the decision; it moves the date on which the precondition to a civil action is met.

Ten working days, in a rule that never defines a working day

A decision under (d) is not the last dated step. Section 703.5(h) adds one more: "If the warrantor has agreed to perform any obligations, either as part of a settlement agreed to after notification to the Mechanism of the dispute or as a result of a decision under paragraph (d) of this section, the Mechanism shall ascertain from the consumer within 10 working days of the date for performance whether performance has occurred."

Two things about that sentence resist calendar arithmetic. It counts from "the date for performance," which paragraph (d)(1) leaves to the decision itself as "a specified reasonable time for performance" — the regulation fixes no interval there. And the unit is "working days," which section 703.1 does not define. Its paragraphs (a) through (h) define the Act, consumer product, written warranty, warrantor, Mechanism, members, consumer, and "on the face of the warranty." Neither "working day" nor "business day" appears.

That leaves the conversion to be stated as an assumption rather than read off the page. The figures below rest on three assumptions, all of them chosen and none of them supplied by Part 703. First, a working day is a Monday through Friday that is not a legal public holiday under Office of the Law Revision Counsel, 5 U.S.C. 6103, which lists eleven, from New Year's Day through Christmas Day. Second, the count begins the day after the date for performance, so that date is not itself counted. Third, the observed-holiday shifting practice used by some federal offices when a listed date falls on a weekend is not applied; only the dates named in 6103(a) are removed.

Under weekends-only counting, a ten-working-day window occupies exactly three possible lengths. If the date for performance lands on a Monday through Friday, the tenth working day arrives 14 calendar days later. If it lands on a Saturday, 13 days. On a Sunday, 12 days.

Adding the eleven holidays widens that. Across all 365 possible starting dates in calendar year 2026, the window occupies 12 days for 33 of them, 13 days for 33, 14 days for 166, 15 days for 89, 16 days for 22, 17 days for 19, and 18 days for 3. The longest case, 18 calendar days, arises from a date for performance of 17 December 2026, where Christmas Day and New Year's Day both fall inside the count.

Calendar length of a ten-working-day window across 2026 start dates Bar chart of how many of the 365 possible 2026 start dates produce a ten-working-day window of each calendar length, from 12 to 18 days, under the stated weekend and federal holiday assumptions. Chart — how many calendar days a "10 working days" window takes up, 2026 All 365 possible dates for performance in 2026. Assumptions: Mon–Fri, minus the eleven 5 U.S.C. 6103 holidays, count starts the next day. 0 50 100 150 33 33 166 89 22 19 3 12 days 13 days 14 days 15 days 16 days 17 days 18 days reachable with weekends alone reachable only when a listed holiday falls inside the count Source: holiday list from 5 U.S.C. 6103(a); the distribution is a calculation, not a published figure.

Chart — the seven bar values total 365, one for each possible date for performance in 2026.

The segments laid end to end

Part 703 fixes no total. It fixes segments, and they join only once a decision has named a date for performance. Take notification reaching the Mechanism on Monday, 5 October 2026. Day 40 falls on Saturday, 14 November 2026. Where the (e)(2) ground applies, day 47 falls on Saturday, 21 November 2026, and 703.5(i) places satisfaction of the resort requirement at the end of that delay period rather than at day 40.

Suppose the decision then names a date for performance 30 calendar days out. That 30 is an assumption for the illustration, not a figure from the regulation, which says only "a specified reasonable time for performance." It puts the date for performance at Monday, 21 December 2026, day 77. The 703.5(h) confirmation window then runs ten working days from there: to Monday, 4 January 2027 under weekends-only counting, day 91, or to Wednesday, 6 January 2027 once Christmas Day and New Year's Day are removed, day 93. Two days of difference in the same file, produced by a definitional choice the regulation does not make.

Date axis for the segments in 16 CFR 703.5, using a worked example A timeline from notification at day zero through day 40, day 47, an assumed date for performance at day 77, and a ten-working-day confirmation window ending at day 91 or day 93. Diagram 2 — the segments joined, notification on 5 October 2026 day 0 notification day 40 outer limit of the (d) duties day 47 if the (e)(2) seven-day delay applies day 77 date for performance — set by the decision, not by the regulation (30 days assumed here) day 91 or day 93 703.5(h): ten working days after the date for performance Segment lengths from 16 CFR 703.5(d), (e)(2) and (h). The join between them is an illustration, since the regulation sets no total.

Diagram 2 — the shaded bands are the segments Part 703 fixes; the join between them is not fixed by the regulation.

What the record has to show

Section 703.6 states what a Mechanism keeps, document by document. Paragraph (a) opens: "The Mechanism shall maintain records on each dispute referred to it which shall include:" and then enumerates:

  1. Name, address and telephone number of the consumer.
  2. Name, address, telephone number and contact person of the warrantor.
  3. Brand name and model number of the product involved.
  4. The date of receipt of the dispute and the date of disclosure to the consumer of the decision — the two dates that bound the forty-day count.
  5. All letters or other written documents submitted by either party.
  6. All other evidence collected by the Mechanism relating to the dispute, "including summaries of relevant and material portions of telephone calls and meetings between the Mechanism and any other person."
  7. A summary of any relevant and material information presented by either party at an oral presentation.
  8. The decision of the members, "including information as to date, time and place of meeting, and the identity of members voting; or information on any other resolution."

Retention is fixed in 703.6(f): "The Mechanism shall retain all records specified in paragraphs (a) through (e) of this section for at least 4 years after final disposition of the dispute." Section 703.5(g)(3) is the access side of the same record: copies are obtainable "at reasonable cost."

Section 703.7(a) adds an independent check on the whole file: "The Mechanism shall have an audit conducted at least annually, to determine whether the Mechanism and its implementation are in compliance with this part." Paragraph (c) directs that the audit report "shall be submitted to the Federal Trade Commission, and shall be made available to any person at reasonable cost."

Where this framework does not apply

Part 703 binds a Mechanism, and a Mechanism exists only where a written warranty incorporates one. Where a warranty contains no such procedure, the forty days, the seven days and the ten working days have nothing to attach to. Section 703.5(j) also limits what a completed process produces: the decision is "not legally binding on any person."

State frameworks run on their own numbers and are not measured by 703.5. The California Department of Consumer Affairs, Arbitration Certification Program describes its certified programs in operational terms, stating that "decisions usually come within 40 days after the arbitration program gets your application" and that "arbitrator decisions must be performed by the manufacturer within 30 days of the consumer's acceptance (with few exceptions)." Those are program descriptions from a state agency page carrying no citation to Part 703, not the federal deadlines above.

A separate California route displaces the sequence entirely where a manufacturer elects into it. California Code of Civil Procedure section 871.24 requires notice to the manufacturer at least 30 days before filing, containing "the consumer's name, the accurate Vehicle Identification Number ("VIN") of the motor vehicle, and a brief summary of the repair history and problems with the motor vehicle." The manufacturer has 30 days after receipt to offer restitution or replacement, and performance is to be "completed within 60 days from the date of receipt of the original notice." That trailing phrase fixes the starting point: the sixty days is measured from receipt of the original notice, not from the later offer or acceptance. The section "shall become operative on July 1, 2025." Its reach is set by section 871.20(a), which applies the chapter to an action "brought against a manufacturer who has elected under Section 871.29 to proceed under this chapter."

Deadlines on the outside of that chapter differ again. California Code of Civil Procedure section 871.21 requires a covered action to be "commenced within one year after the expiration of the applicable express warranty," bars any such action more than "six years after the date of original delivery of the motor vehicle," and tolls the period following the 871.24 notice for a span "which time period shall not exceed 60 days." None of those figures interact with 703.5(d).

Numbers to Re-check

  • 40 days from notification of the dispute for the four duties in 703.5(d), "except as provided in paragraph (e)" — eCFR, 16 CFR Part 703
  • 7 days of permitted delay under 703.5(e)(2), where no direct approach to the warrantor was made — same source
  • 10 working days after the date for performance under 703.5(h); "working day" is undefined in 703.1 — same source
  • 4 years of record retention after final disposition under 703.6(f), and an audit "at least annually" under 703.7(a) — same source
  • 11 legal public holidays listed in 5 U.S.C. 6103(a), the basis for the 12-to-18-day spread — 5 U.S.C. 6103
  • 30 days of pre-suit notice and 60 days to complete performance under CCP 871.24, operative 1 July 2025; 1 year and 6 years under CCP 871.21

Effective dates move. The CCP 871.24 operative date of 1 July 2025 post-dates the federal text, which is itself amendable under 15 U.S.C. 2310(a)(2).

This is not legal advice

This post describes what published regulations and statutes say and how their conditions split. It is not legal advice, it does not assess any particular vehicle, warranty or dispute, and it reaches no conclusion about whether any vehicle qualifies for any remedy. Deadlines turn on facts, on the terms of a specific written warranty, and on state law that varies. Anyone weighing a warranty dispute should consult a licensed attorney in the relevant state about their own situation.

Popular posts from this blog

Four Repair Attempts Create a Presumption in California, Not an Automatic Buyback

A California owner whose new vehicle has been in the shop four times for the same defect is often told the car "qualifies as a lemon." The statute says something narrower. Four repair attempts inside a defined window create a rebuttable presumption that a reasonable number of attempts has been made. A presumption is an evidentiary starting position, not an entitlement to a check. Understanding the difference determines what a repair file has to prove, and it explains why two owners with identical repair histories can end up in very different positions. The window comes first, and it is short Civil Code section 1793.22, the Tanner Consumer Protection Act, opens every one of its thresholds with the same clause: the qualifying events must occur within 18 months from delivery to the buyer or 18,000 miles on the odometer, whichever occurs first . Not 18 months and 18,000 miles. Whichever arrives sooner closes the window. A commuter driving 1,600 miles a month reaches 18,000...
Read more

Texas Lemon Law Deadlines Run on 24,000 Miles, Refunds on One Repair Order Date

Two vehicles can carry identical repair histories and land in different places under Texas law, because Chapter 2301 of the Texas Occupations Code measures its qualifying window from the date of original delivery and closes it on whichever arrives first, the calendar or the odometer. Section 2301.605 supplies the presumption — a rebuttable one, not an entitlement. A rule of the Texas Department of Motor Vehicles, 43 TAC §224.260, supplies the arithmetic, and its output turns on one date most owners never write down: the first report of the defect. What follows reads both, with section numbers and effective dates attached. Three Presumption Tests, One Shared Cutoff Section 2301.605(a) establishes the presumption “that a reasonable number of attempts have been undertaken to conform a motor vehicle to an applicable express warranty” if any of three conditions is met. The first, §2301.605(a)(1), is the four-attempt test: “the same nonconformity continu...
Read more

When Florida Counts 30 Days Out of Service, the 15-Day Letter Comes First

Florida’s motor vehicle warranty chapter does not convert a broken car into a refund on the third failed repair. It builds a presumption, and the presumption is what the state’s arbitration board works from. Section 681.104(3) of the Florida Statutes contains two ways to reach it, and they count different things: one counts repair attempts on a single defect, the other counts days the vehicle sat out of service for any number of defects. Each route carries its own written-notice step, sent by registered or express mail and addressed to the manufacturer rather than to the dealership doing the work. As printed in the 2026 Florida Statutes, section 681.104 closes with a history note whose last entry is s. 4, ch. 97-245, so the thresholds in that section have stood since 1997. Two Routes to the Presumption, and They Count Different Things The presumption is stated once and then splits in two. Section 681.104(3) opens: “It is presumed that a reasonable number of attemp...
Read more