Directoryz

Write unambiguous listing field definitions

A field name alone may not tell contributors what belongs in it. Definitions keep different editors from storing different concepts in the same column.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Give each field a plain-language meaning, an accepted example, and an exclusion. Keep those definitions with the import or submission instructions.

Worked example · illustrative

What this looks like

Service area can mean locations served, while office location means the physical base. Treating them as one field makes remote providers difficult to classify.

Before you move on

Would two editors enter the same kind of information for this field?

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. Choose a representative set of listings.
  2. Record the source and meaning of each field.
  3. Review the public result before applying changes widely.

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 →