RW InstituteRW Institute

Start here

One front door to every asset in the Applied AI Labs for Nonprofits curriculum: orientation and setup, the seven labs with their facilitator run sheets and participant kits, the mock data packs, and the cross-lab Edge Cards. Search or filter to find what you need; each lab material offers a quick HTML review view and the original source file.

Seven labs over seven weeks · Updated October 6, 2026

For the RW Institute and Wells Fargo PCI teams. This hub links facilitator run sheets and answer keys. Do not forward it to participants or to nominated organizations. Send them the invitation page, or a direct link to the one kit they need.

How it runs

Every lab runs Brief, build with Check-ins, Debrief. Everyone works in Claude's desktop app in Cowork from their own workspace folder, with Claude in the browser when IT blocks the install.

Safe data

Lab 1 sets what never goes into any AI tool. Lab 4 runs the full placeholder round trip on each organization's own spreadsheet, with the placeholder key kept outside the folder.

Rooms of about eight

Colleagues from four organizations and one facilitator per breakout room, the same room all seven weeks. Everyone works solo with their own Claude, on their own material, and the facilitator brings the room together at set moments.

Situational analysis · Master view

Where things stand

Full rolling agenda & decision trail →

Nominations closed Monday, September 14: 32 submissions covering 41 organizations as of Sep 16. PCI ranked the pool and sent the initial invitations to 25 organizations on Tuesday, September 15, with 16 on the waitlist; replies show on the dashboard's responses view. Seat confirmations closed Friday, September 18 and the cohorts were confirmed Thursday, September 24: 25 nonprofits hold seats across the two cohorts. Lab 1 ran Monday, September 28 for Cohort A and opens Friday, October 2 for Cohort B. Each participant sets up and owns an individual Claude Pro account, and Wells Fargo covers the cost for six months. November 16 is the program wrap, and a separate leadership showcase for a few standout projects follows after Thanksgiving, likely December or January. The Monday cohort's Lab 3 stays on Monday, October 12. RW Institute sends the cohort calendar invites. The program site, nomination tool, review dashboard, participant hub and intake form are all live. Recruitment is by PCI nomination, and all funded cohort seats go to nonprofit organizations.

Sep 9First rolling review Sep 14Nominations closed Sep 16Check-in held: invitations out Sep 17Initial-reply deadline Sep 18Confirmations close Sep 24Cohorts confirmed Sep 28Lab 1, Cohort A Oct 2Lab 1, Cohort B Nov 16Program concludes

