Ethics, Compliance, and Procurement Boundaries

20.1 What Sales Teams Must Understand About Government Procurement Integrity

Procurement integrity: the principle that federal acquisitions must be conducted fairly, impartially, and without improper disclosure, influence, or preferential treatment. Sales teams should understand that government officials are not ordinary commercial buyers. They are stewards of public funds, and their conduct must protect competition and public confidence. FAR Part 3 describes government business as requiring high public trust and warns against conflicts of interest or even the appearance of conflict in government-contractor relationships.

The practical implication is simple: a government customer may like the company, believe the company is capable, and want the company’s market input, but the customer still cannot give the company unfair access, private evaluation information, or special treatment. Account executives must not interpret warmth, familiarity, or mission urgency as permission to cross procurement boundaries. In this market, the customer’s ability to buy safely is part of the sale.

Sales teams must be especially careful with nonpublic information. Federal procurement integrity rules address contractor bid or proposal information and source selection information, including protection against unauthorized disclosure. FAR 3.104 covers procurement integrity, including prohibitions, restrictions, disclosure protections, disqualification issues, and ethics advisory opinions related to former officials. 

Source selection information: information prepared for use by the government in evaluating bids or proposals, when its disclosure could compromise the procurement. Sales teams should never seek proposal rankings, evaluation plans, internal scoring, competitive range information, government cost estimates where protected, or evaluator views that have not been released through official channels. If an account executive receives information that appears nonpublic or competitively sensitive, the right response is not to use it quietly. The right response is to stop, document, and involve compliance, legal, or contracts leadership.

Contractor bid or proposal information: information submitted by another offeror that is not meant to be disclosed, such as pricing, technical approach, indirect rates, proprietary data, or proposal strategy. A contractor must not solicit, accept, or use a competitor’s protected information. This includes information that arrives through former employees, teaming partners, consultants, customer contacts, or careless documents. “We did not ask for it” is not a sufficient defense if the team recognizes sensitive information and uses it anyway.

Procurement integrity also affects timing. Before procurement is active, the government may conduct market research and communicate with industry. Once a solicitation is released, communication may be restricted to official channels. Salespeople must know which stage they are in. A conversation that is appropriate during market research may become inappropriate during evaluation. The safest account teams define communication rules for every major opportunity before the formal procurement window begins.

For sales leaders, procurement integrity should be translated into operating rules. Every priority account should have a known procurement-status view, a defined communication protocol for active opportunities, and a clear escalation path for sensitive information. The account executive should not have to improvise when a customer asks for input on draft requirements or when a partner shares competitive rumors. The company should already know what is acceptable, what requires review, and what must stop immediately.

Four questions are useful before any sensitive engagement. Is the information we are seeking available appropriately? Would the customer be permitted to share it with other vendors? Are we helping the government understand the market rather than asking for preferential treatment? Would our conduct look reasonable if reviewed after a protest? These questions do not replace legal analysis, but they create a field-level discipline that prevents most avoidable mistakes.

The key mindset is disciplined helpfulness. The contractor can educate the market, share lessons learned, provide technical insight, explain risks, and help the customer understand available solutions. It cannot ask the customer to tilt the field, reveal protected information, or make commitments the customer has no authority to make.

20.2 Appropriate vs. Inappropriate Customer Engagement

Appropriate customer engagement: communication that helps the government understand the market, clarify mission needs, assess risks, and prepare a fair acquisition. Examples include capability briefings before an active procurement, responses to RFIs and sources sought notices, participation in industry days, technical demonstrations, white papers, market education, delivery performance reviews, and formal Q&A during a solicitation. These interactions should be substantive and professional. The customer should receive useful information, not merely a sales pitch.

Appropriate engagement is usually transparent. The account team can explain why the meeting occurred, who attended, what was discussed, what information was provided, and what follow-up actions were taken. The conversation stays focused on mission problems, industry capabilities, implementation risks, and acquisition practicality. The contractor does not ask for special treatment. The customer does not disclose protected information. The account executive documents what matters and coordinates with capture, contracts, and legal when needed.

