# What a 7-Day Diagnostic Actually Produces — Sample Artefacts

> A 7-day diagnostic produces three concrete artefacts: a real org chart with task ownership, a Plan vs Fact vs Gap report, and a routine-cost baseline. See what owners of 30-500 person companies…

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-30
- Updated: 2026-10-30
- Source: https://aiadvisoryboard.me/blog/what-a-7-day-diagnostic-actually-produces-sample-artefacts

Before any AI tool is bought, an owner needs to see what the company actually does — not what the org chart says it does.

## TL;DR
- A 7-day diagnostic produces three concrete artefacts: a mapped org chart, a Plan vs Fact vs Gap report, and a routine-cost baseline.
- These artefacts show where time actually goes before any automation is chosen.
- Owners use them to decide the first AI agent — or decide none is needed yet.

> **Definition:** 7-day diagnostic — a one-week visibility sprint that maps departments, tasks, and routine work before AI is introduced.

> **Definition:** Plan vs Fact vs Gap — the operating taxonomy that compares what leadership planned, what teams actually did, and the difference between them.

> **Definition:** Routine-cost baseline — an estimate of monthly hours spent on repeatable, low-judgment work that AI agents could absorb.

## What the diagnostic covers in seven days

Day 1 is the org chart. Not the one on the website — the real one, built from who reports to whom and who owns which recurring tasks. Day 2–3 captures the tasks under each role: which are daily, weekly, monthly, and which ones feel like groundhog day. Days 4–5 separate value work from routine. Day 6 builds the Plan vs Fact vs Gap report. Day 7 is the review with the owner.

The output is not a slide deck. It is a set of artefacts the owner can open on Monday and act on.

> **Tool tip (AiAdvisoryBoard.me):** The diagnostic starts with a free org chart tool: enter your website address and headcount, and it draws departments, tasks, and the routine work that can gradually be handed to AI agents — with an estimate of hours per month. No questionnaire; first result in about 30 seconds.

## Artefact 1: The real org chart with task ownership

Most companies have an org chart that shows titles. The diagnostic produces one that shows work. For each department, it lists:

- The recurring tasks owned by that team
- Which tasks are daily, weekly, or monthly
- Which tasks require judgment and which are routine
- Who actually does them, not who is supposed to

For a 60-person professional services firm, this often reveals that three people are doing the same client reporting task in slightly different ways. For a 120-person ecommerce operation, it shows that the warehouse supervisor spends six hours a week on inventory reconciliation that never made it into any job description.

This artefact answers one question: where does the work actually sit?

## Artefact 2: Plan vs Fact vs Gap report

This is the core of the diagnostic. For a sample of key roles, the report compares:

- **Plan:** What leadership expected the role to deliver this week
- **Fact:** What the team actually shipped, based on async updates and daily reports
- **Gap:** The difference, with a short note on why

Example gap:

- Plan: Sales team updates CRM after every call
- Fact: CRM updated twice a week, mostly on Fridays
- Gap: 80% of customer interactions not logged in real time

The owner does not need to fix the gap in the diagnostic week. They need to see it. Once the gap is visible, the decision about AI becomes obvious: automate the capture, train the habit, or change the process — but do not buy a tool to fix a problem you cannot see.

> **Tool tip (AiAdvisoryBoard.me):** The diagnostic uses the Plan → Fact → Gap framework to surface operational truth before any AI subscription is purchased. See how the 7-day diagnostic works.

## Artefact 3: Routine-cost baseline

The third artefact estimates how many hours per month go to automatable routine across the company. It is not a precise audit — it is a directional number that helps the owner decide whether an AI pilot is worth the attention.

Sample output for a 40-person logistics company:

- Customer support: 110 hours/month on ticket triage and status replies
- Operations: 75 hours/month on schedule coordination and driver updates
- Finance: 60 hours/month on invoice matching and payment reminders

Total: 245 hours of candidate routine work. Even if AI takes half, that is 120 hours returned to the team every month.

## Manager scan (2-minute digest example)

Here is what the owner sees on day 7, before any AI tool is selected:

- Sales: Plan — 15 new demos booked; Fact — 9 booked; Gap — pipeline entry delayed by 2 days
- Support: Plan — first response under 4 hours; Fact — 6.5 hours average; Gap — weekend coverage missing
- Operations: Plan — weekly vendor review completed; Fact — review skipped for 3 weeks; Gap — no owner assigned
- Finance: Plan — monthly close by day 5; Fact — close on day 9; Gap — manual invoice chasing

Each gap is a candidate for process fix, training, or AI — in that order.

## Micro-case (what changes after 7–14 days)

A founder of a 90-person manufacturing supplier ran the diagnostic because his COO kept saying the team was "at capacity" while output was flat. The org chart artefact showed two planners doing the same expediting work in parallel. The Plan vs Fact report revealed that production schedules were revised daily but never communicated to procurement. After 14 days, the founder had cancelled one redundant weekly meeting, reassigned one planner to procurement coordination, and had a concrete first automation candidate: a daily schedule digest that goes to procurement automatically. No AI was bought in week one. The decision came from seeing the work, not from reading a vendor pitch.

> **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.

## FAQ

**How long does the diagnostic take for the owner?**
About 30 minutes across the week — mostly reviewing the artefacts on day 7. The team spends time on updates they should already be sending.

**Do we need an IT team to run it?**
No. It starts with an org chart and task mapping. No code, no integrations, no vendor access required.

**What if the diagnostic shows we are not ready for AI?**
That is a valid result. The artefacts give you a process baseline to fix first, which is cheaper than automating chaos.

**How is this different from an audit?**
An audit looks for errors. A diagnostic looks for where work actually goes, so you can decide what to hand to AI — or what to stop doing.

**Can we repeat it?**
Yes. Many owners run a light version quarterly to check whether gaps are closing or new ones have appeared.

A 7-day diagnostic does not sell you AI. It shows you the company. If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.

https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/what-a-7-day-diagnostic-actually-produces-sample-artefacts. More articles: https://aiadvisoryboard.me/blog