Recent changes

  • Oct 5: the Monday cohort's Lab 2 ran. Participants connected their Claude to the Lab Guide so Claude could walk them through the lab at their own pace; where the direct connection failed, often because of security settings on their computers, they added a downloaded copy to their AI Labs project, which works but will not pick up later updates, so the team is working on a connection that works for everyone. Browser users keep their lab files inside the Claude project, and the free Claude plan cannot run the labs. Lab 3 stays on Monday, October 12; anyone who cannot join catches up from the post-session resources. Check-ins with the Wells Fargo team are on the calendar for Wednesdays October 14, 21 and 28 and November 4.
  • Oct 2: the Friday cohort's Lab 1 ran. Most rooms got through setup and into the interview, and some went further. The Lab Guide, which lets a participant's Claude answer questions about the program, was shown; its setup steps go out in the follow-up. From Lab 2, breakout rooms are grouped by how far along people are with each organization's two participants together, each lab opens with a quick homework check, and sessions start right at the top of the hour. Friday Lab 2 is October 9.
  • Oct 1: the official calendar invites for every lab session are on the team's calendars, through November 9 for the Monday cohort and November 13 for the Friday cohort, replacing the earlier calendar holds. The Wells Fargo team is on the invites and sees the follow-up after each session.
  • Sept 30: the Monday cohort received a Lab 1 recap and a Lab 2 prep email. Setup was the hardest part of Lab 1 for most people, mostly connecting a folder in Cowork, which now has to go through a Project; the team will make sure everyone is set up before Lab 2, and plans to use the Lab 1 recordings and facilitator notes to update every lab still to come.
  • Sept 28: the Monday cohort's Lab 1 ran. The main session was recorded, and breakout rooms are recorded unless someone in the room asks in the chat not to be. Lab 2 is next Monday, October 5, same time, same group; the Friday cohort's Lab 1 is October 2.
  • Sept 27: 16 participants from 12 organizations have sent their intake. The participant page was tightened after a walk-through: Start here is the one place for setup, search matches every word, and the intake ends with an optional question about setup or access. Lab 1 makes room for anyone who has not finished setup (six Monday-cohort participants had not started as of the intakes): they finish in their breakout room, with a catch-up step, a facilitator floating for setup problems and an optional 15-minute stay-after. An organization that works in Copilot joins on Claude with the practice files only.
  • Sept 27: the Monday cohort's Lab 3 stays on Monday, October 12, with no poll.
  • Sept 25: the program is now Applied AI Labs for Nonprofits. Each participant sets up and owns an individual Claude Pro account, Wells Fargo covers the cost for six months, and no account invitation goes out. 25 nonprofits hold seats across the two cohorts. October 12 goes to a poll of the Monday cohort. Every lab gets a teaching layer that shows how each prompt works and where else it fits (Labs 3 to 7 as they are rebuilt, Labs 1 and 2 after), and Lab 5's deck is started with Claude in the session.
  • Sept 24: homework Started and Done buttons went live on the lab pages, with a participation view on the review dashboard that shows totals only.
  • Sept 23 check-in: showcase event approach confirmed (Lab 7 stays the completed-workflow demo; a separate session follows, likely December or January, not necessarily the full group); nominators now CC'd on welcome emails alongside the primary org contact.
  • Sept 21: cohort sessions confirmed on Zoom rather than Teams so every nonprofit can join easily; RW Institute manages the session invites and follow-ups through a Zoom event page, with Wells Fargo included for visibility.
  • Sept 16 check-in: invitations confirmed out with replies due Sept 17; November 16 confirmed as the program wrap with a separate showcase event to follow; RW Institute confirmed as the calendar-invite sender; nominator thank-you emails made standard; Lab 1's facilitator run-of-show reworked so Copilot is no longer the opening frame.
  • Sept 14: nominations closed; the pool number above is live from the dashboard. The rolling agenda and every page were refreshed for the Sept 16 check-in, and the curriculum materials now reflect the all-nonprofit cohorts.
  • Sept 8: the participant intake and pre-flight are a web form on the participant hub; the dashboard adds RW's after-a-yes checklist, a city-by-city view of nominations, and the intake list.
  • Pipeline tracker added to the review dashboard: invited, reply, seat form, cohort day and welcome per organization, with the two email templates beside it. Wells Fargo sends and records; RW reads the same board.
  • Leadership cleared the nomination call in late August; it is out with PCI members and nominations are arriving.
  • Invitation route settled Sept 2: PCI emails the organization directly, nominator copied, framed as an opportunity to sign up with a short window and an easy decline.
  • Review cadence set: first rolling review Sept 9, next batch at the Sept 16 check-in, 5 to 10 seats held until after Sept 14.
  • Facilitator contingency confirmed for the full seven-week run.
  • Sept 9: the review dashboard now updates itself when an organization submits its seat form, and a "Not this time" decline button lets an organization free its seat right away.
  • Sept 10: PCI is giving nominators a short extension past the Sept 9 review before sending the first round of invitations, targeting all initial invitations out by Sept 16.

Open next steps

  • PCIRecord each reply on the dashboard; set the cohort day and send the you're-in note. as replies land
  • RW InstituteRewrite the placeholder calendar-invite language, then send the calendar series to each confirmed pair and tell each participant how the Claude Pro cost, covered by Wells Fargo for six months, reaches them. within 2 days of a yes
  • RW + PCIPlan the storytelling, comms & data approach. working session to schedule
  • RW + PCIFinalize the showcase event for leadership and nominators: exact date and length, likely December or January; may not include every participant. working session to schedule
All surfaces Check-in / rolling agenda Timeline Nomination tool Nominator kit Seat confirmation Review dashboard Lab reflections Ecosystem map Participant hub

Orientation & setup

