Agency

Nature of Agency Relationships

An agent is a person who acts in the name of and on behalf of another, having been given and assumed some degree of authority to do so. Most organized human activity—and virtually all commercial activity— is carried on through agency. No corporation would be possible, even in theory, without such a concept. We might say “General Motors is building cars in China,” for example, but we can’t shake hands with General Motors. “The General,” as people say, exists and works through agents. Likewise, partnerships and other business organizations rely extensively on agents to conduct their business. Indeed, it is not an exaggeration to say that agency is the cornerstone of enterprise organization. In a partnership each partner is a general agent, while under corporation law the officers and all employees are agents of the corporation.

The existence of agents does not, however, require a whole new law of torts or contracts. A tort is no less harmful when committed by an agent; a contract is no less binding when negotiated by an agent. What does need to be taken into account, though, is the manner in which an agent acts on behalf of his principal and toward a third party.

Types of Agents

There are five types of agents.

General Agent

The general agent possesses the authority to carry out a broad range of transactions in the name and on behalf of the principal. The general agent may be the manager of a business or may have a more limitedbut nevertheless ongoing role—for example, as a purchasing agent or as a life insurance agent authorized to sign up customers for the home office. In either case, the general agent has authority to alter the principal’s legal relationships with third parties. One who is designated a general agent has the authority to act in any way required by the principal’s business. To restrict the general agent’s authority, the principal must spell out the limitations explicitly, and even so the principal may be liable for any of the agent’s acts in excess of his authority.

Normally, the general agent is a business agent, but there are circumstances under which an individual may appoint a general agent for personal purposes. One common form of a personal general agent is the person who holds another’s power of attorney. This is a delegation of authority to another to act in his stead; it can be accomplished by executing a simple form, such as the one shown in Figure 38.2 “General Power of Attorney”. Ordinarily, the power of attorney is used for a special purpose—for example, to sell real estate or securities in the absence of the owner. But a person facing a lengthy operation and recuperation in a hospital might give a general power of attorney to a trusted family member or friend.

Special Agent

The special agent is one who has authority to act only in a specifically designated instance or in a specifically designated set of transactions. For example, a real estate broker is usually a special agent hired to find a buyer for the principal’s land. Suppose Sam, the seller, appoints an agent Alberta to find a buyer for his property. Alberta’s commission depends on the selling price, which, Sam states in a letter to her,

“in any event may be no less than $150,000.” If Alberta locates a buyer, Bob, who agrees to purchase the property for $160,000, her signature on the contract of sale will not bind Sam. As a special agent, Alberta had authority only to find a buyer; she had no authority to sign the contract.

Agency Coupled with an Interest

An agent whose reimbursement depends on his continuing to have the authority to act as an agent is said to have an agency coupled with an interest if he has a property interest in the business. A literary or author’s agent, for example, customarily agrees to sell a literary work to a publisher in return for a percentage of all monies the author earns from the sale of the work. The literary agent also acts as a collection agent to ensure that his commission will be paid. By agreeing with the principal that the agency is coupled with an interest, the agent can prevent his own rights in a particular literary work from being terminated to his detriment.

Subagent

To carry out her duties, an agent will often need to appoint her own agents. These appointments may or may not be authorized by the principal. An insurance company, for example, might name a general agent to open offices in cities throughout a certain state. The agent will necessarily conduct her business through agents of her own choosing. These agents are subagents of the principal if the general agent had the express or implied authority of the principal to hire them. For legal purposes, they are agents of both the principal and the principal’s general agent, and both are liable for the subagent’s conduct although normally the general agent agrees to be primarily liable.

Servant (Employee)

The final category of agent is the servant. Until the early nineteenth century, any employee whose work duties were subject to an employer’s control was called a servant; we would not use that term so broadly in modern English. The Restatement (Second) of Agency, Section 2, defines a servant as “an agent employed by a master [employer] to perform service in his affairs whose physical conduct in the performance of the service is controlled or is subject to the right to control by the master.”

Independent Contractor

