When the Question Is About a Buried Drain, Define the Image Record’s Limits
An aerial overview may help locate visible site features associated with a drainage question. It cannot by itself establish the route, condition or connection of a buried pipe. Before requesting documentation, decide which visible context would actually help the next reviewer and which information must come from another source.
List visible and concealed questions separately
Visible questions might concern the location of an accessible outlet or the relationship between surface features. Concealed questions concern what is below the surface or inside a component. Keep the two lists distinct in the request. A line drawn on a map is an annotation unless its meaning is supported by an identified source; its appearance does not convert it into a verified utility record.
Identify supporting records without overstating them
If the owner has plans or prior service records, identify their date and stated purpose. Ask whether the provider can include a clearly attributed reference rather than blending it into the image as a new finding. Old drawings may still be useful context, but the documentation scope should say whether their accuracy was evaluated. Preserve uncertainty about features that were not directly established.
Give the next reviewer a bounded packet
Ask for labels that distinguish visible features, owner-supplied references and unresolved questions. The reviewer can then decide whether another investigation or qualified service is needed. Avoid treating a documentation deliverable as confirmation that water reaches a particular outlet or that a buried component functions correctly. The value is organized context, not an unsupported assurance about hidden infrastructure.
Copyable worksheet
Use one row for each field. Mark unknown information clearly and retain the original records.
| Field | Your note |
|---|---|
| Visible feature to document | ____________________ |
| Concealed question outside imagery | ____________________ |
| Owner-supplied record and date | ____________________ |
| Meaning of any annotation | ____________________ |
| Reviewer needing the resulting context | ____________________ |
Worked example
Illustrative example: an owner wants to know where an old buried drain runs. The scope instead documents accessible visible features and labels an owner-supplied sketch as unverified reference information. The subsequent drainage reviewer receives a useful orientation packet while the buried route and operating condition remain explicitly unanswered.