PMP 2026 | 09 | Project Artifacts, Registers, and Logs

A project can have plenty of documents and still lack a clear basis for a decision. This glossary lesson explains what the main artifacts are meant to establish, from approved scope, schedule, and cost baselines to change, risk, issue, and assumption records. It highlights disti…

In this glossary session, we will focus on the core artifacts and logs that guide project decisions. These documents and records are referenced constantly in real work, and understanding them will make complex situations clearer. Each definition is explained in plain language, with practical details that show why the artifact exists and how it is used.

Welcome to Certified, the P M P prepcast. This is episode nine of season one. Today we are exploring the project artifacts, registers, and logs that support decisions.

Scope baseline. The scope baseline is the approved version of the project scope statement, the work breakdown structure, and the dictionary that explains each component. It defines exactly what the project will deliver and what it will not deliver. By setting this boundary, the scope baseline becomes the standard for controlling changes and keeping the team aligned. Without a clear scope baseline, projects are vulnerable to uncontrolled scope growth and shifting expectations.

We will connect these records through a fictional school-library renovation. The approved scope includes a study area, electrical improvements, accessible shelving, and a checkout workstation. It excludes replacing the school's entire wireless network. A teacher asks the project team to include new wireless equipment because the renovation seems like a convenient opportunity. The request may be sensible, but convenience does not establish authorization. The scope baseline helps the team identify the boundary before evaluating whether that boundary should change.

The work breakdown structure organizes the deliverable scope, not merely the order in which people happen to work. A work package for the checkout workstation might include the defined workstation capability and its associated completion conditions. Its dictionary entry can explain boundaries and assumptions that the short label cannot carry. The schedule then connects the activities needed to produce that result. Confusing the two can leave a project with an attractive list of dates but no agreement about what each promised result actually includes.

A useful artifact is therefore not just a document to name in an answer. It contains information needed for a particular decision. If the question concerns whether new wireless equipment is included, the authorized scope and relevant agreements are more useful than the latest spending total. If the question concerns when the electrician can begin, the network of dependencies and resource availability matters. Start with the decision, then identify the evidence. Do not reach for a favorite record simply because it often appears in practice questions.

The schedule baseline is the approved schedule used as the reference for comparing performance. The current schedule model reflects actual progress, remaining work, dependencies, and updated forecasts. A new forecast can show that a commitment is at risk without silently changing the approved reference. Investigate the cause and use the applicable authority route for a proposed baseline change. Keeping the reference and the forecast distinct lets stakeholders see both what was agreed and what the team now expects.

The cost baseline is the approved, time-phased cost reference used to monitor and control project cost. It includes the contingency reserves assigned within that baseline, while management reserve is outside it. Spending less than planned does not automatically mean efficient performance; the project may also have accomplished less work. Where earned value is used, compare the value of completed work with its actual cost and planned value. Also examine cash needs and spending authority separately, because a favorable performance measure does not itself authorize a new commitment.

At the end of a reporting period, the library project has spent less than the amount planned. The administrator calls this a saving. The project manager discovers that the shelving has not been delivered and its installation has not started. Less spending may simply reflect less accomplished work. The cost report needs to be read with progress evidence, commitments, and the schedule. Otherwise, an apparent financial success could conceal a delivery problem.

The same reporting discipline applies when a forecast worsens. The project manager should make the new expectation visible without quietly changing the approved target. A report that shows the baseline date, the current forecast, and the reason for the difference allows a useful decision. A report that replaces last month's target with this month's estimate destroys that comparison. Version control and status dates matter because a perfectly accurate number can still mislead when someone compares it with a different period or a different scope.

Change log. The change log is the record of all requests to modify the project scope, schedule, or cost. Each entry documents the request, the analysis of its impact, and the final decision. The log provides transparency and accountability, showing how decisions were made and by whom. It also helps prevent confusion by keeping a single source of truth for change history.

Return to the wireless request. The change log might record the request, its origin, its current status, and links to the impact analysis and decision. While the request is under review, it should not be presented as approved work. If it is rejected, the record should preserve that decision and its rationale rather than simply delete the entry. If approved, the affected planning and delivery information must be synchronized so that the team does not continue building from superseded instructions.

