Internal Comms & Meetings

How to write a weekly team update as Small IT and ITOps Teams

Internal Comms & MeetingsFor Small IT and ITOps Teams3 apps10 steps~20 min to set up

Your two-person IT team closes out every week with a pile of context that lives nowhere useful: Jira tickets resolved, AWS cost anomalies flagged to finance, three Okta provisioning requests processed, a Zoom license reclaimed from a departed employee, a Slack thread about the flaky VPN that never got an owner. Writing a weekly update means opening five browser tabs, scrolling through your own Slack messages to reconstruct what actually happened, and producing a Google Doc that half the company ignores anyway. It takes 45 minutes you don't have, and it still misses the Jira ticket that went stale for two weeks because nobody escalated it.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small IT and ITOps Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

An automated weekly IT update that pulls from Jira, AWS, and GitHub — so you stop reconstructing your own week from memory and Slack scroll

A structured digest your team and finance stakeholders can actually read: open tickets, cost anomalies, license changes, and incidents — all in one place with no copy-paste

A running archive of every weekly update stored in Knowledge Management, so when someone asks 'when did we reclaim those Zoom seats?' you can search for it instead of guessing

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

Project Management Knowledge Management Email Agent

Data sources & config

Connect Jira and PagerDuty from Starch's integration catalog — the agent queries them live each Friday when the automation runs. Starch connects directly to AWS through its scheduled sync, pulling Cost Explorer data on a schedule so anomalies are ready when the update drafts. Connect Slack from Starch's integration catalog for delivery. Notion syncs on a schedule as the backing store for Knowledge Management.

Prompts to copy

Every Friday at 4pm, pull all Jira tickets closed or updated this week, list any open P1/P2 incidents from PagerDuty, summarize AWS cost anomalies flagged this week, and draft a weekly IT update I can review and send to the all-hands Slack channel.

Save this week's IT update to Knowledge Management under 'IT Weekly Updates / 2026' and tag it with any recurring themes like 'license reclaim', 'onboarding', or 'AWS cost'.

Draft an email version of this week's IT update for the Finance team — keep it to five bullet points, focus on cost anomalies and headcount changes, skip the ticket-level detail.

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

Walkthrough

Step-by-step

1 Connect Jira from Starch's integration catalog. The agent will query your Jira instance live each Friday — no scheduled sync needed — to pull tickets closed, updated, or escalated during the week.

2 Connect PagerDuty from Starch's integration catalog so the update automatically includes any P1/P2 incidents that fired or resolved during the week, with resolution status and owner.

3 Wire AWS through Starch's direct connection. Cost Explorer data syncs on a schedule, so when the automation runs on Friday, the anomalies are already staged and ready to surface without a live query delay.

4 Set up the Project Management app and describe your weekly IT digest: 'Every Friday at 4pm, pull this week's Jira activity, PagerDuty incidents, and AWS cost alerts. Draft a structured IT update grouped by: Incidents, Provisioning & License Changes, Infrastructure Costs, and Open Risks.'

5 Review the draft in Starch before it sends. The first two or three weeks, check that the Jira filters are catching the right projects and that the AWS anomaly threshold matches what you'd actually flag to finance.

6 Once the format looks right, tell Starch to post the final update to your IT Slack channel automatically: 'Post the approved weekly update to #it-ops every Friday at 4:30pm.'

7 Set up Knowledge Management with Notion connected on a scheduled sync. Tell Starch: 'After each weekly update is sent, save a copy to Knowledge Management under IT Weekly Updates, tagged by month and any recurring issue categories.'

8 Create a second, shorter version for finance: 'Draft a 5-bullet summary for Finance every Friday — include total AWS spend delta, headcount changes that affected licensing this week, and any cost anomalies over $500. Send it to the Finance Slack channel or email thread.'

9 Set up the Email Agent to handle the handful of stakeholders who reply to the update with follow-up questions. Tell it: 'When someone replies to the weekly IT update email asking about a specific ticket or cost item, draft a reply pulling the relevant Jira or AWS detail.'

10 After four weeks, ask Starch: 'Look at the last four weekly IT updates in Knowledge Management. What recurring issues appear more than twice? Draft a short trend summary I can bring to the next all-hands.' This turns your update archive into an actual ops review artifact.

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 — IT Weekly Update

Sample numbers from a real run

Jira tickets closed	14
Open P2 incidents (VPN flap, unresolved)	1
Okta provisioning requests completed	6
Licenses reclaimed (Zoom seats, departed employees)	3
AWS Cost Explorer anomaly flagged — Lambda spike	2,400
New laptops enrolled in Jamf (onboarding batch)	4

