Internal Comms & Meetings

How to schedule meetings across timezones as Small Legal and Compliance Teams

Internal Comms & MeetingsFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

You're a two-person legal team coordinating external counsel in London, a compliance vendor in India, and internal stakeholders across three US time zones. Every scheduling thread is a five-email chain: 'Does 3pm ET work?' 'That's 8pm for me.' 'How about Thursday?' You're doing this for vendor-risk review calls, DSAR interviews, quarterly attestation walkthroughs, and outside counsel briefings. Google Calendar shows your availability; nothing surfaces it automatically. Calendly exists but you've never configured it for legal-specific meeting types — 30-min vendor-risk intake, 60-min contract negotiation, 15-min DSAR triage. Meanwhile the actual legal work is waiting while you play timezone Tetris in your inbox.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A public booking page with legal-specific meeting types (vendor-risk intake, DSAR triage, contract review kickoff) that shows real-time availability across your calendar and books both parties automatically

Automated meeting notes for every scheduled call — transcribed, summarized, and action items extracted — so you have a documented record for DSAR logs, vendor-risk files, and audit trails

An inbox triage layer that catches scheduling requests buried in your Gmail and drafts replies with your booking link, so no coordination request goes unanswered for more than an hour

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

Scheduling Meeting Notes Email Agent

Data sources & config

Starch connects directly to Google Calendar via scheduled sync to read availability in real time and write new booking events. Gmail is synced on a schedule so the email agent can read incoming messages and draft replies. Calendly is connected from Starch's integration catalog; the agent queries it live for existing booking data. Zoom and Google Meet are connected from Starch's integration catalog for meeting link generation.

Prompts to copy

Build me a booking page with three meeting types: '30-min Vendor Risk Intake' (for new SaaS vendor reviews), '60-min Contract Review Kickoff' (for MSA or DPA negotiations), and '15-min DSAR Triage' (for data subject access requests). Add 15-minute buffers between all meetings. Block Fridays after 2pm. Make the link shareable.

After every meeting booked through my scheduling link, transcribe the call, write a one-paragraph summary, extract any action items with owner names, and save the record to a searchable archive I can reference when outside counsel asks what was discussed.

Monitor my Gmail for any email that includes scheduling language — phrases like 'can we find time,' 'when are you available,' 'let's set up a call' — and draft a reply with my booking link and a one-line context note about which meeting type fits the request.

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

Walkthrough

Step-by-step

1 Connect your Google Calendar — Starch syncs it on a schedule and uses it as the live availability source for your booking page. Any blocks you add in Calendar (client calls, court deadlines, focus time) are respected automatically.

2 Open the Scheduling app from the Starch App Store and tell it your three meeting types: Vendor Risk Intake (30 min), Contract Review Kickoff (60 min), DSAR Triage (15 min). Starch builds the booking page; you don't configure a form builder.

3 Set your availability rules in plain language: 'Available Monday through Thursday, 9am to 5pm ET, with 15-minute buffers between meetings and no meetings after 2pm on Fridays.' Starch applies these as constraints on the booking page.

4 Connect Zoom or Google Meet from Starch's integration catalog so booking confirmations include a generated video link automatically — no manual copy-paste from your calendar.

5 Share the booking link in your email signature, in your standard vendor onboarding email template, and in any DSAR acknowledgment letters. Vendors and counterparties book without emailing you first.

6 Install the Email Agent and tell it: 'Watch my Gmail for scheduling requests. If someone asks when I'm free or asks to set up a call, draft a reply with my Starch booking link and note which meeting type is most appropriate based on what they're asking about.' Starch syncs Gmail on a schedule and monitors continuously.

7 Install Meeting Notes and tell it: 'After every call that comes through my scheduling page, transcribe the meeting, write a summary of key decisions, list action items with assigned owners, and tag the record by meeting type — Vendor Risk, Contract Review, or DSAR.' This gives you a timestamped audit trail without taking notes yourself.

8 For cross-timezone calls with outside counsel or international vendors, tell Starch: 'When I book a meeting with someone whose email domain is outside the US, surface their likely timezone in the confirmation email and convert the meeting time to their local time in the invite body.' Starch handles this through the calendar connection.

9 Build a lightweight dashboard: 'Show me all meetings booked in the last 30 days, grouped by meeting type, with the action items from each call and whether they've been marked resolved.' This becomes your running legal-ops status view without a separate project tracker.

10 Set a weekly automation: 'Every Monday at 8am, send me a Slack summary of the week's scheduled meetings, who I'm meeting with, what type of call it is, and any outstanding action items from last week's calls.' Starch composes this from Calendar sync and the Meeting Notes archive.

11 For recurring compliance calendar events — quarterly attestation walkthroughs, annual policy reviews — tell Starch: 'Create a recurring booking for our annual SOC 2 policy attestation walkthrough every November. Invite the same internal stakeholders and add a 30-minute prep slot the day before.' Starch writes this to your calendar.

12 When outside counsel or a vendor needs to reschedule, they use the same booking link — Starch updates the calendar entry and sends revised confirmations to both parties, no email thread required.

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 Vendor Risk Intake — CloudSign SaaS Review

Sample numbers from a real run

