At a glance
Use this workflow for an internal review across delivery work. You request each report and review the result; this guide does not set up a recurring schedule or change source records.
Give the brief a reporting window and source rules
An internal operations review asks where work is moving, where it is blocked, and which decision belongs to whom. It differs from a single-client account brief: the audience is your team and the scope can span multiple delivery items.
Connect Google Sheets and Linear separately in a private Geniusly Slack DM. Name the spreadsheet, tab, range, and Linear project. Specify the reporting dates and timezone. Explain status labels such as blocked, in review, and done rather than assuming the two systems use the same definitions.
A current spreadsheet snapshot can show today's status without establishing what changed this week. Ask for week-over-week changes only when accessible source history or dated snapshots support them. Otherwise request a current-state brief with that limitation stated.
Ask for the report you need to discuss
Prepare our operations brief for [start date] through [end date], using [timezone]. Read rows [range] of [tracker and tab] in Sheets and the [Linear project]. Group the result into confirmed progress, current blockers, decisions needed, and open questions. Link each factual item to its source. Keep recorded owners and due dates separate from suggestions. Flag disagreements between the sources. If change history is unavailable, describe current status without claiming a weekly change. Return a concise brief here and a Markdown report.
Illustrative task prompt. Use only information appropriate for the team receiving the result.
A reporting cutoff makes later reviews reproducible. A status updated after the cutoff should not silently become evidence for an earlier report. Ask the assistant to flag uncertain dates instead of assigning them to a reporting period.
A sample brief with one decision to resolve
Confirmed progress
Acme access review is marked complete in the tracker and the linked Linear issue. This establishes recorded status; change history was not supplied. [S1, L1]
Current blocker
Northstar onboarding is waiting on account access. The tracker names Priya as the internal owner and contains no confirmed access date. [S2]
Discrepancy
The tracker marks the Northstar handoff as ready while Linear marks it blocked. Review the two records before reporting the handoff as complete. [S2, L2]
Decision needed
Confirm which status is current and who will request the remaining access. Proposed next step: the recorded owner checks the two sources with the delivery team.
The labels above stand in for source references and are not live links. For a real report, request links to the relevant sheet and issues. Missing information and contradictions are part of the output, not details to hide.
Check evidence before the operations meeting
- Does the report cover the intended dates and projects?
- Can each progress or blocker claim be checked against a named source?
- Are current status and changes during the week clearly separated?
- Are owners and deadlines recorded facts, or clearly labeled suggestions?
- Are conflicting statuses visible as questions to resolve?
Use the report to prepare your team's conversation. Review it before sharing and update source systems through your existing process. Geniusly does not edit the tracker, create or update Linear issues, or schedule the next report as part of this workflow.
Reuse the prompt with a new reporting period when you need the next brief. To evaluate whether it helps, record the corrections and review effort over several real reports; these examples do not establish time savings.
Continue with a more specific handoff
For a new project, use the Gmail and Drive handoff guide. For broader preparation tasks, explore Geniusly for RevOps and operations or compare Geniusly with Lindy when your process also requires connected-app actions.
Questions & answers
What belongs in a weekly operations brief?
Confirmed progress, current blockers, decisions needed, and open questions, with a reporting window and source references. Distinguish recorded status from a change during the week.
Does this require Gmail?
No. This workflow uses Google Sheets and Linear. Connect the accounts holding those sources separately. The client account brief is a different workflow using Gmail, Sheets, and Drive.
What if I do not have source history?
Request a current-state report. Do not treat current status as proof that something changed during the reporting period. Supply dated snapshots if you want a supported comparison.
Does Geniusly update Linear or run the report every Monday?
This guide describes an on-request report. It does not update connected records or configure a recurring schedule. Reuse the prompt with the next reporting period.