Home / Recipes for everyday work
Recipe: building a text in separate steps rather than in one go
An important text is broken into named steps, each with a single role, an approved plan first, then the drafting, then aligning the tone as a step in its own right, then a reread handed to an editor role rather than a simple request to rewrite.
This recipe comes from the author's own method, it does not rest on any dated product documentation. A single long request, write the note to members about this month's meeting, produces a text that Cowork builds in one block, plan, content and tone all mixed into the same pass. Breaking this request into four separate steps, each approved before the next, gives a text you correct at each step rather than all at once at the end.
Four requests, four roles
The first request covers only the plan, which sections, in what order, roughly how long each one should be. Approve this plan before asking for a single sentence of drafting. The second request covers the drafting itself, section by section if the text is long. The third request covers the tone, align the already drafted text on a precise register, a note to members is not written like the minutes of a technical meeting. The fourth request hands Cowork a reread with an explicitly named editor role, look for repetitions, sentences that run too long, words that need a definition, rather than a general rewrite of the text.
Demandes envoyées séparément à Cowork :
1. Proposer un plan pour la note aux adhérents du 12 septembre.
2. Rédiger la section Décisions votées à partir du plan validé.
3. Aligner le ton de cette section sur celui d'une note officielle.
4. Relire cette section en tant qu'éditeur et signaler les phrases trop longues.Why separate rather than ask for everything at once
A single long request forces you to correct the plan, the content and the tone all at the same time as soon as one of the three is off, and it often means redoing everything to change just one of them. A step approved before the next limits correction to the step concerned, a rejected plan is fixed before a single sentence is written, a poorly judged tone is fixed without touching content already approved. The raw material to gather before this breakdown is covered in turning scattered notes into a clean document or spreadsheet.
When this breakdown matters most
A short reply to a member does not justify four separate requests, the gain shows on a text meant to circulate as it is, an official note, a set of minutes, an updated set of bylaws. On this kind of text, a poorly calibrated sentence or an overly technical term is noticed once the document has been circulated, not before. Asking for the editor reread as the last step, once content and tone are already fixed, stops that reread from turning into a fresh, full rewrite that erases the choices already approved at earlier steps.
Four separate requests for a cooperative text
A cooperative secretary drafts a note to members in a single request to Cowork, write the full note about the 12 September meeting. He rereads the text obtained and spots a thirty seven word sentence in the third section.
Write one sentence stating what this situation establishes, and one sentence stating what it does not establish.
What this establishes: It establishes that the initial request covered the whole note in a single block, and that the sentence spotted counts thirty seven words in the third section.
What this does not establish: It does not establish whether the note's plan had been approved before drafting, nor whether a particular tone had been requested for this section.
The three most common miscalibrations
- Trop large It establishes that a request made in a single block always produces sentences that run too long, whatever the text requested.
- Trop étroit It establishes only that the third section contains a thirty seven word sentence, without saying anything about how the initial request was worded.
- À côté It establishes that the 12 September meeting covered at least three distinct topics, since the note has three sections.
- A request broken into plan, drafting, tone alignment and reread limits correction to the step concerned rather than to the whole text.
- The plan is approved before a single sentence of the text is drafted.
- Aligning the tone is asked for as a step in its own right, not as a simple general reread.
- A reread handed to an editor role looks for repetitions and sentences that run too long, not just spelling mistakes.
Take a text you need to write this week and send Cowork four separate requests, a plan, the drafting from the approved plan, a tone adjustment, then a reread as an editor, rather than a single long request.