Scheduling request received via email from IT vendor procurement	0
Email Agent drafts reply with Vendor Risk Intake booking link within 4 minutes	0
CloudSign vendor books 30-min slot for April 9, 10am ET (3pm BST for their UK team)	0
Timezone conversion note auto-included in confirmation email	0
Meeting Notes transcribes 28-minute call, generates summary in 90 seconds	0
3 action items extracted: vendor to send updated DPA, legal to review data-residency clause, IT to confirm storage region	0
Record archived and searchable under 'CloudSign / Vendor Risk / April 2026'	0

IT flagged CloudSign as a new SaaS tool they wanted to onboard for e-signature redundancy. The vendor's security team was in the UK; your legal team is in New York. The old flow: three emails to find a time, a manually generated Zoom link, someone taking notes in a Google Doc that lived in a folder nobody could find six weeks later. With Starch, the IT procurement contact forwarded the vendor's intro email to you. The Email Agent caught the scheduling request within the next sync cycle, drafted a reply with your Vendor Risk Intake booking link, and you sent it with one click. The CloudSign team picked a slot — 10am ET — and the confirmation email they received automatically showed '3:00pm BST' in the body so there was no timezone confusion on their end. The 30-minute call ran 28 minutes. Meeting Notes produced a summary paragraph, flagged the data-residency clause as the open legal issue, and extracted three action items with owners. Two weeks later when your CISO asked 'where did we land on CloudSign storage regions?' you searched the meeting archive, found the exact moment in the transcript where the vendor said their EU data stays in Frankfurt, and forwarded the timestamp. No digging through email. Total scheduling coordination time for the whole intake: under 5 minutes.

Measurement

How you'll know it's working

Time from scheduling request received to meeting booked (target: under 10 minutes with no back-and-forth)

Percentage of vendor-risk intake calls with a documented action-item record in the archive (target: 100% — this is your audit trail)

Number of 'when are you free?' email threads that required more than one reply from you (target: zero)

Outstanding action items from legal calls older than 7 days with no resolution status

Meetings booked per week broken down by type (Vendor Risk, Contract Review, DSAR Triage) — surfaces where legal time is actually going

Comparison

What this replaces

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

Calendly standalone

Calendly handles booking pages well but doesn't connect to your Gmail, can't monitor your inbox for scheduling requests, and produces no meeting notes or action-item archive — you still need three separate tools to get what Starch does in one.

Microsoft Bookings (if you're on Outlook)

Built into M365 and fine for simple availability sharing, but no AI email monitoring, no meeting transcription, and no cross-system automation — it's a booking form, not a workflow.

Otter.ai + Calendly + Gmail manual triage

Each tool does one job adequately, but you're stitching them together yourself, paying three subscriptions, and the notes from Otter don't connect to the bookings from Calendly or the email threads in Gmail — no unified legal-call archive.

Ironclad or Evisort scheduling features

These CLM platforms include some scheduling and workflow tooling, but they're designed for dedicated legal-ops teams at enterprise scale, cost six figures annually, and require significant configuration work before they're useful for a two-person team.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, email agent 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

Does Starch actually write to my Google Calendar, or does it just read it?

Both. Starch syncs your Google Calendar on a schedule to read your current availability and existing events. When someone books through your Starch scheduling page, Starch creates the calendar event for both parties. You'll see new bookings appear in Google Calendar like any other event.

We use Outlook, not Gmail. Does this work for us?

Yes. Starch syncs Outlook messages, events, calendars, and contacts on a schedule — the same way it handles Gmail. If your team runs on Microsoft 365, you'd connect Outlook instead of Gmail and the email monitoring and scheduling flows work the same way.

Will meeting notes from DSAR or vendor-risk calls be stored somewhere secure? We can't have those transcripts floating around.

Meeting notes are stored in Starch's database and accessible only to your account. One honest limit to name: Starch is not SOC 2 Type II certified today. If your organization requires SOC 2 Type II certified storage for call transcripts, you'd want to export records to a system that carries that certification. We'd rather you know that upfront.

Can the Email Agent tell the difference between a vendor asking to schedule a call and a sales rep cold-emailing me?

You define the rules in plain language. You can tell Starch: 'Only treat a scheduling request as worth acting on if it comes from a domain already in my calendar history, or if the email is a reply to a thread I started.' That filters out cold outreach without you having to build a rules engine.

What if someone needs to reschedule after they've booked?

The booking page lets counterparties reschedule or cancel through the same link they used to book. The calendar event is updated automatically and both parties get a revised confirmation. You don't need to be in the loop unless you want to be.

We already use Calendly. Do we have to replace it?

No. Starch connects to Calendly from its integration catalog; the agent queries it live. If you want to keep Calendly as your booking page and just add the Gmail monitoring and meeting-notes layers on top, you can build that as a custom workflow without touching your existing Calendly setup.

Can I get a weekly summary of what legal calls are coming up and what's still open from last week's calls?

Yes. Tell Starch: 'Every Monday at 8am, send me a Slack message with this week's scheduled meetings by type and any action items from last week's calls that haven't been marked resolved.' Starch pulls from Calendar sync and the Meeting Notes archive to build that summary automatically.