Smart Watering Decision Form — Read Your Yard's Micro-Weather Before You Turn On the Tap

1. How This Form Works

This form helps you make a calmer, more informed outdoor watering decision by combining three simple observations: how much rain fell recently, how wet the soil is a few inches down, and how thirsty each planted zone actually is. The goal is to avoid watering ground that is already moist, and to give water only where it will do some good.

Nothing here is a professional horticultural, engineering or regulatory assessment. Conditions vary widely from property to property, so treat the results as a practical planning prompt rather than a guarantee. When in doubt, check local guidance from your water provider or extension office, and observe how your own plants respond over time.

Please complete the sections in order. Fields marked as required must be filled in before the form can be submitted.

 

Have you already watered any part of this property within the last 24 hours?

 

Please note which areas were watered, roughly how long, and what time of day:

 

Would you like this form to suggest a first-time baseline watering plan for a new or recently planted area?

Is this the first time you are using a micro-weather based watering check on this property?

 

Briefly, what worked or did not work during your previous watering checks?

2. Garden & Property Profile

Property or garden label (for your own reference)

General location or climate description

Which setting best describes the area you are assessing?

 

Please describe the setting:

Approximate total planted or lawn area

Which unit are you using for area measurements in this form?

Which sun and exposure conditions apply to the property today? (Select all that apply)

What is the dominant soil texture you observe when you dig a small hole?

 

Does water tend to puddle on the surface for more than a few minutes after rain or irrigation?

 

Do you notice water running off or draining away very quickly during watering?

Is there a mulch layer (wood chips, straw, leaf litter, gravel or similar) over most planted beds?

 

Roughly how deep is the mulch layer?

 

Is there a reason mulch is not used? (Optional — this helps interpret how fast the soil dries out)

3. Micro-Weather Observations

Micro-weather means the conditions in your own yard, which can differ from the nearest official weather station. A shaded corner, a wind tunnel between buildings, or a heat-reflecting wall can change how quickly soil dries out. Record what you can actually see and feel.

 

Which rainfall unit are you using for this form?

Yesterday's local rainfall (mm or inches)

How did you measure or estimate yesterday's rainfall?

Approximate rainfall total over the last 7 days (same unit as above)

Did rain fall in a short heavy burst rather than a slow soak?

 

Please describe what you observed, such as runoff, pooling or erosion:

Soil Depth Moisture Test

 

Can you squeeze the soil and see water between your fingers or standing in the hole?

 

How does the soil feel at about 5 cm (2 inches) deep?

 

Have plants in the affected area already shown signs of stress such as wilting, leaf curl or dull colour?

Where on the property did you perform the soil moisture test?

Is more rain expected within the next 24 hours?

 

Roughly how much rain is expected, and when?

 

Is a stretch of dry, hot or windy weather expected in the coming days?

Approximate daytime high temperature expected today

Which temperature unit are you using?

Approximate relative humidity today (percentage)

How windy does it feel on the property today?

Any unusual local conditions worth noting today? (Select all that apply)

4. Plant & Landscape Sensitivity

Different plants hold water differently. Deep-rooted or drought-tolerant plants can often skip a watering day, while shallow-rooted or moisture-loving plants may need shorter, more frequent drinks. Use your own observations alongside these general categories.

 

Which plant categories are present on the property? (Select all that apply)

 

When was the new lawn seeded or laid?

 

Which crops are currently growing in the beds or boxes?

 

Please describe the other plantings:

Were any plants installed or transplanted within the last four weeks?

 

Which plants are newly installed, and how are they settling in?

Overall, how would you describe the current health and appearance of the planting?

 

Which stress signs have you noticed? (Select all that apply)

Are there any plants with unusually high water needs, such as shallow-rooted vegetables or moisture-loving flowers, in a sunny or windy spot?

 

Please list those plants and where they are located:

Are any plants deliberately being kept on the dry side to encourage deeper rooting or hardening off?

 

Please note which plants and the reason:

5. Irrigation System Details

How is water normally delivered to the garden?

 

Do the spray heads overlap so that some areas receive water twice during a cycle?

 

