← Resources

Working with counsel

Prepare a local-government software negotiation for counsel

Separate current service, proposed commitments and a team member’s public role before counsel reviews a local-government software engagement.

If a city, county or other local-government customer is already using your software, give counsel two separate records: what is happening today and what the proposed agreement would change. Identify any public role a team member holds with the customer, and describe their involvement in this relationship. Ask counsel to assess that connection before treating contract wording as the whole assignment.

A worked handoff

Fictional example: a town department has been using a vendor’s scheduling tool with ten staff accounts. A draft order form proposes forty accounts and support for two additional departments. The founder sits on a town advisory committee, and the team has not established whether that role affects this engagement. The town’s legal office asks to discuss the draft with the vendor’s lawyer.

These invented facts are a preparation exercise, not a conclusion that the arrangement is permitted or prohibited.

Current service

What the team can establish
Operations confirms the ten active accounts, departments using them, data held and support actually provided. Attach existing terms, emails and approvals; flag anything missing.

Question for counsel
What obligations and unresolved issues arise from the current arrangement, and what should happen while the review is open?

Proposed service

What the team can establish
The draft adds accounts, departments and support. Sales has not confirmed the support commitment with Operations. Keep that commitment marked proposed.

Question for counsel
What changes need negotiation, and what customer approval or procurement steps need checking?

Public role

What the team can establish
Record the founder’s committee duties, involvement in this customer relationship and any existing disclosures or written guidance. Keep sensitive records in the agreed restricted location.

Question for counsel
Which rules and decision makers apply to this role, and what advice or action is needed before further participation?

The request to counsel

“Please review our current software arrangement and the proposed expansion with a local-government customer. The attached record separates confirmed service from proposed commitments and identifies a team member’s public role. Please assess the relevant contract, procurement and ethics questions; identify missing records and any time-sensitive action; and agree who should handle further communications. We need a marked draft and a short list of decisions, owners and next steps.”

Before sharing a detailed matter file, ask prospective counsel how to provide the information needed for their conflict check. Agree who they will represent and whether any individual needs separate advice. Use an approved channel for sensitive documents; the public example above requires none.

Define the engagement before the next exchange

Ask for experience with the relevant state and local public body as well as software agreements. Agree whether the engagement covers reviewing the drafts, communicating with the customer’s lawyer, examining the public-role issue, and any approval or advisory process counsel identifies. Record exclusions and how additional work will be agreed.

Keep the public-role and approval questions open until counsel identifies the decisions needed, who can make them and what record to retain. Flag current operations and deadlines for counsel’s advice; this exercise is not permission to continue, stop or expand service.

For an existing U.S. federal procurement contract, see the separate government contract change guide. Its federal modification rules are not the basis for this local-government preparation exercise.

Back to top ↑