Barnes v. United States
Opinion of the Court
ORDER
On November 3, 2005, this court granted plaintiffs’ motion to certify a class in this civilian pay case. See Barnes v. United States, 68 Fed.Cl. 492 (2005). On February 17, 2006, the parties filed a joint status report indicating that they were unable to agree on a proposal for meeting the notice requirements of Rule 23(c) of the Rules of the United States Court of Federal Claims (RCFC).
Generally in a class action lawsuit, a representative plaintiff is expected to bear the cost of notice to the class as part of the “burden of financing his own suit.” Eisen v. Carlisle & Jacquelin, 417 U.S. 156, 178-79, 94 S.Ct. 2140, 40 L.Ed.2d 732 (1974); see also Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340, 357, 98 S.Ct. 2380, 57 L.Ed.2d 253 (1978). While “ordinarily there is no warrant for shifting the cost of the representative plaintiffs performance of these tasks to the defendant,” the court, in its discretion, may order a defendant to “perform one of the tasks necessary to send notice, such as iden
In such situations, the defendant’s costs of performing identification tasks normally are shifted to the representative plaintiffs.
Once again, a rough analogy might usefully be drawn to practice under the discovery rules. Under those rules, the presumption is that the responding party must bear the expense of complying with discovery requests, but he may invoke the district court’s discretion under Rule 26(c) to grant orders protecting him from “undue burden or expense” in doing so, including orders conditioning discovery on the requesting party’s payment of the costs of discovery. The analogy necessarily is imperfect, however, because in the Rule 23(d) context, the defendant’s own case rarely will be advanced by his having performed the tasks. Thus, one of the reasons for declining to shift costs under Rule 26(c) usually will be absent in the Rule 23(d) context. For this reason, a district court exercising its discretion under Rule 23(d) should be considerably more ready to place the cost of the defendant’s performing an ordered task on the representative plaintiff, who derives the benefit, than under Rule 26(c). In the usual case, the test should be whether the expense is substantial, rather than, as under Rule 26(c), whether it is “undue.”
Id. at 358-59, 98 S.Ct. 2380 (footnote omitted). While the Court did not purport to define all of the circumstances in which a “court might be justified in placing the expense on the defendant,” it cautioned that “courts must not stray too far from the principle underlying [Eisen] that the representative plaintiff should bear all costs relating to the sending of notice because it is he who seeks to maintain the suit as a class action.” Sanders, 437 U.S. at 359, 98 S.Ct. 2380.
But what does this entail? Defendant sketchily has stated that the identification of putative class members can be broken down into three groups of employees. For individuals employed within the most recent 26 pay periods (current-year), defendant has access to electronic records maintained by the Defense Finance and Accounting Service (DFAS) which can provide information including names, addresses and the last four digits of social security numbers. For prior years, dating back to 1999, defendant claims that “separate retrieval programs must be written,” as the database structure has changed over the years, and CDs containing each year’s data exist in different formats. In addition, it notes that the electronic records from these years do not contain addresses and further research is required to obtain a current address. Finally, defendant reports that data from 1998 predate the DFAS data repository and will need to be retrieved from the actual tape storage medium. These data apparently also do not contain addresses.' In the joint status report filed February 17, 2006, defendant stated that the cost estimate for querying the electronic records of the DFAS would be $7,000. No estimate of costs for the additional work required to obtain addresses for employees not part of the current-year period was provided, but defendant indicated that it “is expected to exceed the cost for the DFAS work.”
At the status conference held on March 20, 2006, the court indicated that it expected defendant to work with the DFAS to provide “very detailed cost components of their figure, and not just their normal hourly rate.” In this regard, the court explained that the “internal charging process is irrelevant,” and that it “want[ed] to know what the actual costs are.” In particular, recognizing that some of the costs could be “employee driven,” the court indicated that it would like to see “an estimate of hours and the pay rates of the people involved.” More broadly, it asked for a “breakdown by component” of the “different tasks involved” in obtaining the required information for the various periods in suit in order to “gauge the reasonableness of the estimates.” Concluding, the court stated — “DFAS better be able to give you very detailed cost components of their figure and not just their normal hourly rate,” because “if they come back to me with some sort of generic quote that I [cannot] get beneath ... that [is] probably going to result in the cost being imposed upon the agency.”
In response to this order, on April 7, 2006, defendant filed a short status report in which it indicated, in relevant part, that—
The cost to provide the information that can be retrieved from the DFAS electronic records is $8,373.47, which is based upon 109.5 hours times $76.47 per hour. The rate is established by the Office of the Secretary of Defense (“OSD”) upon a yearly basis in connection with working capital funds as part of program budgeting. See 10 U.S.C. § 2208 (authorizing Secretary of Defense to establish working capital funds); 31 U.S.C. § 9701(b) (authorizing agency heads to prescribe regulations establishing the charge for a service or thing of value provided by the agency); 32 C.F.R. § 204.1 (implementing the Department of Defense program under 31 U.S.C. § 9701 and OMB Circular A-25). The rate is the rate established for Information Services Direct Billable Hours in Program Budget Decision (PBD) 426 (December 27, 2004), setting rates for fiscal years 2006 and 2007. The direct and indirect costs considered in establishing rates are described in the attached OSD Comptroller iCenter document, entitled “Core Elements Of DWCF [Defense Working Capital Funds] Rate Setting, Full Cost Recovery And The Setting Of Rates” (available at http://www. dod. mil/comptroller/icenter/ dwcf/ratesetting. htm).
The materials referenced in this passage do not provide any further breakouts of the salaries or other expenses involved with providing the various data retrieval services at issue. Rather, the webpage listed suggests that the hourly rate of $76.47 is set using “activity-based costing,” a form of accounting that is designed to recoup the overall cost of running the DFAS. See http:llwww.dod.mil/ comptroller/icenter/leam/abcosting. htm (as viewed on July 14, 2006); http://www.dod. mil/comptroller/icenter/dwcf/costvisibility.htm (as viewed on July 14, 2006). Inter alia, that rate not only covers general depreciation and overhead expenses, but is designed potentially to recoup “losses of prior years” incurred by the DFAS.
Defendant’s April 7, 2006, status report comports with neither the court’s expressed expectations nor, more importantly, the legal requirements upon which those expectations were based. For one thing, any correlation between the composite hourly rate cited by defendant and the actual costs it will incur in performing the retrieval would be a mere coincidence. More likely, applying that rate would pass on to plaintiffs costs wholly unrelated to the tasks at hand, perhaps including losses that occurred at the DFAS in a prior year. While undoubtedly such losses, as well as overhead and depreciation, might, from an accounting or institutional standpoint, appropriately be spread among Department of Defense components, it does not follow that those same costs should be imposed on outside parties in a situation such as this. Indeed, defendant would have this court charge plaintiffs the same hourly rate whether the actual work performed is done by a GS-14 systems expert or a GS-5 staff assistant—
Defendant also did not provide any detailed breakdown of the tasks associated with the data retrieval, let alone some indication as to how it arrived at its estimate of 109.5 hours to perform the retrieval. Without some level of detail as to the former, one must wonder about the accuracy of the latter. But, this is only one of many questions left unanswered by defendant. We do not know, for example, whether the estimate provided relates only to the time needed to obtain data from the current year for existing employees, as opposed to data from earlier years for retired or separated employees, or even how much of that time relates to obtaining names versus addresses. It would seem highly unlikely that the entire 109.5 hours would be needed to cull data for existing employees from a database that contains data used to pay those employees on a biweekly basis, but if that is true, then defendant has failed to provide any estimate of the time needed to obtain data for past years. Either way, there is a problem. Nor do we know what sort of effort or sophistication is needed to mine this data — do some queries require a few keystrokes and several minutes, others need a spreadsheet and a few hours, and still others require manual searches that could go on for days? Costs associated with some of these tasks might be insubstantial, while those associated with others might drive an accurate estimate of the costs involved here. Again, we do not know. Indeed, while defendant conceivably could not accurately estimate all the time and costs associated with every task involved here, it surely could have provided more information as to the key tasks to be undertaken, perhaps enough to convince the court to shift certain costs to plaintiffs, at least ab initio. But, for reasons unexplained, defendant did not provide even this basic information. Given what defendant has provided (or, more accurately, has not provided), the court can only relieve defendant of the costs of identification if it presumes that defendant’s estimate is reasonable. But, the court neither will indulge in that blithe assumption nor speculate as to details that defendant was provided not one, but two opportunities to supply. Were the shoe on the other foot, defendant would demand at least as much — and it would be right.
Under the circumstances, requiring defendant to bear certain identification costs should not be viewed as sanction, cf. Nagy v. Jostens, Inc., 91 F.R.D. 431, 432 (D.Minn. 1981), but rather as the result of its failure to put this court in the position to exercise its discretion. Several courts, indeed, have held that a defendant should bear the cost of identification or notice where it fails to provide adequate information from which the court can determine the substantiality of the costs involved.
Finally, recalling that Sanders did not “attempt to catalogue the instances in which a ... court might be justified in placing the expense on the defendant,” 437 U.S. at 358, 98 S.Ct. 2380, the court finds that the somewhat unique posture of this case buttresses its conclusion that the costs of data retrieval ought to be borne by defendant. Although Sanders teaches that “[a] bare allegation of wrongdoing ... is not a fair reason for requiring a defendant to undertake financial burdens and risks to further a plaintiffs case,” id., a series of cases have held that where a defendant’s liability has either been preliminarily or finally established, via preliminary injunction or partial summary judgment, the costs of notice may more readily be imposed upon a defendant.
In sum, based on defendant’s representations, the court is left with no option but to conclude that the costs associated with most of the identification tasks are insubstantial, and, therefore, will not be shifted to the representative plaintiffs. Accordingly,
(1) On or before October 16, 2006, defendant shall provide to plaintiffs a list of all civilian employees at Navy medical facilities who, at any time since April 18, 1998, received some amount of “premium pay” for working at night.
(a) This list shall contain the following information for each individual:
(i) Name;
(ii) Last four digits of the individual’s social security number;
(iii) A unit identification code (UIC) identifying the location of the responsible employing facility;
(iv) A submitting office number (SON) identifying the servicing personnel office; and
(v) A code identifying whether the individual received night differential premium pay (ND) and/or night shift work pay (ZJ).
(b) Defendant will also provide the UIC codes for all Navy medical facilities, including facility name and location, and with the SON codes, including office location.
(c) For the current-year list, defendant will also provide a home address for each employee listed.
(d) For any identified employee for whom an address is needed and who can be identified as having retired, defendant will request the Office of Personnel Management to provide a home address.
(e) For any identified employee for whom an address is otherwise needed, defendant shall cooperate with plaintiffs’ efforts to locate those class members, including making available any databases maintained by the United States that might contain those addresses, to the extent permitted by law.
(f) Defendant shall bear the cost of all the above tasks.
(g) To the extent addresses are not available for an employee after pursuing the above methods, the parties will confer further regarding the best alternative method for identifying the most recent home address for each employee.
(2) On or before August 25, 2006, the parties shall file a joint status report containing a proposed protective order for the information that will be contained in the lists, and the content of the class notice to be sent to each identified employee. To the extent that the parties are unable to agree upon the language for these items, each party will submit, as part of the joint report, their separate views.
(3) On or before October 30, 2006, the parties shall submit a joint status report indicating how this ease should proceed.
(4) The court expects that, in good faith, the parties will fully cooperate in accomplishing the various tasks that need*14 to be performed to perfect the class action here.
IT IS SO ORDERED.
. Like its federal counterpart, RCFC 23(c)(2) requires that "[f]or any class certified ... the court must direct to class members the best notice practicable under the circumstances, including individual notice to all members who can be identified through reasonable effort.”
. Paralleling the Federal rules, the court's power to require a defendant’s cooperation in effectuating notice stems from RCFC 23(d) — “the court may make appropriate orders: ... (2) requiring ... that notice be given in such manner as the court may direct to some or all of the members” in the action.
. Plaintiffs contend that they are entitled to the list of putative plaintiffs at defendant’s expense under this court's discovery rules. However the rules governing the discovery of information under RCFC 26 do not apply in this context, as the names and addresses are being sought for purposes of notification in a class action, not as "relevant to the subject matter involved in the pending action.” See Sanders, 437 U.S. at 350-55, 98 S.Ct. 2380 (discussion in analogous setting involving the Federal rules).
. In Sanders, 437 U.S. at 359 n. 28, 98 S.Ct. 2380, the Court gave the following example— "Thus, where defendants have been directed to enclose class notices in their own periodic mailings and the additional expense has not been substantial, representative plaintiffs have not been required to reimburse the defendants for envelopes or postage.”
. At the hearing, the court also offered defendant the option of releasing the raw data to plaintiffs and allowing them to sort through the information. It does not appear this option has been pursued.
. Emphasizing this, one page on this website explains.—
Should a Business Area record a positive or negative Net Operating Result, DoD revolving fund policy requires the prior year operating gains or losses to be returned or recovered through customer rates changes set during the budget review. Profits from prior year operations are returned to customers through decreased rates; losses are recouped through increased rates. A surcharge is imposed on customer bills to recoup losses. The amount of losses to be recouped is determined at the first budget execution review meeting of the fiscal year. Additional adjustments are determined during the mid-year review as needed. Customers are required to absorb or finance all cost increases.
http://www.dod.mil/comptroller/icenter/dwcf/ratesetting.htm (as viewed on July 14, 2006). Another page on the website cited by defendant indicates that the rates are set to cause the revolving fund to "break even over the long-term.” See http://www.dod.mil/comptroller/icenter/dwcf/revolvingfund.htm (as viewed on July 14, 2006).
. See Alzawkari v. Am. S.S. Co., 1989 WL 75917 at *1 (6th Cir. 1989); Kan. Hosp. Ass'n v. Whiteman, 167 F.R.D. 144, 147 (D.Kan. 1996); see also Comment, "Cost of Notice in Class Actions After Oppenheimer Fund, Inc. v. Sanders,” 78 Colum. L.Rev. 1517, 1528 (1978) (Sanders infers that “trial courts will have the discretion to evaluate the reasonableness of the defendant's estimate.
. See, e.g., Zubulake v. UBS Warburg, LLC, 216 F.R.D. 280, 283 & n. 30 (S.D.N.Y. 2003); Marshall v. S.K. Williams Co., 462 F.Supp. 722, 724 (D.Wis. 1978); see also Gulf Oil Co. v. Bernard, 452 U.S. 89, 101-02, 101 S.Ct. 2193, 68 L.Ed.2d 693 (1981); Charles Alan Wright, Arthur R. Miller & Richard L. Marcus, 8 Federal Practice and Procedure § 2035 atp. 484 (2d ed. 1994).
. To be sure, the Newburg treatise states that "the representative plaintiff has the burden to show that the costs and difficulty to defendant is minimal.” 3 Newburg, supra, at § 8:8 & n. 12. As authority for this proposition, that treatise cites only Sanders, 437 U.S. at 357 n. 24, 98 S.Ct. 2380. However, neither the cited footnote nor any other passage of the Supreme Court’s opinion addresses who must demonstrate substantiality as it relates to notice costs. The court believes that the better rule is as stated above.
. See, e.g., Allen v. Leis, 2002 WL 1752279 at *2 (S.D.Ohio 2002); Six (6) Mexican Workers v. Ariz. Citrus Growers, 641 F.Supp. 259, 264 (D.Ariz. 1986), judgment modified on other grounds, 904 F.2d 1301 (9th Cir. 1990); Catlett v. Mo. Highway & Transp. Com’n, 589 F.Supp. 949, 951-52 (W.D.Mo. 1984); Kyriazi v. W. Elec. Co., 465 F.Supp. 1141, 1144 (D.N.J. 1979), aff'd, 647 F.2d 388 (3d Cir. 1981); Meadows v. Ford Motor Co., 62 F.R.D. 98, 102 (W.D.Ky. 1973), judgment modified on other grounds, 510 F.2d 939 (6th Cir. 1975), cert. denied, 425 U.S. 998, 96 S.Ct. 2215, 48 L.Ed.2d 823 (1976); Ostapowicz v. Johnson Bronze Co., 54 F.R.D. 465, 467 (W.D.Pa. 1972).
. Should it ultimately prevail in this action, defendant, of course, could seek to have the actual expenses associated with the retrieval tasks be taxed as costs. See, e.g., Leist v. Tamco Enters., Inc., 1984 WL 2425 at *9 (S.D.N.Y. 1984); Chevalier v. Baird Sav. Ass'n, 72 F.R.D. 140, 147 n. 12 (E.D.Pa. 1976); Herbst v. Int’l Tel. & Tel. Corp., 65 F.R.D. 13, 21 (D.Conn. 1973), aff'd, 495 F.2d 1308 (2d Cir. 1974).
Case-law data current through December 31, 2025. Source: CourtListener bulk data.