Not every contract for services necessarily creates a master-servant relationship. There is an important distinction made between the status of a servant and that of an independent contractor. According to the Restatement (Second) of Agency, Section 2, “an independent contractor is a person who contracts with another to do something for him but who is not controlled by the other nor subject to the other’s right to control with respect to his physical conduct in the performance of the undertaking.” As the name implies, the independent contractor is legally autonomous. A plumber salaried to a building contractor is an employee and agent of the contractor. But a plumber who hires himself out to repair pipes in people’s homes is an independent contractor. If you hire a lawyer to settle a dispute, that person is not your employee or your servant; she is an independent contractor. The terms “agent” and “independent contractor” are not necessarily mutually exclusive. In fact, by definition, “… an independent contractor is an agent in the broad sense of the term in undertaking, at the request of another, to do something for the other. As a general rule the line of demarcation between an independent contractor and a servant is not clearly drawn.” [1]

This distinction between agent and independent contractor has important legal consequences for taxation, workers’ compensation, and liability insurance. For example, employers are required to withhold income taxes from their employees’ paychecks. But payment to an independent contractor, such as the plumber for hire, does not require such withholding. Deciding who is an independent contractor is not always easy; there is no single factor or mechanical answer. In Robinson v. New York Commodities Corp., an injured salesman sought workers’ compensation benefits, claiming to be an employee of the New York Commodities Corporation. [2] But the state workmen’s compensation board ruled against him, citing a variety of factors. The claimant sold canned meats, making rounds in his car from his home. The company did not establish hours for him, did not control his movements in any way, and did not reimburse him for mileage or any other expenses or withhold taxes from its straight commission payments to him. He reported his taxes on a form for the self-employed and hired an accountant to prepare it for him. The  court agreed with the compensation board that these facts established the salesman’s status as an independent contractor.

The factual situation in each case determines whether a worker is an employee or an independent contractor. Neither the company nor the worker can establish the worker’s status by agreement. As the North Dakota Workmen’s Compensation Bureau put it in a bulletin to real estate brokers, “It has come to the Bureau’s attention that many employers are requiring that those who work for them sign ‘independent contractor’ forms so that the employer does not have to pay workmen’s compensation premiums for his employees. Such forms are meaningless if the worker is in fact an employee.”  Vizcaino v. Microsoft Corporation.

In addition to determining a worker’s status for tax and compensation insurance purposes, it is sometimes critical for decisions involving personal liability insurance policies, which usually exclude from coverage accidents involving employees of the insureds. General Accident Fire & Life Assurance Corp v. Pro Golf Association [3]involved such a situation. The insurance policy in question covered members of the Professional Golfers Association. Gerald Hall, a golf pro employed by the local park department, was afforded coverage under the policy, which excluded “bodily injury to any employee of the insured arising out of and in the course of his employment by the insured.” That is, no employee of Hall’s would be covered (rather, any such person would have coverage under workers’ compensation statutes). Bradley Martin, age thirteen, was at the golf course for junior league play. At Hall’s request, he agreed to retrieve  or “shag” golf balls to be hit during a lesson Hall was giving; he was—as Hall put it—to be compensated “either through golf instructions or money or hotdogs or whatever.” During the course of the lesson, a golf ball hit by Hall hit young Martin in the eye. If Martin was an employee, the insurance company would be liable; if he was not an employee, the insurance company would not liable. The trial court determined he was not an employee. The evidence showed: sometimes the boys who “shagged” balls got paid, got golfing instructions, or got food, so the question of compensation was ambiguous. Martin was not directed in how to perform (the admittedly simple) task of retrieving golf balls, no control was exercised over him, and no equipment was required other than a bag to collect the balls: “We believe the evidence is susceptible of different inferences.…We cannot say that the decision of the trial court is against the manifest weight of the evidence.”

Employee versus Independent Contractor

Vizcaino v. Microsoft Corp., 97 F.3d 1187 (9th Cir. 1996)

Reinhardt, J. Large corporations have increasingly adopted the practice of hiring temporary employees or independent contractors as a means of avoiding payment of employee benefits, and thereby increasing their profits. This practice has understandably led to a number of problems, legal and otherwise. One of the legal issues that sometimes arises is exemplified by this lawsuit. The named plaintiffs, who were classified by Microsoft as independent contractors, seek to strip that label of its protective covering and to obtain for themselves certain benefits that the company provided to all of its regular or permanent employees. After certifying the named plaintiffs as representatives of a class of “common-law employees,” the district court granted summary judgment to Microsoft on all counts. The plaintiffs…now appeal as to two of their claims: a) the claim…that they are entitled to savings benefits under Microsoft’s Savings Plus Plan (SPP); and b) that…they are entitled to stock-option benefits under Microsoft’s Employee Stock Purchase Plan (ESPP). In both cases, the claims are based on their contention that they are common-law employees.

