Status reports are one of the most universal time-sinks in knowledge work. Every week, teams across every function spend 30–60 minutes writing a summary of what they did — pulling from memory, checking commit histories, scrolling through Slack, counting closed tickets.
The readers skim it in 3 minutes.
There’s a better way. An AI agent can write your weekly status report automatically — pulling from the tools where work actually happened (GitHub, Linear, Jira, Slack, HubSpot) — and deliver it to your team before anyone asks for it.
Here’s how to set it up.
Why Status Reports Are a Waste of Time (In Their Current Form)
The problem isn’t the status report itself. It’s that the work happened in your tools, but the report has to be reconstructed from memory.
What your brain does every Friday:
- Try to remember what you worked on Monday–Thursday
- Open GitHub, scroll through commits
- Open Linear or Jira, look at closed tickets
- Check your calendar for meetings that produced decisions
- Open Slack, find relevant messages
- Synthesize all of this into prose
All of that information already exists in your tools. You’re just manually aggregating it. That’s exactly what agents are for.
What the Agent Does
The automated status report agent connects to the tools where work is recorded, reads activity from the past 7 days, synthesizes it into a structured report, and delivers it to the right place at the right time.
What it reads:
- GitHub: commits, PRs opened/merged/reviewed, issues closed
- Linear or Jira: tickets completed, moved to review, blockers added
- Google Calendar: external meetings and internal syncs attended
- Slack: threads you contributed to significantly (optional)
- HubSpot/Salesforce: deals progressed, calls logged (for sales roles)
What it writes:
Week of March 17 — Engineering Summary
✅ Completed
- Merged PR #482: API rate limiting for webhook endpoints
- Closed 4 Linear issues: session token refresh, mobile nav fix, CSV export bug, onboarding skip step
- Completed code review for PR #479 (auth refactor)
🔄 In Progress
- PR #485: Database migration for user preferences (awaiting review)
- Linear issue: Implement retry logic for failed agent runs (in review)
⚠️ Blocked / Needs Attention
- PR #481 has been waiting 3 days for review from @jake
📅 Key meetings
- Wednesday: Product planning — decided to move mobile to Q3
- Thursday: Customer call with Acme — flagged onboarding drop-off
🔜 Next week
- Complete retry logic, start on MCP connection pooling
- Follow up on PR #481That report took the agent 40 seconds to generate. It would have taken a human 35 minutes.
Two Versions: Individual and Team
Individual status report
Best for: Individual contributors, freelancers, or anyone reporting up on personal output.
The agent reads your activity across connected tools and writes a first-person summary of what you worked on, what’s in progress, and what’s coming next. Delivered Friday afternoon to your email or a Notion page.
Templates to start with: Standup Generator — configure it for weekly cadence instead of daily.
Team standup report
Best for: Engineering managers, team leads, or anyone aggregating status across a team.
The agent reads activity across all team members’ GitHub usernames and Linear accounts, writes a per-person summary, and rolls them up into a single team view. Posted to your team Slack channel Monday morning before standup.
What the team view looks like:
Team Status — Week of March 17
@alice: Merged 3 PRs, closed 6 Linear issues. In progress: auth refactor (awaiting review). Blocker: none.
@bob: Merged 1 PR, closed 2 issues. In progress: mobile nav redesign. Blocker: waiting on design spec from @charlie.
@charlie: Closed 4 issues. In progress: export feature. Blocker: none.
Team velocity: 13 issues closed (vs 11 last week ↑)
Open PRs waiting review: 2 (avg 1.8 days open)How to Set It Up
Step 1: Identify your activity sources
Where does your work actually get recorded? Common setups:
| Role | Primary sources |
|---|---|
| Engineer | GitHub + Linear (or Jira) |
| Product manager | Linear + Notion + Google Calendar |
| Sales rep | HubSpot + Google Calendar + Gmail |
| Marketing | Notion + Google Sheets + Google Calendar |
| Support | Zendesk (or Intercom) + Slack |
| Designer | Figma + Notion + Google Calendar |
Pick 2–3 sources that capture 80% of your work. Don’t try to connect everything at once.
Step 2: Open Shogo Studio
Go to studio.shogo.ai and start from the Standup Generator template.
Step 3: Connect your sources
OAuth authorize each tool — typically 2 clicks per integration. For a GitHub + Linear setup:
- “Connect GitHub” → authorize with your GitHub account (read-only)
- “Connect Linear” → authorize with your Linear workspace
Step 4: Configure the report format
Tell the agent what sections you want:
“Write a weekly status report covering: (1) what was completed this week, (2) what’s still in progress, (3) any blockers, (4) what’s planned for next week. Use bullet points. Keep it under 300 words. Group by work type if there are more than 5 items.”
You can also give it formatting preferences: emoji bullets, plain text, markdown headers — whatever matches your team’s conventions.
Step 5: Set team members (if team report)
For a team report, add the GitHub usernames and Linear user IDs for each team member. The agent reads each person’s activity and writes their section individually.
Step 6: Configure delivery
Friday 4pm → email or Notion: Good for individual async reports Monday 8:30am → Slack #standup: Good for team digests before the morning sync Any time → Slack DM to manager: Good for reporting-up use cases
Set it and forget it. The agent runs on schedule without any manual trigger.
What Makes a Good Automated Status Report
The difference between a good automated status report and a robotic-sounding one is in how you write the configuration prompt.
Too generic:
“Write a summary of what I did this week.”
Better:
“Write a status report in my voice — concise, specific, no buzzwords. Focus on outcomes, not activities. Instead of ‘worked on authentication,’ say ‘fixed the session timeout bug affecting mobile users.’ If something was blocked or delayed, name the blocker specifically. Don’t pad with filler.”
The more specific you are about tone and format, the more the output sounds like you wrote it — which is the whole point.
Tips from teams using this in production
Tip 1: Review before it sends for the first month
Configure the agent to send you a draft for review first, then post publicly. After a month, you’ll have enough confidence in the quality to go fully automated.
Tip 2: Add a “wins” section
Weekly status reports are often too neutral. Add a dedicated wins section:
“Start with a ‘this week’s wins’ section that calls out 1–3 things that went particularly well or shipped something notable.”
This makes the reports more energizing to read and keeps team morale visible.
Tip 3: Use it to spot blockers before 1:1s
If you’re a manager, read the automated team report Monday morning before 1:1s. Blockers that show up in the report become your agenda: “I saw you’ve been waiting 3 days for a review on #481 — what do you need to get that unstuck?”
Tip 4: Keep the sources tight
Connecting 5 sources sounds thorough but usually creates noisy reports. GitHub + one project management tool is usually the right starting point. Add a calendar source if meeting decisions are important to capture.
Get Started
The Standup Generator template is the fastest path to an automated status report. It defaults to daily standup format but configures to weekly with a single prompt change.
For team aggregation across multiple engineers, it also supports per-member activity rollup.
Deploy the Standup Generator → | Browse engineering templates → | Try free →