Course 04 — Interpreting Requirements and Obligations

Series · Case · Glossary · References

Interpret a retrieved statement to understand whether and how it governs work. You must establish its authority, applicability, meaning, and conditions. You must also recognize where the available sources cannot support a conclusion.

This course teaches a method for interpreting project requirements and organizing an external-requirements enquiry. The offline exercise uses Northbank Packet A. It does not assign Northbank a real jurisdiction or code edition.

Prerequisites and outcomes

Complete Courses 01 to 03. Read A01, A02, A05, and A06 closely. Keep your evidence packet available.

By the end, you can:

• Identify the authority and purpose of a requirement source.
• Explain how applicability differs from technical relevance.
• Read definitions, conditions, exceptions, and cross-references in context.
• Distinguish a requirement, proposal, assumption, and interpretation.
• Prepare an interpretation memorandum with unresolved matters and affected decisions.

Lesson 1 — Establish why the statement governs

Sources enter a project through different relationships. Legislation can impose obligations within its jurisdiction and scope. Contracts can establish obligations between identified parties. Approved project decisions can define the assignment. A technical reference can inform analysis without itself governing the assignment.

Establish the relationship for the actual source. Do not infer it from a familiar title or an organization's reputation. A standard can be technically useful without being adopted into the governing requirements. Its role may also follow a contract or another applicable instrument.

An applicable obligation can govern before the team recognizes it. Interpretation identifies that obligation. It does not create project authority to waive it.

The National Research Council explains that Canadian model construction codes acquire legal authority through government adoption. Adoption can include amendments. This example shows why a publication's existence does not establish its applicability. It does not identify the requirements for Northbank. NRC model-code context

The governing edition needs evidence. A recently published edition may differ from the edition adopted or specified for the assignment. Check the effective dates, relevant amendments, transition provisions, and actual work conditions. Obtain suitable expertise where the interpretation requires it.

Do not build a universal precedence ladder from source categories. Several obligations can apply together. Their relationship depends on the actual instruments and circumstances. A contract may specify a conflict process, but that process does not erase applicable external duties.

Apply this authority enquiry:

1. Identify the exact statement and source edition.
2. Identify the instrument or decision that gives it standing.
3. Identify the people, asset, activity, and location it covers.
4. Check its effective period and amendments.
5. State its role for this assignment.
6. Record any missing basis for that role.

At Northbank, A02 Rev 1 has a recorded project-development approval. A06 leaves external legal applicability open. These are separate findings.

Lesson 2 — Read the requirement in its context

A clause can change meaning when separated from its definitions and conditions. Read enough of the source to preserve those relationships. Follow relevant cross-references rather than assuming that the local sentence is complete.

Find the actor, required act or result, object, conditions, and limits. Identify any exception and the evidence needed to invoke it. Check whether the source defines ordinary words differently. Preserve those definitions in the interpretation.

A statement can contain both a requirement and an unresolved definition. A02 requires 18 litres per second at the distribution header. It also requires the project to establish the operating conditions. The number alone does not define a complete performance examination.

Read qualifying language carefully. “Under the operating conditions that the project must establish” makes those conditions necessary to the requirement's application. Removing that phrase would enlarge the apparent evidence from a single measurement.

Do not treat permission as an obligation, or a recommendation as an adopted commitment, without the relevant basis. Use the source's actual conventions. The force of a word depends on the instrument and its definitions.

Use a contextual reading method:

1. Read the surrounding section.
2. Identify the relevant definitions.
3. Find the required actor and result.
4. Identify the stated conditions and limits.
5. Follow the relevant cross-references.
6. Restate the requirement without losing its conditions.

Keep the original passage available beside the restatement. Ask another participant to compare them. A useful interpretation makes the source actionable while preserving its meaning.

Lesson 3 — Connect applicability to the actual assignment

Applicability is the relationship that makes a requirement govern the work under stated conditions. Technical similarity alone cannot establish it. Two systems may use similar components while falling under different requirements.

Identify the actual asset and work boundary. Determine what is existing, what changes, and which activities the assignment includes. Record relevant operating conditions and facility characteristics. These facts help the competent participants evaluate applicability.

The Northbank description states that the water is non-potable. That fact cannot establish a complete legal classification. The case gives no real jurisdiction, permit basis, adoption instrument, or contract references. A06 requires the team to identify those gaps.

For each candidate requirement, record the source, applicability conditions, matching project evidence, conclusion, and unresolved questions. A conclusion can be “unresolved” when a necessary fact or instrument is missing. Explain the decisions that it prevents.

Assign an owner who can obtain the input or arrange competent interpretation. State the point of need. An open enquiry becomes manageable when people know what result is required before dependent work proceeds.

Apply this applicability method:

