DC Federal Court Rejects Employee Challenge to Arbitration Agreement

Friday, April 26, 2013 by Team PCT Law Group

An employee who claimed an agreement he entered to arbitrate all employment related claims was unconscionable has his challenged rejected as the Court found the arbitration agreement to be neither procedurally or substantively unconscionable.

In the case of Fox v. Computer World Services Corp., et al. (2013), when Plaintiff Phillip Fox (“Fox”) began his employment with Computer World Services Corp. and C2 Essential, Inc. (joint employers of Fox and collectively referred to as “Defendants”) he electronically signed a number of forms, one of which was an arbitration agreement.  The arbitration agreement provided that the parties agreed to arbitrate, inter alia, any claims alleging violation of federal and state statutes.  Approximately eighteen months after he began working for Defendants, Fox’ employment was terminated.  Fox alleged that his job termination was in violation of the Age Discrimination in Employment Act, and also alleged retaliation and violations of the District of Columbia Human Rights Act.  Fox refused to arbitrate his claims and instead sued Defendants in state court.  Defendants removed the case to federal court and also filed a motion to dismiss and to compel arbitration.    

For his part, Fox challenged the arbitration agreement and claimed it was procedurally unconscionable because it was buried within a larger series of employment documents; it was presented to him on a take it or leave it basis; and, he did not understand that by acknowledging the arbitration agreement he was agreeing to the terms within the agreement.  Fox also challenged the agreement because he signed it electronically.  The Court rejected each of these arguments and found that the Agreement to Arbitrate was presented in a separate document and the title of the document was in all caps and in bold font.  In addition, the Court found that immediately before the signature line of the agreement was an acknowledgement, again in all caps, which stated that the signatory read and understood the terms of the agreement and was been provided the opportunity to discuss the agreement with legal counsel.  Finding that Fox had a choice as to whether to enter the agreement, acknowledged that he read and understood the agreement and was given a chance to consult legal counsel, the Court found the arbitration agreement was not procedurally unconscionable. 

Fox also raised a number of substantive challenges to the arbitration agreement, including challenging the agreement on the grounds that it contained a fee-sharing provision wherein all parties were required to share the fees and costs of the arbitrator in an amount and manner determined by the arbitrator.  While the Court easily disposed of most of Fox’ substantive challenges to the arbitration agreement, the fee- sharing issue raised by Fox and whether forcing him to go through arbitration would be prohibitively expensive was not so easily resolved.  Ultimately, the Court found that the risk that Fox might incur prohibitive costs was too speculative to invalidate the agreement.  The Court relied on the fact that Defendants had waived the fee-sharing provision in the agreement, and that the agreement (although somewhat ambiguous) appeared to allow the arbitrator discretion as to how to allocate fees and costs. Therefore, Fox’ argument as to what portion of those fees he would have to bear were too speculative to deem the arbitration agreement substantively unconscionable.  The Court held that the arbitration agreement was enforceable and compelled Fox to arbitrate his claims.

Written By Malik K. Cutlar 

Maryland Highest Court Determines Proper Calculation of Lost Profits in Contract Case

Thursday, April 25, 2013 by Team PCT Law Group

Since the amount of damages sought on a lost profits claim can be substantial, any variations in the standard will likely have a drastic impact on the recovery.  The Maryland Court of Appeals (the highest court in the state) in CR-RSC Tower I, LLC v. RSC Tower I, LLC recently addressed the issue of whether the trial court properly excluded post-breach market conditions to mitigate consequential lost profits in a jury trial which resulted in an award of $36 Million in damages. 

The landlord defendants in CR-RSC Tower I, LLC deliberately breached a real estate agreement causing plaintiff developer’s financing to fall through.  The developer sued for breach of contract and sought recovery of lost profits basing its market projections at the time of the breach.  The landlords did not dispute the breach, but countered that the current market conditions were relevant and necessary to meet the requirement that lost profits be proven with “reasonable certainty.” The landlords sought to offer the testimony of an expert to show that the developer would not have suffered any damages given the subsequent downturn in the real estate market. 