Read and send before Lab 1. The path in is nomination: each PCI member put forward one or two partner organizations by Sept 14 (now closed; late nominations join the reserve list), then every nominated organization receives a personal invitation and confirms its two seats. 25 nonprofits hold seats across the two cohorts. The Curriculum Map is the full design.

Step 1 · PCI Nomination ToolFor the PCI team: the rubric and nomination form for putting forward one or two partner organizations. Score the fit against a short qualifier and five questions, then submit the nomination, about ten minutes end to end. Nominations closed Sept 14; late nominations join the reserve list. PCI teamHTML Nominator KitFor the PCI team: how nominating works, the nomination link, and ready-to-send email templates you can copy, one to rally your colleagues and one to forward to a partner. Opens in the browser, nothing to download. PCI teamHTML Step 2 · Invitation & Seat ConfirmationGoes only to nominated organizations: what the program asks, five reasons to take a seat, a readiness quiz, and the form where an organization confirms its two seats. Submissions are now live. Once a nominated organization confirms its seats, the data goes to the Supabase backend. Ready to send to nominated organizations after PCI review. ParticipantLiveHTML Admin · Nomination DashboardFor the PCI working group: a visual dashboard showing all nominations side by side with readiness scores, organization details, and nominator rationale. Passcode-gated. Refreshes on each page load. PCI + RWLiveHTML Admin · Lab ReflectionsFor the PCI working group and RW Institute: one page for every lab session, showing how far each room got, what stuck, what we changed and what we saw. Group and room level only, no names. Passcode-gated. Each session fills in after its lab. PCI + RWLiveHTML Participant HubThe stripped-down hub for participating organizations: program overview, Claude setup, all seven participant kits, mock data packs, and Edge Cards. Share this link with confirmed organizations. ParticipantLiveHTML Curriculum MapThe full program design: all seven labs and how each one runs (Brief, build with Check-ins, Debrief), the workspace folder, the rooms of two organizations, the three homework levels, and where each scope topic went. EveryoneHTML Curriculum Map, Word versionWord download. Editable copy of the curriculum map for sharing or marking up with the Wells Fargo team. FacilitatorDOCX Anonymization OptionsWord download. How identifying details stay out of AI tools: the green, yellow and red sort, three options, and the own-sheet rule for Lab 4. One decision is open with PCI: a yes on Lab 4 using each organization's own spreadsheet. PCI teamDecision openDOCX Intake & Pre-FlightWord download, superseded September 8 by the web form at /intake, which is what participants use. Kept as the master copy of the question set. FacilitatorDOCX Claude Setup GuideWord download. Walks every participant through installing the Claude desktop app and proving the file workflow end to end, or setting up Claude in the browser where IT won't allow the install. Send the day the cohort is confirmed, and flag that a managed computer may need IT approval first. ParticipantDOCX

The seven labs

Each lab has a facilitator run sheet and a participant kit. Labs 1 to 5 each come with practice files, which each person chooses as an equal option to their own material, and nobody has to explain the choice; Labs 6 and 7 reuse earlier practice files. Answer keys and the capture sheet are facilitator only. The facilitator card holds the moves that stay the same every week, and the reflection protocol holds the pulse, room round and Debrief wording. The communications templates, such as the weekly emails and the breakout guide, live in the repo's 06-Communications folder and are not deployed.

