Weekly

Get a weekly status summary of a project Doc

Each Friday you get the current status and open risks from a long project Doc.

Runs: Weekly
Apps: Google Docs
AI: Yes, uses the built-in AI allowance
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Friday at 3pm, read my Project Plan doc, summarise the current status and open risks, and email it to me.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A project lead keeps one long Google Doc for a product launch: decisions, risks, open questions, meeting notes and a status section that gets edited by six people. By Friday it is forty pages. Executives ask where things stand, and she either writes a status update from scratch or sends them a link that nobody has time to read. Important changes in the middle of the Doc go unnoticed.

Every Friday, ClickRuntime reads the whole Doc, flattens it to text, then lets its built-in AI draft a summary of the current state: where the project stands, what was decided, what is blocked and what is next. It emails the summary so the update exists before anyone asks.

Product managers and program leads use it for long-running documents like plans, wikis and runbooks.

What you get out of it

Status updates write themselves
The summary is ready at the end of the week. You review and forward it instead of composing a message from scratch, which saves the Friday afternoon hour that nobody enjoys.
Executives read something short
A page of summary gets read where a forty-page Doc does not. Stakeholders stay informed and trust the project because the update is regular and readable. Executives respond to short updates.
Blocked work gets called out
When the Doc mentions a dependency or an open risk, the summary highlights it. Problems that sit quietly in a long document become visible while there is still time to fix them.
The Doc remains the single source
People keep editing the one Doc, and the summary follows. You avoid maintaining a separate status report that falls out of date and disagrees with the plan. One source, one summary, no drift.
A weekly archive of project state
Each Friday email is a snapshot. When someone asks how the project looked in week six, you can read it, with no need to dig into version history. Each Friday email is a snapshot, so when someone asks how the project looked in week six, you can read it.

How it works

What happens, step by step

Once a week ClickRuntime reads the full text of your project Google Doc.
AI writes a short status summary: where things stand, what's next and any risks.
The summary is emailed to you.

Before it runs live

Connect Google Docs

What you get

RunsWeekly

Get a weekly status summary of a project Doctoday, 9:00Succeeded

Email · Project Plan: weekly statusStatus: design done, build 60% through, on track for 14 Nov. Risks: Northwind API access still pending.

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Slack
Combine it with other Google Docs steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

weekly_ai_summary_of_a_living_doc.pyexample

from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, ai, notify

DOC_ID = "project-plan-doc-id"

@on_trigger
def run(event):
    docs = build("docs", "v1", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)
    doc = docs.documents().get(documentId=DOC_ID).execute()
    text = "".join(r["textRun"]["content"] for el in doc["body"]["content"] if "paragraph" in el
                   for r in el["paragraph"]["elements"] if "textRun" in r)[:24000]
    summary = ai.generate("From this project plan, summarise the current status and list the open risks:\n" + text,
                          max_output_tokens=700).text
    notify.email_me(f"{doc['title']}: weekly status", summary)
    return {"chars": len(text)}

FAQ

Common questions

Does it summarize the whole Doc or only recent changes?

It summarizes the current content of the entire Doc as it stands on Friday. If you want only what changed this week, the change summary automation compares with a stored copy. Many teams use both, one for the overview and one for the delta.

What if the Doc has tables and images?

Text in tables is included, though complex layouts may read less naturally. Images carry no text for the AI, so they are not described. If key information is in screenshots, add a sentence about it in the text.

Can the summary go to a different audience than me?

Yes. It can be sent to a list, such as the leadership team, or to a Slack channel. Many leads send it to themselves first for a quick edit, and then forward it, which keeps a person responsible for what executives actually read.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a scheduleAI