Inappropriate customer engagement: communication that seeks unfair advantage, protected information, private evaluation insight, improper influence, or commitments outside the customer’s authority. Examples include asking how the company is ranked during evaluation, requesting a competitor’s price, seeking unreleased evaluation criteria, encouraging a customer to write requirements that only the company can meet without legitimate justification, asking program staff to bypass the contracting officer during restricted communications, or pressing for assurances that the award is “ours.”

A useful test is whether the same communication would seem appropriate if it were described in a protest, audit, or inspector general review. If the account executive would be uncomfortable seeing the interaction summarized in writing, the interaction probably needs review. Government contracting is not only about actual fairness. It is also about the appearance of fairness. A customer may withdraw from useful engagement if the contractor creates avoidable risk.

Account teams should distinguish between shaping and steering. Shaping: helping the government understand realistic alternatives, risks, market practices, and implementation choices before a procurement is fixed. Steering: attempting to push the customer toward a procurement structure, specification, or evaluation approach for the purpose of excluding competitors unfairly. Shaping is part of responsible market engagement. Steering creates risk.

Good engagement also requires preparation. Before an important customer meeting, the account owner should define the meeting purpose, expected attendees, topics to cover, topics to avoid, materials to provide, and follow-up process. For active opportunities, the team should confirm whether the meeting is allowed at all. This discipline does not make the conversation stiff. It makes the contractor appear professional, coordinated, and safe. Government customers notice when vendors understand the rules.

Inappropriate engagement often begins innocently. A customer says, “Off the record, here is what we are thinking.” A partner says, “I heard the incumbent’s price.” A former official says, “Let me call my old team.” These moments are where account culture matters. The account executive should be able to pause the conversation without embarrassment and say, “I want to make sure we handle this correctly.” That sentence can prevent a small mistake from becoming a serious procurement problem.

During active procurements, the account executive’s role changes. The team should follow the solicitation’s communication instructions, route questions through official channels, avoid side conversations about the procurement, and remind delivery personnel and executives of restrictions. A delivery manager working on a related contract should not casually discuss the active bid with program staff. A CEO should not call a senior official to “check on where things stand.” A technical expert should not continue informal solution discussions if the government has directed all vendors to use the Q&A process.

After the award, engagement remains important. The team may attend kickoff, clarify expectations, manage transition, and build performance trust. If the company lost, it may seek a debrief where available and maintain professional account engagement. But even post-award discussions should avoid sensitive competitor information or improper attempts to reopen a decision outside the prescribed process.

20.3 Organizational Conflicts of Interest, Gifts, Lobbying, and Revolving-Door Risks

Organizational conflict of interest: a situation where a contractor’s work, relationships, access, or prior role may impair objectivity, create unfair competitive advantage, or affect the integrity of a procurement. FAR Subpart 9.5 addresses responsibilities, general rules, and procedures for identifying, evaluating, and resolving organizational and consultant conflicts of interest. 

OCI risk appears in several common forms. The first is biased ground rules, where a contractor helps write requirements, acquisition materials, or specifications and then seeks to compete for the resulting work. The second is unequal access to information, where a contractor gains nonpublic information through one role that could benefit it in another competition. The third is impaired objectivity, where a contractor may be asked to evaluate its own work, review a competitor in a way that affects its interests, or advise the government on decisions in which it has a financial stake.

Sales teams often encounter OCI risk before legal teams do. A customer may ask whether the company can help develop a roadmap, assess an incumbent program, support acquisition planning, or provide systems engineering and technical assistance. That work may be attractive, but it could restrict future bidding or require mitigation. Account executives should not casually accept advisory roles without understanding downstream implications. The right question is not only “Can we win this work?” It is also “Will this role limit our ability to compete later?”