1
First safe win
Each person sets up their own AI-Labs folder, has Claude interview them for their own AGENTS.md, sets the model-training setting, and gets one small piece of real writing checked and ready to send, from their own notes or the practice email thread.
The Brief's surprise: Claude is more capable than you think and less trustworthy than it sounds. In step 8, each person has Claude read their AGENTS.md as an outsider would, then the room hears one question from each. Bring to Lab 2: the mission, two writing samples and an outcomes summary if there is one (or a voice note transcript, or the practice pack), a live RFP if there is one, and the workflow's name with its old-way time from a stopwatch.
AI Mindset & Foundations · Governance & Risk
2
Writing and the org brain
Each person builds their org brain as plain files (mission, two writing samples, outcomes and voice notes, plus "How we sound" in AGENTS.md) from their organization's public documents or the practice pack, then writes one real piece in that voice or a compliance matrix for a live RFP.
The Brief tests "it can't sound like us": two thank-you notes from the same ask, one from a bare chat and one from a folder, and the room guesses which came from the folder. In the outside read, a fresh Claude session lists the lines in each draft that don't sound like the voice notes, and each person reads aloud the line that sounds most like them. Bring to Lab 3: one messy real reporting input, plus the name of the report and who reads it, or the practice mess pack.
Quality & Accuracy
3
Board-ready reporting and the second chair
Each person takes one report section, from their own reporting input or the practice mess pack, through draft, second chair and revision, and saves the second chair as a recipe, Recipes/second-chair.md, with a rule from a real catch.
The Brief tests "if it reads well, it's right" with a vote on a draft made from the mess pack, re-tested on the current default model before the lab. In the outside read, each person runs a prompt in a fresh session that reads their revision as a different skeptic and quotes what their second chair never asks, then reads the most important question aloud in the room round. Bring to Lab 4: the recurring spreadsheet exported as a .csv with red and notes columns deleted, plus one total from the organization's own system, or the practice sheet.
Reporting & Narrative Building
4
Data, clean and extract
Each person takes a spreadsheet, their own recurring one or the practice sheet, through the round trip: organization names swapped for ORG-01 placeholders by hand, cleaned by Claude 10 rows first with a change log, reconciled by hand, the names put back outside AI-Labs, and the brief saved as a cleanup recipe.
Red and notes columns are deleted by hand, then each person checks their own column headings (the top row only) with Claude before anything is saved. The placeholder key never goes near Claude or into AI-Labs. In the outside read, each person's own cleanup recipe is read in a fresh session and each person reads one rule aloud, never a key. Bring to Lab 5: the meeting the next deck is for and its numbers with placeholders still in, or the practice set.
Metrics & Data Review · Governance & Risk
5
Numbers to narrative to deck
Each person writes a context file, then checked insights, a narrative checked by the second chair as the meeting's skeptic, and a slide outline for a real upcoming meeting, on their own numbers or the practice set. The .pptx is started with Claude in the session and finished at home if needed.
The Brief tests "start in the slide tool" with a deck made from the raw numbers. Near the end, Claude plays the meeting's skeptic on one of each person's slides, and the room hears each question aloud. Bring to Lab 6: a draft about to ship and the files it came from, and a research brief in the four parts, saved as Working/research-brief.md.
Metrics + Reporting, combined
6
Skills, research and the wider toolbox
Each person saves their second chair as a skill, Skills/second-chair/SKILL.md, and runs it on a real draft, then turns a Claude Research report on their own question into a one-page summary of claims checked at the source.
The Brief tests "research gives answers" with a pre-run report: a confident claim, its source's date, and whose voices the sources leave out. A five-minute tool map follows the demo. In the outside read, a fresh session reads each person's skill and draft as a funder they've never applied to and names one question the skill never asks, and each person reads it aloud. Bring to Lab 7: the workflow's pieces gathered in Workflows, and the ship log with its old-way and new-way minutes.
Workflow Design · Governance applied
7
Build session and 90-day roadmap
Each person writes their workflow down so a colleague could run it without them, with the tool for every step and old-way and new-way minutes, and a 90-day plan with month 1 filled in. No new teaching.
The Brief reads back participants' Lab 1 words. The build and the showcase run in the usual breakout rooms of about eight, each with a note-taking facilitator. In the showcase, each person has 90 seconds on what the workflow does, what it replaced, their old-way and new-way minutes, what surprised them and what it can't do, then one question from someone in another organization. The 90-day plan takes the place of the homework levels. A separate leadership showcase follows after Thanksgiving, in December or January.
Workflow Design · Build Session & Roadmap

Cross-lab edges

The working habits that run across every lab. Four are reinforced inside the labs; four are genuine extras for openers and asides.

The Working Edges · Edge CardsTen habits, five the labs build and five extras, each with a copyable prompt and a one-line reason it earns its time. The quick reference participants keep, and the facilitator's source for special-section asides. EveryoneHTML

No assets match that search or filter.

Ecosystem Map