Build the line items
List the selected posts and the intended quantity for each one. If the package uses a range or automatic selection, confirm exactly which messages are included. A channel-level budget should be translated into supported target-level requests before cost comparison.
Apply the correct minimum
Read whether the minimum applies per message, per batch or under another defined package rule. Those conditions can produce different totals. Do not assume that unused quantity on one message can be reassigned to another unless the offer explicitly supports that allocation.
Revise the scope deliberately
If the proposed configuration is below the allowed minimum, reduce the target list or change the quantities with approval. Avoid quietly increasing the budget during submission. Keep the final purchasable configuration in the brief so the client can compare it with the original plan.
Decision checklist
| Decision | What to check |
|---|---|
| Targets | Approved message list |
| Minimum | Per-message or package rule |
| Revision | Explicit budget approval |
Worked example
For illustration, a buyer plans 50 views on each of eight messages, but the selected option requires 100 per message. The original 400-unit plan is not valid under that rule. A revised target list or an approved 800-unit scope would need a fresh cost check.
Example figures explain the decision; they are not current prices or promised results.