Internal Comms & Meetings

How to write a weekly team update as Small Legal and Compliance Teams

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

You're two people covering the legal and compliance surface area of a 150-person company. Every Friday, someone — usually the General Counsel or the compliance lead — spends 45 minutes pulling together a status update from memory, half-read Slack threads, and a Notion tracker that hasn't been touched since Q3. The update goes out late, misses the three contracts that are stuck waiting on a counter-party redline, and says nothing useful about which policies are up for annual attestation next week. Nobody reads it carefully because it doesn't tell them anything they couldn't guess. And you spent nearly an hour producing it.

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

An automated weekly digest that pulls open contract statuses, pending vendor-risk reviews, and policy-attestation deadlines into a single structured update — drafted for you, ready to edit and send

A searchable archive of every weekly update, so when a board member asks 'when did we last review the data-processing agreement with Vendor X?' you have an answer in ten seconds

An action-item tracker that carries forward unresolved items from last week's update automatically, so nothing falls off the list because the drafter forgot

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

Email Agent Knowledge Management Project Management

Data sources & config

Starch syncs your Gmail data on a schedule so the Email Agent can see inbound contract threads and flag which counter-parties have gone quiet. Connect your Notion workspace from Starch's integration catalog — the agent queries it live to pull policy-attestation dates and contract tracker rows when building the weekly draft. DocuSign and Google Drive are connected from Starch's integration catalog; the agent queries them live to check envelope status and pull the latest redlined documents. Project Management lives natively inside Starch with no external sync needed.

Prompts to copy

Every Friday at 8 AM, pull all open tasks tagged 'contract-review' or 'vendor-risk' from Project Management, check for any policy-attestation items due in the next 14 days from our Knowledge Management wiki, summarize what moved forward this week and what is still blocked, and draft a weekly legal team update email addressed to the leadership team.

Create a standing project called 'Legal & Compliance Weekly' with recurring tasks: 'Draft weekly update' (owner: me, due every Friday 8 AM), 'Review pending contract redlines' (weekly), and 'Check policy attestation calendar' (weekly). Flag any task that has been open more than 10 days.

Build a knowledge base section called 'Weekly Updates Archive' and automatically save each week's finalized update there. Tag each entry with the contracts mentioned and the policies referenced so I can search by either.

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

Walkthrough

Step-by-step

1 Connect Notion from Starch's integration catalog so the agent can read your contract tracker and policy calendar live when the weekly automation runs.

2 Connect Google Drive from Starch's integration catalog so the agent can reference the latest versions of MSAs, DPAs, and vendor-risk questionnaires without you attaching them manually.

3 Connect DocuSign from Starch's integration catalog so the agent can query live envelope status — which agreements are out for signature, which have been signed, which have expired — and include that in the weekly digest.

4 Starch syncs your Gmail data on a schedule; the Email Agent reads inbound threads to flag which counter-parties have gone quiet for more than five business days, a signal you'd otherwise have to track by memory.

5 In Project Management, set up a 'Legal & Compliance Weekly' project with recurring task types: contract reviews, vendor-risk assessments, DSAR tracking, and policy attestations. Tag tasks so the automation can filter by type.

6 Tell Starch: 'Every Friday at 8 AM, pull all open tasks from the Legal & Compliance Weekly project, check Notion for policy attestations due in the next 14 days, check DocuSign for envelopes that have been out more than 5 business days, and draft a team update organized into four sections: Contracts in Flight, Vendor Risk Queue, Policy Deadlines, and Carried-Forward Items.' Starch builds the automation.

7 Review the draft in Email Agent — it surfaces in your inbox as a pre-written update. Redline anything that needs human judgment (a litigation hold you don't want in writing yet, a deal you haven't disclosed to the team) before sending.

8 Send the finalized update from Email Agent with one click; the agent logs the sent version to Knowledge Management automatically under the 'Weekly Updates Archive' section.

9 Knowledge Management tags each archived update by contract names and policy references mentioned, so a future search for 'DPA — Acme Vendor' surfaces every weekly update where that agreement appeared.

10 Any action item that wasn't closed by the following Friday automatically carries forward in Project Management with a 'Stale — second week' tag, so the next draft explicitly names what's been sitting.

11 If a counter-party sends a redline over the weekend, Email Agent flags the thread as 'Contract — needs review' when you open Starch Monday morning, so it makes the next Friday update without relying on you to remember to log it.

12 Once the rhythm is stable, tell Starch to add a one-sentence risk flag to each Contracts in Flight item: 'If the envelope has been out more than 10 business days, note it as At Risk.' No separate tracking spreadsheet needed.

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

Week of April 14, 2026 — legal team update

Sample numbers from a real run

Contracts in Flight	4
Envelopes stale >5 business days (DocuSign)	2
Vendor-risk questionnaires in queue	3
Policy attestations due in 14 days	2
Carried-forward items from last week	3

