Morning Huddle Workflow

Record your meeting. The Huddle Agent extracts the insights. Action items flow to the right boards.

The morning huddle is where most landscape teams start their day. It's also one of the highest-value workflows in LeanScaper AI. What used to disappear into thin air now becomes documented knowledge and tracked action items.

---

The Workflow

1

Gather Your Team

Whether it's a crew in the yard, an office meeting, or a leadership check-in, get your people together. Huddles work for any recurring meeting where information needs to be captured.

2

Start Recording

Open the LeanScaper AI mobile app and tap Record Huddle. Place the phone in the center where it can pick up everyone speaking, and pass it around as needed. You're all sharing one phone for the recording.

Speak clearly. The Huddle Agent needs to hear you to transcribe accurately. When it's your turn to talk, make sure the phone can pick you up.

[SCREENSHOT: Huddle recording screen]

• Screen/location: Mobile app > Record Huddle

• Key elements: Record button, timer

• Annotations: Highlight the record button

3

Run Your Meeting

Talk like you normally would. A good crew huddle covers:

• Wins — What went well yesterday or recently

• Working — What processes are clicking

• Wants — What the team needs

• Safety — Any safety topics or reminders

Don't worry about speaking in any special way, but identify yourself by name when you talk. The Huddle Agent doesn't do voice detection, so saying "This is Marcus, I need..." helps the system know who's speaking.

The huddle will be owned by whoever's account is being used to record. Mention people by name so the Huddle Agent knows who said what and who owns action items.

4

Stop and Upload

When you're done, tap Stop. You may need to tap Upload to send the huddle for processing. If you don't see an upload button, automatic uploading is enabled and it will process on its own.

If you're offline, the recording saves locally and uploads when you reconnect.

Processing typically takes a few minutes depending on length.

5

Review the Summary

Once processed, view the summary on the web app. (Viewing summaries on mobile is coming soon.)

The Huddle Agent extracts structured insights from your conversation:

Output	What It Captures
Summary	High-level overview of what was discussed
Wins	What went well, successes worth noting
What's Working	Processes and approaches that are clicking
Wants	Requests, needs, things the team is asking for

Safety matters. While the Huddle Agent doesn't extract Safety as a separate section, building it into every huddle creates a culture where it's always top of mind.

6

Wants Flow to Boards

Wants don't just sit in a summary. They become cards on the appropriate LeanBoards, ready to be tracked and completed.

A crew member saying "we need more mulch at the Johnson site" becomes a card on the Ops Board. "We should update our safety checklist" lands on Continuous Improvement. Requests that don't fit a specific board land on Action Items.

---

What Makes a Good Huddle

The Wins, Working, Wants, Safety structure gives huddles a consistent flow that the Huddle Agent can extract cleanly. But beyond structure, a few things help:

Do

Identify yourself. Since everyone's sharing one phone and the Huddle Agent doesn't detect individual voices, say your name when you speak:

• "This is Marcus. The Johnson site went really well yesterday."

• "Hey, it's Sarah. We need more mulch delivered to Oak Street."

Name names for action items. "Marcus, can you handle the equipment check?" is much more useful than "Someone should check the equipment."

Be specific. "We need mulch at Johnson" is better than "we need stuff."

Cover the basics. Wins, Working, Wants, Safety. Hit these consistently and you'll have solid summaries.

Keep it focused. 10-15 minutes is ideal. Long meetings can be recorded but produce noisier summaries.

Don't

---

Huddles Aren't Just for Crews

The morning crew huddle is the obvious use case, but the same workflow works for:

• Office meetings — Weekly team syncs, project check-ins

• Leadership meetings — Strategy discussions, planning sessions

• One-on-ones — Capture commitments and follow-ups

• Client meetings — Record (with permission) to capture requirements and decisions

• Training sessions — Create documentation from live instruction

Any meeting where you want to capture what was said and turn it into action works with this workflow.

---

Huddles Don't Have to Be Formal

The morning crew huddle is the flagship use case, but huddles can be quick and informal too.

Quick voice note huddles:

• Capture a thought or update as it happens throughout the day

• Record a brief check-in after a client meeting

• Document a safety observation on the spot

• Log a problem and your solution while it's fresh

Think of it like leaving yourself (and your team) a voice note that gets processed into structured insights. It doesn't have to be a formal meeting with your whole crew gathered around.

Multiple huddles per day are fine. Some teams do a morning huddle plus quick captures throughout the day. Each one gets processed separately. Use whatever rhythm works for your operation.

---

Tips for Getting Started

Start with one huddle. Don't try to record everything on day one. Pick your most important recurring meeting and run it through the workflow. See what comes out. Adjust from there.

Make it visible. Share the huddle summary with your team. When people see their words turning into documented insights and tracked tasks, adoption accelerates.

Review before acting. The Huddle Agent is good, but not perfect. Glance through the summary before acting on it. Make sure it captured what you meant.

Build the habit. The value of huddles compounds over time. Patterns emerge. Institutional knowledge builds. One huddle is interesting. A hundred huddles is transformational.

---

Related Pages

Huddles Overview

Managing huddles, labels, access, and viewing outputs.

Mobile Getting Started

Download the app and start recording.

LeanBoards Overview

Where your Wants become tracked cards.