Directoryz

Write review notes another editor can use

Review notes should capture evidence and unresolved questions. Personal shorthand can make a listing dependent on one editor's memory.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Record the checked source, decision, and next action in plain language. Avoid storing unnecessary personal details in notes.

Worked example · illustrative

What this looks like

Documentation confirms one-way export only; revise the two-way sync description before approval gives the next reviewer a clear task.

Before you move on

Could another editor continue the review without contacting you?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Explain the information required before submission.
  2. Review facts separately from presentation.
  3. Give contributors a clear next step.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →