--- title: "Document roles, processes, and vendors so AI works from how your operation runs" description: "Keep team roles, SOPs, process dependencies, vendors, metrics, and incidents in files so AI drafts SOPs, reports, and vendor email from your real operation." canonical: "https://scalewithsearch.com/articles/ai-for-operations-managers" date: "2026-01-28" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Document roles, processes, and vendors so AI works from how your operation runs. An operations manager documents a workflow that touches three departments, two software systems, and four approval steps. The AI assistant does not know the org structure or the current SOPs. It does not know that a similar process already exists for a related function. Operations work runs on context: team roles, process dependencies, system access, vendor relationships, and performance data. That context lives in the manager's head, in scattered documents, or in knowledge nobody wrote down. When the manager asks the assistant for process documentation, performance tracking, or workflow improvement, most of the time goes to explaining how things work today. The assistant becomes a transcription service. A set of operations files turns it into a working partner, because the explanation happens once. ## Why operations needs a persistent record Operations is not a set of one-off tasks. It is systems that run again and again, teams that change over time, and processes that connect across departments. An assistant that forgets between sessions cannot help you manage those links. Process documentation needs to know what is already documented. A new customer onboarding SOP should reference the account setup process, the support ticket workflow, and the billing procedure. Team management needs history: who owns which functions, who is trained on which systems, and who is good at which tasks. Performance tracking needs baselines. You collect data all the time: project completion times, error rates, customer satisfaction scores. That data usually sits in spreadsheets, where the assistant cannot use it. ## What the operations files hold | File | Contents | |---|---| | `team.md` | Each person's role, responsibilities, systems access, trained workflows, and backup for each critical function | | `processes/` | One SOP per process, in one format, with owner, approval steps, and links to dependent SOPs | | `vendors.md` | Each vendor: contact, account rep, contract terms, service levels, renewal date, performance notes | | `metrics.md` | Monthly tables for the measures you report: cycle times, error rates, cost per transaction, satisfaction | | `incidents.md` | Each incident: date, issue, response, root cause, fix, process change | | `budget.md` | Spend by category, budget against actual, subscriptions and their use | Keep `team.md` to roles and skills. Performance reviews and HR records stay in their own systems. ## Inspect two of the files These are synthetic examples. ```markdown # team.md updated:: 2026.09.25 ## Vendor invoicing owner:: A. Rivera backup:: J. Chen (trained 2026-05) systems:: accounting system, vendor portal ## Customer onboarding owner:: J. Chen depends_on:: processes/account-setup.md, processes/support-tickets.md, processes/billing.md ``` ```markdown # incidents.md ## 2026-09-12: payment processor timeout issue:: checkout failed for 40 minutes response:: switched to backup processor at 10:25 root_cause:: expired API certificate fix:: certificate renewal added to monthly checklist process_change:: processes/payments.md rev 4 related:: 2026-03-02 (same cause) ``` The `related::` line is where pattern recognition starts. The second timeout with the same cause is a process problem, not bad luck. ## Load the files each session Claude Code reads a file named `CLAUDE.md` from the working folder when a session starts ([Claude Code memory documentation](https://code.claude.com/docs/en/memory), checked 2026.09.25). Keep `CLAUDE.md` short. Describe the business in a few lines and list where each file lives. Then ask Claude Code to read the files a job needs. The guide to [AI agent memory architecture for a small business](/articles/ai-agent-memory-architecture-small-business) shows how to lay out the folders as the record grows. The files stay on your computer. The text Claude Code reads goes to Anthropic for processing. Retention and training terms depend on your plan. Keep credentials, customer records, and personnel files out of the operations folder. ## Write SOPs that connect Most operations documentation happens in reaction. Something breaks, someone asks how to do a task, or an audit needs written procedures. You write it, save it, and move on. Six months later, the document is out of date and nobody remembers it exists. With the process folder, documentation adds up. When you write a new SOP, the assistant knows which processes already exist. It suggests links to related workflows, flags overlap with existing SOPs, and names gaps where no procedure exists. The format stays consistent. The assistant applies the format of your last three SOPs, including approval steps, revision history, and owner fields. For cross-functional work, the `depends_on::` lines map the links. When one department changes its process, ask the assistant which other SOPs reference it. ## Answer coverage and capacity questions Ask: "Who can handle vendor invoicing while A. Rivera is out?" The assistant answers from the documented owner and backup, not from a guess. For capacity planning, `team.md` shows how work is spread. If one person owns six critical processes and everyone else owns two, the imbalance is visible. Ask the assistant to propose a redistribution from the documented responsibilities, then decide yourself. Cross-training works the same way. The file shows who is trained on what, so you can find single points of failure and plan training to add backups. ## Find and fix bottlenecks Most operations managers know where the bottlenecks are, because they live with them. The hard part is to pick which one to fix first and to prove that a change helped. Log how long each step takes and where work gets stuck. When you change a process, the before-and-after comparison already exists. Patterns appear over time. Some order types always hit the same delay. Some handoffs always wait a day. Ask the assistant to list the delays from the log and rank them by total time lost. ## Coordinate vendors from their history Vendors create steady administrative work: IT support contracts, facility maintenance, logistics providers, and software subscriptions. `vendors.md` holds the contact, the contract terms, the service level, and the performance notes. When you need to escalate an IT issue, the assistant knows the account rep and what the service level requires. When a contract comes up for renewal, it pulls the performance notes to inform your position. If the cleaning service has declined over six months, the notes show it. If a software vendor keeps missing support response times, the record supports a switch. When you ask for a vendor email, the assistant drafts it with the past issues, the contract terms, and the right contact. You review and send it. ## Report from recorded metrics Operations managers report up: monthly reviews, quarterly updates, budget cases. Each needs metrics. Most managers compile them by hand each time. Record each metric as it happens. At month end, add the invoice volume and error rate. At project close, add the timeline and the outcome. Ask: "What was average order processing time in Q4?" or "How many support tickets did we close last month?" The assistant answers from `metrics.md`. Check any total or trend against the source system before it goes into a report. The assistant reads the table well. It can still add a column wrong. A report number must match the system of record. ## Use incidents to prevent repeats Incidents need a fast response and a tracked resolution. Most managers handle them through email threads and memory of what went wrong. Log each incident when it happens. The log survives staff turnover and prevents repeat mistakes. When an incident recurs, the assistant surfaces the earlier ones. It shows that this is the second payment timeout with the same cause, or that a customer complaint matches three from last quarter. For post-incident reviews, ask the assistant to count incidents by type, compare response times, and check whether each fix reduced recurrence. The guide on [how corrections become part of the system](/articles/corrections-become-system-memory) shows how to turn each fix into a rule the next run follows. ## Onboard and cross-train from the same files New hires need to learn systems, processes, and team habits. Many managers train through shadowing and forwarded email. Written training material often covers only part of what a new person needs. With the files, the assistant generates a task list for the new person's role. It pulls the relevant SOPs and builds a checklist for the first 90 days. Training material stays current because it comes from the SOPs. When you update a process, the training checklist changes with it. ## Ground budgets in actual spend Budgets built from hope fail review. `budget.md` records vendor spend, subscriptions, project budget against actual, and labor by function. When you need to justify an increase, the record shows why costs rose. For cost reduction, the assistant lists high-spend categories and low-use subscriptions. A license nobody uses shows up. An outsourcing option can be compared with in-house cost. You make the call. ## Set the limits and start The assistant drafts SOPs, reports, and vendor email. It does not change a live process, sign a contract, or message a vendor on its own. Each job needs a named source list and a stop, as [give every agent a job, sources, and stopping point](/articles/give-every-agent-a-job-sources-and-stopping-point) describes. Setup takes a few hours: 1. List team members with roles, responsibilities, and backups. 2. Write or collect the SOPs for your five most important processes. 3. List vendors with contacts, terms, and renewal dates. 4. Define the metrics you report and add the last three months. 5. Start the incident log with the last incident you remember. After that, maintenance is part of the work: log incidents, record metrics, revise processes. When a manager leaves, the files stay with the business, and the [AI system ownership and transfer checklist](/articles/ai-system-ownership-transfer-checklist) covers the handoff. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```