Gifts and hospitality: another area where commercial habits can create government risk. Federal employees are subject to rules on gifts from outside sources, including restrictions on gifts from prohibited sources and gifts given because of official position. OGE’s training materials for 5 CFR Part 2635 Subpart B focus on applying the general prohibition, definitions, and exceptions for gifts from outside sources. 

Account teams should adopt a conservative posture. Do not offer meals, tickets, entertainment, travel, discounts, conference benefits, or personal favors to government personnel without clear policy review. Small exceptions may exist, but exceptions are not a sales strategy. Many companies simplify the rule for field teams: do not give anything of value to government officials unless compliance has approved it. This rule protects the employee, the customer, and the company.

Lobbying risk: the risk that sales or advocacy activity crosses into regulated lobbying or uses prohibited funds. Federal rules limit the use of appropriated funds to influence certain federal transactions, and FAR Subpart 3.8 implements the statutory restrictions related to influencing federal contracting and financial transactions. Contractors may engage in lawful government relations, but they must understand disclosure, registration, cost allowability, and funding restrictions. Account executives should not assume that every conversation with agency or congressional stakeholders is ordinary sales activity.

Revolving-door risk: risk arising from hiring, compensating, or using former government officials in ways that violate post-employment restrictions or create appearance concerns. Former federal employees can work for contractors, but restrictions may limit communications or appearances before the government on certain matters. DOJ guidance notes that 18 U.S.C. § 207 does not generally prohibit former federal employees from working for a particular employer, but restricts what they can do for that employer in certain circumstances.

These restrictions can be complex and fact-specific. A former program manager may have valuable expertise, but may be barred from representing the contractor back to the agency on particular matters. A former acquisition official may have access to memories or information that should not be used. A newly hired executive may trigger compensation restrictions tied to certain procurements. Sales leaders should involve legal before assigning former officials to account roles, customer meetings, capture strategy, or proposal reviews connected to matters they handled in government.

20.4 How to Train Account Teams on Compliant Relationship Building

Compliance training for account-based selling must be practical. Annual online modules are not enough. Account executives need to know what to do in real customer situations: a program manager shares something that sounds sensitive, a contracting specialist says all questions must go through the portal, a former agency official offers to call an old colleague, a partner forwards a competitor’s pricing rumor, or a customer asks the contractor to help draft language for an upcoming requirement.

Scenario-based training: training built around realistic situations that account teams face in the field. This is the most effective way to teach judgment. The training should present ambiguous facts, require discussion, and show the right escalation path. The goal is not to make sellers afraid of customers. The goal is to help them recognize red flags early and respond professionally.

Training should cover the full account life cycle. Before procurement, teams should learn how to conduct market education, capability briefings, demonstrations, and RFI responses appropriately. During procurement, they should learn how to follow communication instructions, handle accidental disclosures, avoid side conversations, and coordinate official questions. After awarding, they should learn how to manage debrief information, protect competitor data, and transition proposal commitments into delivery without creating new risk.

Role-specific training is also important. Account executives need training on relationship boundaries, procurement stages, stakeholder engagement, gifts, former officials, and documentation. Capture managers need training on competitive intelligence, black hat reviews, price-to-win inputs, OCI, teaming, and proposal information handling. Delivery leaders need training on expansion conversations, scope boundaries, procurement restrictions, and what to do when customers discuss future work. Executives need training because senior outreach can create outsized risk if poorly timed or badly prepared.

The company should create simple escalation rules. If the team receives possible source selection information, competitor proposal information, unusual customer direction, a gift question, an OCI concern, a former-official issue, or a lobbying question, the account executive should know exactly whom to contact. Escalation should be treated as good judgment, not as a failure. People hide problems when they fear punishment. They raise problems when leadership rewards early reporting.

Training should also be embedded in pursuit governance. Every major opportunity should include a compliance review at qualification and again before proposal submission. The review should ask whether communication restrictions apply, whether any advisory work creates OCI concerns, whether former government employees are involved, whether customer engagement has been properly documented, whether partner information is clean, and whether gifts or hospitality issues exist.

