--- title: "AI Memory for Project Managers: Keep Decisions, Deadlines, and Dependencies Across Tools" description: "Build a project context register for decisions, owners, dates, dependencies, risks, corrections, weekly status drafts, and source receipts." canonical: "https://scalewithsearch.com/articles/ai-memory-for-project-managers" date: "2026-08-23" 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 Project Managers: Keep Decisions, Deadlines, and Dependencies Across Tools. A status assistant reports that a milestone is on track. Three days earlier, a meeting changed the dependency and moved the delivery date. The transcript exists, but nobody promoted the accepted decision into the project record. Project memory is the change record the next update can trust. It keeps decisions, owners, effective dates, dependencies, risks, corrections, and evidence distinct from conversation history. Start with one weekly status job. Build a small context register. Test a changed deadline and a missed dependency before connecting every project tool. The context path must remain clear from source event to approved status draft. ## Project memory is the change record Project systems contain tasks, comments, documents, messages, transcripts, calendars, and dashboards. AI can summarize those surfaces. It cannot infer which statement became the accepted project decision unless the operating record makes that authority visible. Project memory should answer: - What changed? - Who accepted it? - When did it take effect? - Which deliverable or dependency changed? - Which source proves it? - Which older record is superseded? - What review or approval remains? PMI's current AI standard for project work emphasizes human oversight, data quality, risk, governance, and accountability across the life cycle. [PMI: Standard for AI in Project Work](https://www.pmi.org/about/press-media/2026/pmi-publishes-worlds-first-global-standard-for-ai-in-project-work) The project manager remains accountable for the record and decision. The model helps prepare work from it. ## Capture decisions, owners, dates, dependencies, and risks Give each record a stable ID. Avoid burying the controlling fact in prose. ```csv record_id,type,project_id,summary,owner,effective_date,source_id,depends_on,supersedes,status,next_review DEC-041,decision,PRJ-048,Move launch to Sep 17,OWNER-01,2026-08-21,MEET-118,MILE-07,DEC-033,approved,2026-08-28 RISK-019,risk,PRJ-048,Vendor access may slip test,OWNER-02,2026-08-22,TICKET-771,MILE-06,,open,2026-08-25 ``` Each row preserves a source and an accepted change. Keep the CSV editable; do not use a model summary as the only record. Use exact project, client, and source identifiers. Add data sensitivity and approval state when the work requires them. ## Separate source systems from the working packet The project tool may remain the source for tasks. The contract repository may remain the source for scope. The calendar may remain the source for accepted meetings. The register does not need to duplicate every object. For comparing that owned record with a hosted Notion workspace, read [Owned Business Memory vs Notion AI: Compare the Handoff.](/articles/owned-business-memory-vs-notion-ai) Build a working packet for the weekly status job: ```text weekly-status/ context-manifest.md project-context-register.csv open-milestones.csv approved-risks.md corrections.md status-brief.md receipts/ ``` For each imported field, record its source system and retrieval time. A stale copy should be visible as stale. The [AI context manifest](/articles/ai-context-manifest-template) can define required sources, source order, exclusions, and stopping point. If status evidence crosses email, CRM, and notes, the [customer timeline pattern](/articles/customer-conversation-memory-across-tools) adds stable identity, source events, and explicit supersession. ## Keep a readable brief for each project Without a project record, a request such as "status update on the redesign" gets a question back: which redesign, and what scope? The manager explains the project again in every chat. The register holds the controlling rows. A short Markdown brief, `project-brief.md`, gives the status job the plain context around them. Add one brief per project to the working packet, with seven sections. For choosing between capture notes and inspectable project files, read [Apple Notes vs Obsidian for AI Memory.](/articles/apple-notes-vs-obsidian-ai-memory) **Project info:** name, client ID, start date, target launch, status, and goal. The budget stays in the contract repository, not in the brief. ```markdown ## Project: three-location clinic website redesign client:: CLIENT-048 start:: 2026-01-15 target_launch:: 2026-03-31 status:: in progress, phase 2 goal:: mobile-first redesign with fast pages and a local search structure for each location ``` **Scope:** what is in, what is out, and the success criteria that decide acceptance. ```markdown ## Scope in:: full redesign (10 pages); mobile-first responsive design; 3 location landing pages; blog template and CMS setup; speed work to under 2 seconds load; basic on-page SEO out:: booking system (future phase); content writing (client provides); ongoing maintenance (separate agreement); social media integration success:: mobile PageSpeed score above 90; load time under 2 seconds; all pages responsive; client approval on design mockups ``` **Team and cadence:** each role and when each pair meets. ```markdown ## Team OWNER-01:: project lead, client contact, content structure designer:: mockups, UI and UX developer:: build and speed work client contact:: content, feedback, approvals cadence:: weekly client check-in Tuesday 9am; developer sync Thursday 2pm; design review on demand ``` **Timeline:** phases and milestones, each with a plain status word. ```markdown ## Timeline Phase 1, discovery and design (Jan 15 to Feb 5): kickoff, audit, wireframes, mockups, client approval Feb 7. All done. Phase 2, development (Feb 10 to Mar 15): - environment setup, Feb 10: done - homepage build, target Feb 20: in progress, moved to Feb 25 - location pages, target Feb 28: in progress - blog template, Mar 5: not started - speed work, Mar 10: not started - QA and testing, Mar 15: not started Phase 3, launch (Mar 16 to Mar 31): staging review Mar 18; final revisions Mar 20 to 25; go live Mar 31 ``` **Decisions:** each decision with its date and its reason. The reason is what a later reader needs most. ```markdown ## Decisions 2026-01-28: mobile-first design (70% of the client's traffic is mobile) 2026-02-05: blue and white color scheme (matches existing brand) 2026-02-07: removed the animated hero (slow load, looked gimmicky) 2026-02-12: added location-specific service pages (local search benefit) 2026-02-18: moved the homepage build 5 days (developer out; better than a rushed build) ``` **Blockers and risks:** what holds work now, and what could. ```markdown ## Blockers current:: homepage 5 days late; team headshots requested Feb 10, not received risks:: the Mar 31 launch is tight if more delays occur; location content needed by Mar 1 is incomplete; speed work may show that the hosting plan needs an upgrade ``` **Weekly updates:** a short log, newest first. ```markdown ## Updates Week of Feb 17: homepage build started (moved to Feb 25); location wireframes final; partial content received, location 3 copy missing; developer back Week of Feb 10: environment live; homepage build started; hosting plan may need an upgrade for the speed target Week of Feb 3: mockups approved; small layout changes to location pages; development kickoff scheduled ``` Update the brief each week, or at once after a major change. The brief is context, not a task manager, and it does not replace the project tool. It also does not update itself. When a blocker appears, someone writes it down. ## Promote meeting decisions without importing whole transcripts Transcripts are evidence. They can contain transcription errors, jokes, proposals, unresolved disagreement, and personal information. After a meeting, extract candidate decisions and obligations. A responsible owner confirms them. Promote only the accepted records into the decision register. Link back to the source segment or meeting ID. Do not give a status agent permanent access to every transcript when the job needs six approved records. Keep raw transcripts in the governed source system and retrieve them only for a named dispute or review. If the speaker is unclear, do not attribute the decision. Mark it unresolved. ## Correct and supersede project facts Never erase the history needed to explain a project change. Mark the old record superseded and link the replacement. For a correction, record: - old value; - accepted value; - source; - owner; - effective date; - records and outputs affected; - retest status. Then run the next status job from a fresh session. The correction is not complete until the output uses it. The [AI correction log template](/articles/ai-correction-log-template) provides the full control pattern. ## Build one weekly status job Define a fixed output: - reporting period; - accepted progress; - current milestone dates; - new decisions; - active dependencies; - open risks; - unresolved conflicts; - next permitted actions; - source references; - approval and stopping state. The job may draft the update. It should stop before sending it to stakeholders unless a separate approved executor owns that action. Require an explicit no-work receipt when no project meets the eligibility rule. That proves the system inspected the queue. Without the brief, the exchange runs in circles. The assistant asks which redesign. It then asks for the status, then the timeline. The manager gives up and writes the update by hand. With `project-brief.md` in the packet, the same request returns a draft like this: ```text Clinic redesign: week of Feb 17 Status: phase 2 (development), on track with a minor delay Done this week: - homepage build under way; developer back - location page wireframes final - partial content received from the client In progress: - homepage build (moved to Feb 25 from Feb 20) - location pages (on track for Feb 28) Blockers: - team headshots, requested Feb 10, not received - location 3 content missing, needed by Mar 1 Next: - follow up with the client contact on headshots and location 3 copy - homepage review, target Feb 26 - blog template build starts Mar 1 Risk: the Mar 31 launch is tight if content delays continue. Sources: project-brief.md (Updates, Blockers, Timeline); DEC and RISK rows as cited State: draft; stopped before send ``` Each line traces to a section of the brief or a register row. The draft stays a draft until the project owner approves it. ## Extend the register across a portfolio A project manager with eight active projects asks a model for eight status updates. Without the register, the model returns eight similar paragraphs about momentum and alignment. It does not know which project is two weeks late, which approver has not responded, or which slip moves another project's date. The manager then rewrites each draft from memory. The weekly status job needs portfolio records that a single-project register does not hold: - which projects are on track and which are at risk; - each stakeholder's role, the decision they approve, and the update format they accept; - the cadence each stakeholder expects; - dependencies between projects, not only inside one project; - open blockers, their age, and the escalation path; - pending decisions and the person who makes each one; - team capacity by period. Keep these as separate files beside the register: ```text portfolio/ stakeholders.csv blockers.csv cross-project-dependencies.csv capacity.csv ``` Synthetic example, not a client result: ```csv stakeholder_id,project_id,role,approves,update_format,cadence,escalation_to,source_id STK-01,PRJ-048,marketing director,homepage design,short email with the open question first,weekly,STK-03,KICKOFF-12 STK-02,PRJ-048,development lead,build start,ticket comment,on change,,KICKOFF-12 STK-03,PRJ-048,chief executive,launch date and budget,one-paragraph summary of cost and return,weekly,,KICKOFF-12 ``` ```csv blocker_id,project_id,summary,waiting_on,since,deadline_effect,next_action,next_action_date,source_id BLK-12,PRJ-048,homepage design not approved and build cannot start,STK-01,2026-08-31,final assets due to STK-02 by 2026-09-15 or launch moves one month,escalate to STK-03,2026-09-10,MEET-121 BLK-13,PRJ-048,fifth round of scope revisions requested,CLIENT-048,2026-09-02,budget overrun likely,schedule scope freeze meeting,2026-09-09,MEET-121 ``` ```csv dependency_id,upstream_project,upstream_milestone,downstream_project,downstream_milestone,latest_safe_date,status,source_id DEP-07,PRJ-048,design approval,PRJ-052,marketing site update,2026-09-15,at risk,BLK-12 DEP-08,PRJ-052,final feature set,PRJ-052,sales training materials,2026-09-30,on track,PLAN-09 ``` ```csv team_id,period,committed_projects,available_from,condition,source_id TEAM-DEV,2026-10,PRJ-048;PRJ-052,2026-10-15,DEP-07 resolved by 2026-09-15,PLAN-09 ``` The blocker file carries the prepared next actions: escalate the approval, freeze the scope, and prepare a delay notice if the date passes. Each action stays a draft until the project owner approves it. ## Run the portfolio jobs from the same records The same files support six recurring jobs. Each job reads named rows, cites them, and stops before any message leaves the team. 1. Friday status set. One draft per active project. A project with progress reports progress. A project with an aged blocker flags the risk. A project past its escalation date proposes the escalation. A project with no change says so. 2. Meeting lookup. A stakeholder asks about one dependency during a meeting. The job returns the `DEP-07` row, its upstream blocker, and the latest safe date. 3. Executive portfolio summary. Counts of projects on track and at risk, the top three blockers across the portfolio, capacity limits, and the decisions that need an owner. 4. Escalation draft. The job uses the recipient's `update_format` from `stakeholders.csv`. It names the blocker, its age, the deadline effect, and the decision needed this week. 5. Client check-in talking points. The job lists status, confirmed dates, open dependencies, and the mitigation already approved. 6. Capacity answer for new work. The job states when each team becomes available and which dependency that date relies on. A capacity answer must carry its condition. "Available from 2026-10-15 if `DEP-07` resolves by 2026-09-15" is a record. "Available mid-October" is a guess. To measure the change, time one Friday status set before the register exists and one after. Record both times in the receipt. Do not quote a saving that you did not measure. ## Inspect `project-context-register.csv` Add fields that make conflicts testable: ```csv record_id,project_id,client_id,record_type,current_value,owner,effective_date,source_id,source_role,supersedes,dependency_id,approval_state,last_tested DEC-100,PRJ-048,CLIENT-048,deadline,2026-09-17,OWNER-01,2026-08-21,MEET-118,approved-decision,DEC-099,MILE-07,approved,pending COR-100,PRJ-048,CLIENT-048,wording,use data owner,OWNER-03,2026-08-22,REVIEW-44,accepted-correction,COR-088,,approved,pending ``` Store the canonical file in a controlled location. Generate read-only job packets from it when needed. Do not let each assistant maintain its own divergent copy. ## Test a missed dependency and changed deadline Create a synthetic fixture with one original deadline, one accepted new deadline, and one dependency hidden from the task list but present in the approved register. Also add: - a transcript proposal that was never approved; - a superseded risk state; - a second-project canary; - a downstream project whose milestone depends on the changed date; - a request to email the status. The draft must use the new deadline and identify the dependency. It must flag the downstream milestone as at risk, ignore the proposal, avoid the canary, and stop before email. Remove the approved decision source and rerun. The output should block rather than recover the old date from conversation history. Save the source IDs, output hash, conflicts, and stopping state in the receipt. ## Keep human accountability visible AI can prepare status material, detect missing fields, compare dates, and surface conflicts. It cannot own the stakeholder consequence of a schedule or scope decision. Name the people who accept decisions, approve the external update, own data quality, and resolve conflicts. Keep these roles in the project operating record. PMI's AI standard describes human-in-the-loop oversight across project stages. That control must occur at a defined step, not as a vague promise that someone may review the result later. ## Approval and stopping boundary The setup may create synthetic project records, read-only exports, a context register, weekly status drafts, canary tests, and receipts. It stops before connecting live project systems, importing private transcripts, changing tasks or deadlines, messaging stakeholders, or using AI output as an approved decision. The project owner, data owner, and communication owner approve those actions. If the team cannot identify who accepted a decision, the status job reports it as unresolved. It does not infer authority from the loudest or latest message. ## Sources - [PMI: Standard for AI in Project Work](https://www.pmi.org/about/press-media/2026/pmi-publishes-worlds-first-global-standard-for-ai-in-project-work) - [PMI: AI Essentials for Project Professionals](https://www.pmi.org/-/media/pmi/documents/public/pdf/artificial-intelligence/ai-essentials-for-project-professionals.pdf) - [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) ## Questions about AI Memory for Project Managers: Keep Decisions, Deadlines, and Dependencies Across Tools ### Would you use an AI as a project coordinator to manage your board and timelines based on your raw notes? Use it first to extract proposed decisions, owners, dates, dependencies, risks, and status changes into a reviewable register. Keep accountable people responsible for approving assignments, commitments, and material schedule changes. ### What AI tools are you using in your project management work, and how effectively are they helping you? Judge the system by one recurring job, such as producing a weekly status draft from named project sources. Verify whether it preserves decisions, owners, dates, dependencies, risks, corrections, and evidence links instead of measuring output fluency. ### Any practical examples of AI actually improving delivery or decision-making? A bounded example is a weekly status job that compares the current register with source systems and flags changed deadlines, missed dependencies, unresolved risks, and conflicting updates. The project manager reviews the draft and remains accountable for the decision and communication. ## Related: Owned Memory - [AI Memory for Freelancers: Keep Client Context Separate Without Re-Explaining Every Brief](/articles/ai-memory-for-freelancers) - [AI Memory for Meeting Notes: Preserve Decisions Without Treating Every Transcript as Truth](/articles/ai-memory-meeting-notes-decisions) - [Best AI for Team Conversation Memory: Test the Decision Trail](/articles/best-ai-team-conversation-memory) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```