A sponsor acquires an asset, identifies an experienced operator, and agrees that the operator will “help run the business.” That sentence can create more risk than clarity. It does not establish who can hire, approve spending, negotiate contracts, speak to lenders, or make decisions when the operating plan changes.
Operating partner agreement responsibilities should turn that broad intention into a controlled commercial mandate. The agreement must identify the work, the decision rights, the reporting line, the economics, and the limits of authority before execution begins. It is not a description of goodwill. It is an operating instrument.
For owners, sponsors, and executive teams, the central question is straightforward: what is this partner accountable for delivering, and what remains with the principal?
Why operating partner agreements fail
Most disputes do not begin with bad intent. They begin with a role that was never made specific enough for the pressure of real operations. A partner may believe they were retained to improve performance. The owner may believe they were retained only to advise management. Both positions can sound reasonable until a hiring decision, capital request, vendor commitment, or missed milestone requires an answer.
The risk increases in complex mandates. A real-asset operating partner may be asked to stabilize occupancy, oversee a redevelopment program, manage local contractors, and prepare lender reporting. An operating partner in an aviation, equipment, resource, or data-center project may coordinate technical workstreams while the owner retains all capital commitments and final commercial approvals. These are different scopes. They should not rely on the same generic agreement language.
A disciplined agreement separates responsibility from authority. A party can be responsible for preparing a recommendation without having authority to approve it. A party can manage a process without being authorized to bind the owner. That distinction protects both sides.
Operating partner agreement responsibilities to define first
The agreement should start with the mandate, not the compensation model. Economics matter, but they cannot repair an undefined assignment.
Scope of work and stated outcomes
Define the asset, business unit, project, territory, and time period covered by the mandate. If the partner is engaged for a specific site, portfolio, geography, or operating phase, say so directly. Do not use broad language such as “all related activities” unless the parties genuinely intend an open-ended scope.
Then identify the required work. This may include developing an operating plan, establishing a local team, sourcing suppliers, supervising construction interfaces, improving unit economics, preparing commercial materials, or producing reports for the owner and approved stakeholders.
Outcomes should be framed as deliverables and milestones, not unsupported guarantees. An operating partner can commit to produce a 90-day plan, complete a supplier review, launch a leasing process, or deliver a monthly variance report. The same partner should not promise a revenue level, financing approval, construction completion date, or asset valuation when those results depend on third parties, market conditions, or owner decisions.
Authority and approval gates
This is often the most consequential section. It should state what the operating partner may do independently, what requires prior written approval, and what the partner may never do.
Routine authority might cover tasks within an approved operating budget, ordinary vendor coordination, staff supervision, or implementation of an agreed plan. Reserved matters typically include borrowing, granting security, selling material assets, entering long-term contracts, changing approved budgets, litigation decisions, related-party transactions, and material hiring or termination decisions.
Use monetary thresholds where they help. For example, the partner may approve individual expenses within the approved budget up to a stated amount, while commitments above that amount require owner consent. Thresholds alone are not enough. A series of smaller commitments can create a material exposure. The agreement should also address aggregate limits, contract duration, and any commitment that cannot be readily canceled.
If the partner has no authority to bind the owner, state that plainly. If the owner wants the partner to act as an authorized signatory for defined documents, list those documents and conditions. Silence creates assumptions. Assumptions create claims.
Milestones, reporting, and operating cadence
An accountable role requires a review rhythm. The agreement should establish what the partner reports, to whom, how often, and in what format. A monthly operating report may cover financial performance, budget variance, sales or occupancy activity, staffing, project status, material risks, decisions required, and next-period priorities.
For a turnaround or development assignment, weekly reporting may be appropriate during the first 60 to 90 days. For a stabilized asset, monthly reporting may be enough. The cadence depends on the stage of the mandate and the speed of the underlying business.
Milestones should have acceptance criteria. “Improve operations” is not a milestone. “Deliver a baseline assessment, approved action plan, vendor transition schedule, and first monthly variance report by the stated dates” is measurable. The owner should have a defined period to review a deliverable and either accept it, request revisions, or identify a material deficiency.
Budget control and financial discipline
The operating partner may prepare budgets, manage approved budgets, or recommend changes. Those are separate responsibilities. The agreement should identify which one applies.
It should also define access to bank accounts, accounting records, procurement systems, and financial data. If the partner may initiate payments, the controls should specify approval levels, dual authorization requirements, documentation standards, and reconciliation procedures. If the partner cannot access funds, the agreement should explain how urgent operating payments are escalated.
Incentive compensation deserves equal precision. If a fee, carried interest, profit share, or promote is tied to performance, define the calculation base, timing, exclusions, accounting policy, clawback conditions, and dispute process. A performance fee based on “profit” is incomplete if the parties have not agreed on reserves, owner overhead, debt service, capital expenditures, taxes, or sale costs.
Team, vendors, and third-party relationships
An operating partner may work through its own personnel, existing management, local contractors, or a combination of all three. The agreement should identify who directs each group and who carries employment, insurance, compliance, and payment obligations.
Vendor authority requires special attention. The partner may be asked to source and evaluate providers, but the owner may retain final contracting authority. Where the partner can engage vendors, the agreement should require conflict disclosures and address whether affiliate transactions are permitted. A partner should not be able to award work to a related entity without transparent approval.
The same logic applies to brokers, advisers, lenders, and capital sources. An operating partner can prepare information, coordinate introductions, and support diligence within its mandate. It should not represent that a third party will approve financing, purchase an asset, or deliver a result outside the partner’s control.
Boundaries that protect the principal and the partner
A strong agreement includes what the operating partner is not responsible for. These exclusions are not defensive filler. They prevent the mandate from expanding through informal requests and changing expectations.
Common boundaries include legal advice, tax advice, securities activities, lender approval, environmental certification, engineering certification, employment decisions reserved to the owner, and commitments outside an approved budget or geography. The exact list depends on the asset and assignment.
The agreement should also address information rights, confidentiality, intellectual property, insurance, indemnification, compliance obligations, and conflicts of interest. These provisions need to match the mandate rather than appear as generic boilerplate. A partner handling customer data has different exposure from one overseeing field operations at a remote industrial site.
Change control and exit terms
Operating mandates change. The asset may be refinanced, sold, paused, expanded, or placed under new management. The agreement needs a controlled method for changing scope, fees, authority, or timing. A written change order is usually more effective than a chain of informal emails.
Termination provisions should cover notice periods, termination for cause, payment for completed work, handover requirements, return of records, continuity of operations, and treatment of incentive economics. If the partner has built vendor relationships, assembled reporting, or supervised a transition, the handover process should be practical and timed to protect the business.
For longer mandates, consider transition assistance after termination. This should be defined, limited, and compensated where appropriate. It is unreasonable to expect unlimited support after the relationship ends. It is equally unreasonable to leave a critical operation without a documented transfer process.
Blue Harbor Group approaches operating mandates with the same discipline: define the geography, milestones, responsibilities, and scope before execution begins. The agreement does not replace commercial judgment or legal counsel. It gives both a clear record of how that judgment will be applied.
The useful closing test is simple. If a material decision had to be made tomorrow, each party should be able to identify the responsible person, the approval required, the information needed, and the deadline for action. If the agreement cannot answer those questions, the mandate is not yet ready to carry out.