The Court explained that the contract in this case did not address or allocate the possibility of future market downturns.  The only evidence established that, at the time the parties entered into the agreement, the parties contemplated a relatively stable market and did not foresee the cataclysmic crash of real estate.  Thus, evidence of post-breach booms or even busts was not relevant to the determination of the expected value of performance as of the time of breach.  As a result, the Court upheld the trial court’s exclusion of the defendants’ evidence of “post-breach market conditions.” 

Written By Angela H. France

Fourth Circuit Substantially Reduces Jurys Emotional Damages Award

Wednesday, April 24, 2013 by Team PCT Law Group

Please see, Angela France's article featured within Virginia Business Law Update.


Written By Angela H. France 

US Citizenship and Immigration Services Releases New & Revised Federal I-9 Form

Wednesday, April 24, 2013 by Team PCT Law Group

Please see, Angela France's article featured within Virginia Business Law Update.

http://www.virginiabusinesslawupdate.com/2013/04/articles/small-business-1/us-citizenship-and-immigration-services-releases-new-revised-federal-i9-form/

Written By Angela H. France 

Government Contractor Teaming Agreement Ruled Unenforceable

Monday, April 22, 2013 by Team PCT Law Group

Please see, Malik Cutlar's article featured within Virginia Business Law Update.

Written By Malik K. Cutlar

Use of Misappropriated Trade Secret Not Required For a Trade Secrets Act Violation

Tuesday, April 16, 2013 by Team PCT Law Group

If an employee misappropriates their current or former employer’s proprietary information, and discloses such information to its new employer and/or any other unauthorized person(s), that is enough to establish a violation under the Virginia Uniform Trade Secrets Act (“VUTSA”) so says the Virginia Supreme Court. There is no requirement under the Act that the employee or new employer actually use the misappropriated information to compete with the former employer.

In the case of Geographic Services, Inc. v. Collelo, et al. (2012), the Virginia Supreme Court held that once an employer establishes the existence of a trade secret, all that they are then required to show is that the trade secret was misappropriated as that term is defined under the Trade Secrets Act. The entity from which the trade secret was misappropriated does not have to show that defendants used the trade secret in order to establish a claim under the VUTSA and recover damages. Disclosure of the trade secret is sufficient where it can be shown that the new employer and/or person to whom the trade secret was disclosed knew, or had reason to know, that the trade secret was acquired by improper means. In such cases, where the plaintiff cannot readily prove measurable damages, then the VUTSA provides that the court can impose a reasonable royalty upon the wrongdoers for the unauthorized disclosure of the trade secret.

This decision by Virginia’s highest court provides a cautionary note for Virginia employers: if you know, or should have known, that an employee has obtained proprietary information from its prior employer without its knowledge, you could be on the hook for damages if the employee discloses the information to your company – even if your company never uses the information. The disclosure, in and of itself, will be enough to expose companies to monetary damages. Conversely, companies in which an employee has taken proprietary information can seek legal redress and possibly obtain damages even if the employee and its new company did not use the information.

Written By Malik K. Cutlar

Trademark Licensing Agreement Foreclosed Naked Licensing Defense

Tuesday, April 16, 2013 by Team PCT Law Group

Please see, Angela France's article featured within Virginia Business Law Update.

http://www.virginiabusinesslawupdate.com/2013/04/articles/intellectual-property/trademark-licensing-agreement-foreclosed-naked-licensing-defense/

Written By Angela H. France 


PCT Law Group Blog

Space Act Agreements: An Overview

Tuesday, June 12, 2012 by Team PCT Law Group

stacks of paper

Image credit:Florian

