AdvancedLesson 29 of 305 min read

Handling Marketing Projects

Scope a client project, plan tasks with dependencies, find the critical path and slack with a real program, and answer two change requests with a number instead of a worry.

In this lesson you will

  • Write a project scope
  • Plan tasks and find the critical path
  • Answer a change request with a number
  • Report and close a project cleanly

About 26 minutes

The bakery wants a launch in three weeks

Noor agrees to run a marketing launch for the bakery, and the owner wants it live by the end of November. The work is more than posting. It needs an audit, a tracking set-up, a plan, new pages, emails, testing, a launch and a first report. Half-way through, the owner asks for another landing page. This lesson shows how to run such a project calmly: write the scope, plan the dependencies, use the critical path to see what really threatens the date, and answer a change request with a number instead of a worry.

Scope, in writing

  • Goal. One measurable aim and a date.
  • Included. The audit, the plan, three pages, four emails, tagged links and a first report.
  • Not included. Photography, paid advertising spend, anything not named.
  • What you need from the client. Access to accounts, product facts and one person who approves.
  • Success measures and the report date. What you will measure and when you will show it.
  • Change process. New requests are costed and dated before work starts.

Plan the order of work

The program below lists nine tasks with the days each takes and what each waits for, starting on Monday 9 November 2026. It finds the total number of working days, the critical path, and the slack, meaning how many days a task could slip without moving the finish. Then it tests two change requests: an extra landing page of three days, and a bigger one of six days.

import numpy as np

TASKS = {"kick-off": (1, []), "audit": (3, ["kick-off"]), "tracking set-up": (2, ["kick-off"]),
         "plan": (2, ["audit"]), "build pages": (4, ["plan", "tracking set-up"]), "write emails": (3, ["plan"]),
         "test": (2, ["build pages", "write emails"]), "launch": (1, ["test"]), "first report": (2, ["launch"])}

def plan(tasks):
    end = {}
    def done(n):
        if n not in end:
            d, deps = tasks[n]
            end[n] = max([done(x) for x in deps], default=0) + d
        return end[n]
    for n in tasks: done(n)
    total = max(end.values())
    path, cur = [], max(end, key=end.get)
    while cur:
        path.append(cur)
        deps = tasks[cur][1]
        cur = max(deps, key=end.get) if deps else None
    late = {}
    def lf(n):
        if n not in late:
            nxt = [k for k in tasks if n in tasks[k][1]]
            late[n] = min([lf(k) - tasks[k][0] for k in nxt], default=total)
        return late[n]
    return total, path[::-1], {n: lf(n) - end[n] for n in tasks}

def finish(days):
    return str(np.busday_offset("2026-11-09", days - 1, roll="forward"))
total, path, slack = plan(TASKS)
print("days:", total, "finish:", finish(total))
print("critical path:", " > ".join(path))
print("tracking set-up slack:", slack["tracking set-up"])
print("write emails slack:", slack["write emails"])
T2 = dict(TASKS)
T2["extra landing page"] = (3, ["plan"])
T2["test"] = (2, ["build pages", "write emails", "extra landing page"])
t2, p2, s2 = plan(T2)
print("change request adds", t2 - total, "days")
print("new finish:", finish(t2))
print("extra page on critical path:", "extra landing page" in p2)
T3 = dict(TASKS)
T3["big landing page"] = (6, ["plan"])
T3["test"] = (2, ["build pages", "write emails", "big landing page"])
t3, p3, s3 = plan(T3)
print("bigger change adds", t3 - total, "days")
print("bigger change finish:", finish(t3))
print("bigger change on critical path:", "big landing page" in p3)
days: 15 finish: 2026-11-27
critical path: kick-off > audit > plan > build pages > test > launch > first report
tracking set-up slack: 3
write emails slack: 1
change request adds 0 days
new finish: 2026-11-27
extra page on critical path: False
bigger change adds 2 days
bigger change finish: 2026-12-01
bigger change on critical path: True

The project takes 15 working days and finishes on 2026-11-27. The critical path is kick-off > audit > plan > build pages > test > launch > first report. Tracking set-up has 3 days of slack and writing emails has 1 day, so a small delay to either would not matter, but a delay to the audit, the plan or the page build moves the end date. Now the change requests. The extra page of three days adds 0 days, because it can be built alongside the longer page build, so the owner can have it without changing the date. The bigger page, of six days, does sit on the critical path and adds 2 days, moving the finish to 2026-12-01. The skill is in saying this clearly: ‘a small page fits in the plan, a large one costs two more days, and here is the new date.’

Run the project

  1. Kick off with the scope in writing, and confirm who approves each stage.
  2. Plan with dependencies, find the critical path and watch it more closely.
  3. Review every deliverable against the source and the plan before it goes to the client, including anything written with AI tools.
  4. Report on a fixed rhythm, with three lines: what was done, what is next, and what is at risk.
  5. Handle change in writing, with the effect on date and cost.
  6. Close the project with the first report, the lessons learned and a handover of accounts and documents.
Common mistake: yes first, check later

Saying yes to a small request without checking. Small requests add up, and the one that lands on the critical path moves the whole date. Check the plan before you answer, even when it seems minor.

Protect client access and data

Keep client logins, data and documents safe: use separate accounts where possible, share only what is needed, and remove access when the project ends. Keep a record of decisions and approvals.

Plan a small project of your own with eight tasks. Find the critical path and the slack of each task. Imagine one extra task and decide whether it moves the date.

Practice for this lesson

Check what you learned

Five quick questions. Pick an answer and you will see straight away whether it is right and why.

What does slack mean?

  1. A mistake
  2. A type of task
  3. A fee
  4. Days a task can slip without moving the finish

Tasks off the critical path have slack.

Why did the three-day extra page add no days?

  1. It was free
  2. It could run alongside the longer page build
  3. It was ignored
  4. It was cancelled

It sat off the critical path.

What did the six-day page do?

  1. Add nothing
  2. Cancel the launch
  3. Add two days by joining the critical path
  4. Shorten the plan

It took the finish to 1 December.

What belongs in a status report?

  1. Done, next and at risk
  2. Only good news
  3. A full log
  4. Nothing

Three short lines keep everyone informed.

How should change requests be handled?

  1. By phone only
  2. Ignored
  3. In writing, with the effect on date and cost
  4. Always accepted

Written changes avoid disputes later.

Summary

  • Write scope, deliverables, exclusions and the change process.
  • The critical path sets the finish; slack is spare time off it.
  • Not every change moves the date; check the plan.
  • Report briefly on a rhythm and close with a handover.

Next lesson

Lesson 30 is the Advanced capstone: a quarterly marketing plan.

Questions

How do I know a task has slack?

Work out the latest it could finish without delaying the end, and subtract when it is planned to finish. The program does this automatically.

Are the dates real?

They are a worked example that assumes working days from Monday 9 November 2026 with no holidays. Use your own calendar.

What if the client will not agree a scope?

Start with a small, clearly defined first phase, and agree the rest only when it is written down.

Progress is saved in this browser.