Scope of Work
From findings to a written scope
A scope of work translates assessment findings into a clear, biddable, and verifiable set of tasks. Candidates must know the components of a complete scope: description of existing conditions, specific measures, quantities, specifications and standards referenced, responsibilities, sequencing, and acceptance criteria. In multifamily, scope must also address tenant coordination, access to units, and protection of occupied space.
Writing measurable requirements
Good scopes use measurable language. Instead of "improve air sealing," specify target leakage reduction, locations, materials, and verification method. Understand how to reference standards without copying them and how to define exclusions clearly. Know the difference between prescriptive and performance approaches: prescriptive scopes list exact measures; performance scopes state outcomes and let the contractor propose means.
Traps to watch for
Common question traps include scopes that omit verification, scopes that conflate design and installation responsibility, and scopes that fail to address health and safety items discovered during work. Watch for ambiguity in quantities and unit counts, and for scopes that do not define who handles tenant relocation or scheduling.
Worked example
For air sealing, a defensible scope might read: seal penetrations at top plates and rim joists in units 101-112 and common corridors; use listed sealants; verify with pre- and post-testing using the same test method and conditions; target a defined reduction in leakage. That is measurable, bounded, and verifiable.
Standards and Reporting
Which standard applies
Candidates should know that standards and reporting frameworks serve different purposes: test standards define how to measure, installation standards define how to build, and program standards define eligibility and documentation. Be able to distinguish consensus standards from program-specific requirements and to cite the correct one for a given task. Know that reporting must be traceable: raw data, test conditions, instrument calibration, and assumptions belong in the record.
Reporting structure
A strong report states objectives, methods, findings, limitations, and recommendations. In multifamily, reports often need unit-level detail plus building-level summaries. Understand the role of quality assurance review, data retention, and confidentiality of tenant information. When savings are reported, state the baseline, the normalization method, and the uncertainty.
Traps to watch for
Questions frequently test whether a candidate knows that a standard's scope may exclude certain building types or conditions. Another trap is reporting a result without documenting the method, or citing a standard that addresses installation when the question is about testing. Watch for confusion between required program documentation and optional best practice.
Worked example
If asked which document governs how a leakage test is performed versus how a report is formatted, separate the two: the test standard governs procedure and conditions; the program's reporting template governs format and required fields. Citing one for the other is a common error.