Automation Coverage Map

Hands off, mostly

Which parts run themselves, and which parts still need you

An honest coverage map. Where a bar is short, that is a step we have not automated yet rather than one we think should stay manual.

0

times a member detail is retyped between stages

Soft blue gradient backdrop

Referral to invoice

Referral
Offer
3
Intake
4
Visit

Three of these four stages need nobody at all.

The stages a member passes through, whether or not anyone at the practice is watching them do it.

Referral arrives

90% Automatic

Letters and portal referrals become records with a name attached rather than a PDF in an inbox.

Still needs a person: Anything handwritten is checked by reception before it is filed.

First offer goes out

100% Automatic

Real capacity is matched against the referral and the first genuine opening is sent to the member.

Still needs a person: Nothing. This step has had no manual fallback for a year.

Intake form

75% Automatic

Prefilled from what the referral already told us, so the member confirms rather than transcribes.

Still needs a person: Clinical history sections are reviewed by a clinician before the visit.

The appointment

20% Automatic

One record with the referral, the form, and the history on it, and the note written in the same place.

Still needs a person: The consultation itself, obviously, and the note that comes out of it.

Follow-up and invoice

95% Automatic

Both created from the visit, with the charge attached to the appointment that produced it.

Still needs a person: Insurer exceptions are reviewed by finance once a month.

See what is still manual
About this block

Automation Coverage MapPRO

A workflow that scores each stage on how much of it runs unattended, drawing an accent bar per stage and naming what still needs a person, against a sticky column with one headline figure and a live stage tracker.

Workflow51: Automation Coverage Map

A workflow that scores each stage on how much of it runs unattended, drawing an accent bar per stage and naming what still needs a person, against a sticky column with one headline figure and a live stage tracker.

Upgrade to Pro

Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.

Upgrade Now

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

bash
npx shadcn add "https://ui.beste.co/r/workflow51?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
npx shadcn add "https://ui.beste.co/r-base/workflow51?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/workflow51.tsx, the progress16 tracker piece it floats on the tile (installed to components/beste/piece/progress16.tsx), and the badge23 and button21 components it uses for the eyebrow and the action.

Quick start

The installed file exports workflow51Demo alongside the block: the exact props behind the preview above. Spread it to get a working map in one line.

tsx
import { Workflow51, workflow51Demo } from "@/components/beste/block/workflow51";

export default function AutomationPage() {
  return <Workflow51 {...workflow51Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

tsx
import { Progress16 } from "@/components/beste/piece/progress16";
import { Workflow51 } from "@/components/beste/block/workflow51";

export default function AutomationPage() {
  return (
    <Workflow51
      badge={{ label: "Hands off, mostly" }}
      heading="Which parts run themselves, and which parts still need you"
      description="Where a bar is short, that is a step we have not automated yet."
      headlineValue="0"
      headlineLabel="times a member detail is retyped between stages"
      automaticLabel="Automatic"
      manualLabel="Still needs a person"
      stages={[
        {
          stage: "First offer goes out",
          description: "Real capacity is matched and the first genuine opening is sent.",
          automatic: 100,
          manual: "Nothing. This step has had no manual fallback for a year.",
        },
        {
          stage: "The appointment",
          description: "One record with the referral, the form, and the history on it.",
          automatic: 20,
          manual: "The consultation itself, and the note that comes out of it.",
        },
      ]}
      media={
        <Progress16
          title="Referral to invoice"
          steps={["Referral", "Offer", "Intake", "Visit"]}
          activeIndex={2}
          caption="Three of these four stages need nobody at all."
        />
      }
      image={{ src: "/backdrops/blue.jpg", alt: "Soft blue gradient backdrop" }}
      mediaCaption="The stages a member passes through."
      button={{ label: "See what is still manual", href: "/product/automation" }}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string }–Eyebrow above the hairline rule, rendered through Badge23
headingstring–Section heading in the left column of the header
descriptionstring–Supporting paragraph, right-aligned from md up
headlineValuestring–One figure in the sticky column, at display scale
headlineLabelstring–What that figure counts
automaticLabelstring–Word appended to each percentage
manualLabelstring–Lead-in for what still needs a person
stagesStage[][]The stages, one hairline row each
mediaReactNode–Live asset on the tile, progress16 in the demo
image{ src: string; alt: string }–Backdrop behind the media tile
mediaCaptionstring–Caption under the tile
button{ label: string; href: string }–Outline action under the stages
classNamestring–Extra classes for the outer section
ts
type ActionLink = {
  label: string;
  href: string;
};

type TileImage = {
  src: string;
  alt: string;
};

type Stage = {
  stage: string;
  description: string;
  automatic: number;
  manual: string;
};

Behavior notes

  • automatic is a number used both as the bar width and as the printed percentage, so the two can never disagree. It is on a 0 to 100 scale and is not normalised.
  • manual is required on every stage, including the fully automated ones, where the demo answers "Nothing". A coverage map that omits the manual column on its best rows is the pattern this block avoids.
  • The bar is aria-hidden, since the percentage is printed beside the stage title.
  • The 20 percent row in the demo is the consultation itself. Publishing a low bar next to a good reason is what makes the high bars believable.
  • The sticky column is lg:sticky lg:top-24 lg:self-start. The self-start is required, otherwise the column stretches to the row height and sticky has nothing to travel within.
  • The headline figure runs to md:text-8xl, so the sticky column reads as a single claim while the stages beside it do the qualifying.
  • The layout is a 1fr to 1.8fr split, giving the stages most of the width.

More Workflow blocks

View all Workflow
PRO

workflow54

Data Flow Map

An integration map naming every system as a card, inverting the first-party one so it reads as the origin, then listing each crossing on a hairline row with what travels and how often.

PRO

workflow44

Overview & Phases

A sticky process overview with summary stats beside an expandable phase accordion.

PRO

workflow34

Phase Outcomes

Each engagement phase mapped from its inputs to its outcomes.

PRO

workflow17

Workflow Analytics Dashboard

Full-width analytics card with four KPI tiles, a CSS bar chart of the last 30 days, and a top-workflows leaderboard with share bars.

PRO

workflow28

Phase Tabs

Tabbed engagement phases with deliverables, duration and imagery.

PRO

workflow4

Workflow Stats With Live Tiles

Three-column stats strip where each metric is anchored by a real workflow piece: active runs, success rate, and approvals.