How to Send Meal Plans to Clients: PDF, App or Link?

You spent an hour building a good plan. Then you exported it to a PDF, attached it to an email, and it's now sitting in a downloads folder between a boarding pass and a phone bill. Three weeks later the client asks what they should eat for lunch.

How a plan is delivered matters almost as much as what's in it. This guide compares the common ways coaches send meal plans, what each one does to adherence, and how to choose.

What a delivery method needs to do

Before comparing options, be clear about the job. A client checks their plan in the supermarket, at work, in the kitchen with their hands dirty, and at a restaurant while the waiter waits. The delivery method needs to:

• Open on a phone in one tap, without hunting through email or logging in.
• Show today, not a 14-page document the client scrolls through.
• Stay current when you change something, without a new file being sent each time.
• Look like it came from you, not from a generic app.
• Be printable for the clients who want it on the fridge.
• Protect the client's data, since a plan contains their name, weight and goals.

Measure every option against that list.

Option 1: PDF by email or WhatsApp

Still the most common method, and it has real strengths: everyone can open a PDF, it prints well and it feels like a deliverable the client paid for.

The problems show up after day one:

• The client has to find it again. Email search, WhatsApp scroll, "can you resend it?"
• Every change means a new file, and now there are three versions and nobody knows which is current.
• PDFs built for A4 are hard to read on a phone. Pinch, zoom, scroll, lose your place.
• It's static. No today view, no shopping list, nothing that updates.

A PDF works if the plan never changes and the client is organized. That describes very few coaching relationships.

Option 2: Spreadsheet or Google Doc

Shared documents fix the version problem: you edit, the client sees the change. Coaches who build plans in Sheets often just share the sheet.

In practice the client is looking at your working file. Formulas, macro columns, notes to yourself, a grid that doesn't fit a phone screen. It's current but not usable, and it's easy to accidentally share more than you meant to (other clients' tabs, your calculation sheet).

Option 3: Coaching apps

All-in-one coaching platforms deliver plans inside their app. The client installs it, logs in and sees the plan next to their workouts and check-ins. If you already run your coaching through one of these platforms and your clients use the app daily, delivering the plan there is sensible.

The friction is the app itself. Clients have to install it, create an account and remember a password, and the plan lives behind a generic interface with the platform's branding. Many clients who are happy to follow a plan from a coach won't adopt another app to do it. Nutrition is also usually a secondary feature on these platforms: the meal plan builders tend to be basic compared with the workout side.

Option 4: A web link

The approach we built SendFit around: the plan is a web page at a private link. You send the link once, by whatever channel you already use with the client. On their phone it opens as a page built for a phone, they can add it to their home screen so it looks and opens like an app, and it always shows the latest version. No install, no account, no password unless you choose to set one. The link stays the same from one plan to the next, so a new block appears there on its start date, and if you coach their training too, the day's workout sits right next to the day's meals.

What a link does well:

• One tap to today's meals. The client sees the current day first, with the rest of the plan a swipe away.
• Changes appear automatically. You edit the plan, the client's link updates. There is never an old version.
• Your brand, not the software's. Your logo and color are on the page; the tool stays in the background.
• Works offline and prints. Once it's been opened, the last version is available without signal, and there's a print button for the fridge crowd.
• Extras the plan can carry. A shopping list for the week, rest days marked, daily totals against targets.

The honest limitation: a link needs a browser, so it's a web page rather than a native app. For almost every client that's an advantage, because there's nothing to install.

Comparison

Whatever you use, do these

• Walk the client through it once. A two-minute voice note or screen recording showing where today's meals are, how swaps work and where the shopping list is prevents most "I didn't know" messages.
• Tell them to put it on the home screen. For a link, that's Share → Add to Home Screen on iPhone, or Install on Android. For an app, make sure notifications are on.
• Keep one source of truth. If the plan lives at a link, don't also send a PDF. The moment there are two versions, one of them is wrong.
• Protect the data. Don't post plans in group chats, use a private link or an app with a login, and if the client shares a phone, set a password on the plan.
• Explain the rest days. If some days have different targets, label them so the client doesn't think it's a mistake. See rest day macros for how to set them.

Delivery is part of the plan

Most of the reasons clients don't follow meal plans come down to friction: the plan was hard to find, hard to read or out of date. Picking a delivery method that removes that friction is the cheapest improvement in adherence a coach can make.

If you want to see what a link-based plan looks like from the client's side, our meal plan software page has a live demo you can open on your phone.