One file room. Two doors for the client. AI on watch.

Connect Google Drive once and the engagement gets a working folder plus a synced Engagement Files subtree. Seeding the PBC list auto-creates a Drive folder and a matching in-app folder for every request - clients deliver through the PBC portal or straight into the shared folder, and both land in the same synced file room.

Illustrative engagement: Hudson & Vale CPAs, LLP (Albany, NY) auditing Riverbend Community Services, Inc. (Rochester, NY) - a NYS-funded nonprofit, GAAS audit, FYE December 31, 2025, with a NYS CFRDec25 Examination add-on. Fictional firm, client, and data.

Google Drive

Your Drive is the file room

WorkpaperOS follows folders by identity, not by name - renames and moves inside the sync boundary never break the file room. OneDrive support is on the roadmap; Google Drive is live today.

attestwork.workpaperos.com/settings/cloud-sync

▣

Google Drive

✓ Connected

d.okafor@hudsonvalecpas.com

📁 WorkpaperOS ›

Firm root › Riverbend Community Services - Audit - FYE 2025-12-31 › Engagement Files (synced · last sync 8 minutes ago)

The bot does the heavy lifting

Seeds the standard PBC list for the engagement type - and creates a Google Drive folder plus a matching in-app folder per request, both synced.
Reads every upload with the built-in OCR and Google Document AI engine - scanned PDFs included - then matches it to the right PBC request and tags the audit areas it supports.
Copies received PBC files into the Engagement Files subtree so the firm holds its own copy, then reads that evidence when drafting workpapers.

You stay in control

You share the Drive folder with the client - they can work where they already work.
You approve every message before it reaches the client.
Only the configured Engagement Files subtree syncs - the rest of the engagement working area stays a private team space.

PBC requests

A shared workspace per request - not an email thread

Each request carries its category, audit areas, a per-request folder, a comment thread, and status. Questionnaire-backed requests - like the Entity & Environment questionnaire and per-cycle process walkthroughs - are filled in the portal itself.

attestwork.workpaperos.com/engagements/riverbend-audit-2025/pbc

#	Category	Request	Audit areas	Status	Files
1	Financial Records	Trial balance, general ledger, and draft reporting package	GEN · C	Received	3
2	Financial Records	Prior year audited FS, Form 990, and CFR as filed	P · GEN	Received	4
6	Compliance	Entity and environment questionnaire	P	Questionnaire · 100%	-
7	Compliance	Accounting cycle walkthroughs (Contributions & Grants, Payroll, Cash, Fixed Assets, Functional Allocation...)	F1 · F11 · F12	Partial	2
12	Cash	All bank statements for the audit period and subsequent period	F1	Partial	9
16	Assets	Asset listing, depreciation schedules, and supporting documentation	F5 · F6	Outstanding	0

Guardrail: PBC folders are a shared space with the client. Evidence is tagged from Engagement Files - the bot (or you) copies received PBC files into the Engagement Files subtree, so the firm holds its own copy that the client can never change or update after the fact.

Folders, not flat lists

Files live in folders - in Drive and in the app

Most PBC portals collect a flat pile of individual uploads. AttestWork keeps the folder tree: what you see in Google Drive is what you see in the app. Whole folders can be tagged to procedures - the cash-testing folder is accessible from every cash procedure - files inside folders carry their own tags, and clients upload into the specific folder each request created.

drive.google.com - My Drive › WorkpaperOS › Riverbend ... › Engagement Files

Google Drive

📁 4. Requests12 folders - one per PBC request

📁 Cash testing support11 files

📁 Grants & Contracts22 files

📁 Fieldwork20 files

📁 Meeting Minutes10 files

📄 GHC TB DEC25.xlsx306 KB

attestwork.workpaperos.com/engagements/riverbend-audit-2025/files

Engagement Files - same tree, synced

📁 4. Requests📁 Cash testing support · F1📁 Grants & Contracts · F12📁 Fieldwork📁 Meeting Minutes · P

File	Type	Uploaded by	Audit areas	Index	Date
Dec Bank Statement.pdf	PDF	Client	F1	Indexed	Jul 24
Revenue Testing 2025.xlsx	XLSX	User	F12 · F13	Indexed	Jul 24
Rev22-Remittance.pdf	PDF	Client	F12	Indexing	Jul 24
Vehicle purchase invoice.pdf	PDF	Client	F6	Partial	Jul 23

The Index column is the OCR / Google Document AI pipeline at work - once a file shows Indexed, the bots can search it, quote it, and cite it in workpapers.

AI on watch

Schedule your assistant to mind the inbox

Antigravity, Claude, and ChatGPT all run scheduled tasks. Point one at the engagement each morning and the follow-ups write themselves - as drafts.

Google Antigravity - scheduled task, weekdays 7:30 AM

Morning check - Riverbend audit file room: 3 new uploads overnight. “July-Sept Bank Statements.pdf” and “Oct-Dec Bank Statements.pdf” matched to PBC #12 - I've marked it Received and indexed both to F1 Cash. “Vehicle purchase invoice.pdf” indexed to F6 PP&E. Still outstanding: PBC #16 asset listing and depreciation schedules. I've drafted a client comment on #16:

Draft comment - awaiting your approval

“Hi Jordan - thanks for the bank statements. To start property testing we still need the fixed-asset listing and current depreciation schedule as of 12/31/2025. The folder for this request is ready in the shared Drive. - Hudson & Vale CPAs”

Approve and post it.

Guardrail: The assistant drafts comments and follow-up emails; a person at your firm approves before anything is sent. Client-facing communication is never automatic.

▶ Watch: PBC seeding, Drive sync, and the morning AI check

← Previous

Set up the engagement

Trial balance to statements

Screens on this page are illustrative: Hudson & Vale CPAs and Riverbend Community Services, Inc. are fictional.