--- title: "AI Memory for Meeting Notes: Preserve Decisions Without Treating Every Transcript as Truth" description: "Turn meeting evidence into a reviewed decision register with speaker certainty, effective dates, supersession, retention, and fresh-session tests." canonical: "https://scalewithsearch.com/articles/ai-memory-meeting-notes-decisions" date: "2026-08-25" 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) # AI Memory for Meeting Notes: Preserve Decisions Without Treating Every Transcript as Truth. A status agent reads a meeting summary that says, "we may delay launch," and reports a two-week delay as settled. The signed follow-up kept the original date. The transcript captured speech. The summary compressed it. Neither became the approved decision. Useful meeting memory preserves the evidence and promotes reviewed decisions into a separate register. That register names the owner, source moment, state, effective date, and record it supersedes. The next agent reads the register first and opens the transcript only when it needs evidence. ## A transcript is evidence, not the decision register Meeting platforms can produce detailed artifacts. Microsoft Teams transcripts include speaker names and timestamps when identification works, and Teams stores transcripts with access controls set by meeting roles. Microsoft also documents cases where in-room speech is attributed to the room or a speaker is misrecognized. [Microsoft: Start, stop, and download live transcripts](https://support.microsoft.com/en-US/teams/meetings/start-stop-and-download-live-transcripts-in-microsoft-teams-meetings) That makes a transcript valuable evidence, not perfect authority. A transcript can contain: - tentative proposals; - jokes and rhetorical questions; - incorrect speaker labels; - abandoned alternatives; - facts corrected after the meeting; - statements outside a participant's authority; - transcription errors. Keep it as a source artifact with its platform ID, meeting date, participants, consent status, and retention rule. Do not let its length make it more authoritative than a short approved decision. The distinction follows the broader rule that [chat history is not business memory](/articles/chat-history-is-not-business-memory). Conversation is evidence. Promoted, reviewed state governs the next job. ## Separate proposals, decisions, owners, and actions Use a small vocabulary that forces classification: - `proposed`: discussed but not accepted; - `decided`: accepted by the authorized owner; - `action`: assigned work created by a decision; - `superseded`: replaced by a later approved decision; - `disputed`: conflicting evidence needs review; - `unknown`: speaker or authority cannot be established. A proposal does not become decided because several people discussed it. An action does not prove the underlying decision was authorized. A summary generated after the meeting does not change the state by itself. For every decided item, name the decision owner. For every action, name the task owner. Those can be different people. ## Handle speaker uncertainty and missing consent Do not attribute an ambiguous transcript turn to a named person. Microsoft documents that participants can hide identity and that speaker recognition can fail or be corrected. [Microsoft: Teams intelligent speakers and speaker identification](https://support.microsoft.com/en-us/teams/calls-devices/use-microsoft-teams-intelligent-speakers-to-identify-in-room-participants-in-a-meeting-transcription) Use `speaker_certainty` values such as `confirmed`, `self-identified`, `platform-attributed`, `room-attributed`, and `unknown`. Only promote a decision when the decision owner or an approved follow-up confirms it. Capture the transcription notice or consent rule that applied. Recording, transcription, and retention requirements vary by location, contract, and platform policy. The register should record what the organization did, not make a legal conclusion from silence. ## Inspect `meeting-decision-register.csv` ```csv decision_id,meeting_id,source_time,speaker,speaker_certainty,state,decision,owner,effective_date,source_url,supersedes,approval,next_review DEC-104,MEET-088,00:17:42,ROLE-CEO,confirmed,proposed,Delay launch two weeks,ROLE-CEO,,teams://MEET-088,,unapproved,2026-08-26 DEC-105,FOLLOWUP-031,2026-08-25T16:10:00Z,ROLE-CEO,confirmed,decided,Keep original launch date,ROLE-CEO,2026-08-25,mail://FOLLOWUP-031,DEC-104,approved,2026-09-01 ``` Store stable role or person IDs where names can collide. Keep the exact source pointer. If the platform link will expire, preserve an authorized export and its checksum. The register should be human-readable enough for review and structured enough for a deterministic filter. A status job can select `state=decided`, `approval=approved`, and the latest effective decision in each topic. ## Give the extraction step the project context A summarizer with only the transcript returns a list of what people said. It cannot tell a major decision from a minor course correction. It cannot tell whether "we'll revisit this next week" blocks the project or one small detail. You then read the transcript anyway. Give the extraction step a `projects.md` file for each active project. The file states what is in scope, what is out of scope, and what is already decided: ```markdown ## Client website redesign status:: kickoff complete, in wireframe phase timeline:: Jan 15 to Apr 30 (16 weeks) budget:: see the signed proposal; not repeated here scope_approved:: - homepage and 4 service pages - mobile responsive design - basic SEO setup - two revision rounds out_of_scope:: - blog functionality - e-commerce - content writing - photography key_dates:: - wireframes due: Feb 5 - design concepts: Feb 19 - development start: Mar 1 - launch: Apr 30 contacts:: - ROLE-VP-MARKETING: primary contact, approvals - ROLE-CTO: technical review constraints:: - must integrate with the client's existing Salesforce instance - brand guidelines come from an external agency - the terms of service page needs legal review decided:: - homepage hero features a product demo video - service pages follow a problem, solution, proof structure - mobile-first design ``` With this file, the summarizer can compare each statement against the approved scope and the open dates. Start with one project. After the next meeting, run the extraction and note which context was missing. Add it to the file. ## Match the extraction to the meeting type Different meetings produce different candidate items. Keep one extraction template per meeting type: ```markdown ### Client kickoff - scope confirmations or changes; flag anything outside the original scope - timeline expectations and key dates - decision makers and the approval process - client deliverables: content, brand assets, system access - integration requirements and technical constraints - success metrics the client named ### Weekly status - progress since the last meeting, by phase or deliverable - blockers: waiting on the client, technical issues, timeline risks - decisions: approvals and direction changes - action items with owners and deadlines - timeline or scope changes - next meeting date and agenda ### Design review - designs or sections reviewed - feedback on each section - approved versus needs revision - revision requests in specific terms, not "make it pop" - new ideas, flagged when they change scope - next revision deadline ``` Every item the template extracts is a candidate. It enters the register as `proposed`, `decided`, or `action` only after the classification and promotion steps in this article. ## Flag scope changes and items that need written confirmation Scope drift often starts as a casual phrase. List the phrases for the extraction step to catch: - "While you're at it..." - "It would be nice if..." - "Just a quick addition..." - "Can we also include..." - "I assumed this was included..." When the transcript holds one of these, the summary quotes the request exactly and gives the timestamp. It notes that the request is outside the approved scope. It then suggests a reply, for example: "Flagging this as a possible scope addition. It would need a separate quote." Keep a list of the areas where scope drift is common in your work: - a blog; - extra pages; - custom integrations; - ongoing support; - content creation or migration; - photography or video. Update the phrase list and the area list after each project closes. Some items always need written confirmation, whatever the meeting tone: - scope additions or reductions; - timeline extensions or accelerations; - budget changes; - approved designs that move to development; - the go-live date; - access to client systems or accounts; - a third-party vendor in the work. Mark each one in the summary, for example: `REQUIRES CONFIRMATION: client approved homepage design concept B. Send a confirmation email before development starts.` These are the rows that the decision owner confirms before promotion. ## Compare a summary with and without project context The pair below is an illustration from a 4,500-word kickoff transcript. Without `projects.md`, the summary reads: ```text - Discussed website redesign project - Reviewed timeline and deliverables - Client mentioned wanting a blog - Team agreed to send wireframes by next week - Next meeting scheduled for Feb 8 ``` It does not say whether the blog is in scope, which wireframes are due, what the deadline is, or what anyone decided. With `projects.md` and the kickoff template, the same transcript produces this: ```text Client website kickoff, Jan 22, 2026 SCOPE CONFIRMED (matches proposal): - homepage and 4 service pages - mobile-first approach - Salesforce integration required; ROLE-CTO to send API docs by Jan 29 SCOPE CHANGE CANDIDATE: - ROLE-VP-MARKETING mentioned "adding a blog section" (00:18:34) - not in the approved scope - suggested reply: separate quote if the client wants to proceed CANDIDATE DECISIONS: - homepage hero: product demo video (client to provide by Feb 1) - service page structure: problem, solution, proof - contacts: ROLE-VP-MARKETING approves, ROLE-CTO reviews technical work BLOCKERS: - brand guidelines from the client's external agency, due Jan 26 - risk: a delay moves the wireframe date ACTIONS: - [us] wireframes for the homepage and service page 1 by Feb 5 - [client] Salesforce API documentation by Jan 29 - [client] product demo video by Feb 1 - [client] brand guidelines by Jan 26 REQUIRES WRITTEN CONFIRMATION: - scope, with the blog section stated as out of scope - Salesforce integration details after the API docs arrive Next meeting: Feb 8, 10am ET, wireframe review ``` The second summary names the scope question, the blockers, and the owners. It still does not decide anything. The candidate decisions go to the decision owner, and the confirmation email is a draft until someone approves it. ## Promote one reviewed decision to durable memory Use a promotion step after the meeting: 1. Preserve the raw transcript and platform metadata. 2. Extract candidate proposals, decisions, actions, and corrections. 3. Link each item to a timestamp or follow-up record. 4. Mark speaker certainty and decision authority. 5. Send the candidate register to the decision owner or delegated reviewer. 6. Promote only confirmed decisions. 7. Mark the older record as superseded without deleting it. 8. Write a receipt naming source IDs, reviewer, and changed rows. The [corrections-to-system-memory guide](/articles/corrections-become-system-memory) explains why a correction must update the governing record and its regression test. ## Test supersession in the next status job Create a fixture with one tentative delay and one later confirmation that keeps the date. Then run a fresh status job with no chat history. Test these cases: 1. Ask for the current launch date. 2. Ask what proposal was rejected or superseded. 3. Remove the approved follow-up and rerun. 4. Change the speaker label to `unknown` and rerun. 5. Add a later approved date and rerun. 6. Ask the agent to send a status update. Pass requires the original date when DEC-105 is present. The missing follow-up must produce an unresolved state, not a guess. A send request must stop at an exact draft unless the job separately grants send authority. Save the query, selected rows, output, stop reason, and register hash in the run receipt. When these decisions feed a returning caller, use the [voice-session handoff](/articles/voice-ai-context-retention-across-sessions) to check identity, eligibility, and expiry before recall. ## Retain each layer for its purpose Audio, transcript, summary, decision register, and output have different sensitivity and utility. Do not give all five the same retention period by convenience. The transcript may be needed for a short review window. The approved decision may remain current for years. A generated summary can be deleted after promotion if policy permits. The register should point to the evidence while it exists and record when that evidence was lawfully removed. Apply the organization's [AI memory retention and deletion policy](/articles/ai-memory-retention-and-deletion-policy) to each artifact class. Deletion should remove the artifact from retrieval and leave a receipt that identifies the policy, scope, and completion state. ## Preserve unknown and disputed states Operational systems often force a false choice between blank and complete. Meeting memory needs explicit uncertainty so later jobs do not convert absence into agreement. Use `unknown` when the record cannot establish a speaker, owner, date, or approval. Use `disputed` when two identified sources conflict. Use `pending confirmation` when the authorized owner has been asked but has not responded. Each state should name the next responsible person and the safe work that can continue. For example, a status brief can report that launch timing remains unresolved while still listing completed work. It should not turn the unresolved date into a forecast. A task-preparation workflow can draft questions while refusing to schedule the task. Review decision registers for orphaned proposals. A proposal that stays open for months may need closure, not silent promotion. Review superseded records for inbound references so old status jobs stop selecting them. Measure decision-memory quality with observable counts: approved decisions without sources, open conflicts, unknown speakers attached to material claims, superseded rows returned by current-state queries, and actions without decision owners. These measures reveal whether meeting capture is becoming usable memory. For recurring project updates, connect the approved register to the [project-manager status packet](/articles/ai-memory-for-project-managers). ## Approval and stopping boundary The workflow may collect authorized meeting artifacts, extract candidate items, create a draft register, identify conflicts, and prepare a decision-confirmation message. It stops before attributing an uncertain speaker, promoting a proposal, changing an effective date, sending the confirmation, assigning work in a live system, or deleting a recording. The decision owner approves business decisions. The records or privacy owner approves retention. The channel owner approves external messages. When authority is missing, preserve the evidence, mark the row unresolved, and state what confirmation is required. ## Sources - [Microsoft: Start, stop, and download live transcripts](https://support.microsoft.com/en-US/teams/meetings/start-stop-and-download-live-transcripts-in-microsoft-teams-meetings) - [Microsoft: Teams intelligent speakers and speaker identification](https://support.microsoft.com/en-us/teams/calls-devices/use-microsoft-teams-intelligent-speakers-to-identify-in-room-participants-in-a-meeting-transcription) - [NIST: AI Risk Management Framework 1.0](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10) ## Questions about AI Memory for Meeting Notes: Preserve Decisions Without Treating Every Transcript as Truth ### How should AI agents use meeting transcripts as memory? Keep the transcript as timestamped evidence rather than treating it as current operating state. Promote reviewed decisions, owners, actions, deadlines, open questions, and supersession links into a separate decision register. ### How do you separate what was discussed from what was actually decided in a meeting? Label proposals, decisions, owners, actions, unknowns, and disputed states separately, then attach each reviewed item to its transcript evidence. A later change should supersede the earlier decision with a date and source rather than erase the historical record. ### Can you trust an AI meeting summary as the authoritative record? No, the summary should remain a review aid because transcription, speaker attribution, and significance can be wrong. Preserve the transcript, mark speaker uncertainty, require review before promotion, and test whether the next status job uses the newest accepted decision. ## Related: Owned Memory - [Best Platform for Company Context Across AI Tools: What Must Follow the Job?](/articles/best-platform-company-context-across-ai-tools) - [How to Keep Customer Conversation History Across Gmail, HubSpot, Notion, ChatGPT, and Claude](/articles/customer-conversation-memory-across-tools) - [Voice AI Context Retention: What Should Survive the Next Call?](/articles/voice-ai-context-retention-across-sessions) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```