Compliance & Legal

How to respond to a subpoena or legal hold as Chief of Staff and Founder's Office

Compliance & LegalFor Chief of Staff and Founder's Office4 apps12 steps~24 min to set up

When a subpoena or legal hold lands on your desk as chief of staff, you become the de facto discovery coordinator — even though that's not in your job description. You're immediately on the hook to identify every relevant email thread, Slack conversation, contract, and calendar invite across a 150-person company, often within 72 hours. Gmail search is manual and incomplete. Notion pages aren't indexed by date or custodian. Slack exports require IT admin rights you may not have. Legal counsel is billing by the hour while you're still trying to pull the right QuickBooks invoices and figure out which HubSpot contacts were involved. There's no process, no tracker, and no single person who knows where everything lives.

Build this on Starch → See the apps used

Compliance & LegalFor Chief of Staff and Founder's Office4 apps12 steps~24 min to set up

Outcome

What you'll set up

A legal hold tracker that maps every custodian, data source, and document status in one place — built in natural language on top of your connected Notion, Gmail, Slack, and calendar data

An automated email triage workflow that flags incoming correspondence tagged to the matter (from opposing counsel, your own legal team, or relevant parties) and drafts acknowledgment replies so nothing gets missed

A task checklist with P1–P4 priority levels and due-date alerts that keeps you on track from initial hold notice through document production, without letting the rest of your week collapse

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Task Manager Knowledge Management

Data sources & config

Starch syncs your Gmail data on a schedule (messages, labels, thread history), Starch syncs your Google Calendar data on a schedule (events and attendees relevant to custodian identification), Starch syncs your Notion data on a schedule (pages and databases for the legal matter wiki), and Starch syncs your HubSpot data on a schedule (contacts and companies to identify which counterparties are relevant to the matter). Slack is connected from Starch's integration catalog and queried live when you need to identify relevant channel history or custodians. QuickBooks is connected directly by Starch and queried live for any invoices or payment records named in the subpoena.

Prompts to copy

Build me a legal hold tracker that lists every custodian by name and department, the data sources they own (Gmail, Slack, Notion, HubSpot, QuickBooks), the date the hold was placed on each, and the current collection status. Add a field for whether outside counsel has confirmed receipt of each custodian's data package.

Monitor my Gmail inbox for any emails from outside counsel at [firm name] or the opposing party, summarize each thread in one sentence, and draft a holding reply that acknowledges receipt and confirms our legal team is coordinating. Flag anything that mentions a response deadline.

Create a task list for the full subpoena response workflow with P1 deadlines: identify custodians (due day 1), issue hold notices (due day 2), collect Gmail and Slack exports (due day 5), review with outside counsel (due day 10), produce documents (due day 21). Alert me if any task goes overdue.

Build a legal matter wiki page that documents the case name, issuing court, response deadline, list of custodians, data sources in scope, outside counsel contact, and a running log of all actions taken and by whom.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Within an hour of receiving the subpoena, open Starch and tell it to build a legal hold tracker — name the case, paste in the response deadline, and list the initial custodians you already know. Starch scaffolds the tracker immediately.

2 Connect Gmail (scheduled sync) and Notion (scheduled sync) so Starch can pull existing email threads and documentation related to the matter's time window and parties.

3 Use the Email Triage app to set up a filter for correspondence from outside counsel and opposing counsel. Ask Starch to summarize all threads from those senders going back to the relevant period and flag any that include deadlines or production requests.

4 Run the Task Manager app to capture every step between now and the production deadline with P1–P4 levels. Tell Starch: 'Set P1 for anything with a hard legal deadline, P2 for internal coordination tasks, and remind me every morning what's overdue.'

5 Query HubSpot (Starch connects directly) to pull every contact and company associated with the counterparty or transaction named in the subpoena — you need this to verify which employees had relevant interactions.

6 Query QuickBooks (Starch connects directly) to pull invoices, payments, and vendor records in the date range specified by the subpoena. Export the summary to your legal hold tracker in Starch.

7 Tell Starch to pull your Google Calendar history for all custodians whose calendars you can access, filtering for meetings that include any of the counterparty contacts identified in step 5. This gives you a record of who met with whom and when.

