PRIVATE WORKING SITE · Our House Senior Living × SAVANT-AI · Wednesday team frame
AI Mastery Week · Wednesday · The Team Frame

What each person sees
becomes what the team can share.

The advance conversations found practical work, not abstract enthusiasm. These are the highest-value starting points for turning individual capability into repeatable team patterns—while keeping sensitive work inside the right enterprise boundary.

The questionWhat repeats?

Find the work that consumes time across people, houses, or reporting cycles.

The design ruleProve one slice.

Start from an export, template, or known-good example before building a system.

The team outcomeShare the pattern.

Leave with a reusable workflow, a named owner, and a boundary for what still needs review.

The Wednesday use-case wall

Twelve people.
Twelve starting points.

Each card holds the strongest practical use cases from the deep dives. “Best place” means where the work should be developed first—not a final platform decision. Sensitive lanes remain export-first, human-reviewed, and subject to Our House IT, privacy, compliance, and BAA confirmation.

Explore nowVerify firstEnterprise approval required
Angie GrahamExecutive

Turn capability into direction

  • Set shared AI priorities and standards.
  • Shape the 30/60/90-day leadership path.
  • Decide what the monthly team conversation should keep learning.
Eric KingenFinance & AR

Reconcile exported finance files

  • Find rent-roster and invoice mismatches.
  • Compare care-level and billing information.
  • Review Sage Intacct exports and vendor usage.
Lori NardinCompliance

Standardize self-report narratives

  • Clean and standardize self-report narratives.
  • Track overdue investigations and draft reminders.
  • Support Plans of Correction and structured investigation interviews.
Stacy SisClinical

Support safe clinical operations

  • Prepare infection-control and audit support.
  • Organize care-process questions and follow-up.
  • Help staff learn safe, non-PHI uses of AI.
Amy StaadsRegional operations

Make director development visible

  • Standardize director training across regionals.
  • Track a 12-week leadership-progress project.
  • Turn recurring audits into a management view.
Nikki McGinnessAdministration

Reduce repeat coordination

  • Keep job postings consistent across houses.
  • Make the bus-trip calendar easier to maintain.
  • Consolidate occupancy reports into concise updates.
Mike ArchibaldEnablement & marketing

Make good work teachable

  • Coach colleagues through Claude and Copilot.
  • Turn prompt patterns into portable Markdown instructions.
  • Build bounded social and marketing reporting.
Haley SchoolSales & experience

Give the team a better tour system

  • Build a care-level estimator.
  • Standardize sales meetings and room checklists.
  • Practice tours and shape a future website assistant.
Jenna RepkaMedication & revenue

Turn MedCart review into a queue

  • Compare approved MedCart exports.
  • Flag missing documentation and care hours.
  • Prepare follow-up emails and an Excel review queue.
Tish CarlsonRegional operations

See who owes the next response

  • Track responses to required approvals.
  • Prepare follow-ups and regional exception summaries.
  • Turn walkthroughs and audits into teachable SOPs.
Lauren MethenyOccupancy & regional ops

Make occupancy reporting less manual

  • Summarize occupancy across houses.
  • Support regional operations and follow-up.
  • Keep source checks visible in recurring reports.
Dana PhilbrickPayroll

Build the 28-house payroll run

  • Filter ADP exports into house summaries.
  • Preserve variable templates, formulas, and totals.
  • Track overtime, formulas, and mailbox responses.
Where to work

Use the place
that can see the work.

Claude Code is not the default answer for these leaders. It becomes relevant only if Our House later designates a technical owner for backend integration, permissions, or a durable internal service around a proven workflow.

01

Claude chat / project

If you are thinking, drafting, or learning, go to chat or a project where the context can stay with you and your team.

02

Claude add-in for Excel

If you are already in Excel, stay there. The workbook, formulas, tabs, and templates are in the room with you.

03

Claude Desktop / Cowork

When the steps work, go here for enterprise files, bounded multi-step workflows, repeatability, and scheduled work.

04

Claude Code

Keep this place with IT or the builders for integrations, validation scripts, backend services, and governed automation.

GREEN · Prove now

Public information, generic training, de-identified examples, templates, and administrative work without sensitive data.

AMBER · Verify first

Employee data, internal reports, finance exports, SharePoint, mailboxes, connectors, and shared assistants.

RED · Hold until approved

PHI, resident identifiers, clinical records, medication data, autonomous action, or automatic external communication.

The Wednesday working session

Compare the work.
Choose the pattern.

The point is not to make twelve unrelated assistants. It is to identify a few patterns that can travel safely: export → inspect → reconcile; context → draft → review; and repeatable method → shared skill.

01

Show the source

Bring the real template, export, checklist, or example that defines “good.”

02

Compare the pattern

Which other role has the same shape of work, even if the content is different?

03

Name the owner

Who maintains the instruction, checks the output, and decides when it changes?

04

Carry one decision

Choose one safe team experiment for Friday’s governance and pilot conversation.

Wednesday’s closing question

“Which useful pattern can travel across Our House—and what must stay role-specific, reviewed, or protected?”