# The Baseline You Need Before Automating — What to Measure for 7 Days

> Before you automate, measure what your team actually does for 7 days. Learn how to track plan vs fact vs gap to spot your first automation target — and avoid guessing.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-19
- Updated: 2026-10-19
- Source: https://aiadvisoryboard.me/blog/the-baseline-you-need-before-automating-what-to-measure-for-7-days

When a founder of a 40-person logistics team told me they’d already bought three AI licences but couldn’t point to a single saved hour, I realized the problem wasn’t the tools — it was the missing baseline.

## TL;DR
- Measure what your team actually does for 7 days before automating anything.
- Track plan vs fact vs gap by role to surface hidden work and misalignment.
- Use this baseline to pick your first automation with confidence, not hope.

**Definition:** Plan → Fact → Gap — the operating taxonomy for owners. Plan is what you expect the team to do. Fact is what they actually do. Gap is the difference — where work hides, duplicates, or drifts.

**Definition:** Baseline — a 7-day snapshot of real work, not ideal process. It shows routine tasks, handoffs, and where time actually goes.

**Definition:** Owner visibility — the ability to see Plan, Fact, and Gap across teams without daily check-ins or micromanagement.

### What should you measure during the 7-day baseline?
Start with three layers: what people say they do (plan), what they log as done (fact), and where the two diverge (gap). Focus on repeatable, computer-based work — the kind AI can take over.

For each role or team, capture:
- Key recurring tasks (e.g., invoice matching, lead enrichment, status reporting)
- Time spent per task (estimated or logged)
- Tools used and handoff points
- Where work stalls or gets duplicated

This isn’t about perfection. It’s about spotting the 20% of routine that eats 80% of time — the prime target for your first AI agent.

## Tool tip (AiAdvisoryBoard.me):
> The Plan → Fact → Gap framework turns vague feelings about 'inefficiency' into something you can see, measure, and act on. For example, if your sales team plans to spend 2 hours a day on outreach but fact shows 45 minutes — and the gap is spent in CRM updates — that’s your automation candidate. See how the 7-day diagnostic works.

### How do you collect this data without adding burden?
Use lightweight, existing signals: calendar blocks, task managers, async updates, or end-of-day notes. Ask team leads to spend 5 minutes each day noting:
- What they planned to work on
- What they actually completed
- Any blockers or surprises

Aggregate this at the team level. You’re not auditing individuals — you’re mapping the system’s real rhythm.

Avoid surveys or retrospective recall. They distort. Instead, capture work as it happens or within 24 hours. The goal is accuracy, not completeness.

## Manager scan (2-minute digest example)
- Sales: Planned 3 hrs/day outreach; Fact: 1.2 hrs; Gap: 1.8 hrs in CRM logging and lead research
- Support: Planned 2 hrs/day ticket resolution; Fact: 1.5 hrs; Gap: 0.5 hrs in triple-checking past resolutions
- Ops: Planned 4 hrs/day inventory sync; Fact: 2.8 hrs; Gap: 1.2 hrs in manual spreadsheet reconciliation
- HR: Planned 1 hr/day screening; Fact: 0.3 hrs; Gap: 0.7 hrs in scheduling and follow-up emails
- Finance: Planned 2.5 hrs/day invoice processing; Fact: 1.1 hrs; Gap: 1.4 hrs in 3-way matching and exception handling

This scan shows where plan and fact diverge — and where AI can close the gap without adding process.

## Micro-case (what changes after 7–14 days)
A founder running a 60-person professional services firm suspected their team was spending too much time on meeting prep and follow-up. After 7 days of tracking plan vs fact, they discovered that 60% of 'project work' time was actually consumed by internal coordination — scheduling, status chasing, and version control. The gap wasn’t in client delivery; it was in invisible work. Armed with this, they introduced an AI agent for meeting notes → action items and automated status updates via existing tools. Within 14 days, the team reclaimed 5 hours per person per week on coordination — not by working harder, but by removing the drag.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

### Why most teams skip the baseline (and pay for it later)
Founders often jump to tools because they feel pressure to 'do something.' But automating without a baseline is like optimizing a car blindfolded — you might speed up, but you could be going in circles.

The baseline does three things:
1. It replaces opinion with observable data — critical when teams disagree on where time goes.
2. It reveals the true candidates for automation — not the loudest complaints, but the biggest time sinks.
3. It gives you a before picture. After automation, you can measure what actually changed — not what you hoped would change.

Without this step, you risk automating the wrong work, duplicating effort, or building agents that solve non-problems.

## FAQ
**What if my team resists tracking their work?**
Frame it as ‘seeing what’s really happening so we can remove drag,’ not monitoring performance. Keep it light, team-based, and temporary — 7 days only.

**Can I use existing tools like Asana or Clockify instead of manual logs?**
Yes — if they capture task-level time and are used consistently. The goal is data, not perfection. If your tools don’t show what people actually did, supplement with lightweight notes.

**What do I do with the baseline once I have it?**
Look for large, consistent gaps between plan and fact — especially in repetitive, rule-based work. Those are your first automation targets. Share the findings with the team: ‘Here’s where we’re losing time to coordination — let’s see if AI can help.’

**Is 7 days enough? Isn’t a month better?**
Seven days captures a full cycle of weekly rhythms (e.g., Monday planning, Friday wrap-up). Longer isn’t better — it just delays action. Start with 7 days, act, then re-measure after automation.

**How is this different from a process audit?**
A process audit maps ideal workflows. This baseline maps real work — including the gaps, shortcuts, and workarounds that never make it into official docs.

### Conclusion
The best AI implementations start not with a tool, but with a truth: what your team actually does. A 7-day baseline of plan vs fact vs gap gives you that truth — fast, fairly, and without micromanagement.

**What to do today:** Ask each team lead to spend 5 minutes at day’s end noting what they planned to work on, what they actually completed, and where time disappeared.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.

---

When citing, link to https://aiadvisoryboard.me/blog/the-baseline-you-need-before-automating-what-to-measure-for-7-days. More articles: https://aiadvisoryboard.me/blog