Custom AI Assistant: Build Your Personal Office Knowledge Base with Claude Projects

What This Builds

Instead of hunting through SharePoint, digging through old emails, or walking over to ask a colleague "what's the process for that?", you'll have a private AI assistant that already knows your office's SOPs, policies, vendor contacts, and common processes. You ask it questions in plain language and it answers in seconds — with context specific to your organization, not generic advice.

Prerequisites

• Claude Pro subscription ($20/month at claude.ai)
• 1-2 hours to load your documents initially
• Permission to paste internal documents into a work AI tool (check with your manager if unsure)

The Concept

A Claude Project is like giving a new, very capable assistant a filing cabinet full of your office's documents and saying "read all of this so I can ask you questions." You load the Project once with your SOPs, policies, org charts, and vendor info. Every future conversation starts from that shared knowledge — so you never have to re-explain context, and every answer is specific to your organization, not a generic internet answer.

The analogy: it's like having a junior admin who has read every document in the department and can answer your questions instantly, 24 hours a day.

Build It Step by Step

Part 1: Create the Claude Project

1. Log into claude.ai with your Pro account
2. In the left sidebar, click "+ New project"
3. Name it something clear: "Office Admin Knowledge Base" or "[Your Name] Admin Assistant"
4. You'll see a Project page with: a "Project instructions" area, a "Files" area, and a chat window

What you should see: A dedicated project space separate from your regular Claude conversations. This space persists — documents you add here are available in every future conversation within the project.

Part 2: Write the Project Instructions

This is the most important step. In the "Project instructions" box, write a description of who you are and what this project should do:

You are an administrative assistant's reference tool for [Your Organization Name / Your Department].

You have been loaded with documents including:
- Office SOPs and procedures
- Vendor contact information
- Org charts and team structures
- Policies (expense, travel, purchasing, PTO)

When I ask you questions:
1. Answer based on the documents I've loaded — don't guess or use general internet knowledge if the answer should be in our documents
2. If the answer isn't in the documents, say so clearly and suggest where I might find it
3. Keep answers concise and practical — I'm usually looking for a quick reference, not an explanation
4. If I ask you to help me draft something, use the context from our documents (vendor names, process steps, contacts) to make it specific to our organization

My role: General Administrative Assistant
My common tasks: scheduling, expense reports, travel booking, meeting coordination, document management

Click "Save."

Part 3: Load Your Documents

In the "Files" section of the Project, click "Add files" and upload your key documents. Good candidates:

Highest priority:

• Office SOPs (expense submission, PO process, onboarding steps, meeting room booking)
• Vendor contact lists (supplier names, account reps, phone/email)
• Org chart or team directory (who is who, what they own)

Medium priority:

• Travel policy document
• Expense policy (reimbursement limits, approval thresholds)
• Frequently asked questions you've been asked
• Department-specific process guides

Format notes:

• PDFs and Word documents upload directly (click and drag)
• For spreadsheets (vendor lists in Excel), export as PDF or copy-paste the relevant table as text
• Keep each file under 10MB; very large files (200+ pages) should be split

Upload 5-10 documents to start. You can always add more later.

What you should see: Each uploaded document appears as a tile in the Files section with its name.

Part 4: Test and Refine

In the project chat window, ask questions you would normally look up:

• "What's our process for submitting a PO over $5,000?"
• "Who's the account rep at [Vendor Name]?"
• "What's the mileage reimbursement rate?"
• "What does [Person's Name] own in the department?"

Review the answers. If an answer is wrong or outdated, update the source document in your Files and re-upload. If an answer is missing, either add the relevant document or add the information directly to the Project instructions as a note.

Real Example: A Week with Your AI Knowledge Base

Setup: You loaded 8 documents: expense policy, vendor list, org chart, onboarding SOP, travel policy, PO process, meeting room guide, and your department's FAQ doc.

Monday: New colleague asks you "what's the process for getting a visitor badge?" You ask your Claude Project → it pulls from the onboarding SOP → gives the step-by-step in 5 seconds. You copy and send.

Wednesday: Manager asks you to process an urgent PO for $8,200. You ask: "Our PO process for purchases over $5k — who needs to approve and in what order?" Claude Project answers with the exact approval chain from your SOP. You follow the steps correctly without reading the whole 12-page document.

Friday: You're onboarding a new hire. You ask Claude Project: "Give me a first-week schedule for a new marketing coordinator joining our department." It generates a schedule using the onboarding SOP, names the right IT contacts from your vendor list, and references the correct badge access request form from your FAQ.

Time saved: Estimated 30-45 minutes per week in document lookup and "where is that process again?" cycles.

Input: Your 8 documents, loaded once. Output: Instant, organization-specific answers available every time.

What to Do When It Breaks

• "I don't have information about that in the provided documents" → This is correct behavior. Add the relevant document to your Project Files. Don't try to force an answer from incomplete information.
• The answer is outdated (e.g., old vendor contact) → Update the source document → delete the old version from Files → upload the new version. Claude Project uses the current Files content.
• The answer is wrong → Review the source document — the error may be in your SOP, not in Claude. If the SOP is correct and Claude's answer is wrong, add a corrective note directly in Project Instructions: "Note: The PO approval threshold changed to $3,000 as of January 2026."
• It's mixing up two similar processes → Give the documents clearer names (rename before uploading) and add a brief note in Project Instructions: "The Expense SOP covers reimbursements. The PO SOP covers vendor purchases. These are different processes."

Variations

• Simpler version: Instead of a full Project, keep a OneNote page with your SOPs and paste relevant sections into a regular Claude conversation when needed. Less persistent, but no subscription required.
• Extended version: Add email templates, standard meeting agendas, and past briefing documents to the Project — it becomes a complete "Admin Playbook" that covers both knowledge lookup and drafting support.

What to Do Next

• This week: Build the Project, load 5 key documents, test with 10 questions you'd normally look up
• This month: Add more documents as you identify gaps; share the approach with other admins on your team
• Advanced: Create a second Project specifically for a particular executive's preferences, communication style, and frequently needed materials

Advanced guide for General Administrative Assistant professionals. Claude Projects requires a Claude Pro subscription at $20/month. Subscription pricing may change — check claude.ai for current plans. Do not upload documents containing personally identifiable information (PII), personnel records, or legally privileged content.