Are the drip emitters or lines checked regularly for blockages or splits?

 

Approximately how many litres or gallons of stored rainwater are currently available?

Is the irrigation on an automatic timer or controller?

 

What start time and run duration is currently programmed?

 

Would you consider watering in the early morning or evening to reduce evaporation losses?

Estimated flow rate of your water source (litres or gallons per minute)

Have you checked for leaks, broken heads, split hose or dripping connections recently?

 

What did the leak check find?

 

Please describe the leak and where it is located:

 

When do you think you last checked the system for leaks?

Date of the most recent irrigation system maintenance or adjustment

Does the property have any local watering rules, community guidelines or shared agreements to follow?

 

Please summarise the watering days, times or limits that apply:

 

Who could confirm the current guidance?

6. Irrigation Zones

List each separately watered area as its own zone. For Plant Type Sensitivity, use the general categories 'Deep Roots/Drought Tolerant' or 'Shallow/Moisture Loving'. For Watering Action, choose one of 'Skip Today', 'Half Cycle' or 'Full Run'. The planned run time column is calculated automatically from the action you record and the full cycle time you enter.

Suggested starting logic, which you can adjust to suit your own observations: saturated or muddy soil usually points toward Skip Today; damp soil around 2 inches down often suits a Half Cycle for shallow-rooted plantings; dry and dusty soil with thirsty plants may call for a Full Run. Deep-rooted, drought-tolerant plantings can often wait longer between waterings.

 

Irrigation Zones

Zone Name

Plant Type Sensitivity

Watering Action

Zone Area (sq m)

Full Cycle Run Time (min)

Planned Run Time (min)

Checked for Leaks?

A
B
C
D
E
F
G
1
Front Lawn
Deep Roots/Drought Tolerant
Skip Today
60.0
30
0.0
2
Side Flowerbed
Shallow/Moisture Loving
Half Cycle
18.0
20
10.0
3
Raised Veggie Box
Shallow/Moisture Loving
Full Run
6.0
15
15.0
4
 
 
 
 
 
0.0
5
 
 
 
 
 
0.0
6
 
 
 
 
 
0.0
7
 
 
 
 
 
0.0
8
 
 
 
 
 
0.0
9
 
 
 
 
 
0.0
10
 
 
 
 
 
0.0

Any zones that need special handling, such as slopes, shaded corners, or areas with poor drainage?

7. Estimated Water Use & Savings

A rough estimate of water use can help you see the effect of skipping or shortening a cycle. Enter the planned run time and the flow rate for each zone, and the estimated volume is worked out for you. These are simple planning figures only and will not match a metered reading exactly.

 

Estimated volume equals run time multiplied by flow rate

V=t×fV = t \times f

 

Estimated Water Use by Zone

Zone Name

Planned Run Time (min)

Flow Rate (L per min)

Estimated Volume (L)

Estimated Cost (local currency)

Notes

A
B
C
D
E
F
1
Front Lawn
0.0
12.0
0.0
$0.00
Skipped today because soil is still damp from recent rain
2
Side Flowerbed
10.0
4.0
40.0
$0.00
Half cycle to keep shallow-rooted plants steady
3
Raised Veggie Box
15.0
3.0
45.0
$0.00
Full run, soil tested dry and dusty
4
 
 
 
0.0
 
 
5
 
 
 
0.0
 
 
6
 
 
 
0.0
 
 
7
 
 
 
0.0
 
 
8
 
 
 
0.0
 
 
9
 
 
 
0.0
 
 
10
 
 
 
0.0
 
 

Roughly how much water do you think today's plan saves compared with a full run of every zone?

Which unit are you using for water volume in this form?

8. Weekly Watering Plan

Use this table to sketch the coming week. Repeating the soil moisture check before each planned watering is often the simplest way to avoid unnecessary runs.

 

Seven Day Watering Plan

Planned Date

Start Time

Zone Name

Planned Duration (min)

Soil Check Done First?

Watered As Planned?

Adjustment Made