8 Use Slack (live query from Starch's integration catalog) to identify which channels are in scope — tell Starch to search for any public channel messages that mention the counterparty name, contract number, or transaction ID in the subpoena.

9 As outside counsel issues written hold notices, log each one in the Knowledge Management wiki — tell Starch to create a section per custodian with the hold notice date, acknowledgment status, and a link to their data package.

10 Set the Email Triage app to send you a daily digest of all matter-related correspondence with a one-sentence summary of each thread and a flag if any email has gone unanswered for more than 24 hours.

11 When document production is ready, use the Starch tracker to confirm every custodian's data has been collected, reviewed by counsel, and cleared for production. The tracker becomes your audit log showing you followed the hold process correctly.

12 After the matter closes, ask Starch to generate a post-hold report — what data sources were in scope, how many custodians, timeline from hold notice to production, and any gaps discovered — so you can build a repeatable process for the next time.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 commercial dispute subpoena — 21-day response window

Sample numbers from a real run

Custodians identified	7
Gmail threads flagged for review	340
HubSpot contacts linked to counterparty	23
QuickBooks invoices in date range	18
Calendar events with counterparty attendees	11
Task items tracked to completion	34
Hours saved vs. manual inbox search (estimated)	14

A subpoena arrives on April 3rd naming a former vendor in a contract dispute. The response deadline is April 24th — 21 days. The chief of staff opens Starch and builds a legal hold tracker in under five minutes: case name, deadline, and an initial list of four custodians (CEO, Head of Legal, VP of Ops, and the account manager who ran the vendor relationship). Starch syncs Gmail and surfaces 340 threads mentioning the vendor name within the two-year window specified. The Email Triage app flags 12 threads that include dollar figures or delivery disputes — those go straight to outside counsel for review. Starch queries HubSpot live and finds 23 contacts associated with the vendor's company record, three of whom are employees the chief of staff hadn't originally listed as custodians. Two more people get added to the hold. QuickBooks pulls 18 invoices in the contract period, totaling $412,000 in payments — outside counsel needs that number for the production letter. Google Calendar surfaces 11 meetings where vendor representatives were invited attendees, filling in the relationship timeline. The Task Manager app tracks all 34 action items from hold notices to counsel review to final production, and sends a morning overdue alert on April 18th when the Slack export is still pending — bought three days of buffer before the deadline. The Knowledge Management wiki becomes the authoritative record: every custodian acknowledged, every data source collected, every step logged. When outside counsel asks for a timeline of the company's actions during the hold period, the chief of staff exports it in two minutes instead of reconstructing it from memory.

Measurement

How you'll know it's working

Time from subpoena receipt to all hold notices issued (target: under 48 hours)

Custodian coverage rate — percentage of custodians with confirmed data collection vs. total identified

Open matter-related emails unanswered for more than 24 hours (should be zero)

Days between document collection completion and production deadline (buffer time)

Number of data sources in scope vs. number with confirmed export (gap tracking)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Manual Gmail search + Google Sheets tracker

Gets you a list but doesn't monitor for new incoming correspondence, misses threads where the vendor name is spelled differently, and the sheet goes stale the moment someone forgets to update it.

Relativity or Logikcull (eDiscovery platforms)

Purpose-built for document review at scale, but require IT provisioning, take days to onboard, cost thousands per matter, and don't connect to your operational data in HubSpot, QuickBooks, or Notion — you still have to pull those manually.

Notion manual wiki + Slack reminders

You can build a tracker in Notion, but it's not connected to your actual data — you're copying and pasting from Gmail, QuickBooks, and HubSpot by hand, which is exactly what makes this workflow a 40-hour week on its own.

Outside counsel running the entire process

Fully offloads the legal judgment, but you're still the one pulling the data for them, and billing time while you find the right invoice number adds up fast — Starch doesn't replace counsel, it means you're not paying partner rates to organize a spreadsheet.

On Starch RECOMMENDED

One platform — crm, founder inbox, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Is Starch appropriate for managing legally sensitive documents?

Starch is not a document management platform with legal chain-of-custody controls, and it is not SOC 2 Type II certified yet. It's the right tool for organizing the coordination workflow — tracking custodians, flagging relevant emails, logging action steps, and building the internal tracker. The actual document production and review should still go through your outside counsel's systems. Think of Starch as the chief of staff layer, not the legal platform.

Can Starch search Slack messages for content related to the matter?

Yes — connect Slack from Starch's integration catalog and the agent queries it live. It can search channels and surface messages that match the counterparty name, contract terms, or other keywords you specify. Note that Slack exports for legal hold purposes typically need to be initiated by a workspace admin; Starch helps you identify what's in scope and who was involved, but the formal export still goes through Slack's compliance tools.

What if the counterparty or transaction data lives in a system not on Starch's list?

Starch connects to 3,000+ apps through its integration catalog, plus any website through browser automation. If the system has a web interface you can log into, Starch can automate it through your browser — no API needed. Describe what you need and Starch will tell you whether it can reach it directly or via browser automation.

Will Starch store the emails and documents it pulls for the matter?

Gmail data syncs on a schedule and lives in Starch's database for querying. Data from live-queried apps (like Slack) is queried at the moment you run the app but is not archived in Starch's database. Starch is not a long-horizon data warehouse — it's a live data surface. If you need a preserved snapshot for evidentiary purposes, export it to your outside counsel's system directly.

Can I build a reusable legal hold process template so I'm not starting from scratch next time?

Yes. Once you've built the tracker, task list, and email triage workflow for this matter, ask Starch to document the process in your Knowledge Management wiki. The next time a subpoena arrives, you describe the new matter details and Starch recreates the same structure with the new custodians, deadline, and data sources. You can also publish it as a private app within your Starch workspace so any member of your team can spin up a new matter without rebuilding from scratch.

QuickBooks report views aren't working — does that affect this workflow?

QuickBooks report views (P&L, Transaction List, Vendor Expenses) are temporarily disabled pending a fix. However, entity-level data — invoices, bills, payments, vendors, journal entries — syncs normally. For a subpoena response, you almost always need the underlying transaction records anyway, not a rolled-up report view, so this limitation is unlikely to affect you. You can pull the specific invoices and payment records named in the subpoena without issue.