BU 396 Unit 7 monitoring and review plan example

Managing Project Risks Herzing University Free custom sample in 24 to 48h

The BU 396 Unit 7 monitoring and review plan below keeps a composite riverfront festival's risk register current from late July through the last gate closing, with a cadence that moves from every other Tuesday to every morning. Herzing BU 396 typically asks how the register stays alive, and this project management sample answers with a short, operational plan: which meeting carries the review, who must attend for it to count and how long it takes; five off-cycle triggers such as a scope change, a supplier change or a weather watch; an indicator table naming what is watched, the source, the threshold, the watcher and the frequency; rules for tracking draws on the $35,000 reserve; and escalation criteria. On festival days, weather decisions follow National Weather Service guidance, with authority set in advance so no one improvises in a storm. PMI's risk standard and Kendrick frame the plan.

CourseBU 396 Managing Project Risks
UnitUnit 7
Paper typeMonitoring and review plan
LengthAbout 870 words, 6 pages
FormatAPA 7 student paper
SchoolHerzing University
ProgramBS in Project Management
UpdatedSeptember 2026

Free sample paper for BU 396 Unit 7

1

Every Other Tuesday, Then Every Morning: A Monitoring and Review Plan That Keeps a Composite Festival's Risk Register Current Through the Last Gate Closing

Student Name

Business, Herzing University

BU 396: Managing Project Risks

Instructor Name

July 22, 2026

What this page is doingThe title shows the cadence tightening as the event approaches and names the endpoint. A monitoring plan is operational, and a title built on when reviews happen signals that the document is about practice, not principles.
2

Every Other Tuesday, Then Every Morning: A Monitoring and Review Plan That Keeps a Composite Festival's Risk Register Current Through the Last Gate Closing

Purpose

This plan sets out how the festival's register stays current from late July through the close of the festival on August 23, 2026. It fixes the review cadence and the meeting that carries it, the events that force a review outside that cycle, the indicators watched for each entry with a trigger, how draws on the $35,000 risk reserve are tracked and when an entry escalates to the sponsor. The plan is short and operational by design. Kendrick (2015) observes that registers most often fail not in their construction but in their upkeep, when reviews slip and triggers go unwatched, and each section here answers a practical question about upkeep.

Cadence

The full register is reviewed at the core team's existing meeting, which moves from every other Tuesday to every Tuesday from July 21 and to every morning at 8:00 from August 17 through August 23. A review counts only if the events director, the operations lead and the finance manager attend, along with the owner of any entry whose trigger has fired. The weekly review is expected to take 30 minutes; the daily reviews in festival week, 15. At each review, owners report on their entries' triggers and actions, ratings are updated if conditions have changed and every change is written into the change log before the meeting ends. Entries are never deleted; closed entries remain with the date and reason.

If a scheduled review cannot be held, for example because the core team is on site for a vendor walk-through, the events director holds a shortened review by phone with the three required attendees the same day. A review is never skipped, because a missed week in late July removes one of only four chances to act on a trigger before the festival.

Off-Cycle Triggers

Five events force a review before the next scheduled one, called by the events director within 24 hours. The first is any approved change to scope, such as adding a stage or changing the site layout. The second is a change of supplier or sponsor, including a withdrawal, a substitution or a supplier changing ownership. The third is a severe thunderstorm watch or excessive heat watch issued by the National Weather Service for the county during festival week. The fourth is any new condition placed on the special event permit by the city. The fifth is a serious incident at a comparable outdoor event in the region, such as a structural collapse or crowd crush, since such events often lead authorities to tighten requirements.

Indicators Being Watched

For each entry with a trigger, the plan names what is watched, where the information comes from and who watches it. The table lists them. A usable trigger is specific, observable by the owner without special effort and early enough to leave time to act, which is why the weather triggers look at watches and forecasts rather than at warnings, which may come too late.

EntryIndicatorSourceTrigger levelWatched byFrequency
R01 StormsSevere weather outlook and watchesNational Weather Service forecast office and outlooksWatch or enhanced outlook for the county within 48 hoursWeather monitoring service, reported to events directorTwice daily in festival week
R03 HeatForecast heat indexNational Weather Service forecastsAbove 100 degreesOperations leadDaily from August 15
R02 WindForecast sustained windNational Weather Service forecastsAbove 25 mphProduction managerDaily from August 17
R04 RiverForecast river crestNational Weather Service river forecast for the local gaugeAbove minor flood stageOperations leadWeekly, daily if rising
R07 VolunteersConfirmed volunteer shiftsVolunteer scheduling systemBelow 80% of target on August 1Volunteer coordinatorWeekly
R14 TicketsAdvance sales against planTicketing platform reportBelow plan two weeks runningFinance managerWeekly
R09 VendorsVendor cancellationsVendor coordinator's logThree in one weekVendor coordinatorWeekly
R12 PowerGenerator load testRental company test on August 21Failed testProduction managerOnce, then each morning
What this page is doingEach trigger names an indicator, a source, a threshold, a watcher and a frequency. Those five elements are what make a trigger usable in practice, and the rubric looks for them rather than a general promise to monitor.
3

Tracking the Reserve

The risk reserve of $35,000 set in Unit 5 is tracked in a single line on the register's summary sheet showing the amount drawn, the amount remaining and each draw listed with the entry it paid for, the date and who approved it. The project manager may approve draws up to $5,000; larger draws require the sponsor. The reserve may be used only for the consequences of entries in the register or for responses approved in the register, not for unrelated overruns, which go through the Partnership's normal budget process. At July 22, no reserve has been drawn: a replacement sponsor and the tourism grant absorbed the April withdrawal. The remaining balance is reported at every review, so the team always knows how much protection is left before the weekend.