A
B
C
D
E
F
G
1
4/13/2027
6:30 AM
Raised Veggie Box
15
None
2
4/15/2027
6:30 AM
Side Flowerbed
10
Skipped, rain arrived overnight
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

9. Water-Saving Practices

Which water-saving practices are already in place? (Select all that apply)

 

What time of day do you usually water?

 

How is rainwater collected and stored?

Please rate how well each statement matches your current situation.

Strongly disagree

Disagree

Neutral

Agree

Strongly agree

I check soil moisture before deciding to water

I know roughly how much water each zone uses

My irrigation is free of leaks and misaligned heads

I adjust watering when the weather changes

I feel confident about when to skip a watering day

Overall, how useful was this micro-weather watering check for today's decision?

How do you feel about the watering plan you have put together today?

Please rank these ideas in the order you would most like to try next.

Install a simple rain gauge for more accurate rainfall readings

Add or refresh mulch on the planted beds

Set up a rainwater barrel

Convert part of the garden to drought-tolerant planting

Upgrade to drip or targeted watering

Add a soil moisture meter to the toolkit

10. Review & Confirmation

Please review your entries before submitting. If the weather changes suddenly, or plants show unexpected stress, it is always reasonable to adjust the plan and observe the results.

 

Summary of today's watering decision

Anything else you would like to record for next time?

Name of the person completing this form

Date of this watering assessment

I understand this form offers general planning prompts only and is not a professional horticultural, engineering or regulatory assessment, and that I remain responsible for how I use the information.

I agree that the observations recorded here reflect conditions I checked on the property today.

Please sign to confirm the entries above.

Analysis for Lawn & Garden Micro-Weather Watering Decision Form | Save Water Outdoors

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


 

Overall Summary

This lawn and garden micro-weather watering decision form is a thoughtfully structured, observation-led planning tool. Rather than relying on generic schedules, it guides the respondent through a short sequence of practical yard checks — recent rainfall, soil moisture at depth, plant sensitivity and irrigation condition — and then converts those observations into a zone-by-zone watering decision (Skip Today, Half Cycle or Full Run). The form is unusually well balanced: it collects enough environmental context to make the decision meaningful, while keeping most inputs simple (yes/no, short choice lists, small numeric entries). Its use of conditional follow-ups, a calculated planned run-time column, a water-use estimation table and a forward-looking weekly plan gives the respondent an end-to-end workflow from observation to action to review. The inclusion of clear scope disclaimers and a confirmation step further reinforces that the output is a practical planning prompt rather than a professional assessment.

 

Section: How This Form Works

The opening section sets expectations before any data is captured. The introductory paragraphs explain the three-part logic (rainfall, soil moisture at depth, plant thirst) and explicitly state that the results are planning prompts, not professional horticultural, engineering or regulatory assessments. This is a strong design choice: it reduces the risk of over-reliance on the output and directs the respondent to local guidance when conditions are uncertain.

 

Have you already watered any part of this property within the last 24 hours? This opening question establishes the baseline for the day. Operationally, knowing whether watering has already occurred prevents the form from recommending a second unnecessary run on the same ground. The yes branch captures which areas, duration and time of day, which is proportionate detail for interpreting today's soil readings. The no branch offers a baseline plan prompt for new or recently planted areas, which is a sensible onboarding aid.

 

Is this the first time you are using a micro-weather based watering check on this property? This question supports longitudinal use. When the answer is no, the follow-up invites a short reflection on what worked previously, which helps the respondent (and anyone reviewing the record later) build experience over successive checks rather than treating each entry in isolation.

 

Section: Garden & Property Profile

This section captures the relatively stable characteristics of the site so that the day-specific observations later can be interpreted in context.

 

Property or garden label (for your own reference) A simple self-reference label. It is operationally useful when the same person maintains more than one growing area, and it keeps the record identifiable without requiring formal address data.

 

General location or climate description A free-text climate note gives qualitative context (for example, cool coastal versus hot dry inland) that helps interpret rainfall and evaporation figures. Keeping it optional is appropriate, since the numeric and observational fields already carry much of the decision weight.

 

