Boring Workflow Intake Map

Use this worksheet before turning a repetitive workflow into a website asset.

1. Public role
Who feels the pain? Use a public role, not a private person or customer name.

2. Repeated task
What repeats? Describe it without private records, invoices, contacts, health details, screenshots, or account data.

3. Trigger
When does the workflow start? Daily, weekly, after a request, before review, after a job closes, or another safe public trigger.

4. Output
What should exist at the end? Checklist, summary, folder, proof note, review queue, ready/not-ready decision, or status update.

5. Friction
What makes it slow? Missing steps, unclear owner, repeated checking, handoff gaps, confusing instructions, no proof trail, or too many tools.

6. Private or blocked material
Mark anything that must stay out of the public page:
- customer, prospect, patient, resident, payment, invoice, employee, or health data
- account login, OAuth, inbox, calendar, CRM, EHR, EMR, field-service software, or payment processor
- healthcare, insurance, legal, financial, sober-living compliance, taxes, hiring, or claims
- pricing, savings, revenue, guarantees, or service availability promises
- outreach, scraping, list building, posting, or customer/prospect contact

7. Safe first asset
Choose one:
- checklist
- FAQ
- scorecard
- worksheet
- parked proof packet

Stop before automation launch, account connection, customer/prospect outreach, CRM/form/calendar writes, pricing, spend, credentials, provider changes, TS Sales changes, or public SaaS launch.