dusk bot
routinesweekly google docs report

dusk botroutines

draft the weekly report from the work log in google docs

start friday’s report with what actually happened this week. this routine reads dated entries in your google docs work log.

by the dusk bot team · checked · how we made this

it drafts a short account of outcomes, delays and decisions in dusk chat, with a source date for each claim. once you approve the text, it creates a separate report document.

pixel art: an orange pixel bot, a cyan pixel bot and a pink pixel bot beside the docs mark on a white tile, a newspaper and a notebook, on a sandy path in front of green terraced fields, one saying "ready for your edit"

the message

paste this into a chat with your bot

each friday at 3pm, read the work log in google docs. ask me once for its document link, relevant tabs and team name. use entries dated monday through today in my time zone, including table rows. ignore older entries even if someone edited the document this week.

draft at most 150 words in this chat under outcomes, delays and decisions needed. give the source tab and entry date for each bullet. call future work planned. omit empty headings. stay quiet after a complete read with no entries this week. flag inaccessible tabs or ambiguous dates.

ask me before you change anything. after approval, search for the exact title “weekly report draft” plus team name and friday's date. if one matches, return its link without edits. if several match, show their links and stop. if none match, create one new google doc with the approved text and return its link here. never overwrite the log or share the report.
when
fridays at 3pm in your time zone, after the last work-log update
needs
google docs reads by id, document search and permission to create a document from the approved draft

what comes back

an example, not a real run

weekly report draft · print team · 20 november
outcomes: vera lane approved the winter sleeve proof. [production, 18 november]
delays: the binding sample has not arrived. [supplies, 19 november]
decision needed: keep monday’s press slot or release it? [production, 20 november]
create this draft?

make it yours

  • write for the reader. for a department lead, keep only decisions they can make. for teammates, keep the work that affects handoffs.
  • cap the length. ask for one sentence per outcome when the report goes into a larger update.
  • choose the evidence. name the tab holding sign-offs if several tabs discuss the same work. a plan in monday’s notes can change by friday.

when it goes wrong

  • old news fills the draft. use dates inside the work log. the document’s last edit can belong to a spelling fix in an old entry.
  • a table row loses its context. read the column headers with its cells. if a date could belong to two entries, ask before including either.1
  • a retry finds several reports with the same title. stop and show their links. use the approved document id before doing anything else.

distinguish a finished result from a friday intention

look for the entry that confirms the work happened. “proof due friday” belongs under plans. “buyer approved the proof” can go under outcomes. keep the tab and date so the reader can find the same line.

if the team needs an audited report with signed figures, use its reporting process. dusk bot can prepare prose for review.

questions

can i run it with read-only google docs access?

yes, for the chat draft. keep the approved text in chat or copy it into a document yourself. creating a new doc needs the corresponding write action.1

what if my work log has several tabs?

name the tabs that feed this report. the text read can include selected tabs and tables. use a separate source label for each tab with a similar heading.1

sources

  1. composio: google docs actions, checked 20 november 2026
  2. dusk bot docs: routines
  3. dusk bot docs: connected apps

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].