A decision log can complement a change log, but they are not necessarily identical. The team may decide how to conduct an already authorized inspection without changing the approved scope. Recording the decision can still be useful because it identifies the owner and rationale. Conversely, writing a change in a meeting note does not replace the authorization required by the project's change process. Documentation makes a decision traceable; it does not manufacture authority that the person making the note did not possess.

Risk register. The risk register is a living document that captures identified risks, their characteristics, and planned responses. It includes information about probability, impact, triggers, and owners for each risk. As the project evolves, risks are added, updated, or closed out. The risk register keeps uncertainty visible and ensures that the team addresses threats and opportunities proactively.

Assumption log. The assumption log records assumptions, constraints, and dependencies that affect the project. Assumptions are things believed to be true without proof, such as resource availability. Constraints are limits that restrict options, such as budget or regulatory requirements. The log makes these conditions explicit so they can be validated or revisited as the project progresses.

Issue log. The issue log is used to track problems that are happening right now and need resolution. Each entry includes a description, the responsible owner, the priority, and the status. Unlike risks, which are about uncertainty, issues represent actual events that must be managed. Keeping an updated issue log ensures accountability and provides visibility for stakeholders on critical problems.

Now follow one uncertainty through several records. At planning, the team assumes that the existing electrical panel has enough spare capacity for the study area. The assumption log records that belief, who will verify it, and when confirmation is needed. Because an inadequate panel could affect cost and opening dates, the team identifies a related risk. The risk register describes the possible condition and its consequence, assigns an owner, and records a response such as an early assessment by a qualified specialist.

The inspection later establishes that additional work is required. The uncertainty about panel capacity has become a known problem affecting the project. The issue log records the problem, the resolution owner, and its priority. The team updates the risk information rather than continuing to describe the failed assumption as an untested possibility. New uncertainties may emerge, such as the availability of replacement equipment. Those can remain risks even while the panel limitation is an active issue. One event can therefore create connected records without making the records interchangeable.

If the resolution changes an approved commitment, the change process may also be needed. The issue log does not authorize a budget increase just because the issue is urgent. The change log does not replace the operational work of resolving the problem. The links between records preserve the chain: what was assumed, what could happen, what was discovered, what decision was requested, and what action was authorized. A single identifier or a clear cross-reference can support that chain without copying the full narrative into five separate places.

Consider a different event. A shipment might arrive after the installation date, but the supplier has not confirmed a delay and the delivery window has not passed. That is uncertainty to investigate and manage, not automatically a completed failure. If the promised delivery date passes with no shipment, the actual condition must be recorded accurately. The distinction affects urgency and response. Do not label every concern an issue, and do not keep an actual problem hidden in a risk register as though it may never occur.

Lessons learned register. The lessons learned register captures knowledge gained during the project that may help future work. Entries can include successes, mistakes, and recommendations. The register should be updated throughout the project, not just at the end, so that improvements can be applied immediately. This record becomes part of the organization’s knowledge base once the project closes.

A lesson from the panel problem should be more useful than check electrical capacity next time. The record can explain that the initial estimate relied on an old building drawing, that an early site assessment exposed the mismatch, and that the team moved the verification before committing to installation dates. The context matters. A future team needs to understand when the lesson applies and what action prevented a larger disruption. Without that explanation, the entry may become a slogan that nobody can confidently use.

Learning should also affect the current project when it remains relevant. The team might inspect the checkout area's cabling before ordering equipment rather than waiting until installation. That action needs an owner and an appropriate place in the plan. Recording a lesson without applying an available improvement is not the same as closing the learning loop. At closeout, the useful knowledge can move into an organizational repository with enough context to be found and understood, rather than disappear into a final report that nobody can retrieve.

Stakeholder register. The stakeholder register identifies all individuals, groups, and organizations that affect or are affected by the project. It records their roles, interests, power, and engagement strategies. By maintaining this register, the project manager can plan communications, manage expectations, and build relationships effectively. It is a key tool for aligning people with project goals.

Communication management plan. The communication management plan describes how project information will be created, shared, and stored. It outlines who needs what information, when, and in what format. This plan ensures that communication is deliberate and efficient, reducing the risk of misunderstandings. It also defines feedback loops so that messages are not just sent but received and confirmed.