On Friday at 4pm, Starch queries Jira live and finds 14 closed tickets across the IT Help Desk and Infrastructure projects — including the two-week-old 'slow laptop' ticket for the sales floor that finally got resolved with a RAM upgrade. PagerDuty shows one open P2: the VPN flap that fired Tuesday, partially mitigated but still being monitored. AWS Cost Explorer (synced on a schedule) surfaces a $2,400 Lambda spike mid-week that nobody had formally flagged yet. The draft groups all of this into four sections — Incidents, Provisioning, Infrastructure Costs, Open Risks — and adds a plain-English note that the Lambda spike is under investigation and finance shouldn't expect it to recur. The Finance version drops to five bullets and skips the ticket count. Both go out by 4:30pm. The full update saves automatically to Knowledge Management under 'IT Weekly Updates / April 2026' tagged with 'AWS cost' and 'VPN'. Two weeks later, when your manager asks 'is the VPN thing a pattern?', you search Knowledge Management and find it appeared in three of the last four updates — which is now a data point, not a memory exercise.

Measurement

How you'll know it's working

Time to produce weekly update (target: under 10 minutes of human review vs. 45 minutes of manual assembly)

Percentage of P1/P2 incidents included in the update vs. discovered after the fact

License reclaim actions surfaced per week (Zoom, Salesforce, or other SaaS seats flagged for reclaim)

Weekly update delivery consistency — did it go out on Friday, or did it slip to Monday again

Number of finance or leadership follow-up questions answered without a separate meeting

Comparison

What this replaces

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

Manual Google Doc + Slack scroll

Free and flexible, but someone has to spend 30-45 minutes every Friday reconstructing the week from memory and multiple tabs — that person is you, every single week.

Notion weekly template

Good structure if your team actually fills it out, but Notion doesn't pull from Jira or AWS automatically — it's still a manual copy-paste job dressed up in a template.

Jira Automation + Confluence

Jira Automation can generate ticket summaries, but it doesn't cross tool boundaries into AWS Cost Explorer or PagerDuty, and Confluence pages don't write themselves in plain English for non-technical stakeholders.

StatusPage or incident-specific tools

Great for external incident communication, but not built for internal weekly IT ops digests that also cover provisioning, licensing, and cost — you'd still need a separate update for everything outside incidents.

On Starch RECOMMENDED

One platform — project management, knowledge management, 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 connect to Jira, or does it just read from a spreadsheet export?

Starch connects to Jira directly from its integration catalog — the agent queries your Jira instance live when the automation runs. You're not exporting CSVs or maintaining a manual feed. If your Jira has multiple projects, you tell Starch which ones to pull from when you describe the app.

We use PagerDuty for incidents. Will the update include on-call incidents automatically?

Yes. PagerDuty is reachable from Starch's integration catalog and the agent queries it live. Tell Starch to include open and resolved P1/P2 incidents from the current week, and it will pull that data when the Friday automation runs.

Our AWS cost anomalies sometimes show up mid-week. Will the update catch them even if they aren't formally filed anywhere?

Yes. Starch connects directly to AWS and syncs Cost Explorer data on a schedule, so anomalies are staged and ready when the Friday update runs — you don't have to have manually filed them in a ticket first. You can set a dollar threshold in the prompt so only anomalies above, say, $500 make it into the update.

Is Starch SOC 2 Type II certified? We have to ask for any tool that touches our AWS and Jira data.

Not yet. Starch is not currently SOC 2 Type II certified. That's an honest limit worth knowing before you connect production data sources. If your security policy requires it for any third-party tooling, that's a real blocker today.

Can the IT update go to multiple destinations — Slack for the team, email for finance, Notion for the archive?

Yes. You describe each destination separately. For example: 'Post the full update to #it-ops on Slack, send the 5-bullet finance version to the finance email thread, and save the full version to Knowledge Management in Notion.' Starch handles each delivery as a separate step in the same Friday automation.

What if our Jira or AWS data is delayed or the query fails — will the update just send with missing data?

The update drafts for your review before it sends. You'll see what was pulled and what looks thin before anything goes out. You can configure it to flag you if the Jira query returns fewer tickets than a normal week, so you can investigate before approving the send.

We also use Okta and Jamf. Can the update include provisioning activity from those tools?

Okta and Jamf are both web-based platforms. Starch can automate them through your browser — no formal API connector required — to pull provisioning activity, new enrollments, or policy changes into the weekly summary. You'd describe what data you want surfaced and Starch builds the browser-based retrieval step.