The Directoryz field guide

Teams and maintenance

Keep a directory accurate as people, records, and responsibilities change.

13 practical guides1 topic

Find a guide13 guides shown

Onboard a new directory editor

An editor needs examples and decision rules, not only access to the dashboard.

Workspaces should reflect ownership and access needs.

A handoff should preserve what was checked and what remains unresolved.

Review frequency should reflect how quickly information changes and how important it is to visitors.

A failed link check needs interpretation.

An old review date is a signal to inspect, not proof that a listing is wrong.

A scorecard should make review criteria visible, not create a mysterious ranking.

An incident log helps prevent repeated routing or content mistakes.

API keys need clear ownership and purpose.

A webhook handoff should explain the event, receiving system, and failure owner.

Automation works best on well-defined decisions and repeatable checks.

A monthly review should connect activity with listing quality and unresolved work.

A runbook makes routine work repeatable when the usual operator is unavailable.