Free BICSI RTPM sample quiz

At initiation, establish what the project is, where it will occur, what technologies are in scope, and which people own decisions or deliverables. Review the drawings, specifications, as-builts, requests, constraints, and relevant site information. Record gaps and reconcile conflicting inputs before estimating work. A project repository is useful only when the team can tell which file is current and what decision it supports.

An initial budget estimate should expose its basis. Identify labor, equipment, materials, location effects, fees, access conditions, and lifecycle considerations that the project outline calls out. Value engineering is a review of alternatives against requirements and constraints; it is not simply choosing the least expensive item without checking performance or future support.

A proposal carries the project into an authorized scope. Study statements of work, assumptions, exclusions, qualifications, organizational charts, vendor criteria, applicable codes and standards, and the approval path. When a prompt describes a request for proposal, request for quote, or request for information, identify what response is being asked for and what evidence belongs in it.

Project plans describe how work will be organized, controlled, communicated, and verified. The RTPM outline names work breakdown structures, site-specific safety planning, quality plans, change control, risk and issues tracking, communications, environmental planning, and submittals. Understand the purpose of each artifact and how it supports a decision or handoff.

For example, a risk register records potential events, their likelihood or impact as defined by the project process, and a response or mitigation owner. A change control record identifies what changed, why, who approved it, and how schedule, cost, quality, or scope are affected. Exam questions often become clearer when you ask which plan or record makes the next step accountable.

Use actual-versus-plan checks to spot deviations early. If project cost or schedule differs from the baseline, identify the source and update the plan through the established controls. Do not treat a change as approved merely because a stakeholder requested it or field work began. The project manager’s task is to route the decision through the agreed process and communicate the resulting status.

Good status communication says what was planned, what has happened, what is blocked, what the impact may be, and who needs to act next. Use the project’s cadence and audience. A daily field update, a weekly owner summary, and a formal change record serve different purposes even when they concern the same issue.

For study practice, convert a vague update into a useful one by adding a date, milestone, measurable progress statement, dependency, risk or issue, mitigation owner, and decision needed. Keep facts separate from estimates. When a cost or schedule projection is uncertain, label it as an estimate and state the assumption that could change it.

Closure is more than announcing that installation is finished. Review the acceptance criteria, punch list, commissioning results, deficiencies, warranties, as-builts, test results, operations and maintenance information, training, and other deliverables required by the project. Confirm that the final package is complete and accepted by the right stakeholder.

Close financial items, communicate completion, capture lessons learned, and archive the final workbook and documents so the project can be supported after turnover. When reviewing a scenario, distinguish closeout from ongoing execution: if acceptance evidence or a required record is missing, the remaining action may be to resolve or document that gap before the file is considered complete.