Microsoft, one of the country’s fastest growing and most successful corporations and the world’s largest software company, produces and sells computer software internationally. It employs a core staff of permanent employees. It categorizes them as “regular employees” and offers them a wide variety of benefits, including paid vacations, sick leave, holidays, short-term disability, group health and life insurance, and pensions, as well as the two benefits involved in this appeal. Microsoft supplements its core staff of employees with a pool of individuals to whom it refuses to pay fringe benefits. It previously classified these individuals as “independent contractors” or “freelancers,” but prior to the filing of the action began classifying them as “temporary agency employees.” Freelancers were hired when Microsoft needed to expand its workforce to meet the demands of new product schedules. The company did not, of course, provide them with any of the employee benefits regular employees receive.

The plaintiffs…performed services as software testers, production editors, proofreaders, formatters and indexers. Microsoft fully integrated the plaintiffs into its workforce: they often worked on teams along with regular employees, sharing the same supervisors, performing identical functions, and working the same core hours. Because Microsoft required that they work on site, they received admittance card keys, office equipment and supplies from the company.

Freelancers and regular employees, however, were not without their obvious distinctions. Freelancers wore badges of a different color, had different electronic-mail addresses, and attended a less formal orientation than that provided to regular employees. They were not permitted to assign their work to others, invited to official company functions, or paid overtime wages. In addition, they were not paid through Microsoft’s payroll department. Instead, they submitted invoices for their services, documenting their hours and the projects on which they worked, and were paid through the accounts receivable department.

The plaintiffs were told when they were hired that, as freelancers, they would not be eligible for benefits. None has contended that Microsoft ever promised them any benefits individually. All eight named plaintiffs signed [employment agreements] when first hired by Microsoft or soon thereafter. [One] included a provision that states that the undersigned “agrees to be responsible for all federal and state taxes, withholding, social security, insurance and other benefits.” The [other one] states that “as an Independent Contractor to Microsoft, you are self-employed and are responsible to pay all your own insurance and benefits.” Eventually, the plaintiffs learned of the various benefits being provided to regular employees from speaking with them or reading various Microsoft publications concerning employee benefits.

In 1989 and 1990, the Internal Revenue Service (IRS)[,]…applying common-law principles defining the employer-employee relationship, concluded that Microsoft’s freelancers were not independent contractors but employees for withholding and employment tax purposes, and that Microsoft would thereafter be required to pay withholding taxes and the employer’s portion of Federal Insurance Contribution Act (FICA) tax. Microsoft agreed.…

After learning of the IRS rulings, the plaintiffs sought various employee benefits, including those now at issue: the ESPP and SPP benefits. The SPP…is a cash or deferred salary arrangement under § 401k of the Internal Revenue Code that permits Microsoft’s employees to save and invest up to fifteen percent of their income through tax-deferred payroll deductions.…Microsoft matches fifty percent of the employee’s contribution in any year, with [a maximum matching contribution]. The ESPP…permits employees to purchase company stock [with various rules].

Microsoft rejected the plaintiffs’ claims for benefits, maintaining that they were independent contractors who were personally responsible for all their own benefits.…

The plaintiffs brought this action, challenging the denial of benefits.

Microsoft contends that the extrinsic evidence, including the [employment agreements], demonstrates its intent not to provide freelancers or independent contractors with employee benefits[.]…We have no doubt that the company did not intend to provide freelancers or independent contractors with employee  benefits, and that if the plaintiffs had in fact been freelancers or independent contractors, they would not be eligible under the plan. The plaintiffs, however, were not freelancers or independent contractors. They were common-law employees, and the question is what, if anything, Microsoft intended with respect to persons who were actually common-law employees but were not known to Microsoft to be such. The fact that Microsoft did not intend to provide benefits to persons who it thought were freelancers or independent contractors sheds little or no light on that question.…

Microsoft’s argument, drawing a distinction between common-law employees on the basis of the manner in which they were paid, is subject to the same vice as its more general argument. Microsoft regarded the plaintiffs as independent contractors during the relevant period and learned of their common-law- employee status only after the IRS examination. They were paid through the accounts receivable department rather than the payroll department because of Microsoft’s mistaken view as to their legal status. Accordingly, Microsoft cannot now contend that the fact that they were paid through the accounts receivable department demonstrates that the company intended to deny them the benefits received by all common-law employees regardless of their actual employment status. Indeed, Microsoft has pointed to no evidence suggesting that it ever denied eligibility to any employees, whom it understood to be common- law employees, by paying them through the accounts receivable department or otherwise.

