Skills & Planning

Practical guides to documents, data, creative work, and everyday planning.

Showing 37–48 of 102 guides

Product photo shot list for documenting visible condition, including surface coverage, detail views, and location of marks.
10 min read

Plan a product photo shot list to document visible condition

Someone inspecting a physical item from a distance needs to know which surfaces the photographs show and where any visible marks sit. A product photo shot list turns that need into a set of specific pictures before you start. For each proposed view, write down the question it should answer. If a photograph cannot answer its question, take another view or record the gap. The list documents visible appearance; it cannot establish how the item works, what lies beneath a surface, or why a mark appeared.

Meeting agenda planning that defines the questions a group needs to answer before notes and decisions can be recorded.
8 min read

Use meeting agenda planning to clarify decisions in advance

Suppose a workplace group has agreed to meet about how to distribute a handout. The invitation says only “distribution,” and each person arrives with a different idea of the work ahead. One expects a status update. Another expects to compare ways of reaching readers. A third assumes a choice has already been made. Use meeting agenda planning to make the unresolved question visible before anyone meets: what must participants understand, which alternatives remain open, and what outcome is the meeting intended to seek?

document comment resolution: resolving comments before creating a revised report.
10 min read

Plan document comment resolution before revising a report

Three people have commented on the same workplace report. One wants a sentence explained, another disputes a figure, and a third wants the report to cover a new question. Editing in the order the comments arrived risks turning an unapproved suggestion into a change to the brief. Start by preserving what each person asked, identify the passage they meant, and decide what response is possible before rewriting it. For document comment resolution , verify each step.

Report summary writing that keeps a completed report's scope, qualifications, and limits intact in the shorter version.
9 min read

Use report summary writing to preserve important limits

A completed report can answer a narrow question carefully while its short summary makes a much broader claim. To prevent that shift, report summary writing should start with the report's actual conclusion, then retain the evidence and limits a reader needs to interpret it. The job is to produce a standalone account of what the report found, not to repeat every section in miniature. A short summary is successful only if a reader who never opens the full report would still understand where its conclusion applies.

Report appendix planning that places supporting material where readers can find it without crowding the main recommendation.
8 min read

Use report appendix planning to place supporting material

A workplace report recommends revising a meeting-room booking process. Its reader needs to understand why the proposal is worth considering and how much confidence to place in the material behind it. The draft has four kinds of text: the recommendation, a short summary of observations, individual observation entries, and a limitation on the period observed. Which pieces belong in the main discussion, and which could move to an appendix?

Workplace correction notice for a report already shared, identifying the wrong room, corrected account, and recipient action.
8 min read

Write a workplace correction notice for a shared report

A report has already reached colleagues when someone spots a wrong room in its account of a completed activity. Editing your own copy cannot tell those readers what changed. They need to know which report they received, where the error appears, what has actually been confirmed, and whether anyone has authorized a change to their work. Send a correction that answers those questions without suggesting the whole report has been checked again.

Presentation fallback notes for continuing a spoken recommendation when audience slides disappear, including cue sequence and rehearsal.
9 min read

Prepare presentation fallback notes for a display interruption

Suppose the audience loses sight of your slides halfway through an existing workplace presentation, while you can still speak and read your own notes. Which parts of the explanation can stand on their own? Prepare presentation fallback notes by finding sentences that depend on the audience seeing something, writing a spoken alternative where the underlying information is clear, and marking evidence that needs to be viewed later. The goal is an annotated version of the talk you already have. You are deciding what you can explain responsibly without the display, not trying to recreate every slide aloud. For presentation fallback notes , verify each step.

Workplace handover notes that distinguish completed work, the next step a covering colleague can take, and decisions still open.
9 min read

Write workplace handover notes for unfinished tasks

A colleague covering your work needs to know where you stopped, what they can do next and which decision still belongs to someone else. Write those answers while the task is still fresh. For an unfinished internal handout, that might mean recording the last section you revised, pointing to the working copy and stating that a factual question remains unanswered. A note saying “almost done” leaves the covering colleague to reconstruct all three. The aim is to give them a reliable starting point for the period you are away, without treating an unfinished draft as approved work.

Write acceptance criteria for a workplace handout by turning a broad brief into checkable completion conditions.
9 min read

How to write acceptance criteria for a workplace handout

A handout brief can sound settled until someone has to decide whether the draft is finished. One reviewer sees a missing instruction; another dislikes the arrangement of the page. Only the first concern may be supported by the brief. To write acceptance criteria , put each agreed requirement beside an observation a reviewer can make about the handout. Keep unanswered questions visible instead of turning a preference into a rule. The result is a short sheet that explains a decision about this deliverable, not a general verdict on whether the writing feels good.

file naming conventions: keeping recurring reports identifiable across versions.
9 min read

Plan file naming conventions for recurring workplace reports

Someone looking for a monthly equipment-use report usually knows the month they need, even if they do not remember when the file was last edited. A workable name should let that person distinguish the report subject, the period it covers and, when necessary, one revision from another. Consider a fictional set of reports for this exercise. Their names can be designed and tested without changing any real files or pretending that a promising filename proves which copy is approved.

Spreadsheet category mapping that reconciles different labels for the same intended category without changing the underlying records.
8 min read

Use spreadsheet category mapping to reconcile inconsistent labels

A category column can contain labels that look different even when the person who entered them meant the same thing. It can also contain similar-looking labels that point to different uses. If you replace both kinds of variation at once, the resulting worksheet may look tidy while concealing a decision nobody actually made. Spreadsheet category mapping starts with a narrower question: what does each original label mean under the categories you want this particular report to distinguish?