1. Define the asset and work boundary.
2. Identify the jurisdiction and relevant authorities.
3. Identify the facility and activity classifications.
4. Obtain the governing instruments and contract references.
5. Compare their conditions with verified project facts.
6. State the conclusion and unresolved matters.
7. Identify the decisions that depend on resolution.

The method guides an enquiry. It does not make the learner a legal authority. Seek authoritative clarification or legal expertise where the actual question requires it.

Lesson 4 — Resolve ambiguity without inventing authority

An interpretation explains how a source applies or what it means. A decision authorizes an act within a stated authority. A change amends a controlled basis through its governing process. These acts can be related, but their effects differ.

A project engineer may explain that A05 is a proposal. The explanation does not reject the proposal or amend A02. The sponsor's requested impact assessment gives the team further work to perform.

When sources appear inconsistent, preserve their identities and ask what relationship explains the difference. An earlier draft, a proposed change, and an approved basis may contain different values without creating an unresolved authority conflict.

Where a genuine conflict remains, identify both statements and the consequence. Use the actual clarification or dispute process. Do not choose the most convenient statement or automatically choose the one that appears more demanding. Its technical effects may also need examination.

An interpretation memorandum should state the question, sources, context, reasoning, conclusion, limits, and next action. Make uncertainty specific. “More information is needed” gives little direction. Identify the missing input and the decision it blocks.

Use this memorandum method:

1. State the question and proposed reliance.
2. Cite the exact source revisions.
3. Explain the relevant context and applicability.
4. Compare the possible readings.
5. State the supported interpretation.
6. Identify the clarification or decision still required.
7. Name affected work and receiving participants.

An interpretation can reveal an existing obligation missing from the project basis. Record that obligation and assess the affected work. The obligation does not await sponsor adoption.

Any resulting scope, resource, or commitment change still needs its proper authority. Connect that decision to change control. Preserve the earlier reasoning. Notify affected owners and examine adoption in their work.

Northbank worked example — Flow and changeover

The question is: “What must the equipment-development work provide under Packet A?” The consumer is the project engineer preparing the technical assignment.

A02 Rev 1 requires 18 litres per second at the distribution header under conditions the project must establish. It requires two pump units, with one operating and one standby. It requires confirmation of the changeover function with operations.

A05 Rev 0 proposes 22 litres per second and automatic changeover. It records no scope amendment. The sponsor requests an impact assessment.

The memorandum avoids calling automatic changeover an approved requirement. It also avoids treating standby provision as a complete changeover design. The assignment can gather inputs and examine the proposal. Final dependent conclusions still need the stated basis.

Transfer example — A software availability specification

Use this invented contract exercise: Specification S1 says, “Provide a monthly availability report using the measurement method agreed with the customer.” Request S2 says, “Please add automatic compensation calculations.” No amendment is recorded.

S1 requires the report but leaves the measurement method for agreement. S2 proposes additional work. The analyst must obtain the method and assess the proposed calculation scope. The analyst cannot infer a compensation obligation from S2 alone.

These are fictional assignment statements. They are not legislation, code clauses, or legal opinions.

Practice — Interpret and enquire

Use Packet A and Portfolio 03. No external reading is required.

Supply these outputs:

1. An interpretation memorandum for the flow, two-unit, and changeover statements.
2. A list distinguishing approved requirements, proposals, observations, and unresolved matters.
3. An A06 enquiry covering jurisdiction, facility classification, asset boundary, permits, adoption instruments, and contract references.
4. An affected-decision list for each missing applicability input.
5. A request to the appropriate appointed participant for the next action.

State which facts the case supplies and which it leaves open. Do not invent a statute, code clause, adoption edition, exemption, or regulator ruling. Ask a partner to identify any sentence that claims more authority than its source provides.

Knowledge check

1. How does technical relevance differ from applicability?
2. Why does a published code edition not automatically govern an assignment?
3. Which conditions must remain attached to A02's flow requirement?
4. What is the relationship between A02's changeover statement and A05's automatic-changeover request?
5. What inputs does A06 require before a real applicability conclusion?
6. How do an interpretation, an authorized decision, and a controlled change differ?

Assessed assignment — Establish the interpreted basis

Prepare a memorandum for Northbank project development. Include the practice outputs and a requirement table. State a proposed examination for each approved project requirement at the available level of definition.

An instructor assesses five observable criteria:

Defend one interpretation orally. Show the passage and explain an alternative reading. Repair any invented obligation or lost qualification. Training acceptance grants no authority to determine real legal applicability.

Portfolio continuation and references

Keep the memorandum as Portfolio 04. Link each requirement to its controlled source and evidence entry. Course 05 will use this basis to reason about alternatives, uncertainty, and recommendations.

The Field Book, section 3, supports separate treatment of requirements, assumptions, proposals, and open matters.

The NRC model-code explanation illustrates adoption in Canadian construction. It is background reading, not an adoption instrument for Northbank. Read the series reference limits before using an external source.