Escalation

An entry escalates to the sponsor, the Partnership's board chair, within 24 hours if its score rises to 15 or more, if any safety impact is rated 4 or 5, if a reserve draw above $5,000 is needed or if its remaining rating rises by two or more bands between reviews. During the festival itself, weather decisions cannot wait for the sponsor. The events director, with the police lieutenant and the EMS supervisor, has authority to delay, pause or clear the site, following National Weather Service guidance that people should move indoors when thunder is heard and wait 30 minutes after the last thunder before returning (National Weather Service, n.d.). The sponsor is informed immediately after any such decision. Guidance from the Project Management Institute (2019) describes escalation as moving a decision to the level with the authority to make it, and this plan sets that level in advance so no one has to work it out in a storm.

When the Plan Ends

Monitoring ends when the last gate closes on August 23 and the site is cleared. Open entries are then closed, realized entries are linked to their issues and the register, change log and reserve record are archived with the festival's final report for use in planning the next year's event. The event and everyone in it are invented for teaching.

References

Kendrick, T. (2015). Identifying and managing project risk: Essential tools for failure-proofing your project (3rd ed.). AMACOM.

National Weather Service. (n.d.). Lightning safety tips and resources. National Oceanic and Atmospheric Administration. https://www.weather.gov/safety/lightning

Project Management Institute. (2019). The standard for risk management in portfolios, programs, and projects. Project Management Institute.

BU 396 Unit 7 instructions, in plain terms

The Unit 7 assignment asks students to describe how the project's risks will be monitored and the register kept current. Most versions want the review cadence and forum, off-cycle events that trigger additional reviews, the indicators or triggers watched for key risks, how contingency or reserve use is tracked and the criteria for escalating risks to the sponsor. Many rubrics ask for specific, observable triggers rather than general statements about monitoring. Instructors reward operational detail such as attendance requirements and time frames. The plan can adapt an existing workplace process if it is described clearly. Expect a short document of a few pages with an indicator table, with sources in APA 7, and make sure the cadence changes as the project nears its deadline.

How this BU 396 Unit 7 example is built

The sample states its purpose and why upkeep matters. A cadence section names the meeting, the attendance required, the time expected and what happens at each review, and it adds a rule for when a meeting cannot be held. An off-cycle section lists five events that force an early review. An indicator table gives each triggered entry an indicator, a source, a threshold, a watcher and a frequency. A reserve section explains how draws are logged, approved and limited to register entries. An escalation section sets criteria for moving decisions to the sponsor and gives on-site weather authority to named roles. A short final section explains how monitoring ends and records are archived for next year.

Where the points sit in the BU 396 Unit 7 rubric

Herzing's grading for the monitoring plan commonly weighs the review cadence, the triggers and indicators, reserve tracking and escalation rules. Cadence earns full points when the forum, frequency, required attendees and duration are specified, and when the frequency increases as risk rises. Triggers score highest when each is specific, observable and early enough to act on, with a named source and watcher, as the sample's table provides. Reserve tracking is judged by clear rules for logging and approving draws and for limiting the reserve to register entries. Escalation rewards criteria that match the risk plan and account for decisions that must be made immediately. Instructors also credit a defined end to monitoring. Concise, practical writing and citations complete the grade.

Common BU 396 Unit 7 mistakes, and how to avoid them

A frequent Unit 7 mistake is writing that risks will be monitored regularly without saying when, where or by whom. Another is choosing triggers that fire too late to act, such as a warning already in effect. Students often forget to say how reserve spending will be tracked, which lets contingency drain unnoticed. Some plans escalate everything, which overloads the sponsor, or nothing, which leaves serious risks with the wrong person. Others ignore decisions that must be made on the spot. Finally, keep the plan short and usable; a monitoring plan is a set of instructions for busy people, not an essay about risk management theory.

Get a BU 396 Unit 7 example written to your instructions

Attach the Unit 7 instructions and your BU 396 rubric, plus the register and any governance structure the case supplies. We write a custom example that lands the review on an existing meeting, lists off-cycle triggers as events, ties each indicator to an entry, tracks reserve draw and sets escalation by threshold. First custom sample free, returned in 24 to 48 hours.

More BU 396 papers and project management samples

BU 396 Unit 7 questions, answered

How often should the register be reviewed?

Often enough that a trigger cannot pass unnoticed, which depends on how fast the project moves rather than on a standard interval. Tie the frequency to something in the case: the reporting cycle, the gap between milestones, the notice a critical supplier requires. Then say what would make you review sooner, because that sentence is usually what the criterion is looking for.

What makes a usable trigger condition?

Something a person could observe without holding a meeting. A specification unsigned by a stated date, a second defect found in the same component, a lead time quoted longer than the plan allows. Triggers phrased as the risk becoming more likely need exactly the judgment they were meant to replace, and a register full of them gets monitored by nobody in practice.

Can I use the review process my workplace runs?

Not as a document. Governance calendars, escalation matrices and the register review your employer holds are internal arrangements, and coursework travels outside the company. Build the cadence from the case project and the plan written in Unit 1. Knowing how such reviews behave in practice will improve the writing without any of that material being reproduced on the page.

Where can I find a free BU 396 Unit 7 sample paper?

The whole BU 396 Unit 7 plan, cadence through escalation, sits above, open to anyone. Should your project need its own monitoring plan, send over the register and instructions and one will be drafted for you at no charge, typically within 48 hours.

What makes a usable trigger in BU 396 Unit 7?

A trigger is usable when it is specific, observable without special effort and early enough to leave time to act. The sample watches weather watches and forecasts rather than warnings, and it names the source, threshold and person responsible for each trigger.