UPI Study › Courses › Project Management › Free lessons › Lesson 8.10 Free with a free account
Project Communications and Reporting Benefits
Project Management · Chapter 8: Driving Project ExecutionSection 8.10 · lesson 53 of 7314 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Crafting Detailed Project Status Reports →← Resource Leveling, Scheduling, and Deliverable ApprovalsNext lesson: Crafting Detailed Project Status Reports →
In this lesson
Making project messages land through meetings, escalation, feedback and reports.
- Describe the do, check and change cycle of communication during execution
- Match meeting types and report types to their purpose and reader
- Design escalation routes and feedback loops that reveal misunderstanding
- Diagnose common communication failures and revise the communication plan
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,938 words). Read along, or search it.
Opening Case
Seventeen Days Before the Sponsor Knew
The sponsor learned about the delay seventeen days after the project manager did. Where did communication fail? Priya is fitting out a new clinic for Willowbrook Community Clinics, a made-up network. Her sponsor, Helen, the network director, hears about it once a month, as Priya reads out a long progress report. On day eleven, the equipment supplier told Priya that exam-room equipment due on day ten would arrive on day twenty. These are made-up numbers. Fifteen days of fit-out follow the delivery. Planned, that meant day twenty-five, five days ahead of a milestone on day thirty. Now it means day thirty-five, five days late. Two extra technicians could do the fit-out in ten days, and finish on day thirty. But that needs Helen's approval, and she hears about the delay at the monthly meeting, on day twenty-eight.
Execution Cycle
Do, Check That It Landed, Change
Communications management in execution is carrying out the communication plan, through three repeated actions. Do the planned communications on schedule. Check that each one actually landed with the person it was meant for. And change the arrangement when it didn't. Checking and changing are the actions most often skipped. A message that was sent has been delivered. It hasn't necessarily been received, understood, or acted on, and only acting changes the outcome.
Meeting Types
Five Meetings With Different Jobs
Meetings are for what written messages can't easily produce: shared understanding, a decision, or joint work. Each needs a purpose, an agenda sent ahead, and a short record of decisions, actions, owners and dates. A kickoff explains why the project exists, introduces the people, and agrees how the group will work and communicate. A status meeting is short and regular: done, next, and blocked. It surfaces problems, rather than solving them. A working session gathers only the few people needed to produce one piece of work, like the floor layout. A review meeting examines finished work against requirements, with the people who made it, the people who'll accept it, and a reviewer with authority. A decision meeting is called when a choice is beyond the manager, like choosing between two suppliers. Write the options and consequences in advance, so the time goes on choosing. Don't blend them. An hour that mixes status, a design discussion, and a supplier decision usually does all three badly, with the wrong people idle for each part.
Escalation
Handing Over a Decision, Not a Worry
Escalation passes a matter to someone with more authority, because the holder can't resolve it within their authority or the time available. The usual route runs from team member to project manager to sponsor, and, above the sponsor's authority, to a steering board of senior people. Escalating is a normal tool, not a confession. Agree the conditions in advance: a decision outside the manager's authority, a threat to a milestone or cost limit, a matter unresolved past an agreed number of days, or two stakeholders who won't yield. And escalate usefully: the problem in a sentence, its effect, the options, a recommendation, the decision needed, and the date. We have a problem with the supplier hands over a worry. With options and a date, it hands over a decision. The route should be short, because each step adds delay and distortion, and known, so anyone can say who they'd go to, and how fast an answer comes back.
Communication Flow
A Separate Path for Urgent News
Picture the flow for Priya's clinic. Routine reports and meetings run between the team, Priya, Helen, and outside stakeholders, like the neighbors' association and the equipment supplier. The escalation path is separate: Priya reaches Helen the same day, and Helen must decide, or pass it to the steering board, within two working days. If escalation shares the routine path, urgent news travels at the pace of routine news. And the outside stakeholders send something back, a reply. Without that, the plan is only broadcasting. How much to escalate is contested. One side wants strict written triggers, so nobody sits on a problem. The other trusts the manager's judgment, so the sponsor isn't flooded. No position is taken here.
Feedback Loops
Replies That Reveal Understanding
A feedback loop is a return path: the receiver shows what they received and understood, so the sender can correct the message, or act on the reply. The sender sends. The receiver replies in a way that reveals their understanding. And the sender acts on it, confirming, or repairing a gap. The test of a loop is whether it can reveal a misunderstanding. A bare acknowledgment can't, because it reads the same whether the message was understood perfectly, or not at all. Devices that close it: ask for a specific reply that shows understanding. Ask for a read-back, a restatement in the receiver's own words. End meetings with each person stating their actions. Keep an action log, where an overdue action is itself a reply. Even behavior is feedback: a delivery booked on a date the neighbors were told to avoid shows the message never landed. And acting on feedback is the step most neglected. Repeating the same message to a confused reader doesn't close the loop. Change the message, the channel, or the messenger.
Quick Check
Which Two Days Have You Written Down
Quick check. Priya is telling the neighbors' association about two days of noisy work next month. Which closing request is most likely to reveal a misunderstanding? Pause, and decide. Which two days have you written down? The answer shows exactly what they understood, so a wrong date surfaces now, not on the day. A confirmation reads the same whether the dates were understood or not. And let us know of any questions invites silence, which looks just like agreement.
Regular Reporting
Transparency, Early Warning, Trust and Decisions
Regular reporting means reports on a fixed rhythm and in a consistent form, dramatic news or not. Four benefits are claimed, each through a chain of reasoning. Transparency: everyone sees the same facts at the same time, so disagreements are about what to do, not what's true. Early warning: a deviation is cheapest to fix while small, and a trend shows only when periods are compared. So report more often than a typical problem takes to become unfixable. Trust: the sponsor relies on what the manager says, when reports arrive as promised, match what people later see, and carry bad news promptly. Early bad news makes good news believable. Better decisions: options narrow as time passes, so current facts must reach the decision-maker while choices are open. None of this is automatic: unread reports have a cost and no benefit. Some say frequent conversations beat written reports. Others say written reports leave a checkable record, reach absent people, and allow comparison. Many projects use both, and no position is taken here.
Report Types
Status, Progress, Forecast, Exception and Dashboard
Five report types serve different readers. A status report gives the overall position at a date, for a sponsor deciding whether to intervene, redirect or continue. A progress report lists work done against what the plan scheduled, and what's next. It helps a manager assign next period's work. A forecast report says what's expected from now on: the likely finish date and final cost if the present pace continues. An exception report is issued only when an agreed limit is breached: cause, effect, options, recommendation, and the date a decision is needed. It's the only one driven by an event, not the calendar. A dashboard is one visual page of a few measures, refreshed on a rhythm. It trades detail for speed, and tells a reader whether to open anything else. Status and progress get confused. A project can finish every task in a period and still worsen overall, if they were the wrong tasks.
Common Failures
Too Late, Too Long, Too Rosy, Misdirected
Reports fail in four ways. Too late: they describe a problem already past cheap correction, usually because the rhythm was set by convenience, not by how fast problems grow. Too long: what the reader needs is buried under what the writer knew. Put the decision and its deadline first, and move detail to an appendix. Too optimistic: better than the evidence supports, usually from hope or fear of blame, not dishonesty. Readers can't tell it from accuracy, and once it's found, every earlier report is doubted. Defend against it by defining each rating by an observable condition, comparing forecasts with the pace actually achieved, and making clear that early bad news is wanted. And sent to the wrong people: a cost warning mailed to the team, but not the budget holder, is accurate, on time, and useless. So every report should name its reader, the decision they can make, and the date.
Barriers
Distance, Time Zones, Jargon and Silence
Several barriers stop messages landing. Distance removes hallway remarks and visible frowns, so replace them with short daily calls and one shared place for current information. Time zones: find the overlap window, rotate the inconvenient meeting time, and favor written updates, with a recorded summary for those who missed a meeting. Language: plain words, short sentences, no idioms, and a feedback loop. Jargon: write in the reader's vocabulary, explain a term the first time, and keep a glossary. Information overload: send each person only what supports their decisions, main point first, and group routine items into regular reports. And silence from key people, the hardest to detect, because silence looks like agreement. Treat it as missing information: ask a direct question, try another channel, and if it blocks the project, escalate.
Plan Revision
Signals That the Plan Is Not Landing
Plans stop working as circumstances change. The signals: overdue actions, the same question asked again and again, a senior person saying they were never told, unopened reports, falling attendance, and people using side channels. One signal can have a harmless cause. A cluster means the plan isn't landing. The revision cycle: notice a signal, diagnose it with the people affected, change one or two things, record the change with its date and reason, tell everyone, and check again later. Here's one. The neighbors' association missed two booked noisy-work dates in three weeks. Diagnosis: the monthly dashboard went only to its chair, who didn't pass it on, and no reply was requested. Change: a one-line notice to two named contacts, ten days ahead, asking for a reply naming the date. Recorded as revision two. If the next two dates are acknowledged, the change stays.
Case Resolved
Weekly Dashboard and Exception Reports
Back to Priya and the seventeen days. Helen didn't want more to read, so Priya changed what she sent, and when. She replaced the long monthly report with a one-page dashboard every week. She agreed a simple limit with Helen: if any forecast milestone moves by more than three working days, an exception report goes out the next working day. And the monthly meeting became a decision meeting, where only choices are discussed. When a second supplier delay appeared, Priya noticed it on day three, sent the exception report on day four, and had Helen's decision on day five, two days after she first knew. The trade-off: a little more weekly reading for Helen, and some exception reports about problems that turn out minor. In exchange, information arrives while the options are still open.
Quick Check
Finance Asks for Finish Date and Cost
Quick check. Willowbrook's finance office asks Priya: what date is the clinic on course to open, and what will the fit-out end up costing? Which report answers that? Pause, and decide. A forecast report. It looks forward: the likely finish date and final cost, with the assumptions behind them. A progress report looks back at work done this period. An exception report goes out only when a limit is breached, and nothing here says one was.
Key Takeaways
Check, Change and Name the Reader
To recap: carry out the plan, check that each message landed, and change what isn't working. Use the right meeting type, with the right people, and end with a written record. Keep the escalation route short and known, and separate from routine news. Give every report a reader, a decision that reader can make, and a date. And treat silence as missing information, not agreement.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Project Communications and Reporting Benefits
Why should project meetings with different purposes be kept separate?
What is a feedback loop in project communication?
What is the difference between a status report, a forecast report and an exception report?
How should a project manager escalate a problem?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →