Seattle / note 30

Arrange changed drains by floor, time, and use order

Several slow or noisy drains can involve a broader route, but the pattern still does not decide whether the cause is a fixture branch, building drain, private side sewer, shared pipe, or public main.

Call about the plumbing877-702-1610

OBSERVERoom / trigger / extentVERIFYIdentity / scope / terms

Scene note

Stop contributing water if wastewater rises. Place each affected toilet, sink, tub, shower, appliance, or floor drain on a simple level map and identify the first change.

First five minutes

Put these five details on the same page

Each note narrows the conversation without pretending to reveal a concealed cause.

Fixture list

Name every changed drain and keep unaffected observations on the map.

Lowest point

Identify the first low fixture that rises, gurgles, or slows.

Use order

Write which fixture or appliance ran before each visible change.

Wastewater return

Leave the area and stop testing when contaminated water appears.

Building context

Add neighbor reports and notices without turning them into a diagnosis.

Solution map

Keep responsibility visible while the evidence changes

Include the order fixtures were used, the lowest return point, rain context, other unit reports, and any current SPU message. Preserve uncertainty around responsibility.

01Protect the immediate area.
02Write what can be observed safely.
03Identify the responsible party.
04Authorize a supported scope.

Closeout note

Leave the next reader a usable record

File the inspected route, access point, camera or measurement evidence, supported finding, completed work, fixtures retested, and any public or shared issue still open.