Verified BM for Agency: Define Client and Supplier Responsibilities

When evaluating verified BM for agency services, start by identifying whose business the proposed arrangement represents and who will be responsible for each part of the work.

An agency may coordinate the engagement, a client may own the relevant assets, and an external supplier may perform a limited implementation task. These roles need to be clear before anyone grants access or approves changes.

A proposal should explain how those parties will work together, including who supplies information, who authorizes actions, and who confirms completion.

This guide helps agencies turn a broad supplier offer into a practical division of responsibilities.

1. Identify the Business Behind Each Requirement

Begin with the organization that needs the service.

Is the agency requesting assistance for its own business setup? Is it commissioning work for a client? Does the engagement involve several independently owned businesses?

Write a separate brief for each business where responsibilities differ.

Record:

The business requesting the work.
The assets relevant to the request.
The intended operational workflow.
The designated business representative.
The agency’s role.
The supplier’s proposed role.

Avoid using “our BM” when the phrase could refer to either agency-owned or client-owned assets. Use specific references throughout the proposal and handover.

2. Separate Ownership, Access, and Service Delivery

These three concepts answer different questions.

Ownership concerns whose assets are involved. Access concerns what designated people can do. Service delivery concerns the work a provider has agreed to perform.

When considering a verified Business Manager for agency offer, ask the supplier to explain all three.

A configuration service does not, by itself, establish ownership. Likewise, being able to perform an action does not explain the authorization behind it.

Ask for a written description of the proposed arrangement, including any dependencies on another organization. Confirm that the intended work and access arrangement are permitted under applicable platform terms.

3. Assign a Responsible Person to Each Task

Create a responsibility table before implementation begins.

The following is an example to adapt, not a universal allocation:

Task	Example responsibility to agree
Confirm business information	Authorized representative of the relevant business
Explain the intended workflow	Agency project lead with client input
Approve access requests	Designated asset administrator
Perform configuration	Named implementation provider
Approve additional costs	Contracting party’s designated budget owner
Check operational results	Designated agency or client operator
Accept final delivery	Named acceptance owner
Review access at closure	Authorized administrator

Use named contacts in the actual project record.

For each task, identify who performs it and who approves the result. These may be different people.

4. Define the Agency’s Permission Boundaries

Describe the actions your agency needs to perform rather than requesting broad access without context.

For an advertising engagement, distinguish campaign operations from business administration, financial decisions, and changes to other assets.

Ask:

Which assets does the agency need to work with?
Which actions are included in the client’s authorization?
Which changes require separate approval?
Who can authorize additional operators?
Who reviews permissions when staffing changes?

If the supplier needs temporary access, specify its task and review date separately from the agency’s ongoing role.

Use each operator’s own authorized account. Shared personal credentials should not be the operating model.

5. Clarify Who Supplies and Confirms Information

Implementation can stall when each party assumes another person will provide the required inputs.

Create an input list before the supplier schedules the work. Assign an owner and due date to each item.

Depending on the scope, inputs may include business information, asset references, workflow requirements, or administrative approvals.

Where documents or business statements are involved, identify the authorized representative who must confirm their accuracy. The agency can coordinate the process without guessing missing details or making unsupported statements on a client’s behalf.

If an input is unavailable, record the dependency and its effect on the schedule.

6. Keep Supplier Deliverables Separate from Agency Outcomes

A supplier engagement and an agency campaign may have different objectives.

For example, a provider might be responsible for completing a documented configuration task. The agency might separately manage creative production, campaign planning, and reporting.

When reviewing verified BM for advertising agency proposals, ask the supplier to identify the result it is actually committing to deliver.

Do not treat a setup package as evidence that advertising performance, future approvals, or uninterrupted operation have been established.

Define acceptance around the agreed service:

Were the specified tasks completed?
Do the relevant references match the proposal?
Can the designated operator perform the agreed action?
Are dependencies and unresolved issues documented?
Has the responsible person reviewed the result?

This keeps delivery checks connected to the work being purchased.

7. Establish a Clear Communication Route

Agree on who communicates with whom during the engagement.

If the agency manages the supplier relationship, determine when the supplier may contact the client directly. If technical questions require a client administrator, identify that contact in advance.

Record:

The main project contact.
The channel for operational questions.
The person who approves changes.
The escalation contact.
The expected update schedule.

Also clarify how instructions become authoritative. A casual message from an uninvolved team member should not automatically change the scope or authorize extra spending.

Keep material decisions in a shared project record.

8. Plan for Staff Changes and Client Departure

Define the end of the relationship before it becomes urgent.

For an agency-client engagement, clarify what happens when an employee leaves, a supplier finishes its work, or the client appoints another agency.

The closure plan should identify:

Documentation to be handed over.
Open tasks and their owners.
Access that needs review or removal.
Ongoing services that may need cancellation.
The person who confirms the transition is complete.

Describe the required actions precisely. Avoid a vague promise to “transfer everything” without identifying the assets, permissions, and records involved.

Example: An Agency Using an External Implementation Provider

An agency manages advertising work for a retail client and commissions a supplier to perform a limited configuration task.

The client’s designated representative confirms the relevant business information. An authorized administrator approves the required access. The supplier performs the agreed task and documents its changes.

The agency’s operator checks the specified workflow. The client’s named acceptance owner reviews the handover, and temporary supplier access is reviewed at closure.

The arrangement works because each party has a defined role. The supplier’s completion record does not replace the client’s authorization or the agency’s own operating responsibilities.

Questions to Send Before Ordering

“Please describe how your service would work with our agency and the relevant client business. Identify asset ownership, required authorization, agency permissions, supplier tasks, client inputs, approval contacts, acceptance checks, and the access review required at handover.”

Frequently Asked Questions

Should an agency request the same arrangement for every client?

Use a consistent review process, but assess each client’s assets, authorization, operators, and workflow separately. Similar service needs do not make all client situations identical.

What should a verified BM supplier explain to an agency?

The supplier should define its service scope, required inputs, access needs, deliverables, dependencies, and responsibilities after delivery.

Can media buyers approve administrative changes?

Identify the designated approver in the engagement. Do not assume that responsibility for campaign work includes authority over every business or asset setting.

Who should accept the supplier’s work?

Name the acceptance owner before implementation. That person should have the authority and information needed to compare delivery with the agreed requirements.

Build an Agency Arrangement with Clear Responsibilities

A verified BM for agency proposal should explain how the agency, client, and supplier will work together.

Identify the relevant business, distinguish ownership from access, assign task owners, and document approvals. Then connect handover checks to the exact service being purchased.

Visit BMXMDN to discuss your agency requirements and request a proposal covering client authorization, agency permissions, supplier deliverables, implementation costs, handover, and ongoing responsibilities.