Which setting best describes the area you are assessing? The six-option list covers common residential, shared, allotment, container and commercial contexts, with an Other branch that opens a short description field. This is an efficient way to segment the data without over-taxing the respondent.

 

Approximate total planted or lawn area and Which unit are you using for area measurements in this form? Together these give a rough sense of scale. Allowing decimals to one place is proportionate for estimates of this kind. The separate unit question avoids ambiguity in a form that may be used in different measurement conventions.

 

Which sun and exposure conditions apply to the property today? (Select all that apply) The multi-select list captures the micro-weather drivers that most affect drying rate — sun exposure, wind, reflective heat, slope and low-lying ground. This is one of the form's stronger data points, because it explains why two properties with the same rainfall may need different watering.

 

What is the dominant soil texture you observe when you dig a small hole? Soil texture is a practical proxy for drainage behaviour. The conditional follow-ups are well targeted: clay-heavy soil triggers a puddling question, sandy soil triggers a run-off question, and container growing media is distinguished from in-ground soil. The Not sure option is a good usability safeguard.

 

Is there a mulch layer (wood chips, straw, leaf litter, gravel or similar) over most planted beds? Mulch materially affects surface evaporation, so recording its presence and rough depth is operationally relevant to the watering decision. The no branch asks for the reason in optional free text, which is a considerate touch that avoids making the respondent feel judged while still capturing interpretive context.

 

Section: Micro-Weather Observations

This is the core evidence-gathering section. The framing paragraph correctly notes that yard conditions can differ from the nearest official station, which encourages direct observation over assumption.

 

Which rainfall unit are you using for this form? Selecting the unit before entering rainfall figures prevents later ambiguity in the record and keeps the numeric fields unambiguous.

 

Yesterday's local rainfall (mm or inches) This is the primary recent-weather input. Allowing decimals to two places suits gauge readings and app estimates alike. Paired with the soil moisture test, it forms the main basis for the skip or run decision.

 

How did you measure or estimate yesterday's rainfall? Capturing the measurement method is a quietly important quality field: it lets a reviewer distinguish a gauge reading from a visual guess without adding much respondent effort.

 

Approximate rainfall total over the last 7 days (same unit as above) The weekly total adds trend context. A single dry day after a wet week carries a different implication than a dry day at the end of a dry week, and this field supports that distinction.

 

Did rain fall in a short heavy burst rather than a slow soak? Rainfall intensity affects how much water actually reaches the root zone versus running off. The yes follow-up asks for observed run-off, pooling or erosion, which is directly relevant to interpreting the soil test.

 

Soil Depth Moisture Test This is the centrepiece observation of the form and aligns with the stated purpose. The three plain-language options (Muddy/Saturated, Damp 2-Inches Down, Dry & Dusty) are easy to apply without equipment. Each option opens a targeted follow-up: a squeeze test for saturated soil, a tactile grading for damp soil, and a plant-stress check for dry soil. This branching design adds diagnostic depth only where it is relevant, which is an efficient use of respondent attention.

 

Where on the property did you perform the soil moisture test? Recording the test location matters on properties with mixed zones, since one reading may not represent the whole yard. The placeholder example usefully suggests testing more than one spot.

 

Is more rain expected within the next 24 hours? Forward-looking weather is the other half of the decision. The yes branch asks for expected amount and timing; the no branch asks about an upcoming dry, hot or windy stretch. This structure keeps follow-up proportional to the answer.

 

Approximate daytime high temperature expected today, Which temperature unit are you using? and Approximate relative humidity today (percentage) These three fields describe evaporative demand. Separating the temperature unit choice from the value is consistent with the form's other unit fields and avoids mixed-unit records.

 

How windy does it feel on the property today? A simple four-point subjective scale is appropriate here, since wind is being recorded as an on-site impression rather than a measured value.

 

Any unusual local conditions worth noting today? (Select all that apply) The list covers heat events, air quality, frost risk, nearby ground disturbance, soil compaction and a None option. This is a useful catch-all that captures outliers without forcing free text.

 

Section: Plant & Landscape Sensitivity

