is managing a client's vendors out of scope?

It feels obvious to them because they experience the project as one seamless outcome, but your contract almost certainly describes a piece of that outcome, not the whole supply chain that produces it. Delivering your part well is your job; making three other suppliers' parts arrive on time and fit together is production management. Those are different roles with different rates, and the fact that they blur together in the client's mind doesn't merge them in your scope. Quote your deliverable back to them in plain terms, then describe coordination as the separate thing it is. Most clients accept the distinction quickly once it's named — they're usually not trying to extract free labor, they just hadn't separated the two in their head. Your job is to do the separating before the role quietly becomes yours by default.

Don't ignore it, but don't silently absorb it either. A third-party delay that threatens your delivery is a dependency problem, and the right move is to flag it the moment you see it: 'My build is ready, but I can't finish until the photographer delivers the final images — my date moves day-for-day from when those land.' That keeps the consequence where it belongs without dragging you into managing the photographer. You're reporting a blocker, not adopting a chase. If the client wants you to actively wrangle the late vendor to recover the date, that's coordination labor on top of the delay, and it's fair to treat it as either a rush conversation or a producer task. The distinction matters: noting a dependency protects your timeline, while chasing someone else's supplier quietly expands your job.

No — a single, bounded handoff to a vendor the client has already chosen is part of delivering your work cleanly, and refusing to do it would be petty. The line is between handing off and managing. Emailing the final artwork to a named printer, or pushing your code to the client's hosting account, is delivery. Getting on calls to reconcile the printer's specs with the client's expectations, chasing the printer for proofs, and owning the print timeline is management. One is a touch; the other is a role. So do the handoff without fuss, but watch for the moment the handoff sprouts follow-up tasks — 'can you also check their proof, and sort out the paper stock, and confirm their schedule.' That's where a delivery courtesy turns into an unpaid production job, and that's where you draw the line.

Price it as production management, separate from your deliverable, and never fold it into your project fee where it becomes invisible and uncapped. A retainer works well when coordination is ongoing — a fixed monthly amount for being the point of contact across the client's suppliers, with a clear scope of how many vendors and how much chasing that covers. A day-rate or hourly producer rate works when it's bursty around a launch. The key is that the meter is visible: the client should see that coordinating five suppliers through a launch is real, billable work, not a freebie that rides along with the design or the build. Pricing it openly also protects the relationship, because the alternative — absorbing it silently and resenting it — poisons the project far more than an honest line item ever would.

Being on a thread is not the same as owning what's on it, and you get to decide which it is. A cc is information; a request is a task. If the client is just keeping you in the loop, read and move on. The trap is when 'fyi' quietly becomes 'and you'll handle the parts that touch you,' so that you're suddenly accountable for coordinating another freelancer's output into yours. Head that off early with a light, friendly boundary: 'Thanks for looping me in — I'll watch for anything that affects my piece, but I'm assuming you're driving the overall coordination unless we set that up separately.' That one sentence keeps a courtesy cc from curdling into a job. Silence, by contrast, reads as consent, and a month later you'll be the de facto producer wondering how it happened.

Add a short client-responsibilities clause that says the client coordinates their own third-party suppliers unless a production-management scope is agreed in writing, and name any single vendor handoffs you are responsible for. Two or three sentences settle it before the project starts, which is the only time these conversations are easy. The clause does two jobs: it tells the client up front that vendor wrangling isn't bundled into your fee, and it gives you a clean, non-personal thing to point at when the asks start — 'per our agreement, coordination sits on your side unless we set up a producer scope.' That's far less awkward than relitigating it mid-project from memory. The contract is doing the boundary-setting so you don't have to keep doing it by hand, thread by thread, favor by favor.