--- title: "Resource, communication and procurement planning" description: "Plans beyond scope and schedule A plan is only credible if the right people are available, stakeholders are informed in the right way, and external…" url: https://optimizeall.com/learn/project-management-leadership-with-ai/resources-communication-procurement updated: 2026-10-05 --- Project Management Leadership with AI · Planning scope, schedule, budget and resources · lesson 7 of 21 · 13 min # Resource, communication and procurement planning ## Plans beyond scope and schedule A plan is only credible if the right people are available, stakeholders are informed in the right way, and external suppliers are engaged on time. ## Resource planning 1. **Identify skills needed** for each work package or backlog area. 2. **Estimate demand** over time (e.g., FTE per month by role). 3. **Compare with availability**, considering other projects and business-as-usual work. 4. **Resolve conflicts:** level work within float, negotiate with functional managers, hire contractors or re-scope. 5. **Confirm commitments** in writing with resource managers. ## RACI: clarifying responsibilities ``` Activity / Deliverable Sponsor PM Product owner Tech lead QA lead Legal Business case A R C C - C Requirements sign-off I C A/R C C - Architecture design I C C A/R C - Security testing I I I C A/R - Contract with vendor A R C C - C Go-live decision A R C C C I R = Responsible (does) A = Accountable (one per row) C = Consulted I = Informed ``` Rule: exactly **one A** per row. Several A's means nobody is accountable. ## Communication planning A communication plan answers: who needs what information, when, in what format, from whom, and through which channel. | Audience | Need | Format | Frequency | Owner | |---|---|---|---|---| | Steering committee | Decisions, exceptions, forecasts | 2-page report + meeting | Monthly | PM | | Sponsor | Early warnings, escalations | 1:1 | Weekly | PM | | Team | Priorities, blockers | Stand-up, board | Daily | PM / Scrum master | | End users | What changes and when; training | Newsletter, demos | Monthly, pre-launch intensively | Change lead | | Regulator (if relevant) | Required notifications | Formal letter | Per rules | Compliance | Remember cultural and practical factors: time zones for teams across Pakistan, the Gulf, the UK and the US; working weeks that differ (e.g., Friday–Saturday weekends vs Saturday–Sunday); language preferences; and accessibility needs. ## Procurement planning Decide early what to **make vs buy**, then plan procurement lead times into the schedule. ``` Item Make/Buy Contract type Lead time Needed by Start procurement by Cloud hosting Buy Subscription 4 weeks Sprint 3 Week 1 Payment gateway Buy Service agreement 8 weeks Sprint 6 Week 2 UX design Buy Fixed price (phase 1) 6 weeks Week 8 Week 1 Data migration Make — — — — ``` Contract type shapes risk: **fixed price** transfers cost risk to the supplier but needs clear scope; **time and materials** is flexible but needs close control; **outcome-based** contracts align incentives but need measurable outcomes. Involve legal, security and procurement teams early, especially for data processing agreements under laws such as the UK GDPR, the UAE and KSA data protection laws, or US state privacy laws. ## Worked example *Illustrative.* A fictional retail chain in Dubai planned a loyalty app launch for a holiday season. Resource planning showed the only two payment-integration specialists were booked on another project for six weeks. The PM negotiated one specialist part-time, brought in a contractor under a time-and-materials contract with a cap, and started payment gateway procurement in week two because onboarding had an eight-week lead time. The launch met the date; without the early procurement check, it would have missed the season. ## Common mistakes - Assuming people are 100% available for project work. - Multiple accountable roles for one decision. - One-size-fits-all communication (everyone gets the same long report). - Starting procurement when the item is needed rather than when the lead time requires. - Contract type mismatched with scope certainty. ## Quick self-check List the three scarcest skills on your project. For each, do you have a written commitment of availability and a fallback if that person becomes unavailable? ## Making communication two-way A communication plan is not only about sending messages. Build in feedback channels: short surveys after demos, open question sessions for users, and regular one-to-ones with key stakeholders. Track whether messages are understood, not just sent; for example, ask a few users after an announcement what they think will change for them. Misunderstandings discovered early are cheap to fix. ## Supplier relationships Suppliers are part of your delivery system. Include key suppliers in planning sessions where appropriate, share relevant risks, and agree how progress and issues will be reported. Clear expectations at the start prevent many disputes later. ## Hands-on: capacity heat map and lead-time back-scheduling (Excel) ```text Allocation sheet: rows = person × workstream, columns = weeks, values = % of time Person total (per week) =SUMIFS(Week_col, Person_col, $A2) Format rule red if > 100%, amber if > 85% Procurement sheet: A Item | B Need date | C Lead time (weeks, incl. contracting, security review, onboarding) D Latest order date =B2-C2*7 E Status =IFS(TODAY()>D2,"LATE: start now",D2-TODAY()<=14,"Start within 2 weeks",TRUE,"OK") F Contract type Fixed price / T&M with cap / Framework call-off ``` ## Template: communication plan (two-way) | Audience | What they need | Channel | Frequency | Owner | Feedback loop | |---|---|---|---|---|---| | Sponsor and board | Forecast, exceptions, decisions needed | One-page report + meeting | Monthly | PM | Decision log | | End users | What changes, when, training | Release notes, demos, champions | Each release | Product owner | Champions' network, survey | | Suppliers | Priorities, dependencies, issues | Coordination call | Weekly | Workstream lead | Joint RAID | | Service desk | Go-live readiness, known issues | Briefing | Before each release | Tech lead | Ticket trends | ## Prompt template: stakeholder-specific updates (approved AI tool) ```text From the status table below, draft three versions of this week's update: (1) sponsor, 80 words, decisions first; (2) end users, 100 words, what changes for them and when; (3) supplier, 80 words, dependencies and dates. Use only facts in the table; mark anything uncertain as [CONFIRM]. ``` The PM checks facts and tone for each audience before sending. ## How to measure success - No person above 100% allocation for more than a week without an agreed plan. - Every procurement item has a latest order date, and none is past without escalation. - Stakeholder feedback collected and acted on each cycle. ## Video lecture: Resource, communication and procurement planning Lecture coming soon · 10 chapters · about 9 minutes. Read the full transcript below. 1. The plans beyond scope and schedule 2. Why it matters 3. The concept: resources and RACI 4. Communication and procurement planning 5. Worked example one: a RACI for five decisions 6. Worked example two: the Dubai loyalty app 7. Watch me do it: capacity and lead-time checks 8. Making communication two-way 9. Common mistakes, and supplier relationships 10. Recap and try this now ## Lecture transcript ### The plans beyond scope and schedule A retail chain in Dubai, fictional again, planned a loyalty app launch for the holiday season. The scope was clear, the schedule looked fine and the budget was approved. Then someone checked who would actually do the payment integration. The only two specialists were booked on another project for six weeks. And the payment gateway onboarding had an eight-week lead time nobody had started. Two small facts, either of which would have missed the season. In this lecture you'll learn the planning that sits beyond scope and schedule: resource planning, clarifying responsibilities with RACI, communication planning that works in both directions, and procurement planning that respects lead times. By the end, you'll be able to build a RACI and a communication plan in an afternoon, and spot the procurement item that could sink your date. ### Why it matters Why does this matter? Because schedules are built from roles, but projects are delivered by named people, who have other commitments, holidays and limits. Responsibility gaps are just as dangerous: when two people think the other is doing something, it doesn't get done, and when both think they own it, it gets done twice, differently. And procurement hides long lead times: contracts, security reviews, vendor onboarding, hardware delivery. These rarely appear on the critical path until someone checks. The fix is simple planning, done early, with real names and real dates. ### The concept: resources and RACI Here's the key idea: plan the people as carefully as the tasks. A resource plan lists named people, or at least confirmed roles, their capacity and the dates they're needed. A simple heat map of people by week shows over-allocation instantly. Look especially for critical skills held by only one or two people, because they're single points of failure. Then clarify responsibilities with RACI. Responsible: does the work. Accountable: owns the outcome and signs it off, and there should be exactly one per activity. Consulted: gives input before. Informed: told after. Think of it like a restaurant kitchen: several cooks may be responsible for a dish, but only one head chef is accountable for what leaves the pass. Keep RACI to the activities and decisions that matter; a RACI for every task becomes wallpaper. ### Communication and procurement planning Communication planning answers a simple question for each audience: what do they need to know, through which channel, how often, and who owns it? Executives might need a monthly one-page summary; users need release notes and training; suppliers need weekly coordination. And make it two-way: build in feedback loops, such as surveys, office hours or champions' networks, so you hear concerns early. Procurement planning answers: make or buy? Which contract type fits, fixed price for clear scope, time and materials with a cap for uncertain work? And, most importantly, what's the lead time? Draw lead times backwards from the date each item is needed. Any line that crosses today means you're already late, however far away the launch looks. ### Worked example one: a RACI for five decisions Let's build a quick RACI for five decisions. Release go or no-go: product owner accountable, tech lead and QA lead responsible for the readiness evidence, security consulted, the service desk informed. Scope change beyond tolerance: sponsor accountable, project manager responsible for the impact assessment, product owner consulted. Vendor selection: here's the first draft problem. Both procurement and the IT director are marked accountable. That's two A's, which means nobody really is. We agree the IT director is accountable, procurement is responsible for running the process, and finance is consulted. Data migration sign-off: the data owner in the business is accountable, not IT. And customer communications: the marketing lead is accountable, the project manager consulted. Five rows, ten minutes, and several future arguments prevented. ### Worked example two: the Dubai loyalty app Back to the fictional Dubai retailer and its loyalty app. Resource planning showed the only two payment integration specialists were booked on another project for six weeks. So the project manager negotiated one specialist part-time, and brought in a contractor under a time and materials contract with a cap, which suited uncertain integration work while limiting cost exposure. Procurement planning showed the payment gateway onboarding had an eight-week lead time, so procurement started in week two rather than when the developers were ready for it. The launch hit the holiday season. Without those two early checks, it would have missed it, and no amount of heroics in the final month could have recovered eight weeks of onboarding. ### Watch me do it: capacity and lead-time checks Let me show you the two checks I run in the first week. First, capacity. A grid of people by week, with the percentage of each person's time assigned to each workstream. A SUM per person per week, and conditional formatting that turns anything over one hundred per cent red. It takes an hour to build and immediately shows who's double-booked. Second, procurement back-scheduling. For every item we need to buy, I list the date we need it and the realistic lead time, including contracting, security review and onboarding, not just delivery. The latest order date is the need date minus the lead time. Today's date sits at the top, so any latest order date before today flags red. In this example, the gateway onboarding is already a week late. Better to discover that in week one than in week nine. ### Making communication two-way Most communication plans only describe messages going out. The best ones build in routes for messages coming back. A champions' network, one or two trusted people in each affected team, gives you early warning of confusion or resistance. Office hours give people a low-pressure way to ask questions. Short pulse surveys after key changes, three questions at most, tell you whether a message actually landed. And then the part most projects forget: close the loop. When feedback leads to a change, say so, in a simple 'you said, we did' update. For example: you told us training sessions clashed with the evening shift, so we've moved them to mornings. Nothing builds trust faster than people seeing their feedback change something, and nothing destroys it faster than surveys that disappear into silence. ### Common mistakes, and supplier relationships The common mistakes. Plans with roles but no names, so conflicts stay hidden. Several people accountable for the same thing. RACI charts for every task, which nobody reads. Communication that only broadcasts and never listens. And managing suppliers only through the contract. Contracts matter, but relationships deliver. Plan joint planning sessions, regular performance reviews and a shared view of risks with key suppliers, and treat them as part of the team where the contract allows. A self-check: can you name the one person accountable for each key decision, the audience least well served by your current communication, and the procurement item with the least slack? ### Recap and try this now Let's recap. Plan people as carefully as tasks: named resources, capacity checked week by week, and critical skills protected. Clarify responsibilities with a RACI focused on the activities and decisions that matter, with exactly one accountable person each. Build a communication plan for each audience, including feedback loops. And plan procurement early, back-scheduling lead times from need dates, and choosing contract types that fit the certainty of the work. Your try-this-now: build a RACI for six key decisions and a communication plan for four audiences on a project you know. Then find your longest procurement lead time and work out the latest date you could start it. ## Key takeaways - Plan resource demand against realistic availability and confirm commitments. - Use a RACI with exactly one accountable role per activity. - Tailor communication by audience, need, format, frequency and channel. - Start procurement based on lead times and choose contract types that match scope certainty. ## Try it Build a RACI for six key decisions and a communication plan for four audiences on a project you know. - [Previous: Estimating, scheduling and budgeting essentials](https://optimizeall.com/learn/project-management-leadership-with-ai/estimating-scheduling-budgeting) - [Next: Leading execution: kickoff, cadence and RAID](https://optimizeall.com/learn/project-management-leadership-with-ai/leading-execution) - [All lessons of Project Management Leadership with AI](https://optimizeall.com/learn/project-management-leadership-with-ai)