Good and bad. Heaven and hell. Ice cream and Brussels sprouts. Falcon 9 and paper rockets. Space Act agreements and government procurement contracts. Popular opinion seems to clump NASA Space Act Agreements (SAAs) in with all that is good and right with the world while traditional FAR-based contracting is viewed as something to be avoided.  In order to find out why space act agreements are viewed so positively, let’s take a look at what an SAA is, the different flavors they come in and what they’re used for.

What is a Space Act Agreement?

When Congress created NASA, they gave the agency the ability to “enter into…contracts, leases, cooperative agreements, or other transactions as may be necessary in the conduct of its work and on such terms as it may deem appropriate….” NASA uses its “other transactions” authority to form agreements with private companies, other government agencies, and universities to carry out specific objectives. These agreements are commonly known as Space Act Agreements because the law creating NASA and giving them “other transaction” authority is commonly known as the Space Act.

SAAs may take the form of contracts, grants, cooperative agreements, or other relationships. NASA and its partner in an SAA can start from an essentially blank slate in order to create their agreement. This provides enormous flexibility in identifying milestones, establishing responsibilities, and sharing workloads.

SAAs establish how NASA resources like personnel, equipment, and testing facilities may be used to achieve the specific goal defined in the SAA. For example, University of Colorado and BioServe Space Technologiesentered into an SAA to spur use of the International Space Station (ISS) as a national lab. Under their 2008 agreement, NASA provided rides for BioServe experiments to the ISS. BioServe agreed to reimburse NASA for the launch services.

Three flavors of SAA: Reimbursable, Nonreimbursable, and Funded

SAAs generally come in three flavors: reimbursable, nonreimbursable, and funded.

In nonreimbursable agreements, NASA and its agreement partner use limited NASA and partner resources to achieve some goal which furthers NASA’s goals. Under a nonreimbursable SAA, NASA and the partner company work together but no money is exchanged. The partner company gets free access to (limited) NASA resources! Nonreimbursable SAAs are sometimes used when NASA is willing to provide technical expertise and facilities, like wind tunnel time, but is unable to provide additional funding. ATK has entered into several nonreimbursable SAAs related to NASA’s ongoing effort to develop commercial space launch systems. These agreements allow NASA to provide technical expertise to ATK as they develop their Liberty launch system.

Reimbursable SAAs allow the partner company a bit more flexibility, but at a cost. The partner company may use NASA’s resources for their own purposes, but the company must reimburse NASA for the use of NASA resources. NASA can’t provide anything under a reimbursable SAA unless the resources are not “reasonably available” in the US commercial market. BioServe’s 2008 SAA met this requirement because, at the time, the Space Shuttle was the only US launch vehicle capable of docking with the ISS!

Funded SAAs are the most attention grabbing because they are currently used to fund CCDevCCiCap, andCOTS. Funded SAAs are only permitted where NASA’s goals cannot be achieved via any other type of agreement, such as a FAR contract, grant, or some other type of SAA. A funded SAA involves NASA providing resources and funds to a partner company. The funds and resources are used to further NASA’s goals, like creating a commercially developed cargo delivery system for the ISS. Funded SAAs, like the agreements that partially funded SpaceX’s development of the Falcon 9 rocket and Dragon capsule, are used “only sparingly”, when traditional funding methods are inappropriate.

Can they be used for anything?

Image credit: Michael Altenhofen/SpaceX

NASA’s charter and other federal laws like the Chiles Act prevent NASA from using SAAs for most contract formation. The process for entering into a Space Act Agreement is laid out in NASA’s 170+ page Space Act Agreements Guide. Despite the hurdles, about 250 Space Act Agreements are signed a year, providing may companies, universities, and other government agencies access to the unique skills and equipment NASA has. Space Act Agreements have helped develop the Dragon capsule, next-generation robonauts, and opened up the ISS for use as a research lab.

Many Space Act Agreements are available on NASA center websites. For example, Kennedy Space Center has released the CCDev Round 2 Space Act Agreements here. Space Act Agreements from COTS have been published by Johnson Space Center here.

Written by Andrew Rush