Skip to content

Scope and changes

"By others" on the drawings: finding out who the others are before nobody does it

By Review.LivePublished 3 min readHow we write

The corridor detail says blocking by others. The framing foreman checks the package and finds blocking excluded. The millwork quote also excludes it, yet the television mounts are due to be installed after the walls close.

A finger points to one manhole on a civil drawing next to its schedule, with handwritten notes in the margin.
Photo: ThisisEngineering on Unsplash

Trace each by-others note to a named responsible package and its agreed scope before relying on it. Check the scope matrix and the other package's documents; if neither supplies an answer, raise the assignment through the project manager's clarification process. A drawing note identifies an interface, not the identity of an appointed subcontractor. Keep design questions and commercial allocation questions distinct so the response goes to the person who can settle it.

Give the others a name and a reference

  1. Capture the exact note. Record the drawing or specification revision, detail and affected location. Describe the associated obligation, including any supply/installation split. Avoid copying only the two words into a question without enough context to identify the work.
  2. Check the shared allocation first. Look for the obligation in the current scope matrix, then follow its package reference. Confirm whether the assignment is agreed or still proposed. A buyer's pencilled assumption is not the same as an issued package obligation.
  3. Read the receiving package. Verify that its actual scope includes the identified task and relevant conditions. Check exclusions and agreed clarifications. If the package names another party in turn, follow that reference rather than accepting a circular chain.
  4. Route the unresolved question correctly. Ask the project manager to settle the package assignment with the commercial parties. Use the design-query route if the required detail itself is missing or ambiguous. A consultant's technical answer may still leave the contracting allocation to be agreed.
  5. Show the effect of waiting. Identify the workface release or purchasing decision that depends on the answer. Give the responsible coordinator a required decision date from the plan. Do not proceed around an unresolved interface merely because neither trade priced it.
  6. Record and brief the confirmed answer. Update the trace list with the package, agreed scope reference and date. Carry any commercial adjustment through the required process and tell the affected foremen. Keep the drawing's technical requirement and the contractual assignment connected without silently editing either.

Common mistakes

  • Treating a neighbouring trade's verbal expectation as a scope agreement.
  • Sending a commercial assignment question with no design issue to the wrong reviewer.
  • Closing the trace item while the issued package still excludes it.

Action list

Resolve one by-others note

  1. Exact document and location.
  2. Defined obligation.
  3. Matrix and package references checked.
  4. Design and commercial questions separated.
  5. Decision date tied to affected work.
  6. Confirmed scope briefed to the foreman.

Check your understanding

The designer confirms what blocking is required but does not name a subcontractor. Is the by-others assignment resolved?

Show the answer
The technical requirement is clearer, but the project manager still needs to settle the commercial package assignment. Record both decisions and their references. Closing one should not conceal the other open question.