Executive Support Conflict-of-Interest Check

Why executive support needs a specific check

Executive assistants, chiefs of staff, project coordinators, and board liaisons can see calendars, communications, commercial plans, candidate information, and leadership decisions before other people do. That proximity makes conflicts of interest an operating question, not a generic clause hidden in onboarding. The purpose of a check is to find circumstances that could divide duty, distort judgment, expose information, or create an appearance the company cannot reasonably accept. It is not proof that a person is untrustworthy. A useful process identifies the relevant facts, sends them to an authorized owner, and records whether the work may proceed with controls, changed scope, or not at all.

Define a conflict without turning the review into surveillance

Write a definition tied to the role and applicable policy. Relevant conflicts may include competing engagements, financial interests connected to vendors, close relationships with decision participants, gifts, board positions, or prior obligations that restrict information use. Avoid unlimited questions about every friendship, investment, or family member. Ask only for facts reasonably connected to the support scope and let qualified people, legal, compliance, procurement, or HR owners interpret them. The assistant should not have to decide whether their own disclosure is material. They need a clear route to disclose without punishment for raising a good-faith question.

Map the work before asking questions

Start by mapping the access and influence the role will actually have. List systems, information classes, leaders supported, vendors contacted, candidates coordinated, board processes, spending steps, and decisions the person may prepare or execute. A calendar-only engagement creates different exposure from a chief of staff assignment involving acquisition options. Mark where the person can recommend a provider, see a bid before selection, route an employment decision, or hold information affecting another client. This map keeps the conflict check proportionate and exposes where the proposed scope is broader than the hiring team realized.

Cover outside work and overlapping clients

For an outsourced or fractional role, ask whether other engagements overlap by industry, transaction, customer, candidate pool, vendor selection, or confidential subject. The answer need not reveal another client's secrets. It should give the authorized reviewer enough sanitized information to judge separation. Consider scheduling collisions as well as information risk: two clients may both expect priority during a board week or incident. Controls can include separate accounts, devices, storage, teams, and named coverage, but a procedural wall is credible only if the provider can explain who enforces it and how exceptions are detected.

Review relationships and decision proximity

Relationship conflicts matter when the assistant is close to someone whose interests they will route, evaluate, pay, recruit, or investigate. Ask about relevant relationships using policy-approved language and protect the response. A disclosed connection does not automatically disqualify the person. The company might reassign a vendor comparison, require a second reviewer, or prevent access to one matter. What is unsafe is leaving the assistant to manage the conflict informally while colleagues assume neutrality. Recusal needs a replacement owner, a defined period, and enough communication that work does not quietly return through another channel.

Treat gifts and benefits as routing questions

Gifts, travel benefits, referral payments, discounts, and hospitality can create real or perceived pressure. Give support staff a threshold and routing rule rather than asking them to infer whether a benefit is harmless. A vendor may offer an upgrade while an assistant controls the executive's travel relationship; a candidate agency may offer a referral reward while the assistant schedules finalists. Preserve the offer, decline or hold it under the approved rule, and notify the proper owner. Never turn a disclosed offer into public accusation. The company should decide treatment under its policy and any legal or contractual obligations.

Protect confidential information across engagements

Information from one role must not influence another without authorization. An assistant who knows a former employer's negotiating position cannot use it to improve a new employer's deal. A provider supporting two leaders cannot copy contact notes, calendar patterns, templates containing private facts, or strategic context between accounts. General skill travels; confidential content does not. Make source boundaries visible through separate identities and storage. If a request appears to depend on information obtained elsewhere, stop, record the concern without repeating the information broadly, and ask the designated reviewer how to proceed.

Use a disclosed conflict to design controls

Not every disclosed conflict requires rejection. A useful control plan names the affected work, duration, restricted information, replacement operator, additional approval, monitoring owner, and review date. Suppose a candidate's sibling works for a vendor that the assistant would help evaluate. The company might remove vendor-scoring access and assign communications to another employee while allowing unrelated calendar work. Test whether the control is realistic during absence or urgency. If everyone will bypass it when the executive is traveling, it is not a control; it is a hopeful sentence.

Create a safe route for later changes

Conflicts can arise after onboarding through new clients, investments, relationships, responsibilities, or company transactions. Provide a confidential reporting route and examples of changes that should trigger review. State who receives the disclosure, what interim steps apply, and how retaliation concerns are handled. Do not require the assistant to announce personal facts in a team channel. During review, pause only the affected task or access when that is safe, rather than treating disclosure itself as misconduct. Regular reminders are more useful than an annual form nobody connects to daily work.

Handle the founder's personal work separately

Founder support sometimes combines company duties with authorized personal administration. That blend can create unusual conflicts around household vendors, family requests, reimbursements, personal investments, and use of company information. Separate the two scopes, systems, funds, and accountable owners. A family member's request should not override company authority merely because it arrives through the executive's assistant. Likewise, company purchasing power should not be used for a personal benefit without explicit approval and proper treatment. When a request crosses the boundary, pause it until the authorized owner classifies the work.

Document decisions and review dates

Record the disclosure date, relevant facts, reviewer, decision, controls, affected access, effective period, and next review. Keep the record in an approved restricted system rather than the general project tracker. Distinguish the person's statement from the reviewer's conclusion. If facts change, supersede the decision without erasing the earlier basis. The operating team only needs the instructions required to follow the control; it may not need the private reason behind them. Access to conflict records should end when the reviewer or relationship no longer requires it.

Know when the engagement should not proceed

Decline or stop the engagement when the conflict cannot be reduced to an acceptable level, when contractual duties cannot coexist, when information separation is not credible, or when the person would effectively review their own interest. Qualified owners should make that decision, applying relevant law, policy, and contract terms. HireExecutiveTeam can help a buyer map executive support workflows and access before provider selection. The reader's next step is to choose one proposed role, map its decision proximity, and submit the resulting conflict questions through the company's authorized process before credentials or sensitive context are shared.

Related resources

• Executive assistant support
• Executive support security due diligence
• Executive support provider contract checklist

Frequently asked questions