FIELD VALIDATION STUDIES
Consumer Water-Saving Controller in Occupied Homes
Illustrative field validation | installation reality, routine use and household variation
Sector
Consumer water technology
Duration
6–9 weeks
Decision
Deployment route

Decision to be made
Decide whether a household water-saving controller should enter a controlled launch, and what installer guidance, user support and operating limits are required.
Project context
A hypothetical consumer-product team has a controller that works in bench tests and can be used after guided onboarding. The deployment question is whether installation variation, shared household ownership and routine maintenance support dependable use in occupied homes.
Illustrative evidence scope
- 18 occupied homes across three housing types
- 18 installers and primary household users
- Illustrative 6-week post-installation observation period
- Installation checklist, user diary, support-contact record and follow-up interviews
Installation-to-routine-use diary
The evidence follows the product from first installation through ordinary household use, so the recommendation reflects adoption conditions rather than a single onboarding moment.
Installation
Installer checklist and photo record
→
First 72 hours
Short user diary and support contact record
→
Routine use
Weekly online form and controller event summary
→
Maintenance moment
Follow-up interview
Illustrative adoption diary: evidence is followed from installation into ordinary household use, with each point tested against the next.
How the illustrative evidence would be interpreted
- Compare installation records with early-use contacts to identify whether an apparent product issue is instead caused by access, configuration or installer variation.
- Use the weekly diary alongside support records to distinguish a one-time onboarding question from a recurring adoption barrier that requires a product or guidance change.
- Review household ownership, maintenance and routine-use evidence together to define the conditions under which a controlled launch can be supported.
How the work would be delivered
August Research would define the field-equivalence criteria, scout and assess suitable external sites or participant routes, coordinate permissions and data capture, review evidence at agreed checkpoints, and translate the findings into a decision-ready pack. August Research does not own the sites or facilities used for this work.
Stage | Illustrative delivery activity | Decision checkpoint |
|---|---|---|
Week 1 | home and installer-route selection, consent and materials | Review evidence boundary |
Weeks 2–7 | installation capture, user diary and support-record review | Review evidence boundary |
Weeks 8–9 | pattern review and controlled-launch recommendation | Review evidence boundary |
Illustrative outputs
- Household adoption diary showing install, early-use and routine-use evidence
- Installer and user-support changes prioritised by recurrence and decision impact
- Controlled-launch conditions, including required guidance and observation triggers
What the decision pack would contain
The decision pack would combine the household adoption diary with install variation, support contacts and follow-up evidence, then prioritise the installer guidance, user support and launch conditions that most affect dependable use.
Note:
This is a hypothetical illustrative engagement, not a client outcome. Participant numbers, methods, timing and possible outputs are illustrative and conditional on the product, provider and participant response, permissions, logistics, data availability and project scope. Any formal assessment, regulatory interpretation or conformity decision remains with qualified providers and responsible parties.
Research and regulatory context
Numerical values are illustrative. A real study would align household recruitment, privacy controls, consent, device data and any applicable local requirements with the client and selected providers.
What we would confirm before starting
- The deployment decision, target operating conditions and evidence boundary that the study must address.
- Suitable external sites, participant roles, permissions, consent and any data-handling requirements.
- Product readiness, observation methods, escalation procedures and the practical conditions needed for safe, usable field work.
- The review checkpoints, responsible stakeholders and decision criteria for expansion, remediation, repeat testing or deferral.
Let’s Discuss Your Project
Tell us the operating environment, participant roles, workflow handovers, exceptions and deployment decision you need to make. We can shape a field-validation route around the evidence that decision requires.
Illustrative timeline
Illustrative timing: 6–9 weeks. Actual timing depends on response, access, readiness, logistics and scope.