The library's stakeholder register initially includes the school administrator, librarian, construction supplier, and information-technology staff. The team later discovers that the after-school program relies on the same entrance and storage area. This is not merely another name to add. The new information may affect access planning, communication timing, and acceptance of the temporary arrangement. The project manager should update the engagement approach and make the relevant dependencies visible.

A communication plan answers more than how often an email is sent. The after-school coordinator may need advance notice of a closure, the administrator may need decisions about funding, and the librarian may need a clear demonstration of checkout procedures. Sending one technical progress report to everyone does not satisfy all three needs. The plan should connect the audience to the information, timing, channel, and response expected. Sensitive material should also be shared according to access rules, not exposed simply because a central repository is convenient.

Quality management plan. The quality management plan describes how the project will ensure that deliverables meet defined standards. It explains the processes for quality assurance and quality control, including roles, metrics, and review points. By laying out these expectations, the plan provides consistency and helps avoid costly defects or rework. It also aligns the team on what quality means for this specific effort.

Procurement management plan. The procurement management plan explains how goods and services will be obtained from outside the organization. It defines the approach for selecting suppliers, managing contracts, and monitoring performance. This plan ensures that procurement follows rules and that risks such as delays or disputes are minimized. It also clarifies roles between the project team, procurement staff, and vendors.

Resource management plan. The resource management plan outlines how people, equipment, and materials will be allocated and managed. It includes staffing timelines, training needs, and responsibilities. The plan helps balance workload, resolve conflicts, and ensure that resources are used effectively. By making assignments clear, it supports both team performance and accountability.

The quality, procurement, and resource plans come together when the shelving supplier is selected. The quality requirements specify the intended performance and acceptance evidence. Procurement arrangements establish the supplier's obligations and the route for handling changes or disputes. Resource planning identifies who can inspect the installation and when that person is available. A supplier delivery date is not enough if the qualified reviewer is absent and the project cannot establish acceptance before opening.

Imagine that the installer proposes substituting a different shelving system. The team needs the applicable specification, the supplier agreement, and the evaluation by the responsible specialist. It should not treat a lower price as sufficient evidence of equivalence. Nor should it assume that the project manager can amend contractual terms alone. The records support an integrated decision about suitability, obligations, resources, and schedule. Each contributes a different part of the answer.

A plan describes how the team intends to manage an area; a record captures particular information or events. The procurement management plan may explain how supplier changes will be handled, while the actual contract and an authorized amendment establish specific obligations. The quality plan may establish the inspection approach, while inspection results show what was observed. Knowing the plan is useful, but a question about whether this installation passed requires actual evidence rather than a general statement that inspections are planned.

In Scrum, the Product Backlog is an emergent, ordered list of what is needed to improve the product. The Product Owner is accountable for effective Product Backlog management, including ordering and making it transparent and understood. Items are refined as the team learns, and the backlog can include more than new features. Other adaptive approaches may use similar lists without assigning exactly the same Scrum accountabilities. Read the stated approach before assuming that the label backlog settles every role or approval question.

The Sprint Backlog consists of the Sprint Goal, the Product Backlog items selected for the Sprint, and the Developers' plan for delivering them. It is updated as the Developers learn during the Sprint. The commitment associated with it is the Sprint Goal, not an immutable promise to complete an unchanged list of items. Scope can be clarified and renegotiated with the Product Owner as more is learned, while the goal and quality remain protected. This makes the plan responsive without making the Sprint direction arbitrary.

In Scrum, the Definition of Done describes the quality state required for an Increment. It is the commitment associated with that artifact and creates a shared understanding of what work is complete. Applicable organizational standards remain part of the boundary; a team cannot lower a mandatory requirement merely to report more finished work. Acceptance criteria can describe a particular item's intended behavior, while the Definition of Done establishes the common completion requirements. Work that fails those requirements is not counted as part of a usable Increment.

Suppose a small Scrum team develops the checkout interface. A backlog item specifies that a librarian can renew an eligible loan and receive a clear confirmation. Those item-specific conditions describe expected behavior. The Definition of Done may also require integration, testing, and other common quality conditions. A demonstration that the confirmation message appears does not excuse a failure to satisfy those broader completion requirements. Both layers matter, and satisfying one does not automatically satisfy the other.

