How to Measure Landscape Enhancement Proposal Approval Tracking: Practical Metrics

Metrics for landscape enhancement proposal approval tracking should help small commercial landscaping and recurring property-maintenance companies decide what to change next. Avoid universal benchmarks: volume, service model, and exception mix differ. Establish a baseline from your own records and compare the process against itself.

Three useful measures

| Metric | Simple calculation | Decision it supports | |---|---|---| | Observation-to-proposal time | proposal sent - qualified observation | staff estimating handoff | | Proposal decision rate | proposals approved or declined / proposals sent | reduce limbo | | Approved-to-scheduled time | work scheduled - approval received | align production capacity |

Capture the minimum viable data

The calculations only work if the operating record consistently includes Customer property and contract, Request source and desired outcome, Location photos and measurements, Existing condition and constraints, Scope option materials and labor, Price validity and exclusions, Customer decision and evidence, Scheduled window or closed reason. Define when the clock starts and stops. Decide whether paused or waiting time remains inside cycle time, and keep that rule stable across the comparison period.

Segment before interpreting

Separate normal work from exception-heavy work. At minimum, segment by owner, workflow stage, and closed reason. Averages can hide a small blocked queue that creates most of the follow-up burden.

Review decisions, not dashboard colors

For each metric, write an action threshold in plain language. Examples:

• If Observation-to-proposal time changes materially, use it to staff estimating handoff.
• If Proposal decision rate changes materially, use it to reduce limbo.
• If Approved-to-scheduled time changes materially, use it to align production capacity.

Do not automate a response until a person has reviewed several examples. A high number can indicate a broken process, difficult work, or a data-definition change.

Validate each calculation manually

Choose one closed record and calculate every metric by hand from its timestamps and statuses. Save the numerator, denominator, exclusions, and timezone rule beside the definition. Then test an abandoned record, a reopened record, and a record that spent time waiting. If two people produce different answers, the metric is not ready for a dashboard. Fix the event definitions before collecting more data.

Repeat that spot check whenever a workflow status, integration, or reporting period changes.

A four-week measurement loop

Week one defines fields and baselines. Week two fixes missing data. Week three tests one workflow change. Week four compares the same metric definitions and reviews exceptions. Keep the change only if it improves the intended outcome without shifting work somewhere invisible.

Next step

Explore the Enhancement Approval Desk workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Seasonal Service Change Register.