--- title: "Give your remote team one written project record so AI answers from the same facts" description: "Keep project status, decisions, and team hours in a shared folder that every teammate's AI reads, so async work starts from the current record." canonical: "https://scalewithsearch.com/articles/ai-memory-for-remote-teams" 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) # Give your remote team one written project record so AI answers from the same facts. Your designer in Portugal finishes a mockup at 6 p.m. local time. Your developer in Austin wakes at 7 a.m. and sees the Slack notification. It says "updated the homepage," with a Figma link and three follow-up messages about what changed. The developer opens Figma and sees the changes. They do not remember the client's original request from two weeks ago. They scroll Slack, find the thread, and read 47 messages. Half are jokes. A quarter say "approved" or "looks good" with no context. The real decision sits in message 31. By the time the developer knows what to build, it is 9 a.m. Two hours are gone to context, not code or design. An AI assistant could summarize the Slack thread. It does not know which thread matters, what the client first asked for, or which three design directions the team rejected. It starts from zero, the same as the developer. This page shows how to give the whole team one written record that every assistant reads. ## The remote team context problem Remote teams work async, and that is the point. Async work also opens context gaps: - messages pile up overnight while you are offline; - decisions happen in Zoom calls you did not attend; - project history spreads across Slack threads, Notion pages, Loom videos, and email chains; - new team members join with no view of what came before; - long projects collect so much context that nobody remembers the original goal. In an office, you tap a colleague on the shoulder and ask about the homepage redesign. A remote team cannot. You do not interrupt someone in another time zone to ask what happened three weeks ago. So you search Slack, Notion, and Google Drive. You find pieces and assemble the story. By the time you have enough context to start, half the morning is gone. ## Why a general assistant cannot bridge the gap An assistant can summarize, but it needs the right source. You can paste a Slack thread into ChatGPT and ask for the status. Which thread, though? This morning's, last week's, the client channel, or the internal channel? You can upload a Notion page to Claude and ask for open questions. Notion pages go stale. Someone updated the Figma file but not the page. The page says "waiting on client feedback," but the client answered in Slack two days ago. You can ask Perplexity to search your Google Drive for homepage decisions. It returns 30 documents, and you still read them to find the current one. The assistant can search and summarize. It does not know your team's source of truth, where decisions get written, or which version is current. So each teammate asks the same question and gets a different answer from different uploads. [Chat history is not business memory](/articles/chat-history-is-not-business-memory) explains why a log of conversations cannot serve as that source. ## How a shared folder becomes team memory Keep one shared folder, such as a Git repository or a synced drive, with a root `CLAUDE.md` and one file per project. Decisions, project history, and current status go there. When something changes, you update the folder. Every teammate who opens Claude Code in that folder reads the same record. The files are plain Markdown. The model runs on the provider's servers, so any text Claude reads goes to the provider during a session. ### Project context ```markdown ## Homepage redesign (client: Acme Corp) status:: in development (dev: Austin; design: Portugal) launch:: 2026-02-15 phase:: developer builds from approved mockup v4 ### Original request (2026-01-05) Client wants the homepage to focus on product features, not team bios. The current site is too "about us" heavy. Goal: 30% more demo requests. ### Design iterations - v1 (2026-01-08): three-column feature grid. Client: too busy. - v2 (2026-01-12): single-column scroll. Client: too minimal. - v3 (2026-01-18): two columns with hero video. Video loaded too slowly. - v4 (2026-01-22): two columns, static hero image, feature cards. APPROVED. ### Dev notes - Use the current component library; do not rebuild cards. - Hero image: /assets/homepage-hero-2026.jpg - CTA: "Book a Demo" links to the client's Calendly (link in _contacts.md) - Mobile: stack columns; hero image at 60% width ``` The developer in Austin asks what to build. Claude reads this file and answers: the Acme homepage, from mockup v4, with the current component library. The hero image is in the assets folder, and the CTA links to Calendly. The developer skips the thread search and the Figma comment hunt. ### Team availability ```markdown | Role | Time zone (IANA) | Local hours | Austin time (January) | |-----------|------------------|-------------|-----------------------| | PM | America/Chicago | 9am to 5pm | 9am to 5pm | | Designer | Europe/Lisbon | 9am to 6pm | 3am to noon | | Developer | America/Chicago | 10am to 6pm | 10am to 6pm | | Content | Asia/Manila | 8am to 5pm | 6pm to 3am | ``` The PM needs a call with the designer. Claude reports the designer's hours as 3 a.m. to noon Austin time and suggests 10 a.m. Austin, which is 4 p.m. in Lisbon. The developer has a question for the content writer and asks whether the writer is online. Claude answers no: the writer's day starts at 6 p.m. Austin time, so leave an async message. Store time zones by name, not by fixed offset. The United States and Europe change clocks on different dates, and the Philippines does not use daylight saving time. The overlap windows shift for a few weeks each spring and fall. Claude can compute them from the zone names on the day you ask. ### Decision log ```markdown ## Decisions (last 30 days) ### 2026-01-24: Switched from Webflow to Framer why:: Client wants to edit content without a developer. At decision time, the Framer plan with CMS cost less than the Webflow plan with CMS. impact:: Dev timeline extended 3 days to rebuild in Framer. decided_by:: PM, with client approval by email ### 2026-01-18: No custom animations on the homepage why:: Designer proposed scroll-triggered animations. Client liked them but worried about load time. Test: animations added 800 ms. decision:: Static design only. Animations archived for later use. decided_by:: team consensus, 2026-01-18 Zoom call ### 2026-01-10: Blog stays on a WordPress subdomain why:: Client has 200+ posts on WordPress. Migration would add cost and take two weeks. Client declined the cost. decision:: Homepage on Framer (www). Blog stays on WordPress (blog). decided_by:: PM and client ``` On the next project, the designer asks about the team's position on animations. Claude answers from the log: the team decided against them on the last project because of load time, and the work is archived. [Meeting notes that preserve decisions](/articles/ai-memory-meeting-notes-decisions) shows how to move a decision from a call transcript into a log like this one. ## Four remote team patterns **A 7-person SaaS team in three time zones.** The PM works from San Francisco and the designer from Austin. Two developers sit in Poland, the marketer in New York, and two support reps in Manila. The folder holds sprint goals, feature specs, bug tracker links, and support macros. The PM asks what shipped overnight, and Claude summarizes the commits from Poland. Support asks how a new feature works and gets the spec. **A 4-person fully remote agency.** The PM is in Denver, the designer is in Barcelona, and two developers are in Toronto. The folder holds client folders, timelines, and contract details. The designer updates the project file at the end of the European day. The Toronto developers ask for the latest status and get the update without a wait. **A 12-person consultancy on four continents.** The folder holds client histories, deliverable templates, and knowledge base articles. A consultant in Singapore asks what the firm delivered for a client last quarter and gets the summary. A consultant in London asks where the strategy proposal template lives and gets the path. **A 5-person marketing team in the US and Europe.** The CMO is in Boston and the content lead in London. The designer is in Berlin, and two social managers are in Los Angeles. The folder holds the content calendar, brand rules, campaign briefs, and performance data. The London lead publishes a post at 5 p.m. UK time and updates the calendar. The Los Angeles team asks for this week's blog topic and gets the title and link. ## Before and after the shared record Before: the designer finishes a mockup and posts "Homepage v4 ready for dev." The developer reads it eight hours later and does not know what changed from v3. They search Slack, find old client feedback, and piece together the story. Halfway through the build, they learn about a platform switch that was decided in a Zoom recording they did not watch. They rebuild. After: the designer finishes the mockup and updates the project file: "v4 approved, ready for dev." The developer asks Claude for the current Acme homepage status. Claude reads the file: v4 approved, build in Framer, current components, hero image in assets, CTA to Calendly. The developer starts on the right platform. ## What goes in the remote team folder | Area | Contents | |---|---| | Team directory | Roles, time zones, work hours, overlap windows for calls | | Project status | Current phase, blockers and causes, next steps and owners | | Decision history | What was decided, why, and by whom | | Client communication | Latest feedback, open questions, approval status | | Async updates | What shipped overnight, what waits for review, what needs input | Update the folder as work happens, not at the end of the day or in a weekly meeting. Update the file when a mockup is approved, when a feature ships, and when a client sends feedback. After three months, the folder is a complete project history. This is not extra work. You already type "here is what happened" messages for teammates who were offline. The folder puts those messages where the next reader will find them. [Test the decision trail](/articles/best-ai-team-conversation-memory) before you trust any tool with team memory. ## Set up the folder in one afternoon 1. Create the shared folder and a root `CLAUDE.md` that names the project files and the decision log. 2. Add one project file per active project with status, original request, and iterations. 3. Add the team directory with IANA time zone names. 4. Start the decision log with the last month's decisions. 5. Ask each teammate to open Claude Code in the folder and ask for the status of one project. When someone new joins, they ask Claude what the team works on and get a summary with sources. They orient from the written record instead of the Slack archive. ## Approval and stopping boundary The assistant answers status questions, drafts updates, and proposes decision log entries. The project owner approves any change to a decision or a status. The assistant does not message clients, merge code, or change project tools. When the folder conflicts with a signed client approval or the live code, that source controls, and the owner corrects the folder. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```