Pausing a draft: what is the minimum record you need to resume?

When a small team pauses work on a story set in a craft workshop for a month, it should leave behind a reference to the baseline draft and a five-section pause record. The five sections are Decided, To decide, Dependencies, Next step, and Do not redo. The record is sufficient if the person taking over can use it to find the right draft, distinguish decisions from ideas, and begin a clearly bounded action.

“Act Two is nearly there; continue next month” does not preserve the state of the work. “Keep the choice to hand over the key in Act Two; the recipient is still undecided; when we return, first compare two ways of continuing from the choice” leaves a usable point of continuation. Minimum does not mean the fewest words. It means that removing any item could cause someone to do the wrong work, wait unnecessarily, or reopen an old discussion.

The following uses Mending the Lamp on a Rainy Night, a story set in a craft workshop and written by a three-person team, as a fictional teaching example. Writer Ahe, editor Xiaoman, and production coordinator Jichuan pause their collaboration for a month. This is not a real user case, has not undergone real-world testing, and does not represent any product functionality. All drafts, comments, and staffing arrangements described here are illustrative.

Start the record with four details: the pause date, the intended resumption date, the single location of the baseline draft, and the person maintaining the record. The dates express a plan; they do not guarantee that the conditions for resuming will be in place. The baseline must be distinguishable from other versions—for example, “Mending the Lamp on a Rainy Night, sixth draft, Act Two, Scene Eight”—rather than simply “latest file.”

You can copy the blank template below. Any cell may say “Unknown,” but each unknown must be followed by an action to verify it.

The basis for a decision can be a comment in the draft or an explicit confirmation record; there is no need to copy the whole discussion. If all you have is “Everyone seemed to agree,” put it under To decide. Name the person responsible, too. Even in a three-person team, “The writing team will handle it” can mean nobody takes it on.

An unfinished manuscript can still serve as the baseline. What matters is identifying which passages are placeholders and which content has been confirmed. If someone keeps editing after the pause, save their work as a separate candidate draft and note its changes relative to the baseline. A candidate that has not been explicitly adopted before work resumes must not quietly become everyone’s default starting point.

Mending the Lamp on a Rainy Night follows an apprentice repairing an old workshop lamp before a torrential downpour. The team has stopped at Scene Eight: the apprentice discovers a crack in the lampshade and must decide whether to give the key to the master. The existing draft links “handing over the key” with “admitting to having caused the crack,” even though the cause of the crack has not been established.

The sample record begins: “Paused from April 3; intended resumption May 3; baseline: sixth draft of Mending the Lamp on a Rainy Night in the shared project directory; reference: Act Two, Scene Eight, and comments 12–14; Jichuan maintains this pause record.” In actual use, replace the directory and filename with an existing team location that the person taking over can open.

Decided: Keep the choice to hand over the key, with repairing the lamp remaining the main action in Act Two. In this example, comment 12 in the sixth draft provides confirmation. This decision establishes only that the choice exists. It does not establish responsibility for the crack or require an extra scene on every branch.

To decide: Does handing over the key express a request for help or acceptance of responsibility? Ahe will write one continuation for each interpretation, and Xiaoman will judge them against the character information already established in Act One. If a conflict remains, Xiaoman will write the reasons for choosing between them beside the two drafts. “Handing over the key” must not automatically be labeled the admission-of-fault route.

Dependencies: Check whether Act One explicitly states that the apprentice damaged the lampshade. Jichuan will locate the relevant passage. Until the original wording is found, the accepting-responsibility version can only remain a candidate. This gap blocks finalizing that version, but it does not block drafting the help-seeking version.

Next step: When work resumes, Ahe will first open Scene Eight and revise only the continuation after the choice, writing both a help-seeking version and an accepting-responsibility version. The deliverable is a one-page comparison. Completion requires both versions to identify the earlier story information they draw on and mark missing support as “To be supplied.” Do not expand the subsequent endings yet.

Do not redo: Do not reinstate the option in which “a third visitor enters and explains the crack” for now. In this example, it was set aside because introducing that character requires additional setup that conflicts with the scope of the current two-person scene. Reopen it only if the team again permits adding a character. The option has not been tested; it has not been proven ineffective.

With this record, someone returning to the project knows both what to write first and which version cannot yet be finalized. The pause record has not solved the story problem for the team, but it has preserved the problem’s actual state.

First confirm that the baseline still applies, then check dependencies, and finally take up the next step. If the original sentence Jichuan finds in Act One says only “the apprentice touched the lampshade,” it cannot be interpreted as evidence of damage. Add that finding under Dependencies. The accepting-responsibility version remains unresolved, while the help-seeking version can still move forward.

If the team decides to adopt the help-seeking version, move that decision and its rationale into Decided and rewrite the next step. Keep the old candidate labeled; do not leave two current answers in the pause record. It should show the current state while retaining a brief record sufficient to explain what changed.

Before handing over the work, another team member can read only the record and explain “which draft to open, what to do first, and where to stop.” This is a suggested check, not a test already conducted for this article. If they have to ask “What exactly were you thinking at the time?”, add the missing basis or scope of the decision. There is no need to reconstruct all the meeting minutes.

If the baseline file is missing, or two people each hold a different confirmed draft, the next step should become recovering the file or establishing the baseline. Writing further at that point will only carry the disagreement into the new draft. If the record’s maintainer will be unavailable a month later, name a replacement before pausing and clarify who may change items under Decided.

For a single author with no external dependencies, the five sections can shrink to five lines. “Dependencies: None” is still an explicit record. When several people write different scenes separately, one overall pause record can point to smaller scene-specific records. Keep only cross-scene decisions in the overall document so the same conclusion does not need to be maintained repeatedly in every record.

Full meeting minutes help trace how a discussion unfolded, but the entry point for resuming still needs to condense that history into an actionable state. A task board helps assign work, but a card that says only “Continue Act Two” still needs the basis for decisions and a stopping point. If existing documents can hold this information, simply add the fields; there is no need to switch tools.

In particular, “Do not redo” must not become a permanent ban. Changes in budget, length, or the permitted cast may make a previously shelved option suitable again. Recording the conditions under which it was set aside lets you distinguish accidental rework from justified reconsideration.

This pause record also does not replace preservation of the source draft, an asset inventory, or an access handover. If these are dependencies, point to the corresponding records. Before leaving, remove the chatter and reflections that will not affect the action taken on return. Keep the scope of decisions, the limits of what is known, and the first deliverable. A month later, the team should continue from those explicit facts, rather than from whoever sounds most confident in their memory.