A weekly report template for your manager, filled from a week of records
A weekly report to a manager answers four questions: what got done, what is still moving, what is blocked, and what happens next week. Write it as short lines a busy reader can scan, with outcomes first and hours nowhere unless asked. Most of the effort is remembering Tuesday, so start from records instead of memory. In Hina 0.6.0 the Week tab and the daily reports hold most of the facts, and about fifteen minutes is enough to turn them into a draft. The blockers and the plan for next week still come from you, because no record can see them.
What your manager is reading for
A manager reads a weekly report to decide whether to step in. They want to know what finished and can be relied on, what is in motion and when it lands, what is stopping you and whether they can unblock it, and what you will do next. How many hours you spent at the keyboard is rarely the point, and a list of every task you touched buries the one line that needs their attention.
That gives the report a fixed shape. Done holds outcomes someone else can check, such as a merged change, a sent document or a fixed bug. In progress holds work with a state you can name. Blocked holds only what needs another person or system, with the name. Next week holds two or three starting points, not a plan for the quarter.
A template you can paste
English version. Done: two to five lines, each naming the thing and where it can be seen. In progress: one line per item with its current state and what remains. Blocked: one line per item, saying what you are waiting for, from whom, and what you will do meanwhile. Next week: the first thing you will open, and at most two more.
Chinese version. 本周完成，写两到五行，每行写清做成了什么、在哪里能看到。进行中，每项一行，写当前状态和还差什么。卡住的地方，每项一行，写在等什么、等谁、这期间你做什么。下周，写第一件要打开的事，最多再加两件。
English template. Replace the bracketed text.
Done: [outcome], available at [document or delivery link].
In progress: [task], currently [state], with [next step] remaining.
Blocked: [task], waiting for [person or dependency]; meanwhile, [work that can continue].
Next week: [first task to start].
中文模板，可复制后替换括号里的内容。
本周完成：[结果]，可在[文档或交付入口]查看。
进行中：[事项]，目前[状态]，还差[下一步]。
卡住的地方：[事项]，在等[谁或什么]，这期间先做[可推进的事]。
下周：[第一件要开始的事]。
Two habits keep it honest. Write outcomes, not activity, so fixed the export button clipping on narrow screens instead of worked on the export page. And keep unfinished work out of Done, even when it took the most time, because a report that blurs done and in progress is the one people stop trusting.
Fill it from the week in 15 minutes
Spend the first five minutes on the Week tab. In Hina a week starts on Monday and a day runs from 04:00 to 04:00, so late Sunday work stays on Sunday. Use Previous and Next to reach the week you want. The Projects card shows where the time went, the Daily mix card shows each day's makeup by kind of activity, and Versus last week lists which kinds of activity went up or down against the week before. These help you pick which two or three threads deserve a line. They are not numbers to report.
Spend the next seven minutes on the daily reports. On the Day tab, step back through the week with Previous and press Daily report on each day, which builds the report for the day on screen. The Confirmed outcomes section lists what the records back up, and In progress and unconfirmed lists what they do not. The Local commit record shows commits from the folders you chose on the Data page of Settings, and it says plainly when a source is missing. Copy each day's useful lines into a scratch note. A commit proves a change exists in the local repository, not that it was reviewed or released, so check that status yourself before writing it under Done.
Use the last three minutes to write the two parts no record can supply. Blocked comes from messages you are waiting on, and Next week comes from your calendar and your own judgement. Hina reads no remote pull request or issue state, so anything that depends on a review or a ticket needs a glance at that tool.
Where the pieces come from
The Week tab and the daily reports read the same local sessions, and the reports add local git history from the folders you picked. If you opted in, they can also include your own AI prompts and terminal commands. The diagram shows how the draft is assembled and where your own notes enter.
What not to paste
A daily report is written for you, so it carries more than your manager needs. Leave out the Evidence details, Files touched and Commands you ran, which can contain client names, branch names and paths. If you turned on Read agent sessions, leave out What you asked AI and any original prompts, since they hold your own wording about problems you may not want to broadcast.
Leave out the Worth a look notes, such as commits that landed while you were away, and the hours at the keyboard and away time. Those describe the tool's view of your machine, not your work, and they invite a conversation about presence you did not intend. Also read the Sent out into the world section carefully. Hina says writing or submitting there, never published, because it cannot see whether you pressed the button.
Window titles and page paths appear only if you turned them on in Settings, Privacy, but when they are on, they can show up in reports. Read the draft once as your manager would, and remove client or colleague names that do not belong in this report.
Getting the text out, and what stays local
In the daily report, Copy puts the full Markdown on the clipboard, including the Evidence part the window keeps folded, and Export Markdown saves a file named report- and the date. Hovering over Copy shows the boundary plainly: the content comes from local records only. Once you paste into email or chat, that service's rules apply, not Hina's.
Hina reaches the network in only three places, each on a click and none carrying activity: the checkout page, activating a purchased key, and Check for Updates. The records live in ~/Library/Application Support/Hina/hina.sqlite. The command line has a --weekly option that prints a seven-day text bundle for a local assistant you choose. Whatever you send it to is governed by that tool's privacy rules. Daily reports, the Week tab and --weekly need a licence after the 7-day trial, and recording continues either way.
One trap with --weekly: without a date it ends on today and covers the seven days back from there, not the Monday-to-Sunday week the Week tab shows. Run on a Monday morning, it starts on last Tuesday and includes this morning. Pass the last day you want instead, for example /Applications/Hina.app/Contents/MacOS/Hina --weekly 2026-10-18, and compare its first and last dates with the week you are reporting on.
This post is about a report for someone else. The article on a weekly review from records covers the personal version, where you compare the week with your own plan.