In this case, we deal with the difficult question of when an employer can moot a purported collective action under the Fair Labor Standards Act (“FLSA”), 29 U.S.C. §§ 201-219, by paying an employee’s claim in full. In particular, we must consider the complex interplay between Federal Rule of Civil Procedure 68, which stipulates how a defendant can make an offer of judgment that would fully satisfy a plaintiffs claim, and the FLSA’s provision for collective actions under § 216(b). Because Plaintiff-Appellee Courtney Sandoz (“San-doz”) filed a motion to certify her collective action that, if timely and if granted, will relate back to when she initiated her lawsuit against Defendanb-Appellant Cingular Wireless (“Cingular”), 1 we vacate the district court’s judgment and remand for consideration of the timeliness, and, if necessary, the merits of Sandoz’s certification motion.
I. FACTUAL AND PROCEDURAL BACKGROUND
Sandoz worked for Cingular as a part-time retail sales consultant in Lafayette, Louisiana, from October 10, 2004, until she voluntarily resigned on October 5, 2005. On April 23, 2007, Sandoz brought suit against Cingular in Louisiana state court, alleging that the way in which Cingular paid its part-time employees for excess time worked violated the minimum wage provisions of the FLSA. See 29 U.S.C. § 206. In essence, Sandoz argues that Cingular’s accounting system resulted in paychecks that paid her less than the minimum wage for all of the hours she worked in certain weeks. She styled her case as an opt-in collective action under § 216(b) of the FLSA. See id. § 216(b). Sandoz served Cingular with the state court petition on July 27, 2007. On August 13, 2007, Cingular removed the case to the district court. Cingular filed its answer to San-doz’s petition on August 20, 2007.
On September 6, 2007, twenty-four days after removing the case to the district court and a little over a month after receiving Sandoz’s petition, Cingular made Sandoz an offer of judgment under Federal Rule of Civil Procedure 68 for $1,000, plus her reasonable attorneys’ fees. San-doz failed to accept the offer of judgment within ten days. See Fed.R.Civ.P. 68(a) (“If, within 10 days after being served, the opposing party serves written notice accepting the offer, either party may then file the offer and notice of acceptance, plus proof of service. The clerk must then enter judgment.”). Instead, Sandoz filed a motion to strike the reference to the offer of judgment. Cingular filed a motion to dismiss for lack of subject matter jurisdiction, asserting that the offer of judgment fully satisfied Sandoz’s claims. The district court denied Sandoz’s motion to strike and denied Cingular’s motion to dismiss. The court rejected Cingular’s argument that a make-whole offer to a named plaintiff alone in a collective action under *915 the FLSA divests the court of subject matter jurisdiction. However, the court granted Cingular’s motion to allow an interlocutory appeal pursuant to 28 U.S.C. § 1292(b). On June 5, 2008, about three weeks after the district court denied Cin-gular’s motion to dismiss, Sandoz filed a motion for certification of her collective action. This court granted Cingular’s motion to stay the district court’s proceedings and expedited the appeal.
II. JURISDICTION AND STANDARD OF REVIEW
This court has jurisdiction pursuant to 28 U.S.C. § 1292(b), as the district court certified for interlocutory appeal its order denying Cingular’s motion to dismiss. We review de novo a district court’s ruling on a motion to dismiss for lack of subject matter jurisdiction.
See LeClerc v. Webb,
III. DISCUSSION
A. Mootness
Under Article III of the U.S. Constitution, a federal court may adjudicate only “cases” or “controversies.” U.S. Const. art. III, § 2;
see Warth v. Seldin,
The issue in this appeal is whether a FLSA claim becomes moot when the purported representative of a collective action receives an offer that would satisfy his or her individual claim and no other plaintiffs have opted in to the collective action. Therefore, we must determine whether Sandoz represents only herself in this claim or if she also represents other similarly-situated employees in a FLSA collective action.
Section 216(b) of the FLSA provides, [a]ny employer who violates the provisions of [the FLSA] shall be liable to the employee or employees affected in the amount of their unpaid minimum wages, or their unpaid overtime compensation, as the case may be, and in an additional equal amount as liquidated damages .... An action to recover the liability prescribed in [this section] may be maintained against any employer (including a public agency) in any Federal or State court of competent jurisdiction by any one or more employees for and in behalf of himself or themselves and other employees similarly situated. No employee shall be a party plaintiff to any such action unless he gives his consent in writing to become such a party and such consent is filed in the court in which such action is brought.
29 U.S.C. § 216(b). Thus, the FLSA allows an employee to bring a claim on behalf of other similarly-situated employees, but the other employees do not become plaintiffs in the action unless and until they consent in writing.
2
Id.; see
*916
Cameron-Grant v. Maxim Healthcare Servs., Inc.,
The Supreme Court has explained the history behind the opt-in provision of the FLSA:
In 1938, Congress gave employees and their “representatives” the right to bring actions to recover amounts due under the FLSA. No written consent requirement of joinder was specified by the statute. In enacting the Portal-to-Portal Act of 1947, Congress made certain changes in these procedures. In part responding to excessive litigation spawned by plaintiffs lacking a personal interest in the outcome, the representative action by plaintiffs not themselves possessing claims was abolished, and the requirement that an employee file a written consent was added. See 93 Cong. Rec. 538, 2182 (1947) (remarks of Sen. Donnell). The relevant amendment was for the purpose of limiting private FLSA plaintiffs to employees who asserted claims in their own right and freeing employers of the burden of representative actions.
Hoffmann-La Roche Inc. v. Sperling,
In
LaChapelle v. Owens-Illinois, Inc.,
There is a fundamental, irreconcilable difference between the class action described by Rule 23 and that provided for by FLSA [§ 216(b)]. In a Rule 23 proceeding a class is described; if the action is maintainable as a class action, each person within the description is considered to be a class member and, as such, is bound by judgment, whether favorable or unfavorable, unless he has “opted out” of the suit. Under [§ 216(b)] of FLSA, on the other hand, no person can become a party plaintiff and no person will be bound by or may benefit from judgment unless he has affirmatively “opted into” the class; that is, given his written, filed consent.
Id.
at 288. The court continued, “Rule 23(c) provides for ‘opt out’ class actions. FLSA [§ 216(b)] allows as class members only those who ‘opt in.’ These two types of class actions are mutually exclusive and irreconcilable.”
Id.
at 289. We concluded that because the Age Discrimination in Employment Act adopted § 216(b) of the FLSA, a plaintiff could maintain only “opt in” type class actions for age discrimination cases.
Id.
Given this language, the rules and policies underlying “opt out” class actions might not apply when construing the FLSA, as the statute treats the representative plaintiff and opt-in plaintiffs differently. For example, in a FLSA collective action, the statute of limitations for a named plaintiff runs from the date that
*917
the plaintiff files the complaint, while the limitations period for an opt-in plaintiff runs from the opt-in date.
See Atkins v. Gen. Motors Corp.,
The Eleventh Circuit is the only other circuit that has addressed the same type of scenario currently before us. In
Camerortr-Grant,
the court considered whether a named FLSA plaintiff, “whose personal claims are settled and now moot, may appeal the district court’s order denying his motion to notify other potential plaintiffs of this FLSA action.”
Several district courts also have held that a named plaintiff in a FLSA collective action did not represent the interests of similarly-situated employees who had not yet opted in. The facts of
Rollins v. Systems Integration, Inc.,
No. 4:05-CV-408,
The district court here concluded that Cingular’s Rule 68 offer of judgment did not moot Sandoz’s claims, but it rested its decision on cases involving Rule 23 class actions, not collective actions under the FLSA. For example, in
U.S. Parole Commission v. Geraghty,
Here, the district court held that based on
Geraghty
and
Roper,
allowing a defendant to “pick off’ the representative plaintiff in a potential FLSA collective action by making an offer of judgment would frustrate the objective of the statute. The district court also cited
Hoffmann-La-Roche, Inc.,
Generally speaking, we agree with the district court’s concerns. A ruling that
*919
defendant
always
can “pick off’ a named plaintiffs FLSA claims before the plaintiff a chance to certify the collective action obviate one purpose of the collective action provision.
See Prickett v. DeKalb County,
B. Relation Back
Sandoz argues, however, that allowing a defendant to moot a collective action in this manner would violate the policies behind the FLSA because a plaintiff never would be able to certify a collective action. We agree that the mootness principles discussed above would provide an incentive for employers to use Rule 68 as a sword, “picking off’ representative plaintiffs and avoiding ever having to face a collective action. Conceptually, this would seem to be the logical result of the interplay between FLSA § 216(b) and Rule 68. Luckily, however, the relation back doctrine provides a mechanism to avoid this anomaly-
In Sosna v. Iowa, the Supreme Court stated,
[tjhere may be cases in which the controversy involving the named plaintiffs is that it becomes moot as to them before the district court can reasonably expected to rule on a certification motion. In such instances, whether the certification can be said to “relate back” the filing of the complaint may depend upon the circumstances of the particular case and especially the reality of claim that otherwise the issue would evade review.
[t]o deny the right to appeal simply because the defendant has sought to “buy off’ the individual private claims of the named plaintiffs would be contrary to sound judicial administration. Requiring multiple plaintiffs to bring separate actions, which effectively could be “picked off’ by a defendant’s tender of judgment before an affirmative ruling on class certification could be obtained, obviously would frustrate the objectives of class actions; moreover it would invite *920 waste of judicial resources by stimulating successive suits brought by others claiming aggrievement.
This court also has previously discussed the dangers of allowing a defendant to “pick off’ class representatives by making an offer of judgment to the named plaintiff:
By tendering to the named plaintiffs the full amount of their personal claims each time suit is brought as a class action, the defendants can in each successive case moot the named plaintiffs’ claims before a decision on certification is reached. A series of individual suits, each brought by a new named plaintiff, could individually be “picked off’ before class certification .... The fact remains that in those cases in which it is financially feasible to pay off successive named plaintiffs, the defendants would have the option to preclude a viable class action from ever reaching the certification stage.
Zeidman v. J. Ray McDermott & Co.,
The Third Circuit applied these principles to conclude that “[ajbsent undue delay in filing a motion for class certification ... where a defendant makes a Rule 68 offer an individual claim that has the effect of mooting possible class relief asserted in the complaint, the appropriate course is to relate the certification motion back to the filing of the class complaint.”
Weiss v. Regal Collections,
Although these cases arose in the Rule 23 class action context, the differences between class actions and FLSA § 216(b) collective actions do not compel a different result regarding whether a certification motion can “relate back” to the filing of the complaint. The status of a case as being an “opt in” or “opt out” class action has no bearing on whether a defendant can unilaterally moot a plaintiffs case through a Rule 68 offer of judgment. Although the differences between Rule 23 class actions and FLSA § 216(b) collective actions alter the conceptual mootness inquiry, each type of action would be rendered a nullity if defendants could simply moot the claims as soon as the representative plaintiff files suit. Thus, the policies behind applying the “relation back” principle for Rule 23 class actions apply with equal force to FLSA § 216(b) collective actions.
Cf. Rubery v. Buth-Na-Bodhaige, Inc.,
The proper course, therefore, is to hold that when a FLSA plaintiff files a timely motion for certification of a collective action, that motion relates back to the *921 the plaintiff filed the initial complaint, particularly when one of the defendant’s actions is to make a Rule 68 offer of judgment. If the court ultimately grants motion to certify, then the Rule 68 offer to the individual plaintiff would not fully satisfy the claims of everyone in the collective action; if the court denies the motion to certify, then the Rule 68 offer of judgment renders the individual plaintiffs claims moot. 5 Thus, although the district court was correct to suggest that Cingu-lar’s motion to dismiss was premature, it failed to give the proper reason: that so long as Sandoz timely filed a motion to certify her collective action, that motion would relate back to the date she filed her initial state court petition.
Here, Cingular made its offer of judgment about a month after receiving San-doz’s complaint. Other courts have found that there must be some time for a plaintiff to move to certify a collective action before a defendant can moot the claim through an offer of judgment.
See, e.g., Robile v. Celestica Corp.,
No. 06-2934,
However, Sandoz did not file her motion to certify until thirteen months after she filed her complaint, and relation back is warranted only when the plaintiff files for certification “without undue delay.”
See Weiss,
*922 IV. CONCLUSION
Although in theory a Rule 68 offer of judgment could moot a FLSA collective action, the relation back principle applies to ensure that defendants cannot unilaterally “pick off’ collective action representatives and thwart the availability of collective actions under the FLSA. Accordingly, we vacate the district court’s denial of Cingular’s motion to dismiss for lack of subject matter jurisdiction and remand for a consideration of the timeliness and, if necessary, the merits of San-doz’s motion to certify.
VACATED AND REMANDED.
Notes
. Sandoz sued Cingular. Wireless LLC, Cingu-lar Wireless Employee Services LLC, and AT&T Mobility LLC. The Cingular entities are now known as AT&T Mobility LLC. For simplicity, we refer to all of the Defendants-Appellants as "Cingular.”
. More specifically, collective actions typically proceed in two stages. First, the plaintiff moves for conditional certification of his or her collective action.
See Mooney v. Aramco Servs. Co.,
. The precise factual pattern of Cameron-Grant, which involved a voluntary settlement and dismissal of all of the plaintiff's claims— as opposed to a plaintiff's refusal of a Rule 68 offer of judgment that would fully satisfy his or her claims — did not impact the court's analysis of the differences between § 216(b) collective actions and Rule 23 class actions.
. We note that two additional cases that the district court cited in support of its ruling are not on point. In
Higueros v. New York State Catholic Health Plan, Inc.,
.
See Zeidman,
. On appeal, Sandoz also asserts that her case is not moot because she sought equitable relief based on alleged FLSA disclosure violations. However, Sandoz cannot receive equitable relief for this type of claim under the FLSA.
See
29 U.S.C. § 216(b);
Ward,