Managers should reinforce compliant behavior in account reviews. Ask how the team engaged the customer, whether procurement restrictions are known, whether the account plan identifies sensitive relationships, and whether any red flags need review. This normalizes compliance as part of account management rather than an afterthought. A compliance-aware sales culture is built through repeated management behavior, not policy documents alone.

The final training principle is tone. Compliance should be framed as a way to protect customer trust and make awards defensible. Salespeople resist compliance when it is presented only as a list of prohibitions. They adopt it when they see that compliant engagement helps customers buy with confidence and helps the company avoid avoidable losses.

20.5 Compliance Checklist for Account Executives

The following checklist is designed for account executives and sales managers. It should be used before major customer meetings, during opportunity qualification, before capture kickoff, and whenever an engagement feels sensitive. It is not a substitute for company policy or legal review, but it helps account teams identify issues early.

• Procurement stage: Do we know whether the opportunity is pre-procurement, market research, draft solicitation, final solicitation, evaluation, award, protest, delivery, or recompete?
• Communication rules: Have we reviewed the solicitation, notice, or customer instructions to understand who may communicate and through what channel?
• Customer authority: Are we clear on which stakeholders can discuss mission needs, which can discuss acquisition process, and which can bind the government?
• Information boundaries: Have we avoided seeking source selection information, competitor proposal information, internal evaluations, rankings, or protected government estimates?
• Accidental disclosure: Do we know what to do if sensitive information is received unexpectedly?
• Meeting purpose: Can we explain the legitimate business and customer value purpose of the meeting?
• Documentation: Have we documented important customer interactions, attendees, topics, and follow-up actions accurately?
• Requirement shaping: Are we providing market education rather than steering the customer toward an unfairly restrictive requirement?
• OCI review: Have we checked whether our advisory, SETA, roadmap, evaluation, or support roles could restrict future competition?
• Partner information: Are we confident that partner-provided competitive intelligence was obtained appropriately?
• Former government employees: Have legal or compliance teams reviewed the role of any former officials involved in the account or pursuit?
• Gifts and hospitality: Have we avoided offering anything of value to government personnel unless explicitly approved by company policy and compliance?
• Lobbying sensitivity: Are any agency, congressional, or policy advocacy activities being reviewed under lobbying, disclosure, and cost rules?
• Executive outreach: Has senior-level customer engagement been coordinated with the account owner and reviewed for timing, message, and procurement restrictions?
• Delivery conversations: Have delivery teams been briefed on what they may and may not discuss regarding future procurements?
• Proposal firewall: Are proposal materials, competitor information, subcontractor data, and customer information being handled securely and appropriately?
• Escalation: Do account team members know whom to contact for contracts, legal, ethics, OCI, gift, lobbying, or procurement integrity questions?
• Customer trust: Would this interaction strengthen the customer’s confidence that we are professional, fair, and safe to buy from?

The checklist should produce action. If the team is unsure about the procurement stage, it should clarify before engaging. If communication rules are unclear, it should ask contracts or legal. If a former official is involved, it should obtain review before the person contacts the customer. If the team receives possible protected information, it should stop and escalate. If a meeting cannot be explained as legitimate and useful, it should be reconsidered.

Account-based selling requires disciplined relationship-building. The strongest contractors are not the ones that push hardest against procurement boundaries. They are the ones that understand the boundaries well enough to engage confidently inside them. They educate customers without compromising fairness. They build trust without personal favors. They use former officials carefully. They manage OCI before it surprises them. They handle competitive intelligence ethically. They document important interactions. They help the government buy from them in a way that can withstand scrutiny.

Ethics and compliance are therefore not side topics in government contractor sales. They are central to account strategy. A contractor that becomes known as careful, credible, and respectful of the rules earns a kind of trust that matters deeply in public procurement. That trust does not guarantee awards, but it keeps the company eligible, credible, and welcome in the conversations where future opportunities begin.