This section translates plant characteristics into watering tolerance. The framing paragraph correctly presents the two broad categories as general guidance alongside the respondent's own observations.

 

Which plant categories are present on the property? (Select all that apply) The ten-option list spans lawn, ornamentals, edibles, fruit, shrubs, native plantings, containers and protected growing. Conditional follow-ups capture the age of a new lawn, current crops in vegetable beds and a description for Other, which adds useful specificity without burdening every respondent.

 

Were any plants installed or transplanted within the last four weeks? Recent plantings typically have different establishment needs, so flagging them is operationally sensible. The follow-up asks which plants and how they are settling, which supports a more tailored watering action.

 

Overall, how would you describe the current health and appearance of the planting? A five-option health summary gives a quick overall read. The noticeably stressed branch opens a multi-select list of specific stress signs (wilting, leaf curl, yellowing, crispy edges, stalled growth, cracking soil), which converts a vague impression into structured, actionable detail.

 

Are there any plants with unusually high water needs, such as shallow-rooted vegetables or moisture-loving flowers, in a sunny or windy spot? This question targets the zones most likely to need a Full Run even when the rest of the yard can wait. The follow-up asks for plant names and locations, which maps directly onto the irrigation zone table later.

 

Are any plants deliberately being kept on the dry side to encourage deeper rooting or hardening off? This is a thoughtful inclusion, because it prevents the form from recommending water for plants that are intentionally being managed dry. The follow-up captures the plant and the reason.

 

Section: Irrigation System Details

This section establishes how water is actually delivered, which determines what Skip, Half Cycle and Full Run mean in practice.

 

How is water normally delivered to the garden? The six delivery options cover the common approaches. The conditional follow-ups are well chosen: spray-head overlap for pop-up systems, emitter blockage checks for drip systems, and a stored-volume figure for rainwater barrels.

 

Is the irrigation on an automatic timer or controller? The yes branch captures the programmed start time and duration, which is the practical baseline that the zone table will adjust. The no branch offers a gentle prompt about watering timing to reduce evaporation, framed as a consideration rather than a requirement.

 

Estimated flow rate of your water source (litres or gallons per minute) Flow rate is the multiplier used in the water-use estimation table, so capturing it here (with one decimal place) directly enables the later volume calculation.

 

Have you checked for leaks, broken heads, split hose or dripping connections recently? Leak status is a practical water-saving input and affects how reliable the flow-rate figure is. The yes branch records the finding, with a description field if a clear leak was found; the no branch asks when the system was last checked. This is proportionate and avoids assuming a maintenance schedule.

 

Date of the most recent irrigation system maintenance or adjustment A simple date field that supports basic maintenance record-keeping alongside the leak check.

 

Does the property have any local watering rules, community guidelines or shared agreements to follow? The five options distinguish between no known restrictions, voluntary guidelines, shared agreements and formal local schedules, with follow-ups for summarising limits or identifying who can confirm current guidance. The wording is appropriately neutral and does not assert any particular regulatory requirement.

 

Section: Irrigation Zones

The zone table is the operational heart of the form. It asks the respondent to list each separately watered area and assign a Zone Name, a Plant Type Sensitivity category (Deep Roots/Drought Tolerant or Shallow/Moisture Loving) and a Watering Action (Skip Today, Half Cycle or Full Run). Supporting columns capture Zone Area (sq m) and Full Cycle Run Time (min), while the Planned Run Time (min) column is calculated automatically using the formula IF(column3 equals Full Run, column5, IF(column3 equals Half Cycle, column5 divided by 2, 0)). A Checked for Leaks? checkbox closes the loop with the earlier leak question at zone level. The suggested starting logic in the introductory paragraph (saturated soil toward Skip, damp soil toward Half Cycle for shallow plantings, dry soil with thirsty plants toward Full Run) gives the respondent a clear, adjustable starting point rather than a rigid rule. The three sample rows (Front Lawn, Side Flowerbed, Raised Veggie Box) demonstrate the intended granularity well.

 

Any zones that need special handling, such as slopes, shaded corners, or areas with poor drainage? This free-text field captures exceptions that the structured columns cannot, which is important on uneven or complex sites.

 