During the Sprint, the Developers discover that the renewal function depends on an undocumented data field. They update their plan and discuss what they are learning with the Product Owner. The Sprint Backlog is not a frozen contract that forbids adapting the plan. At the same time, the discovery does not give anyone permission to conceal unfinished work or abandon the Sprint Goal casually. The artifact makes the current plan transparent so that adaptation is visible rather than improvised in private.

A backlog also does not replace every other record the organization needs. A feature card may link to a requirement, a decision, or a test result without copying all of those records into the card. The team should tailor the level of detail to the work while keeping important obligations traceable. Lightweight means information is efficient and usable; it does not mean nobody can explain what was agreed, who made the decision, or how completion was established.

Work breakdown structure. The work breakdown structure, or W B S, is a hierarchical decomposition of the project’s scope into smaller components. It divides large deliverables into manageable work packages that can be planned and tracked. The W B S helps clarify responsibilities and prevents scope from being overlooked. It is one of the foundational artifacts in predictive project management.

R A C I matrix. A R A C I matrix is a responsibility assignment chart that clarifies who is Responsible, who is Accountable, who must be Consulted, and who is Informed for each activity. By mapping roles to tasks, it reduces confusion and overlap. The matrix is especially useful in complex organizations where responsibilities may be shared across functions. It creates alignment by making accountability visible.

A responsibility matrix is most useful when it refers to a specific activity or decision. For the library opening, one person might coordinate the readiness review, another have authority to approve opening, and several specialists supply evidence. Saying everyone is accountable for opening sounds inclusive but can conceal the absence of a decision-maker. The matrix should align with actual delegations and agreements, not create a new authority structure merely because someone typed a name into a cell.

The distinction between consulted and informed is practical. A specialist whose input is required before accepting an electrical modification should not learn of the decision afterward through a general update. Someone who only needs the final opening date should not be forced into every technical discussion. The project manager should check whether the matrix matches how the work actually proceeds. When responsibilities change, the affected people need to understand the change rather than discover it when a deliverable is waiting for approval.

Kanban board. A Kanban board is a visual tool for managing work in progress. It displays tasks as cards moving across columns such as “to do,” “in progress,” and “done.” This visualization helps teams limit work in progress, identify bottlenecks, and maintain flow. Kanban boards are commonly used in agile teams but can also benefit other project contexts.

A burndown chart shows remaining work over time using the chosen unit and scope definition. A falling line may indicate completed work, but it can also result from removing work or changing estimates. A flat or rising line may reflect blocked delivery, new scope, or improved understanding. Check the underlying changes before calling the pattern good or bad. Read the chart alongside acceptance evidence and scope information so that a better-looking line does not hide incomplete work or a changed commitment.

The library team visualizes its remaining work on a board. Several items accumulate in a column called waiting for inspection. Moving those cards to done would improve the appearance of the board without completing an inspection. Adding more installation work might increase the queue rather than shorten it. The useful question is why inspection is constrained and what can be done within the relevant responsibilities. A visual board helps reveal the condition, but a column name is not a diagnosis.

Now imagine a remaining-work chart drops sharply. The team explains that it removed an optional display feature after an authorized decision. The drop is real, but it does not represent the same accomplishment as completing that feature. An honest narrative distinguishes scope removed, work completed, and estimates revised. This is why a chart should be read with the underlying records rather than used as a substitute for them. Better-looking progress is not necessarily more delivered value.

Before relying on any project artifact, ask whether it is current, whether its status is clear, and whether you have the relevant version. A draft requirement, an approved requirement, and a superseded requirement can contain identical-looking headings but imply very different authority. Check the owner and effective date when that matters to the decision. If two records conflict, identify the controlling agreement and resolve the discrepancy through the appropriate people. Do not choose whichever version makes the preferred answer easier.

Your practice task is to trace a single library event across its evidence. Start with the assumed panel capacity, move to the risk of extra work, then the confirmed issue, the proposed change, the authorization, and the updated schedule forecast. Finally, identify the inspection evidence and the lesson for future projects. Explain why each record exists and what it cannot authorize on its own. That exercise turns a glossary into a decision trail, which is the real reason these artifacts matter.

For more certification study resources, books, and podcasts, visit Bare Metal Cyber dot com. Thank you for listening to Certified, the P M P prepcast.

PMP 2026 | 09 | Project Artifacts, Registers, and Logs
Broadcast by