Use a reporting work log to make a realistic publishing plan

A small newsroom can publish several short articles in one day and still have no reliable basis for promising the same output every day. Some stories arrive with clear documents. Others need repeated calls, a visit, or a correction after publication. Counting finished pages hides those differences. A modest reporting work log helps an editor see where work actually goes before setting the next publishing plan. Its purpose is to improve decisions, not to turn every minute into a productivity score.

For a solo publisher, the log can be a simple private note. It does not require a particular content management system or a paid tracking feature. Start with a small observation period and a few meaningful categories. The useful result is an explanation of capacity: which assignments fit available working time, which regularly need more room, and which unfinished responsibilities must stay visible when new ideas arrive.

Record stages that explain an editorial decision

A useful entry identifies the assignment and the kind of work performed. Research, reporting, checking, writing, production, and follow-up are possible categories. Choose names that match actual practice. Avoid a long menu that takes more effort to maintain than it saves. If checking documents and making calls overlap, note that relationship instead of pretending every activity belongs in a perfectly separate box.

The entry should help answer a planning question. For example, did the article take longer because the source document was hard to interpret, or because a necessary response had not arrived? Those are different problems. The first may need preparation or assistance. The second may require a more flexible publication decision. A total duration without an explanation cannot distinguish them.

Separate active work from elapsed waiting

An assignment may remain open for several days while requiring only a few periods of active work. Record waiting separately from work where that distinction is useful. Otherwise, a delayed reply can make a straightforward story appear unusually laborious, while the real issue is uncertainty about when it can be completed. Waiting still matters to the schedule, even when it is not active reporting time.

Consider an illustrative notice-based story. Reading the notice, checking its applicability, and writing the explanation are active tasks. Waiting for clarification is a dependency. The next plan might reserve a different article while clarification is pending. It should not assume that spending more continuous hours on the first story will necessarily produce the missing answer.

Include work that produced no article

A lead that does not become a publishable report still consumes effort. Perhaps the claim could not be verified, the document concerned another location, or the supposed development was already resolved. Record a brief outcome such as “not supported by available evidence” rather than treating the work as invisible. Do not turn that note into a judgment about a source's motives without evidence.

Unpublished work is especially important when deciding whether a new beat is manageable. A plan based only on completed articles ignores unsuccessful inquiries and abandoned drafts. However, the log should not become a reason to publish weak material to justify time already spent. A sound decision to stop remains a legitimate editorial outcome, and the planning record should preserve that distinction.

Keep sensitive material out of the planning record

A work log usually needs an internal assignment reference, not the full contents of interviews or confidential correspondence. Avoid copying contact details, private allegations, passwords, or unpublished source material into a general planning sheet. Keep reporting evidence in its appropriate protected location. The planning entry can explain the dependency without exposing the underlying conversation.

If several people use the log, agree on its purpose and who can read it. A record designed to improve assignment planning can become misleading if used later as a crude ranking of individual speed. Different assignments carry different burdens. Discuss unusual entries with the people doing the work before drawing conclusions about effort, competence, or future capacity.

Read the variation before using an average

A single average can conceal both unusually easy and unusually difficult assignments. Review the entries as groups with comparable work. A brief based on a clear public notice is not the same assignment as a reported explanation involving several viewpoints. Small samples also deserve caution: a few convenient stories do not establish a permanent production rate for that topic.

Look for recurring causes rather than chasing a precise forecast. Repeated trouble locating original documents suggests one kind of preparation. Repeated production rework suggests another. A one-off interruption may not justify redesigning the entire process. The log supports editorial judgment; it does not replace judgment with an apparently exact number that the evidence cannot sustain.

Carry follow-up into the next plan

Publication does not always end the assignment. A correction request, a newly available response, or a broken reference may need attention later. Record that work against the original assignment where practical. Otherwise, the first week appears efficient and the following week seems unexpectedly overloaded, even though both periods belong to the same editorial responsibility.

When preparing the next schedule, leave room for those open obligations before filling every available period with fresh stories. This is not a promise that every possible update will be pursued. It is a way to identify the follow-up already accepted and decide how to handle it. If a task is no longer necessary, close it with a reason rather than letting it remain indefinitely ambiguous.

Change one planning assumption and review it

At the end of the observation period, choose a specific adjustment. You might reduce simultaneous assignments, allow more preparation for a recurring document, or stop scheduling dependent stories as if their completion were certain. Write down what the change is intended to improve. Review the next set of entries to see whether the original problem persists or simply moved elsewhere.

Do not promise a fixed output increase from this exercise. A better plan may produce fewer articles while leaving adequate room for checking and follow-up. That can be a useful result. Keep the log lightweight enough to maintain, and discard categories that no longer inform a decision. A realistic publishing plan grows from understanding the work, including its uncertainty, rather than from assuming every available hour can become another finished page.