Section: Estimated Water Use & Savings

This section converts the plan into rough volume figures. The stated equation (Estimated volume equals run time multiplied by flow rate) is presented clearly, and the Estimated Water Use by Zone table applies it via the formula column2 multiplied by column3 in the Estimated Volume (L) column. The table also carries an Estimated Cost (local currency) field and a Notes column, which in the sample rows records the reasoning behind each action (for example, skipping the front lawn because soil is still damp). The introductory paragraph appropriately frames these as simple planning figures that will not match a metered reading exactly.

 

Roughly how much water do you think today's plan saves compared with a full run of every zone? A self-estimated saving figure gives the respondent a tangible sense of the benefit of the exercise, which can support continued use of the practice.

 

Which unit are you using for water volume in this form? Consistent with the other unit questions, this prevents ambiguity between litres and the two gallon conventions.

 

Section: Weekly Watering Plan

The Seven Day Watering Plan table extends the single-day decision into a short forward schedule. Its columns (Planned Date, Start Time, Zone Name, Planned Duration, Soil Check Done First?, Watered As Planned?, Adjustment Made) create a simple feedback loop: the Soil Check Done First? checkbox reinforces the form's core habit, and the Adjustment Made column records deviations such as a skipped run after unexpected rain. The sample rows illustrate this well. This is one of the form's strongest features for building repeatable behaviour over time.

 

Section: Water-Saving Practices

Which water-saving practices are already in place? (Select all that apply) The ten-option list covers timing, mulching, rainwater harvesting, plant choice, targeted watering, soil improvement, grouping, lawn height, water reuse and a None option. Conditional follow-ups capture usual watering time and rainwater storage method. This gives a useful baseline of existing habits.

 

Please rate how well each statement matches your current situation. The five-statement matrix (checking soil moisture before watering, knowing zone water use, leak-free irrigation, adjusting to weather changes, confidence about skipping days) provides a compact self-assessment that can be compared across successive uses of the form.

 

Overall, how useful was this micro-weather watering check for today's decision? A five-star usefulness rating, alongside How do you feel about the watering plan you have put together today? (emotion rating) and Please rank these ideas in the order you would most like to try next. (ranking of six improvement ideas), gives the form owner qualitative and prioritised feedback on both the tool and potential next steps.

 

Section: Review & Confirmation

The closing section brings the record together. Summary of today's watering decision asks for a short narrative of the actions taken, which is the most useful single artefact for anyone reviewing the record later. Anything else you would like to record for next time? captures open observations. Name of the person completing this form and Date of this watering assessment establish who recorded the entry and when. The two confirmation checkboxes and the signature field reinforce the scope limitation stated at the start of the form and confirm that the observations reflect conditions checked on the property.

 

Data Collection Implications

The form collects a mix of observational, numeric and categorical data: rainfall and temperature figures, soil and plant condition categories, irrigation configuration details, and per-zone action decisions with calculated run times. This combination supports structured record-keeping over time and allows simple comparison between successive checks. Data quality is generally supported by clear option labels, explicit unit selectors, sensible decimal limits and measurement-method capture. From a basic privacy standpoint, the form collects a name, a signature and a general location description; the property label is explicitly framed as a self-reference rather than a formal address. Anyone storing these records should consider how personal identifiers and signatures are retained, who can access them, and how long they are kept, in line with their own applicable data handling practices.

 

User Experience Considerations

The form is long but well segmented into ten clearly titled sections, each introduced with a short explanatory paragraph. Conditional follow-ups are used consistently, so respondents only see detail that is relevant to their previous answer, which keeps the effective length manageable. The use of plain-language observation categories (for example, Dry & Dusty) instead of technical measurements lowers the barrier for non-specialists. The calculated columns in the zone and water-use tables reduce manual arithmetic. Potential friction points include the overall number of fields if every branch is triggered, the need to have a rough flow-rate figure to hand for the estimation table, and the fact that the Plant Type Sensitivity and Watering Action columns in the zone table are free-text fields rather than constrained choices, which may allow inconsistent entries. The sample rows in each table are a helpful usability aid, and the closing review step gives respondents a chance to correct entries before submission.

 

