OPINION OF THE COURT
BECKER, Chief Judge.
This is an appeal from an order of the District Court vacating an arbitrator’s award. Plaintiff Roadway Package System, Inc. (RPS) ships small packages for corporate clients. “Independent linehaul contractors,” such as Defendant Scott Kayser, assist in its operations. RPS terminated Kayser’s contract in 1998, alleging that he had failed to fulfill his obligations under the Linehaul Contractor Operating Agreement (LCOA), which governed their association. Kayser exercised his contractual right to demand arbitration and was awarded substantial damages. RPS then brought suit in the District Court for the Eastern District of Pennsylvania, asking the court to vacate the award. Applying the vacatur standards set forth in the Federal Arbitration Act (FAA), the District Court granted the motion on the grounds that the arbitrator exceeded the scope of his authority. We will affirm.
Kayser’s appeal requires us to decide two questions of considerable significance for the law governing arbitration, both of which are currently the subject of circuit-splits. The first question is whether contracting parties may opt out of the FAA’s default vacatur standards and fashion their own. Because the LCOA is a “contract evidencing a transaction involving commerce,” 9 U.S.C. § 2, the FAA governs this case. Resolving a question previously reserved by this Court, we first hold that the FAA permits parties to contract for vacatur standards other than the ones provided in the FAA. The FAA sets out “a substantive rule applicable in state as well as federal courts,” Southland Corp. v. Keating, 465 U.S. 1, 16, 104 S.Ct. 852, 79 L.Ed.2d 1 (1984), but its rule is simply that courts must enforce the terms of private arbitration agreements.
The second question we must decide involves the conceptually complex issue of how courts should determine whether parties have contracted out of the FAA’s default rules. The LCOA contains a generic choice-of-law clause, stating that it “shall be governed by and construed in accordance with the laws of the Commonwealth of Pennsylvania.” Kayser submits that we should read this clause as expressing a desire to opt out of the FAA’s default regime and to incorporate arbitration rules borrowed from Pennsylvania law. We disagree.
We first explain why the choice-of-law clause sheds little, if any, light on the parties’ actual intent. The issue before us is simply a matter of contract construction rather than one of choice-of-law. Because choice-of-law clauses are designed to deal with a different issue from the one with which we are currently faced, and because few federal statutes other than the FAA permit parties to contract out of their requirements, we do not read the LCOA’s choice-of-law clause as evidencing a clear intent to displace the FAA’s default regime. Our conclusion is consistent with Mastrobuono v. Shearson Lehman Hutton, Inc., 514 U.S. 52, 115 S.Ct. 1212, 131 L.Ed.2d 76 (1995), and though Volt Information Sciences, Inc., v. Board of Trustees of Leland Stanford Junior University, 489 U.S. 468, 109 S.Ct. 1248, 103 L.Ed.2d 488 (1989), may appear to the contrary, our review of that opinion, the Supreme Court’s subsequent decision in Mastrobuo-no, and the unanimous holdings of six other Courts of Appeals convince us that Volt is distinguishable.
Because the presence of a generic choice-of-law clause tells us little (if anything) about whether contracting parties [289]*289intended to opt out of the FAA’s default standards and incorporate ones borrowed from state law, we must announce and apply a default rule. We hold that a generic choice-of-law clause, standing alone, is insufficient to support a finding that contracting parties intended to opt out of the FAA’s default regime. This rule will: (1) ensure that parties who have never thought about the issue will not be found to have elected out of the FAA’s default regime; (2) be comparatively simple for arbitrators and district courts to apply; and (3) preserve the ability of sophisticated parties to opt out. Applying our rule to this case, we conclude that the District Court was correct to apply the FAA’s va-catur standards.
Analyzing the issue under those standards, we hold that the District Court correctly determined that the arbitrator exceeded the scope of his authority. Though our cases caution against exploiting an ambiguity in an arbitrator’s award to support an inference that he or she exceeded his or her powers, they also establish that a reviewing court is not precluded from examining an arbitrator’s statement of reasons. In this case, the arbitrator’s written opinion makes crystal clear that his decision was based on the fact that he thought that RPS’s procedures for notifying Kayser of its dissatisfaction with his performance were unfair. Yet the intrinsic fairness of RPS’s procedures was not before the arbitrator — he was empowered to decide only whether the termination was within the terms of the LCOA. Accordingly, we conclude that the District Court was correct in vacating the award, and will, therefore, affirm its order.
I.
A.
RPS and Kayser entered into the LCOA in 1996. It required Kayser to conform to specified service and safety standards, and permitted early termination if he did not meet them. RPS terminated the LCOA in mid 1998, alleging that Kayser had repeatedly failed to fulfill his obligations under the contract.
The LCOA is forty-one pages long and is divided into sixteen sections. This appeal implicates Sections 9 and 16. Section 9.3 binds the parties to arbitrate disputes and outlines the procedures for doing so. Its introductory sentence provides:
In the event that RPS acts to terminate this Agreement ... and [Kayser] disagrees with such termination ... then each such disagreement (but no others) shall be settled by arbitration in accordance with the Commercial Arbitration Rules of the American Arbitration Association ....
Section 9.3(e) states:
The arbitrator shall have the authority only to conclude whether the termination of [Kayser] was within the terms of this Agreement, to deter mine damages if required to do so under this subparagraph, and to provide for the division of the expenses of the arbitration between the parties_If the arbitrator concludes that the termination was not within the terms of this Agreement, then, at the option of RPS ... (2) [Kayser] shall nevertheless be terminated, and ... shall be entitled to damages equal to the arbitrator’s determination of what [Kayser’s] net earnings ... would have been during the period between the date of termination to the last day of the term of this Agreement, (without any renewals). [Kayser] shall have no claim for damages in any other amount, and the arbitrator shall have no power to award punitive or any other damages.
Finally, Section 9.3(f) specifies:
The arbitrator shall have no authority to alter, amend or modify any of the terms [290]*290and conditions of this Agreement (including by application of estoppel, waiver, or ratification), and further, the arbitrator may not enter any award which alters, amends or modifies the terms or conditions of this Agreement in any form or manner (including by application of estoppel, waiver, or ratification).
Section 16 contains a generic choice-of-law provision, stating that the LCOA “shall be governed by and construed in accordance with the laws of the Commonwealth of Pennsylvania.”
B.
Following RPS’s termination of the LCOA, Kayser demanded arbitration, which was conducted before William Mech-mann. Kayser sought $141,961.40 in total damages: $129,930.00 for projected lost profits plus $12,031.40 for expenses incurred in purchasing a tractor-trailer at RPS’s request. Arbitrator Mechmann ruled for Kayser and awarded $174,431.15 in damages — $32,469.75 more than Kayser originally requested.
Mechmann’s written decision consists of twelve short paragraphs. The first is irrelevant to this appeal. The second paragraph acknowledges that “[t]he arbitrator’s authority is set forth in Section 9.3(e) [of the LCOA].” The third characterizes the “[t]he main question” before Mech-mann as whether RPS’s termination of the LCOA was “wrongful or proper.” The fourth, fifth, sixth, and seventh paragraphs of the opinion focus on RPS’s procedures for notifying independent contractors when it is dissatisfied with their performance and discuss the manner in which those procedures played out in Kayser’s case. They read as follows:
The RPS procedure for dealing with performance by its contractors is commendable. [sic] Documentation of breaches by the contractors are written up by Local Managers. This is only verbalized to the contractor....
[Kayser] bought larger equipment at the behest of RPS and took on that financial responsibility, but when his performance was unsatisfactory, he only received verbal warnings until the point of termination which of course, is written. He is aggressive with warehouse people in several locations to get in and out to serve other ... customers. When his own driver employees were remiss, he replaced them once RPS brought a problem to his attention. He was an aggressive business man in a very competitive environment. Verbal warnings did not persuade him of RPS’s serious concerns.
Based on many years of dealing with industrial relations jurisprudence in American business, I find the RPS system lacking in due process toward [Kay-ser].
Here the RPS system, which I respect, blinds itself into thinking — as long as we document our side of the business arrangement, that is sufficient. For a reputable business organization that per forms an important service in the economy, that is inadequate.
Paragraph eight gives Mechmann’s conclusion:
I conclude that this was wrongful termination by RPS of the LCOA and determine the contractor’s earnings (after payment of all expenses which are bor ne by contractor) according to LCOA Section 9.3(e). As Section 9.3(e) provides, the damage period here runs from 05/21/98, the date of RPS’s termination of the LCOA to 01/25/99, the normal date of termination of the present Agreement (LCOA).
Paragraph nine, without explanation, sets Kayser’s damages at $174,431.15. Para[291]*291graphs ten, eleven, and twelve are not relevant to this appeal.
C.
RPS then filed suit, asking the District Court to vacate or modify the arbitrator’s award.1 The District Court granted RPS’s motion, holding that: (1) the FAA, not Pennsylvania law, supplied the standards for judicial review of the arbitrator’s decision; and (2) the arbitrator had exceeded his authority under the contract. In light of this conclusion, the Court did not reach RPS’s other proffered bases for vacatur. Kayser appeals. We have appellate jurisdiction under 28 U.S.C. § 1291. We review a district court’s ruling on a motion to vacate an arbitration award de novo. See Kaplan v. First Options of Chicago Inc., 19 F.3d 1503, 1509 (3d Cir.1994).
II.
We must first decide whether the District Court properly applied the FAA’s vacatur standards or whether it should have, as Kayser submits, used those laid out in the Pennsylvania Uniform Arbitration Act (PUAA). For reasons we set forth in the margin, the answer to this question could be quite important to the ultimate disposition of this case.2 We have [292]*292no trouble in determining that this case is governed by the FAA. Subject to a few exceptions not implicated here, the statute applies to any “written provision in any ... contract evidencing a transaction involving commerce to settle by arbitration a controversy arising out of such contract or transaction.” 9 U.S.C. § 2. This language “extend[s] the Act’s r each to the limits of the Congress’ Commerce Clause power[.]” Allied-Bruce Terminix Cos., Inc. v. Dobson, 513 U.S. 265, 268, 115 S.Ct. 834, 130 L.Ed.2d 753 (1995). The agreement to arbitrate in this case-one between citizens of different states and involving a contract for the delivery and pick-up of packages that have been or will be shipped interstate — was unquestionably within Congress’ power to reach under the Commerce Clause.
Our inquiry is not ended, however, simply because we have concluded that the FAA applies. Congress enacted the FAA “to overcome courts’ refusals to enforce agreements to arbitrate.” Id. at 270, 115 S.Ct. 834. The statute’s ultimate purpose is to enforce the terms of private arbitration agreements. See 9 U.S.C. § 2 (providing that such agreements “shall be valid, irrevocable, and enforceable, save upon grounds as exist at law or in equity for the revocation of any contract”); see also Dean Witter Reynolds Inc. v. Byrd, 470 U.S. 213, 220, 105 S.Ct. 1238, 84 L.Ed.2d 158 (1985) (observing that the statute “was motivated, first and foremost, by a congressional desire to enforce agreements into which parties had entered”). Though the FAA generally embraces a “proarbi-tration policy,” this policy “does not operate without regard to the wishes of the contracting parties.” Mastrobuono v. Shearson Lehman Hutton, Inc., 514 U.S. 52, 57, 115 S.Ct. 1212, 131 L.Ed.2d 76 (1995). Thus, if parties contract to arbitrate pursuant to arbitration rules or procedures borrowed from state law, the federal policy is satisfied so long as their agreement is enforced. See Volt Info. Sci., Inc., v. Board of Trustees of Leland Stanford Junior University, 489 U.S. 468, 478, 109 S.Ct. 1248, 103 L.Ed.2d 488 (1989).
The foregoing does not mean that agreements specifying that arbitration will be conducted pursuant to state rules or procedures cease being subject to the FAA; it means simply that the FAA permits parties to “specify by contract the rules under which ... arbitration will be conducted.” Id. at 479, 109 S.Ct. 1248. When a court enforces the terms of an arbitration agreement that incorporates state law rules, it does so not because the parties have chosen to be governed by state rather than federal law. Rather, it does so because federal law requires that the court enforce the terms of the agreement. Cf. Mastrobuono, 514 U.S. at 58, 115 S.Ct. 1212 (inquiring “what the contract has to say about the arbitrability of petitioner’s claim for punitive damages” rather than whether the agreement was controlled by a New York rule barring arbitrators from awarding them).
Having previously reserved the threshold question, see Apex Fountain Sales, Inc. v. Kleinfeld, 818 F.2d 1089, 1094-95 & n. 4 (3d Cir.1987), we now hold that parties may agree that judicial review of an arbitrator’s decision will be conducted according to standards borrowed from state law. The FAA creates “a substantive rule applicable in state as well as federal courts,” [293]*293Southland Corp. v. Keating, 465 U.S. 1, 16, 104 S.Ct. 852, 79 L.Ed.2d 1 (1984), but Volt and Mastrobuono clarified that its rule is simply that courts must enforce the terms of arbitration agreements. We now join with the great weight of authority and hold that parties may opt out of the FAA’s off-the-rack vacatur standards and fashion their own (including by referencing state law standards).3 This holding makes it necessary for us to decide a truly difficult question — whether Kayser and RPS did so in this case.
III.
We first consider whether RPS and Kayser manifested a clear intent that any judicial review of the arbitrator’s award would be conducted pursuant to standards borrowed from Pennsylvania law. Though our ultimate goal is to effectuate their intent, we have little evidence with which to work. Section 9.3 of the LCOA binds them to resolve any disputes “by arbitration in accordance with the Commercial Arbitration Rules of the American Arbitration Association.” Section 16 directs that the LCOA “shall be governed by and construed in accordance with the laws of the Commonwealth of Pennsylvania.” The LCOA itself says nothing about the issue before us, and there is no extrinsic evidence that RPS and Kayser gave the matter any consideration. All we have to guide us, therefore, is an arbitration clause and a generic choice-of-law clause.
We do not believe that provisions such as these demonstrate a clear intent to displace the FAA’s vacatur standards and replace them with ones borrowed from Pennsylvania law. Choice-of-law clauses are ubiquitous in commercial agreements, and with good reason. Contract law is mostly state law, and it varies from state to state. As a result, parties to commercial agreements often care a great deal about which state’s law will govern their association. And because modern choice-of-law doctrines tend to place great weight on intent, contracting parties have an incentive to include choice-of-law clauses in their agreements. Commercial parties often also bargain for arbitration clauses, hoping to benefit from arbitration’s purported advantages over litigation. As a result, many commercial contracts include both choice-of-law and arbitration clauses.
When required to determine the legal standards governing a particular controversy, courts typically confront two choice-of-law questions. The first is the horizontal question: whether the laws of State X or State Y supply the relevant rule of decision. Choice-of-law doctrines (and, consequently, choice-of-law clauses) speak to this issue. The second choice-of-law question that courts face is the vertical one: whether the rule of decision is supplied by the laws of State X or by federal law. Judge-made choice-of-law doctrines (and, accordingly, attempts by contracting parties to influence their application with choice-of-law clauses) have no applicability [294]*294to answering this question because the relevant rule is supplied by the Constitution itself: a valid federal law preempts any state law purporting to regulate the same issue. See U.S. Const. Art. VI.
The issue before us, however, is not one of choice-of-law or preemption — it is simply a matter of contract construction. No one contests that were this matter governed by state law, then the relevant rule would be supplied by the laws of the Commonwealth of Pennsylvania. But, as we have explained, this case is not governed by state law — it is governed by federal law. The only reason we must decide whether to apply federal or state standards in this case is because the FAA permits parties to “specify by contract the rules under which ... arbitration will be conducted.” Volt, 489 U.S. at 479, 109 S.Ct. 1248. The issue in this case is whether the LCOA’s generic choice-of-law clause should be read as specifying that any judicial review of the arbitrator’s decision should be conducted according to the standards set forth in Pennsylvania arbitration law instead of those set out in the FAA.
We decline to construe the choice-of-law clause in this case as evidencing a clear intent to incorporate Pennsylvania’s standards for judicial review into the LCOA. As we explained above, choice-of-law clauses are generally intended to speak to an issue wholly distinct from the one with which we are currently faced. Moreover, because few (if any) federal statutes other than the FAA even permit parties to opt out of the standards contained in them, we are confident that this particular issue rarely occurs to contracting parties ex ante.
We find support for our conclusion in Mastrobuono v. Shearson Lehman Hutton, Inc., 514 U.S. 52, 115 S.Ct. 1212, 131 L.Ed.2d 76 (1995), which involved a dispute between a securities broker and two of its customers. The parties had agreed to resolve any disputes by arbitration and had indicated a desire to have their agreement “governed by the laws of the State of New York.” Though the FAA permits arbitrators to award punitive damages, the question before the Supreme Court was whether the parties had intended to incorporate into their agreement a New York rule that barred arbitrators from awarding them.
The Court began by examining the choice-of-law clause “in isolation.” Id. at 59, 115 S.Ct. 1212. It noted that the clause could “reasonably be read as merely a substitute for the conflict-of-laws analysis that otherwise would determine what law to apply to disputes arising out of the contractual relationship,” id., i.e., whether to apply the laws of New York or those of another state. If this reading was the correct one, the Court observed, then “there would be nothing in the contract that could possibly constitute evidence of an intent to exclude punitive damages claims.” Id. The Court also stated that even if the choice-of-law clause was intended to be “more than a substitute for ordinary conflict-of-laws analysis” it still “might not preclude the award of punitive damages because New York allows its courts, though not its arbitrators, to enter such awards.” Id. Because of this, the Court reasoned that “the provision might include only New York’s substantive rights and obligations and, not the State’s allocation of power between alternative tribunals.” Id. at 60, 115 S.Ct. 1212.
Though never resolving which interpretation of the choice-of-law clause was the best one, the Court squarely held that it did not clearly evidence an intent to opt out of the federal default rule that arbitrators may award punitive damages and replace it with one borrowed from New York [295]*295law that they may not award them. See id. (remarking that the choiee-of-law clause was “not, in itself, an unequivocal exclusion of punitive damages claims”); see also id. at 62, 115 S.Ct. 1212 (“At most, the choice-of-law clause introduces an ambiguity into an arbitration agreement that would otherwise allow punitive damages awards.” (emphasis added)). Mastrobuono thus supports our conclusion that the LCOA evidences no clear intent to displace the FAA’s default standards for judicial review and to replace them with those borrowed from Pennsylvania law.
Our conclusion that RPS and Kayser have expressed no clear intent as to whether the District Court should have applied federal or state vacatur standards is not undermined by Volt Information Sciences, Inc. v. Board of Trustees of Leland Stanford Junior University, 489 U.S. 468, 109 S.Ct. 1248, 103 L.Ed.2d 488 (1989). In that case, the underlying contract included both an arbitration clause and a choice-of-law clause. See id. at 470, 109 S.Ct. 1248. A California court interpreted the contract to mean that the parties had intended to incorporate California’s arbitration rules into their agreement, see id. at 471-73, 109 S.Ct. 1248, and the Supreme Court of the United States affirmed. Though the contractor “devote[d] the bulk of its argument to convincing [the Supreme Court] that the [California court had] erred in interpreting the choice-of-law clause,” it stressed that “the interpretation of private contracts is ordinarily a question of state law, which this Court does not sit to review. ” Id. at 474, 109 S.Ct. 1248 (emphasis added). The Court acknowledged that it might have needed to review the state courts’ interpretation had that interpretation infringed upon federal rights, but explained that the only “right” conferred by the FAA is to have private arbitration agreements enforced according to their terms. See id. at 474-76, 109 S.Ct. 1248. And, said the Court, because the California courts had found that the parties meant to incorporate the California rules into their agreement, applying those rules to their case was perfectly consistent with the policies of the FAA. See id. at 475, 109 S.Ct. 1248.
We do not view Volt as offering guidance as to how generic choice-of-law clauses should be interpreted; rather, the Court merely followed its obligation to defer to state court constructions of private agreements in cases where no federal rights are at stake. This supposition is supported by Mastrobuono, where the Court was reviewing a federal court’s construction of a choice-of-law clause. Responding to Justice Thomas’s dissent, which relied heavily on Volt, the Court clarified that in that case it had not construed the contract de novo. See Mastrobuono, 514 U.S. at 60 n. 4, 115 S.Ct. 1212. Instead, said the Court, it had “deferred to the California court’s construction of its own State’s law.” Id.
Our understanding of Volt is bolstered by case law from our sister circuits. Six other Courts of Appeals have expressly considered the relationship between Volt and Mastrobuono. All six have unanimously concluded that Volt is inapposite when a federal court is unconstrained by the need to defer to state court constructions. See PaineWebber, Inc. v. Elahi, 87 F.3d 589, 594 n. 5 (1st Cir.1996); National Union Fire Ins. Co. v. Belco Petroleum Corp., 88 F.3d 129, 134 (2d Cir.1996); Porter Hayden Co. v. Century Indemnity Co., 136 F.3d 380, 383 n. 6 (4th Cir.1998); Ferro Corp. v. Garrison Indus., Inc., 142 F.3d 926, 936 (6th Cir.1998); UHC Management Co., Inc. v. Computer Sciences Corp., 148 F.3d 992, 996 (8th Cir.1998); Wolsey, Ltd. v. Foodmaker, Inc., 144 F.3d [296]*2961205, 1212-13 (9th Cir.1998).4 Volt therefore contains nothing that undercuts our conclusion that RPS and Kayser expressed no clear intent to incorporate Pennsylvania standards of judicial review into their agreement.
IV.
Because the presence of a generic choice-of-law clause tells us little (if anything) about whether contracting parties intended to opt out of the FAA’s default standards and incorporate ones borrowed from state law, we need to establish a default rule, and the one we adopt is that a generic choice-of-law clause, standing alone, is insufficient to support a finding that contracting parties intended to opt out of the FAA’s default standards. W e first lay out three considerations that inform our analysis, articulate why the rule we announce today is consistent with them, and show why our rule is in line with case law from both the Supreme Court and six of our sister circuits. We then respond to the alternative approach proposed by Judge Ambro. We conclude by applying our rule to this case.
Three considerations guide us in formulating a default rule. First, we aim to minimize the frequency with which parties will be found to have opted out of the FAA’s default regime when they did not intend to do so. This guidepost is consistent with the Supreme Court’s admonition that the FAA standards control “in the absence of contractual intent to the contrary.” Mastrobuono, 514 U.S. at 59, 115 S.Ct. 1212. It is also consonant with the FAA’s raison d’etre, which is to overcome rules (whether created by state legislatures or by courts) that make it more difficult to enforce arbitration agreements. See Volt, 489 U.S. at 478, 109 S.Ct. 1248 (“The FAA was designed ‘to overrule the judiciary’s long-standing refusal to enforce agreements to arbitrate.’ ”) (quoting Dean Witter Reynolds, Inc. v. Byrd, 470 U.S. 213, 219-20, 105 S.Ct. 1238, 84 L.Ed.2d 158 (1985)). We acknowledge that some states provide as much or more protection to arbitration agreements than does the FAA, see, e.g., 42 Pa. Con. Stat. § 7302 et seq, but others do not, see, e.g., Garrity v. Lyle Stuart, Inc., 40 N.Y.2d 354, 386 N.Y.S.2d 831, 832, 353 N.E.2d 793 (1976) (construing New York law as precluding arbitrators from awarding punitive damages). The FAA’s ultimate goal is to enforce parties’ actual bargains, but any default rule is doomed to be inaccurate in some cases. We must, therefore, decide which error is worse: wrongly concluding that parties intended to opt out, or wrongly concluding that they did not. In light of the FAA’s history, we believe that the former is worse than the latter.
Second, we strive to create a regime under which it will be easy for arbitrators [297]*297and district courts to deter mine whether parties have opted out of federal standards. Finally, we seek to create a rule that sophisticated parties may bargain around without significantly increasing their transaction costs.
In light of these guideposts, we believe that the best rule is that a generic choice-of-law clause, standing alone, raises no inference that contracting parties intended to opt out of the FAA’s default regime. This rule will ensure that parties who have never thought about this particular issue— a characterization that, we suspect, would apply to the parties in this case — will not be found to have opted out. It will also make life easier for both arbitrators and judges because the analysis will be complete once they conclude that an agreement contains nothing more than a generic choice-of-law clause. In contrast, any other rule would often require a protracted analysis to determine whether the parties have contracted out of the default federal standards, a process that would impose two burdens: (1) it would make cases harder to decide for both arbitrators and judges; and (2) the resulting legal uncertainty might deter settlements.
Lastly, the rule we announce will preserve and facilitate the ability of parties to contract around the default federal standards. Sophisticated parties (i.e., those who employ experienced lawyers to draft their contracts) will soon learn that a generic choice-of-law clause is not enough. Assuming that both parties genuinely wish to be governed by standards other than the FAA’s, requiring something more will impose minuscule transaction costs. It is not particularly difficult, for example, to provide that “any controversy shall be settled by arbitration in accordance with the terms of the Pennsylvania Uniform Arbitration Act.” Cf. Ford v. NYLCare Health Plans of Gulf Coast, Inc., 141 F.3d 243, 246 (5th Cir.1998) (noting that the parties’ contract provided that “[a]ny controversy ... shall be settled by arbitration in accordance with the Texas General Arbitration Act”).5 We note also that any other rule would impose transaction costs as well by impelling parties not wishing to opt out to include a provision saying that their choice-of-law clause should not be read to raise such an inference.
Our rule is also consistent with the case law. First, it honors Mastrobuono’s directive that FAA standards apply “in the absence of contractual intent to the contrary.” 514 U.S. at 59, 115 S.Ct. 1212. As we have explained, there is good reason to believe that contracts often contain both generic choice-of-law and arbitration clauses in cases where it is likely that the parties gave absolutely no thought to opting out of the FAA’s default standards.
Second, the rule we announce today is in synch with Mastrobuono’s holding. We acknowledge that that opinion concludes with a discussion that is premised on the assumption that the presence of a choice-of-law clause can render a contract ambiguous as to whether the parties intended to incorporate state arbitration rules into their agreement. See id. at 63-65, 115 S.Ct. 1212. The Court, however, was careful to make clear that it was rendering no holding as to the meaning of the clause itself. See, e.g., id. at 62, 115 S.Ct. 1212 (“At most, the choice-of-law clause introduces an ambiguity into an arbitration [298]*298agreement that would otherwise allow punitive damages awards.” (emphasis added)).6 Third, our holding is in accord with decisions by six of our sister circuits that declined to construe a generic choice-of-law clause as raising an inference that the contracting parties intended to incorporate state law arbitration standards into their agreement.7
Judge Ambro proposes a different approach, arguing that contracts containing generic choice-of-law clauses and arbitration clauses should be construed as incorporating all state arbitration rules that are “procedural” in nature and “substantive” state arbitration rules that do not “conflict” with the FAA. See Ambro Op. at 304-05. We are unconvinced, believing that the reasons outlined above that counsel in favor of the rule we announce today. Additionally, we have three problems with Judge Ambro’s proposal.
First, Judge Ambro’s proposal is based on the false premise that we must find a way to “reconcile[ ]” Volt and Mastrobuono. Id. But as we explained, supra at Part III, the Supreme Court has already clarified the relationship between the two cases. In Volt, the Court followed its rule of deferring to state court interpretations of private contracts so long as no federal rights are at stake. The Court had no such obligation in Mastrobuono because that case (like this one) originated in federal court. See Mastrobuono, 514 U.S. at 60 n. 4, 115 S.Ct. 1212; see also Volt, 489 U.S. at 474-76, 109 S.Ct. 1248. Judge Ambro is apparently unconvinced by Mas-trobuono’s method of distinguishing Volt, see Ambro Op. at 303 & n. 2, but whether we find Mastrobuono persuasive or not is of no moment. It is not the province of this Court to craft a rule based on an assumption that the Supreme Court was wrong or that it could not have meant what it said. As we noted earlier, numerous cases have examined the interrelationship between Volt and Mastrobuono. See [299]*299supra pp. 295-96 & n. 5. We have not located, nor has Judge Ambro cited, a single case that “reconciled” the Court’s two opinions on the basis proposed by Judge Ambro.
The second reason for our disagreement with Judge Ambro’s proposal is that we believe that it would not effectively advance its stated purpose of effectuating the intent of most contracting parties. Judge Ambro concludes his concurrence by arguing that “custom and practice among contract drafters” counsel in favor of construing contracts such as this one as incorporating arbitration standards borrowed from state law. Ambro Op. at 308. But that would not happen even under Judge Ambro’s approach; rather, Judge Ambro’s approach would have courts construe contracts like this one as incorporating all state arbitration rules that are “procedural” in nature, but only those “substantive” rules that do not “conflict” with the FAA. Though reasonable people may quarrel over whether most parties to contracts such as the one before us would wish to be bound by the FAA’s default standards or would instead choose to be bound by standards borrowed from state law, we think it most unlikely that any sizeable number of parties would wish to be bound by some federal standards and some state ones.
Lastly, we believe that Judge Ambro’s proposal would unduly complicate the law in this area. Under Judge Ambro’s approach, arbitrators and courts seeking to determine whether a given rule was supplied by the FAA or was instead borrowed from state law would first need to classify the relevant rule as being either “substantive” or “procedural” for purposes of the FAA.8 It is possible that arbitrators and courts would simply import the distinctions that have been drawn in the diversity context pursuant to Erie Railroad Co. v. Tompkins, 304 U.S. 64, 58 S.Ct. 817, 82 L.Ed. 1188 (1938), but the jurisprudence in that area is not always a model of clarity, and, at all events, we do not understand why distinctions drawn in a totally different context would necessarily transfer well to the FAA.
The problematic nature of Judge Am-bro’s proposal would only increase in any case where the party seeking vacatur complained about multiple issues, at least one of which was “procedural” and at least one of which “substantive” (however those terms are defined). In such a case, a reviewing court could be required to apply some rules borrowed from state law (i.e., “procedural” rules and the relevant state’s “substantive” rules that do not conflict with the FAA) and some rules taken from the FAA (i.e., “substantive” rules where the rule from the relevant state is in “conflict” with the FAA). Issues involving va-catur are difficult enough without the additional challenge of balancing and applying multiple legal regimes within the same case. For all of these reasons, we decline to adopt Judge Ambro’s proposal.
[300]*300C.
Applying our rule to the facts of this case yields an simple answer. The LCOA contains only a generic choice-of-law clause and there is no extrinsic evidence of an intent to contract out of the FAA’s default regime. We therefore hold that the District Court was correct in concluding that the FAA standards of review govern this case.
V.
Applying the FAA standards, we agree with the District Court that the arbitrator exceeded the scope of his authority. Though judicial review under the FAA is “narrowly circumscribed,” Local 863 Int’l Bhd. of Teamsters v. Jersey Coast Egg Producers, Inc., 773 F.2d 530, 533 (3d Cir.1985), the scope of an arbitrator’s authority is defined and confined by the agreement to arbitrate, see, e.g., Swift Indus., Inc. v. Botany Indus., Inc., 466 F.2d 1125, 1131 (3d Cir.1972). Accordingly, the FAA provides that a court “may make an order vacating [an] award ... [wjhere the arbitrators exceeded their powers.” 9 U.S.C. § 10(a)(4).
It is undisputed that the only issue presented to the arbitrator was whether RPS’s “termination of [Kayser] was within the terms of [the LCOA].” The District Court found that the arbitrator exceeded his powers, and it is manifest that the court’s conclusion was based on the text of the arbitrator’s written decision, the relevant portions of which are set out in pages 290 of this opinion. The court noted that the arbitrator had “fram[ed] the issue as one of wrongful or proper termination” and then “proceed[ed] to discuss the inadequacy of RPS’ procedure for warning independent contractors of performance deficiencies and finally conclude[d] that ‘the RPS system[is] lacking in due process toward the Claimant contractor.’ ” Dist. Ct. Op. at 14 (quoting Arb. Op.). The court stressed that “[t]he arbitration provision clearly limits the arbitrator’s authority to decide only whether the termination was within the terms of the Agreement, not to examine the fairness of the extrinsic procedures by which RPS notifies contractors of problems.” Id. It concluded that “[b]y grounding his decision on such considerations of fairness and thereby altering the Agreement to require certain pre-termi-nation procedures, the arbitrator overstepped the bounds of the authority granted to him by the Agreement.” Id. at 14-15. On appeal, RPS essentially adopts the District Court’s analysis.
Kayser advances three arguments in response. He rightly notes that Mechmann was not required to justify or rationalize his decision. See Local 863, 773 F.2d at 534. He also correctly observes that the arbitrator was entitled to make suggestions that went beyond the scope of his authority to decide. See Apex Fountain Sales, Inc. v. Kleinfeld, 818 F.2d 1089, 1095 (3d Cir.1987). Finally, though acknowledging that the arbitrator made “reference to due process issues,” Kayser stresses the eighth paragraph of Mechmann’s decision, which states: “I conclude that this was a wrongful termination by RPS of the LCOA.” Kayser argues that Mechmann did not, “in the final analysis, tie his reference to the due process issues into his decision.” Instead, Kayser claims, “the reference to due process [was] simply surplus, [was] irrelevant to Mr. Mechmann’s decision and should not have been used as a basis by the court to suggest that the Arbitrator went beyond his authority.” Appellant’s Br. at 14-15.
Before parsing the arbitrator’s opinion to determine whether he exceeded his authority, we must first confront the question whether it is proper to do so. Kayser does not argue that courts are barred from [301]*301examining an arbitrator’s statement of reasons, and, at all events, such a contention would be contrary to our cases. See United States Steel & Carnegie Pension Fund v. McSkimming, 759 F.2d 269, 271 (3d Cir.1985) (vacating an arbitrator’s award that ordered the payment of pension benefits where an examination of the arbitrator’s written decision convinced the Court that “the arbitrator’s award [was] patently based on statutory interpretation rather than the Plan”); see also Pennsylvania Power Co. v. Local Union # 272 of the Int’l Bhd. of Elec. Workers, 886 F.2d 46, 49 (3d Cir.1989) (concluding that a particular dispute was not arbitrable and remarking that “[n]othing in the arbitrator’s two rulings convinces us to the contrary” because the opinions revealed that the arbitrator had based his decision “on the general desirability of arbitration” rather than the language of the agreement).
On the other hand, we have also cautioned against exploiting “an ambiguity” in an arbitrator’s decision to support “an inference” that he or she exceeded his or her authority. NF&M Corp. v. United Steelworkers of Am., 524 F.2d 756, 759 (3d Cir.1975). The reason for this policy is that “[t]o require opinions free of ambiguity [could] lead arbitrators to play it safe by writing no supporting opinions. This would be undesirable, for a well-reasoned opinion tends to engender confidence in the integrity of the process and aids in clarifying the underlying agreement.” United Steelworkers of Am. v. Enterprise Wheel & Car Corp., 363 U.S. 593, 598, 80 S.Ct. 1358, 4 L.Ed.2d 1424 (1960).
We distill the following principles from our precedents: (1) a reviewing court should presume that an arbitrator acted within the scope of his or her authority; (2) this presumption may not be rebutted by an ambiguity in a written opinion; but (3) a court may conclude that an arbitrator exceeded his or her authority when it is obvious from the written opinion.
Under these standards, we hold that the District Court was correct in concluding that Mechmann exceeded his authority. Although Mechmann’s opinion begins by acknowledging that his authority is set forth in Section 9.3(e) of the LCOA, it contains only four paragraphs of substantive discussion — all of which focus on the way in which RPS communicated to Kay-ser that it was dissatisfied with his performance. See supra page 290. The conclusion that arbitrator Mechmann derived from this discussion was not that Kayser’s termination had been contrary to the LCOA (the question actually before him), but rather that “the RPS system [was] lacking in due process toward [Kayser].” Kayser would have us believe that the arbitrator devoted four paragraphs to “mere dicta,” but not one sentence to explaining his supposed “holding” that the termination violated the terms of the agreement. That reading is simply not supported by the arbitrator’s opinion, which demonstrates, beyond peradventure, that Mechmann ruled on an issue that was not properly before him.
Moreover, as noted by RPS, the arbitrator never framed or decided the issue in the terms stated by the LCOA: “[W]hether the termination of [Kayser] was within the terms of this Agreement.” Instead, Mechmann stated that “[t]he main question” was whether “the termination” was “wrongful or proper.” And Mechmann’s “conelu[sion]” was “that this was wrongful termination by RPS of the LCOA,” not that the termination violated “the terms of’ the LCOA. Though these latter two references, standing alone, would not suffice to show that the arbitrator exceeded his authority, they lend further support to our conclusion that he did so. We hold that the District Court was correct to va[302]*302cate the arbitrator’s award, and will therefore affirm its order.9