Home » Posts tagged 'Administrative Proceeding'
Tag Archives: Administrative Proceeding
D.D.C.: Laborers on Governmental Job, Who Have Exhausted Their Administrative Remedy, May Bring Case Under Davis-Bacon Act Against Bond of General Contractor; 2 Year SOL Applies
Castro v. Fidelity and Deposit Company of Maryland
It has long been the law that generally employees lack the right to bring a private cause of action under the Davis Bacon Act (DBA). Rather, the sole avenue under which aggrieved employees, on governmental jobs, can seek repayment of their improperly withheld wages under the DBA is through a proceeding brought by the Department of Labor. However, the Department of Labor rarely brings such proceedings and thus, workers on governmental projects are often left without a remedy where they have been the victims of wage theft. This case sheds some light on another avenue that such employees can use to attempt to recover their wages however. In this case, after exhausting their administrative remedies (i.e. filing with the DOL and being told the DOL could not pursue their claims) the plaintiffs—employees of a sub-contractor on a job for the District of Columbia—sued on the bond of general contractor to seek payment of their wages. Denying the defendant-bond company’s motion to dismiss, the court explained that this was a valid cause of action.
Discussing the relevant facts and procedural history, the court explained:
Plaintiffs were employed by S & J Acoustics, a second-tier subcontractor (or subsubcontractor) retained to complete ceiling installation on the Consolidated Forensic Laboratory, a building owned by the District of Columbia. See Am. Compl., ¶¶ 2, 5. Pursuant to the DBA, 40 U.S.C. § 3141, et seq., and the DCLMA, D.C.Code § 2–201.01, et seq., the project’s prime contractor, Whiting–Turner Contracting Co., provided a payment bond to the District of Columbia as an assurance that project laborers would receive payment at Department of Labormandated hourly rates. See Am. Compl., ¶¶ 3, 8. In bringing this action against Defendants (1) Fidelity and Deposit Company of Maryland and (2) Travelers Casualty and Surety Company of America, who insured Whiting–Turner’s bond as co-sureties, see id., ¶ 3, Plaintiffs allege that they were not paid for their contributions to the project in accordance with these designated wage rates. See id., ¶¶ 16–18, 21. As background, the DCLMA requires contractors on governmentfunded projects to secure payment bonds to protect the interests of suppliers of materials and subcontractors, and the DBA establishes prevailing wage rates for workers who contribute to government-funded construction projects.
Prior to initiating this action, Plaintiffs filed an administrative complaint with DOL, requesting that payments to the project’s prime contractor be withheld until an investigation could be completed and Plaintiffs compensated for the alleged back wages. See id., ¶¶ 23–25. As the project had since wound up and all payments had been released to Whiting–Turner, the DOL investigator closed the case without making any findings on Plaintiffs’ eligibility for relief under the DBA. See id., ¶¶ 24–25. After Plaintiffs brought suit and Defendants filed their Motion to Dismiss, the Court sua sponte raised the issue of subject-matter jurisdiction, questioning whether Plaintiffs had sufficiently exhausted their administrative remedies with DOL. See Order to Show Cause at 2–3. Out of deference to DOL’s plenary role in making DBA back-wage determinations, the Court issued a temporary stay in the proceedings and ordered Plaintiffs to return to DOL and request that conclusive findings be made. See ECF No. 16 (Order) at 4. Plaintiffs did so, but without success. DOL refused to take further action on the ground that the government had already made all payments to the prime contractor and had no further funds to withhold. See Joint Status Report, ¶¶ 6–7 & Exh. A. Satisfied that Plaintiffs had made all efforts to exhaust remedies with DOL, the Court concluded that it did have subjectmatter jurisdiction under the DBA and could consequently address the substance of their claims and Defendants’ pending Motion to Dismiss. See Castro v. Fid. & Deposit Co. of Maryland, No. 13–818, 2014 WL 495464 (D.D.C. Feb. 7, 2014).
Under these circumstances, the defendant argued that the plaintiffs lacked any remedy. The court summarized the defendants contentions as follows:
Defendants first argue that Plaintiffs cannot invoke the DCLMA to sue on Whiting Turner’s payment bond because eligibility under the statute is restricted to those suppliers of labor and materials that have been retained either by the prime contractor or by an immediate subcontractor. See Mot. to Dismiss at 9; Reply at 1–2. Since Plaintiffs were hired by a second- tier subcontractor, Defendants suggest that they fall outside of the scope of the statute. See Supp. to Mot. to Dismiss at 3.
Defendants further maintain that Plaintiffs also have no remedy under the DBA. They premise this argument on the text of DBA § 3144(a)(2), which provides that “laborers and mechanics have the same right [of] action … as is conferred by law on persons furnishing labor or materials.” See Reply at 4. The use of the phrase “same right,” according to Defendants, demonstrates that § 3144(a)(2) does not actually grant aggrieved workers an independent cause of action, but merely references the applicable bond statute – in this case, DCLMA § 2–201.02. See Mot. to Dismiss at 9; Reply at 1 (“Plaintiffs do not have separate cause [sic ] of action against the Defendants in this case under the DBA….”). Alternatively, even if § 3144(a)(2) does create a freestanding cause of action, Defendants reason that the result should be the same because “the rights, if any, that were conferred [by § 3144(a)(2) ] were limited by the express terms of the bond statute.” Reply at 7. The DBA, by this logic, merely duplicates the DCLMA, mirroring its procedural requirements and limitations on eligibility.
Addressing the defendants’ contentions, the court first analyzed the scope and requirements of the DCLMA, acknowledging that plaintiffs lacked standing thereunder, because like the federal Miller Act, it applies only to prime contractor and immediate subcontractors. That did not end the court’s inquiry however. It then turned to an examination of § 3144(a)(2) of the DBA to determine whether it provides an independent remedy with its own terms and conditions. Holding that the DBA, under these circumstances, provided the plaintiffs with a remedy the court explained:
The game is not over, however, because the DBA protects precisely those “ordinary laborers” that the Miller Act appears to exclude. The DBA applies to any construction contracts for public works and public projects that exceed $2,000 in value and to which either the Federal Government or the District of Columbia is a party. See 40 U.S.C. § 3142(a). It obliges contractors on such projects to pay workers in accordance with prevailing wage rates, established by the Secretary of Labor. See id. In the event that contractors do not comply with prevailing wage rates, a worker may seek redress through the mechanism set out in DBA § 3144(a)(2). Promulgated in 1935 – just six days after the federal Miller Act was updated to reflect its current language – § 3144(a)(2) is broadly worded, granting a right of action to “all the laborers and mechanics who have not been paid the wages required” pursuant to the DBA. In contrast to the Miller Act and DCLMA, which condition their protections on a requisite level of contractual proximity to the prime contractor, DBA eligibility appears to hinge upon a laborer’s presence at the job site. Section 3144(a)(2) stipulates that each “contractor or subcontractor” involved in a “contract” governed by the DBA “shall pay all mechanics and laborers employed directly on the site of the work, unconditionally and at least once a week … regardless of any contractual relationship which may be alleged to exist between the contractor or subcontractor and the laborers and mechanics.” § 3142(c)(1) (emphasis added).
Although the DBA does not separately delineate the terms “contract,” “contractor,” “subcontractor,” or “laborer,” these terms are defined in corresponding regulations promulgated by the Secretary of Labor. See 29 C.F.R. § 5.2. The term “contract” comprises “any prime contract which is subject … to the labor standards provisions of [the DBA] and any subcontract of any tier thereunder, let under the prime contract.” § 5.2(h) (emphasis added). This definition, unlike that in the DCLMA, is not limited by a particular degree of separation from the prime contractor. The regulations, in fact, expressly disavow any requirement that a worker demonstrate a particular contractual relationship, instead providing that “[e]very person performing the duties of a laborer or mechanic in the construction … of a public building or public work … is employed regardless of any contractual relationship alleged to exist between the contractor and such person.” § 5.2(o). The regulatory definition of “laborer” is governed by function, not by contractual formality, and extends to “at least those workers whose duties are manual or physical in nature.” § 5.2(m).
Even in the unlikely event that a court were to find the text of the DBA ambiguous, it would still be bound to apply DOL’s regulatory definitions in making its decision. “Because the Secretary of Labor has interpreted the Act,” courts must defer to the Secretary’s judgment provided that these “interpretations are reasonable.” AKM LLC v. Sec’y of Labor, 675 F.3d 752, 754 (D.C.Cir.2012) (citing Chevron, U.S.A., Inc. v. Natural Res. Def. Council, 467 U.S. 837, 843 (1984)). In this case, the regulatory interpretations are more than merely reasonable – they are grounded in the most basic common sense. Because a prime contractor should have ample notice of laborers working at its project site, it can institute sufficient controls to ensure that they are accounted for and paid for their contributions, regardless of any particular contractual arrangement. In contrast to the situation with suppliers, who may come and go without any physical connection to a job site, there is far less risk that laborers will be completely “[un]known to the prime contractor,” U.S. ex rel. E & H Steel Corp., 509 F.3d at 187, and thereby expose it to unforeseen liability.
The court then explained that where, as here, workers had exhausted their administrative remedy (i.e. filed with the DOL), they were entitled to bring a private cause of action under the DBA:
Clearly titled as a “[r]ight of action,” DBA § 3144(a)(2) provides that, if the Secretary of Labor’s withholdings under the terms of a contract are “insufficient to reimburse all the laborers and mechanics who have not been paid the wages required[,] … the laborers and mechanics have the same right to bring a civil action and intervene against the contractor and the contractor’s sureties as is conferred by law on persons furnishing labor or materials.” (Emphasis added). Two points are notable here. First, the express title of § 3144(a)(2) indicates that Congress believed that it was creating a new and fully functional right of action, and not merely a superficial reference to remedies already available under the bond statutes. While many battles have been waged over whether or not an aggrieved worker can claim an implied right of action under the DBA and thereby circumvent the administrative-exhaustion requirements of § 3144(a), see, e.g., Univers. Research Ass’n v. Coutu, 450 U.S. 754, 780 (1981), courts have long recognized that § 3144(a)(2) furnishes an express cause of action once remedies have been exhausted. See, e.g., U.S. ex rel. Bradbury v. TLT Const. Corp., 138 F.Supp.2d 237, 241 (D.R.I.2001).
Second, the formulation “all the laborers … who have not been paid” sets an expansive scope of application that is not obviously restricted by what follows. If Congress had intended to limit the scope of eligibility to sue on a bond to the narrow class of workers who might qualify under the terms of the Miller Act, it stands to reason that the legislature would have said so in clear and unambiguous terms or, more plausibly, would have completely omitted § 3144(a)(2) from the DBA. If Defendants are correct, § 3144(a)(2) would be mere surplusage, offering nothing of value over and above the remedies already available via the Miller Act and DCLMA. The Court cannot ignore the ” ‘cardinal principle of statutory construction’ that ‘a statute ought, upon the whole, to be so construed that, if it can be prevented, no clause, sentence, or word shall be superfluous, void, or insignificant.’ ” TRW Inc. v. Andrews, 534 U.S. 19, 31 (2001) (quoting Duncan v. Walker, 533 U.S. 167, 174 (2001)).
Perhaps even more troubling, Defendants’ assessment of § 3144(a)(2) would create two arbitrary classes of workers – first, those who satisfy the technical qualifications imposed by the terms of the Miller Act and DCLMA, and second, all otherwise DBA-eligible workers. If the Court were to endorse Defendants’ highly restrictive interpretation, it might encourage prime contractors to insulate themselves behind several layers of subcontracts and thus opt out of the obligation to pay DBA-mandated wages, particularly as a project draws to a close and the government is no longer able to withhold funds. It should be obvious, accordingly, that all laborers present on the worksite of a DBA-eligible project should stand to benefit from the Act’s protections, regardless of contractual formalities. The Court thus concludes that § 3144(a)(2) of the DBA creates an independent cause of action that grants the ability to collect on a prime contractor’s bond to all eligible on-site workers, regardless of who hired them.
Finally, the court rejected the defendant’s argument that the plaintiff’s were limited by a one year statute of limitations, and held that a two year statute of limitations was applicable to the claims, pursuant to the Portal-to-Portal Act.
Click Castro v. Fidelity and Deposit Company of Maryland to read the entire Memorandum Opinion of the court.