Strengths and Areas for Improvement

The form's principal strengths are its observation-first logic, its consistent use of conditional branching to keep questions relevant, its built-in calculations for planned run time and estimated volume, and its clear, repeated framing of the output as a practical planning prompt rather than a professional assessment. The progression from site profile to weather observation to plant sensitivity to system detail to zone action to forward plan is logical and mirrors how a careful gardener would actually think through the decision. Sample data in the tables and realistic placeholders throughout further support completion.

 

Areas that could be considered for refinement include constraining the Plant Type Sensitivity and Watering Action entries in the zone table to the two and three categories described in the section introduction, which would improve consistency of the records; making the unit selection questions appear immediately before the fields that depend on them so the connection is obvious; and offering an optional short note alongside the soil moisture test location to record multiple test spots on mixed properties. The form could also consider surfacing the calculated planned run times and estimated volumes in a compact summary at the review step, so the respondent sees the full picture before signing. None of these are shortcomings that undermine the form's purpose; they are incremental refinements to an already coherent design.

 

Mandatory Question Analysis for Lawn & Garden Micro-Weather Watering Decision Form | Save Water Outdoors

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.

 

Individual Mandatory Question Analysis

Have you already watered any part of this property within the last 24 hours?
Recommendation: Requiring this question helps establish a clear starting point for the day's assessment. If watering has already occurred, the soil moisture readings and zone recommendations need to be interpreted differently than on an untouched yard. Making it mandatory supports data completeness for anyone reviewing the record later and reduces the chance of a duplicate or conflicting watering recommendation. The necessity of this field depends on how the form creator intends the record to be used; for single-use personal planning it could arguably be optional, but for a recurring log it is a useful anchor.

 

Property or garden label (for your own reference)
Recommendation: Requiring a short self-reference label supports record-keeping when the same person maintains more than one growing area. It allows successive entries to be grouped correctly without collecting formal address details. This is a low-effort field that materially improves the usability of a multi-property log.

 

Which setting best describes the area you are assessing?
Recommendation: Marking this as required ensures every record carries basic context about the type of growing area being assessed, which helps interpret the soil, exposure and irrigation answers that follow. The option list is broad and includes an Other branch, so the requirement should not create significant completion friction.

 

Is there a mulch layer (wood chips, straw, leaf litter, gravel or similar) over most planted beds?
Recommendation: Mulch presence and depth directly affect how quickly soil dries at the surface, so capturing this for every assessment supports consistent interpretation of the soil moisture test. Requiring the yes or no answer while keeping the depth and reason follow-ups conditional is a proportionate approach that collects the essential fact without over-burdening the respondent.

 

Which rainfall unit are you using for this form?
Recommendation: Requiring the unit selection before rainfall figures are entered prevents ambiguous numeric entries and supports reliable comparison between records. This is a short, low-friction field whose necessity is tied to the accuracy of the rainfall data that follows.

 

Yesterday's local rainfall (mm or inches)
Recommendation: Recent rainfall is one of the primary inputs to the watering decision, so requiring it ensures every submitted assessment is based on a stated weather observation rather than an assumption. If a respondent genuinely cannot estimate rainfall, the form creator may wish to consider a not known option or to relax this requirement for casual use.

 

Soil Depth Moisture Test
Recommendation: This field is central to the form's stated purpose of deciding whether to skip, half-cycle or fully run each zone. Requiring it ensures the decision is grounded in a direct soil observation rather than habit or guesswork. The three plain-language options keep the requirement easy to satisfy.

 

Is more rain expected within the next 24 hours?
Recommendation: Forward-looking conditions influence whether watering today is worthwhile, so requiring this answer supports a complete decision record. The follow-up branches collect detail only where relevant, keeping the mandatory portion brief.

 

Which plant categories are present on the property? (Select all that apply)
Recommendation: Knowing which plant types are present is necessary to interpret the zone sensitivity categories used later in the form. Requiring this multi-select supports complete records and helps the respondent think through the full planting mix before assigning watering actions. The broad option list and Other branch should keep completion straightforward.

 

