Landscape Enhancement Proposal Approval Tracking Template: Fields, Statuses, and Rules

The most useful landscape enhancement proposal approval tracking template is a small operating record. It should answer what is happening, who owns it, what evidence exists, and when the next decision occurs. This structure works in a spreadsheet, database, or focused application.

Recommended record fields

| Field | Why it exists | Update point | |---|---|---| | Customer property and contract | Prevents the record from depending on memory or an inbox search | Capture the opportunity from field or customer | | Request source and desired outcome | Prevents the record from depending on memory or an inbox search | Qualify site condition and desired result | | Location photos and measurements | Prevents the record from depending on memory or an inbox search | Create scope options and constraints | | Existing condition and constraints | Prevents the record from depending on memory or an inbox search | Send and follow the proposal | | Scope option materials and labor | Prevents the record from depending on memory or an inbox search | Schedule approved work or record the declined reason | | Price validity and exclusions | Prevents the record from depending on memory or an inbox search | Capture the opportunity from field or customer | | Customer decision and evidence | Prevents the record from depending on memory or an inbox search | Qualify site condition and desired result | | Scheduled window or closed reason | Prevents the record from depending on memory or an inbox search | Create scope options and constraints |

Suggested statuses

Use workflow statuses that describe reality: Capture The Opportunity From Field Or Customer → Qualify Site Condition And Desired Result → Create Scope Options And Constraints → Send And Follow The Proposal → Schedule Approved Work Or Record The Declined Reason. Add Waiting only when you also capture a waiting reason and review date. Add Closed—Not Completed when an item legitimately ends without the desired outcome.

Follow-up rules

• When a crew records work outside recurring scope, assign a next action and review date.
• When the customer requests a property improvement, assign a next action and review date.
• When conditions or price assumptions change before approval, assign a next action and review date.

Avoid reminders with no stop condition. A rule should say when it starts, who receives it, what counts as a response, and when a person should take over.

Example records

• A crew documents a failed shrub row
• A manager requests fresh mulch before an event
• Drainage evidence changes the proposed grading scope

For each example, write the current status, next action, owner, and supporting evidence. This makes the template testable with real work rather than idealized sample data.

Quality-control rules

• Every open enhancement opportunity needs one owner and a next review time
• Completion requires recorded evidence that every qualified enhancement request reaches a priced customer decision with field context, scope assumptions, and a scheduled or closed next action
• Automated reminders stop after verified completion or a documented closed reason
• Keep the landscape CRM, contract, estimate, route, crew, job-cost, and billing platform as the system of record; only necessary coordination data belongs here

Before adding automation, run the template manually for a week. Remove ambiguous fields and confirm that two different users classify the same situation the same way. Consistency matters more than having a long form.

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.