We therefore construe the ambiguity in the plan against Microsoft and hold that the plaintiffs are eligible to participate under the terms of the SPP.

[Next, regarding the ESPP] we hold that the plaintiffs…are covered by the specific provisions of the ESPP. We apply the “objective manifestation theory of contracts,” which requires us to “impute an intention corresponding to the reasonable meaning of a person’s words and acts.” [Citation] Through its incorporation of the tax code provision into the plan, Microsoft manifested an objective intent to make all common-law employees, and hence the plaintiffs, eligible for participation. The ESPP specifically provides:

It is the intention of the Company to have the Plan qualify as an “employee stock purchase plan” under Section 423 of the Internal Revenue Code of 1954. The provisions of the Plan shall, accordingly, be construed so as to extend and limit participation in a manner consistent with the requirements of that Section of the Code. (emphasis added)

[T]he ESPP, when construed in a manner consistent with the requirements of § 423, extends participation to all common-law employees not covered by one of the express exceptions set forth in the plan. Accordingly, we find that the ESPP, through its incorporation of § 423, expressly extends eligibility for participation to the plaintiff class and affords them the same options to acquire stock in the corporation as all other employees.

Microsoft next contends that the [employment agreements] signed by the plaintiffs render them ineligible to participate in the ESPP. First, the label used in the instruments signed by the plaintiffs does not control their employment status. Second, the employment instruments, if construed to exclude the plaintiffs from receiving ESPP benefits, would conflict with the plan’s express incorporation of § 423. Although Microsoft may have generally intended to exclude individuals who were in fact independent contractors, it could   not, consistent with its express intention to extend participation in the ESPP to all common-law employees, have excluded the plaintiffs. Indeed, such an exclusion would defeat the purpose of including § 423 in the plan, because the exclusion of common-law employees not otherwise accepted would result in the loss of the plan’s tax qualification.

Finally, Microsoft maintains that the plaintiffs are not entitled to ESPP benefits because the terms of the plan were never communicated to them and they were therefore unaware of its provisions when they performed their employment services.…In any event, to the extent that knowledge of an offer of benefits is a prerequisite, it is probably sufficient that Microsoft publicly promulgated the plan. In [Citation], the plaintiff was unaware of the company’s severance plan until shortly before his termination. The Oklahoma Supreme Court concluded nonetheless that publication of the plan was “the equivalent of constructive knowledge on the part of all employees not specifically excluded.”

We are not required to rely, however, on the [this] analysis or even on Microsoft’s own unwitting concession. There is a compelling reason, implicit in some of the preceding discussion, that requires us to reject the company’s theory that the plaintiffs’ entitlement to ESPP benefits is defeated by their previous lack of knowledge regarding their rights. It is “well established” that an optionor may not rely on an optionee’s failure to exercise an option when he has committed any act or failed to perform any duty “calculated to cause the optionee to delay in exercising the right.” [Citation] “[T]he optionor may not make statements or representations calculated to cause delay, [or] fail to furnish [necessary] information.…” Similarly, “[I]t is a principle of fundamental justice that if a promisor is himself the cause of the failure of performance, either of an obligation due him or of a condition upon which his own liability depends, he cannot take advantage of the failure.” [Citation]…

Applying these principles, we agree with the magistrate judge, who concluded that Microsoft, which created a benefit to which the plaintiffs were entitled, could not defend itself by arguing that the plaintiffs were unaware of the benefit, when its own false representations precluded them from gaining that knowledge. Because Microsoft misrepresented both the plaintiffs’ actual employment status and their eligibility to participate in the ESPP, it is responsible for their failure to know that they were covered by the terms of the offer. It may not now take advantage of that failure to defeat the plaintiffs’ rights to ESPP benefits. Thus, we reject Microsoft’s final argument.

Conclusion

For the reasons stated, the district court’s grant of summary judgment in favor of Microsoft and denial of summary judgment in favor of the plaintiffs is REVERSED and the case REMANDED for the determination of any questions of individual eligibility for benefits that may remain following issuance of this opinion and for calculation of the damages or benefits due the various class members.

 

CC license: Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0)- Saylor.org