The most time-consuming part of a quarterly summary is never “writing” — it’s “where to start.” Nine out of ten people who get stuck are staring at a blank page thinking “What did I even do this quarter?” — the order is backwards. The right order is to inventory your materials first, set the framework, and let the tool write the body. This article turns the whole process into a 7-step SOP you can save and reuse every quarter.
Seven steps to complete a summary
Step 1 | Inventory materials (you). Weekly reports, retrospective notes, key data, project milestones, customer feedback — list them before you start writing. The most common mistake here is “writing from memory” — memory only keeps the highlights, not the details, and details are exactly what gives a summary its credibility.
Step 2 | Set the framework (you). Just say: “Help me write a quarterly work summary about XX, generate a Word document, including main achievements, key data, existing problems, and plans for next quarter.” Framework first, so the summary doesn’t wander. The four-part structure is the safe solution: achievements cover value, data covers support, problems cover honesty, and plans cover direction.
Step 3 | Feed in materials (you). Give it the original materials and note which section each material corresponds to — “Use these customer feedback items in ‘Existing Problems’; use this progress table in ‘Key Data.’” It is responsible for organizing the language, but the source material must be real; the more specific you feed it, the less the first draft looks like a template.
Step 4 | Produce the first draft (it). This is the smoothest part of MuchSci Office Assistant: document generation and editing is its core function, and when it’s done it converts directly to Word — what you get is a finished .docx with Chinese formatting already set, not a chat transcript you still have to paste into a template.
Step 5 | Check formatting (you). Chinese typography is already configured with the Noto font, so you don’t need to worry about fonts. Focus on two things: whether heading levels are messed up, and whether punctuation mixes full-width and half-width. These two are the most common leftovers in a machine-generated first draft.
Step 6 | Fill in data (optional). For numbers that need charts, have it calculate and verify them — don’t calculate by hand. Hand calculation is not only slow, but you can also get caught at the reporting meeting by a mental-math error.
Step 7 | Export and archive (you). Have it also convert a PDF while you’re at it: use PDF for sending to the group (formatting won’t shift), and use Word for archiving (you can still edit it next quarter). Save both, and you’ll save half of Step 1 next quarter.
Figure 1 | Three buckets of materials: text, numbers, and milestones.
Three lessons
l State the framework up front — it saves half the time compared with changing the structure after the first draft is out; changing the structure is basically rewriting;
l Don’t just throw in “summarize this for me” — note which section each material is used in so it can write the words properly;
l Don’t turn it into a list of accomplishments: the problems section and the plans section are the most valuable parts of this document, and they’re written more for yourself than for your manager — next quarter’s start depends on these two sections.
Figure 2 | This is what the finished product looks like: a four-part skeleton with clear table-of-contents hierarchy.
Scope of this SOP
The four-part framework fits quarterly summaries for most roles; if your role needs additional fixed modules (such as incident retrospectives for safety roles or customer account reviews for sales roles), simply add the section names directly to the instruction in Step 2, and the other six steps stay the same.The value of an SOP isn’t speed; it’s clear responsibilities at every step: you inventory the materials, you state the framework, it writes the body, and you do the acceptance check.