DEV Community

Bay Yard Co
Bay Yard Co

Posted on

I turned a landscape field checklist into a client-side risk score

Most homeowners do not need another photo of a beautiful patio. They need to know whether the ground under that patio is quietly setting up a five-figure repair.

That was the idea behind our yard drainage risk check. It compresses the field questions we ask before exterior construction into eight yes/no checks, then returns a 0-100 exposure score and a short action list. No account. No photo upload. No lead form before the person gets value.

Why not just publish another checklist?

Long checklists are useful to contractors and easy for homeowners to abandon. During storm season, the user is often standing in a wet yard, worried about a slope, muddy path, or water near a door. They do not need a 3,000-word article first. They need to know:

  1. Is this a cosmetic annoyance or a failure pattern?
  2. Should they cover it with gravel, furniture, or pavers now?
  3. What should they document before more rain changes the evidence?

The risk checker answers those questions in plain construction language. Each answer represents a precursor we see before a repair: ponding, flow toward a structure, soil movement, negative slope, a false "permanent" fix, too much impervious cover, adjacent slopes draining into the use area, or repeated moisture.

The scoring model

The first version is deliberately simple. Every question has a weight based on how strongly it correlates with escalation in our project scoping experience:

const questions = [
  { id: "ponding", label: "Does water pond for more than 24 hours after rain?", weight: 20 },
  { id: "foundation-flow", label: "Does roof, patio, or yard water drain toward the structure?", weight: 15 },
  { id: "erosion", label: "Are there rills, exposed roots, or moving soil after storms?", weight: 15 },
  { id: "negative-slope", label: "Does the yard or patio slope toward the house, door, or retaining wall?", weight: 15 },
  // ...
] as const;

const result = questions.reduce(
  (total, question) =>
    total + (formData.get(question.id) === "yes" ? question.weight : 0),
  0,
);
Enter fullscreen mode Exit fullscreen mode

The result maps to four bands:

  • 0-24: lower observed risk, with maintenance and documentation reminders.
  • 25-54: moderate warning signs; this is usually the least expensive correction stage.
  • 55-79: high failure exposure; covering the symptoms can hide evidence and increase scope.
  • 80-100: urgent storm-season risk; protect access and move water away from structures first.

A simple model is not a weakness when the domain knowledge lives in the inputs. The difficult part is not the arithmetic. It is choosing questions that predict field failure and writing labels that a homeowner can answer accurately without a surveying background.

No data collection

The calculation runs in the browser. The result screen uses the score to build a contextual link to a site-review request:

href={`/quote?utm_source=bayyardco&utm_medium=internal_tool&utm_campaign=drainage-risk-check&utm_content=score_${score}`}
Enter fullscreen mode Exit fullscreen mode

That keeps attribution useful without turning the risk check into a surveillance form. A visitor can get the answer, decide whether to contact us, and leave with the page still useful.

Accessibility choices

The form uses a fieldset, semantic radio inputs, and visible labels. The result panel uses aria-live="polite" so the status change is announced after submission. We kept the action list short because a screen-reader user should not have to traverse a wall of conditional paragraphs to learn the next step.

The harder accessibility problem was tone. "Grading section" means something to a builder; it may not mean anything to a renter or first-time homeowner. The final copy mixes construction language with concrete observations: water ponding for more than a day, soil moving, moisture tracking indoors, or a patio sloping toward a door.

What we learned

The most valuable screen is not the score. It is the action list. The score gives people a reason to care; the actions make the tool shareable. Community groups, agents, inspectors, and editors can send the URL without explaining a pricing funnel.

That is also why the result has a citation block asking people to attribute Bay Yard Co if they share the checker. It is a small product surface, but it gives the underlying Bay Area yard failure report a practical entry point.

Limits

This is a triage aid, not a site survey. It does not measure elevations, inspect a retaining structure, calculate hydrology, or identify utilities. A real diagnosis still requires access review, grading, soil, discharge path, structures, and construction constraints.

But as a first digital touchpoint, "answer eight field checks and get a risk band" beats "read our homepage and trust us." It turns tacit field knowledge into something a homeowner can use before the next storm makes the problem more expensive.

The checker is live here: bayyardco.com/tools/yard-drainage-risk-check.

Top comments (0)