Document Audit Worksheet

Your firm's knowledge base is scattered across SharePoint, Google Drive, individual desktops, and that one partner's laptop from 2019. Before you can build an effective Q&A system, you need to know what you have, where it lives, and which version is actually current.

This worksheet gives you a systematic method to catalog every document, identify version chaos, and prepare your materials for indexing. Use it before you touch any AI tool.

Professional services firms typically maintain five categories of reference materials:

Client-Facing Documents

• Engagement letters, proposal templates, SOW frameworks
• Deliverable templates (audit reports, tax returns, consulting decks)
• Client communication templates (status updates, change orders)

Internal Process Documents

• Onboarding checklists, training manuals, desk procedures
• Quality control checklists, peer review guidelines
• Billing procedures, time entry guides

Technical Reference Materials

• Tax code summaries, accounting standards updates
• Legal research memos, case law digests
• Industry-specific compliance guides

Administrative Templates

• HR forms, PTO requests, expense reports
• IT setup guides, software access procedures
• Vendor contracts, NDA templates

Historical Knowledge

• Past project summaries, lessons learned documents
• Client history files, relationship notes
• Archived methodology guides

Start by identifying which categories matter most for your Q&A use case. If you're building a client delivery assistant, focus on categories 1-3. If you're building an internal operations tool, prioritize categories 2, 4, and 5.

Phase 1: Document Inventory (Week 1)

Create a spreadsheet with these exact columns:

| File Name | File Type | Current Location | Owner | Last Modified | File Size | Status | Priority | |-----------|-----------|------------------|-------|---------------|-----------|--------|----------|

File Name: Use the exact filename as it appears in your system. Include the extension.

File Type: Specify format (DOCX, PDF, XLSX, PPTX, Google Doc, Notion page). This matters because PDFs require OCR, Google Docs need export, and Notion has API limitations.

Current Location: Full path. Not "SharePoint" but "SharePoint > Client Services > Engagement Letters > 2024". Include URLs for cloud documents.

Owner: The person who created it or currently maintains it. Get their email address. You'll need to verify accuracy later.

Last Modified: Exact date from file properties. Flag anything older than 18 months for immediate review.

File Size: In MB. Files over 50MB may need chunking before indexing. Files under 1KB are probably empty or corrupted.

Status: Use these four labels only:

• CURRENT: Actively used, confirmed accurate
• REVIEW: Needs subject matter expert verification
• DUPLICATE: Multiple versions exist
• ARCHIVE: Outdated but keep for reference

Priority: Rate 1-3 based on usage frequency and business impact. Priority 1 documents get audited first.

Assign one person per department to complete their section within five business days. Set a hard deadline.

Phase 2: Version Control Assessment (Week 2)

For every document marked DUPLICATE or REVIEW, complete this analysis:

Version Identification

• List all versions you found (include filenames and locations)
• Note the date stamp on each version
• Identify who last edited each version
• Check email for any version sent as attachments

Content Comparison

• Open the two most recent versions side-by-side
• Document substantive differences (not just formatting)
• Identify which version contains the most current information
• Note any conflicting information between versions

Consolidation Decision

• Mark one version as MASTER
• Archive all other versions to a "Superseded" folder
• Update the master filename with version number and date: "Engagement_Letter_Template_v3.2_2024-01-15.docx"
• Add a header or footer to the master noting "Current Version as of [DATE]"

If you cannot determine which version is correct, schedule a 15-minute call with the document owner. Do not guess.

Phase 3: Naming and Organization (Week 3)

Implement this exact naming convention across all documents:

Format: [Category]_[Document-Type]_[Specific-Name]_v[X.Y]_[YYYY-MM-DD]

Examples:

• Client_Engagement-Letter_Standard-Audit_v2.1_2024-03-10.docx
• Internal_Onboarding-Checklist_Tax-Associate_v1.0_2024-01-05.pdf
• Technical_Tax-Memo_Section-199A-Deduction_v3.0_2023-11-20.docx

Version Numbering Rules:

• Major changes (new sections, policy updates): Increment first number (v2.0 → v3.0)
• Minor edits (typo fixes, formatting): Increment second number (v2.1 → v2.2)
• Always start new documents at v1.0

Folder Structure: Create this hierarchy in your document management system:

Knowledge Base/
├── Client-Facing/
│   ├── Engagement-Letters/
│   ├── Proposals/
│   └── Deliverables/
├── Internal-Process/
│   ├── Onboarding/
│   ├── Quality-Control/
│   └── Billing/
├── Technical-Reference/
│   ├── Tax/
│   ├── Audit/
│   └── Advisory/
├── Administrative/
│   ├── HR/
│   └── IT/
└── Archive/
    └── Superseded/

Move every document into the appropriate folder. Delete nothing during this phase.

Phase 4: Metadata Tagging (Week 4)

Add these metadata fields to every Priority 1 and Priority 2 document:

Document Properties (use your system's built-in metadata):

• Title: Human-readable name
• Author: Original creator
• Subject: One-sentence description
• Keywords: 3-5 searchable terms
• Comments: "Last reviewed by [NAME] on [DATE]"

Custom Fields (if your system supports them):

• Practice Area: Tax, Audit, Advisory, HR, IT
• Client Type: Public, Private, Nonprofit, Government
• Review Frequency: Monthly, Quarterly, Annually, As-Needed
• Next Review Date: Specific date
• Approval Status: Draft, Pending Review, Approved

For Google Drive, use the description field. For SharePoint, use managed metadata columns. For Dropbox, use tags.

This metadata becomes searchable context when you index documents for Q&A.

Download the Excel template here: [LINK TO TEMPLATE]

The template includes:

• Pre-formatted inventory spreadsheet with data validation
• Version comparison checklist
• Naming convention reference card
• Folder structure template
• Metadata tagging guide

Fill it out completely before you start any AI implementation work.

Set these recurring calendar events:

Monthly (First Monday):

• Review all documents modified in the past 30 days
• Verify version numbers were updated correctly
• Check for new duplicates

Quarterly (First week of Jan/Apr/Jul/Oct):

• Audit all Priority 1 documents for accuracy
• Update "Next Review Date" metadata
• Archive documents marked for retirement

Annually (January):

• Complete full inventory refresh
• Update folder structure if needed
• Revise naming conventions based on usage patterns

Assign a Knowledge Manager to own this process. Make it part of their job description, not an extra task.

Stop and fix these issues before proceeding with any Q&A implementation:

• More than 20% of documents lack a clear owner
• More than 30% of documents are older than 24 months
• You find five or more versions of the same critical document
• File naming is completely inconsistent across departments
• No one can explain the current folder structure

If you see these patterns, your knowledge base needs structural repair before AI can help. A Q&A system trained on chaos will produce chaotic answers.

Complete this audit first. Then you can index with confidence.