Were any plants installed or transplanted within the last four weeks?
Recommendation: Recently installed plants may have different establishment needs from established plantings, so flagging them for every assessment supports more considered zone decisions. The requirement is a simple yes or no, with detail captured only when relevant.

 

How is water normally delivered to the garden?
Recommendation: The delivery method determines what Skip Today, Half Cycle and Full Run mean in practice, so requiring this answer supports operational clarity in the zone table. The six options cover common approaches, and the conditional follow-ups collect system-specific detail only where it applies.

 

Have you checked for leaks, broken heads, split hose or dripping connections recently?
Recommendation: Leak status affects both water savings and the reliability of the flow-rate figure used in the estimation table, so requiring this answer supports data quality across the form. The yes and no branches both collect proportionate follow-up detail without assuming a particular maintenance schedule.

 

Summary of today's watering decision
Recommendation: Requiring a short narrative summary ensures each record contains a clear statement of the actions taken, which is the most useful single field for anyone reviewing the log later. It also prompts the respondent to consolidate their thinking before signing.

 

Name of the person completing this form
Recommendation: Requiring the respondent's name supports basic accountability and record attribution, particularly where the form is completed on behalf of a shared plot or organisation. Form creators should confirm whether an informal display name is sufficient for their intended record-keeping, and should handle this identifier in line with their own data handling practices.

 

Date of this watering assessment
Recommendation: Requiring the assessment date ensures each record can be placed in sequence, which is essential for a form designed to be used repeatedly over a season. It supports comparison between successive checks and helps interpret weather figures that are time-specific.

 

I understand this form offers general planning prompts only and is not a professional horticultural, engineering or regulatory assessment, and that I remain responsible for how I use the information.
Recommendation: Requiring this acknowledgement reinforces the scope limitation stated at the start of the form and records that the respondent has seen it. It is a proportionate step for a tool that produces practical planning prompts. Form creators should ensure the wording remains consistent with how the output is actually used and presented.

 

Please sign to confirm the entries above.
Recommendation: Requiring a signature provides a clear confirmation point at the end of the assessment and pairs with the name and date fields to complete the record. Whether a signature is necessary depends on the form creator's intended use; for informal personal planning it may be more than needed, while for shared or organisational records it can support clear attribution. Where signatures are collected, appropriate storage and access controls should be considered.

 

Overall Mandatory Field Strategy Recommendation

The form sets a substantial number of fields as mandatory, concentrated in three areas: the opening baseline questions, the core micro-weather and plant observations, and the closing confirmation block. This distribution is broadly logical, because the form's purpose depends on having a complete set of observations before a watering action can be meaningfully assigned. At the same time, the overall count of required fields is on the higher side for a form that may be completed frequently, and a few of the required items (notably the rainfall unit selector, the delivery method question and the leak check question) could arguably function well as optional or conditionally required fields for casual users.

 
  • Balance depth against completion: Consider offering a short or quick mode in which only the core decision inputs (rainfall, soil moisture test, plant categories and zone actions) are required, with the profile, system and reflection sections optional. This would preserve the quality of the watering decision while lowering the effort for repeat daily or weekly use.

  • Use conditional logic where possible: The form already branches well on follow-ups. A similar approach could be applied to requirement status, for example making the flow-rate and water-use estimation fields required only when the respondent proceeds to the estimation section, or making the signature required only for shared or organisational records.

  • Placement and grouping: The mandatory fields are sensibly distributed across the form rather than clustered at the start, which avoids an early wall of required questions. Keeping the confirmation block mandatory at the end is a good practice, since it consolidates the record after all observations have been captured.

  • Observations on volume: With roughly seventeen mandatory items, the form asks for a meaningful commitment of attention. For a tool intended for repeated seasonal use, periodically reviewing which fields are genuinely required for the form creator's purpose — and which could default to optional with a gentle prompt — may improve completion rates without materially reducing data quality. Requirements and expectations can vary by context and intended use, so this is a practical design consideration rather than a fixed rule.

 

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.