On Friday April 18, the automation runs at 8 AM. It pulls four open contract-review tasks from Project Management: an MSA with a new SaaS payroll vendor, a DPA renewal for your CRM, a sub-processor addendum sales wants signed before end of quarter, and an NDA for a prospective partnership. It checks DocuSign live and finds two envelopes that have been sitting for more than five business days — the MSA and the sub-processor addendum — and marks both At Risk. It reads Notion live and finds two policy attestations coming due: the Acceptable Use Policy on April 25 and the Vendor Risk Management Policy on April 28. It checks Gmail and surfaces a thread where the CRM vendor's legal team sent a redline four days ago with no reply — flagged as 'counter-party waiting on us.' The draft lands in Email Agent pre-organized into four sections, with the two At Risk envelopes bolded and the Gmail thread named explicitly. You spend eight minutes editing: you remove a reference to the partnership NDA because the deal is still confidential, adjust the attestation deadline note because you already know the Acceptable Use Policy owner has agreed to sign, and add one sentence about the DSAR that came in Tuesday. You send. The finalized version saves to Knowledge Management automatically. Your head of operations replies within 20 minutes asking who owns the sub-processor addendum follow-up — a question the update answered before they had to ask.

Measurement

How you'll know it's working

Time from automation trigger to finalized update sent (target: under 15 minutes of human editing)

Number of At Risk contracts surfaced per week before anyone escalated them to you verbally

Percentage of policy attestations completed before their deadline (tracked week-over-week in Project Management)

Carried-forward action items as a share of total weekly items — a rising ratio signals the team is under-resourced or deals are genuinely stuck

Vendor-risk questionnaires closed within 10 business days of receipt

Comparison

What this replaces

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

Ironclad or Evisort

Purpose-built CLM with deep contract workflow features, but six-figure pricing assumes a dedicated legal-ops person to configure and maintain it — not the right fit for a two-person team running 20-40 contracts a year.

Manually drafted email from Notion + Slack recall

Free and familiar, but takes 45-60 minutes every Friday, is only as accurate as whoever drafts it, and produces no searchable archive that anyone actually uses.

Google Sheets contract tracker + calendar reminders

Low cost and zero setup, but the tracker drifts out of date within a quarter and the weekly update is still a manual copy-paste job that misses anything not in the sheet.

OneTrust

Excellent for privacy and compliance program management at scale, but priced for compliance teams with dedicated program managers and doesn't solve the weekly-update-drafting problem on its own.

On Starch RECOMMENDED

One platform — email agent, knowledge management, project management 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

Our contract tracker lives in Notion and it's a mess. Will Starch still be able to read it?

Yes. Starch connects to your Notion workspace from the integration catalog and queries it live. The agent reads whatever structure exists — databases, pages, inline tables. If your tracker has inconsistent columns or half-empty rows, the agent will work with what's there and surface gaps rather than silently skipping them. Cleaning up Notion is its own project, but you don't have to do it before Starch is useful.

Does Starch read the actual contract documents, or just metadata?

Both, depending on what you connect. Starch connects to Google Drive from the integration catalog and can query document contents live when the automation runs — so it can pull the name of the counter-party, the contract type, and any deadline dates that appear in the document itself. For DocuSign, it reads envelope status and metadata (sent date, signers, expiration) live. It does not do full legal review or redline analysis — that requires human attorney judgment.

We use Outlook, not Gmail. Does this still work?

Yes. Starch syncs your Outlook data on a schedule the same way it does Gmail. The Email Agent works with Outlook for drafting and sending the weekly update, and inbound threads are flagged the same way.

Is Starch SOC 2 certified? We'll get asked by our own compliance team.

Starch is not SOC 2 Type II certified today. That's a real limit worth naming: if your internal security review requires a current SOC 2 Type II report before approving a new SaaS tool, Starch won't pass that gate right now. It's on the roadmap. In the meantime, the honest answer to give your IT security team is that Starch reads from your existing systems (Notion, Drive, DocuSign, Gmail/Outlook) rather than storing contract documents itself.

Can Starch send the weekly update automatically without me reviewing it first?

It can, but we'd recommend against it for a legal team. The automation drafts the update and delivers it to Email Agent for your review. You control whether to send. For a team where the update may reference sensitive matters — litigation holds, unreleased deal terms, DSAR responses — a one-minute human review before it goes to leadership is the right default. The time savings come from not drafting from scratch, not from removing the attorney's eyes entirely.

What happens if a contract thread comes in over the weekend? Will it make the Friday update?

Yes. Starch syncs your Gmail or Outlook data on a schedule, so inbound threads from over the weekend will be visible when the Friday automation runs. If a counter-party sent a redline Saturday and you haven't replied by Friday morning, the Email Agent flags it as 'counter-party waiting on us' and includes it in the Contracts in Flight section of the draft.

We track vendor-risk assessments in a separate spreadsheet in Google Sheets. Can Starch pull from that too?

Yes. Connect Google Sheets from Starch's integration catalog and the agent queries it live alongside Notion and DocuSign when building the weekly draft. You'd tell Starch which sheet and which columns to treat as the vendor-risk queue. If the sheet is the source of truth, Starch will read it; if it's outdated, the agent will surface whatever is in there and you'll see quickly where the tracker needs attention.