OSB August 2005

Can a county counsel who advises county employees on county business also negotiate the county's collective-bargaining agreement against those same employees?

Short answer: The opinion concludes county counsel may negotiate the collective-bargaining agreement because the county is the lawyer's only client; advising employees on county business does not make them clients, so no current- or former-client conflict arises, though counsel may need to clarify whom they represent.

Apply this to your situation

This page answers the general question as of 2005. Ezel answers yours: whether it's allowed on your facts, under the current Oregon Rules of Professional Conduct, with citations.

Currency note: this opinion is from 2005
Subsequent statutory amendments, court decisions, or later opinions or rule amendments may have changed the analysis. Treat this page as historical context, not current legal advice. Verify current law before relying on any specific rule, deadline, or remedy mentioned here.
Disclaimer: Advisory only. Not binding precedent.
About this page: The plain-English summary, reader guidance, and Q&A below were written by Ezel based on the official ethics opinion. The original opinion (linked on this page as a PDF) is the authoritative source for any reliance.
View original ethics opinion (PDF)

Plain-English summary

County counsel is employed by the county and assigned to negotiate the county's collective-bargaining agreements with county employees. County counsel also advises county employees on various county matters, but not on personal matters. The opinion asks whether county counsel may negotiate the collective-bargaining agreement against those employees.

The opinion answers yes. It applies Oregon RPC 1.13(a), under which a lawyer employed by an organization represents the organization. On these facts, county counsel has only one client, the county. The fact that county counsel may speak with county employees about county matters does not transform those employees into county counsel's clients.

Because county counsel has only one client, the opinion concludes there can be no current- or former-client conflict under Oregon RPC 1.7 or RPC 1.9 as a matter of law. The opinion adds, however, that county counsel may have an obligation under Oregon RPC 1.13(f) to explain that counsel represents the county only when counsel knows or reasonably should know that the county's interests are adverse to those of the employees counsel is dealing with.

In practice

The opinion holds that, under Oregon RPC 1.13 as it stood at the time of the opinion, a government lawyer who represents the entity has the entity as the sole client; routine advice to employees about entity business does not create individual attorney-client relationships, so adverse negotiation against those employees raises no RPC 1.7 or RPC 1.9 conflict. The analysis turns on client identity. Where the entity's interests are adverse to the constituents counsel is dealing with, RPC 1.13(f) calls for counsel to clarify whom counsel represents. Verify the current text of Oregon RPC 1.13 before relying on any specific point.

Common questions

Q: I'm county counsel and I advise our staff on county business. Can I negotiate the union contract against them?

A: Yes. The opinion concludes the county is your only client; advising employees on county matters does not make them your clients, so there is no current- or former-client conflict.

Q: Do the employees become my clients just because I give them advice on county matters?

A: No. The opinion concludes that speaking with employees about county matters does not transform them into the lawyer's clients under RPC 1.13(a).

Q: Do I have to tell the employees anything about whom I represent?

A: Under RPC 1.13(f), counsel must explain that they represent the county only when counsel knows or reasonably should know the county's interests are adverse to the employees being dealt with.

Background and rules framework

The opinion interprets Oregon RPC 1.13 (organization as client), including the constituent-clarification duty in RPC 1.13(f), and explains why RPC 1.7 (current-client conflicts) and RPC 1.9 (former-client conflicts) do not apply when there is a single client. These correspond to Model Rules 1.13, 1.7, and 1.9.

Citations and references

Rules of Professional Conduct:

  • Oregon RPC 1.13(a), (f) / Model Rule 1.13 (organization as client)
  • Oregon RPC 1.7 / Model Rule 1.7 (current-client conflicts)
  • Oregon RPC 1.9 / Model Rule 1.9 (former-client conflicts)

Cases:

  • In re Harrington, 301 Or 18, 718 P2d 725 (1986)

Other opinions cited:

  • OSB Formal Ethics Op. No. 2005-46 (identifying the client)
  • OSB Formal Ethics Op. No. 2005-57 (single-client analysis)

See also

Source

Get today's answer for your situation

You just read a 2005 opinion on this question. Ezel checks the current Oregon Rules of Professional Conduct and answers your specific situation, with citations.

Opens in Ezel Pro. Every answer cites the rules it relies on.