Directoryz

Keep a useful bulk import audit log

An audit log should identify what changed and how to investigate it. A timestamp alone does not explain the source or mapping.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Record the file name, source revision, mapping, affected count, reviewer, and notable exceptions. Store the pre-import snapshot nearby.

Worked example · illustrative

What this looks like

An entry can state that 80 provider records received reviewed website URLs using mapping revision two.

Before you move on

Could another editor identify the exact batch responsible for a changed 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. Keep an untouched source copy.
  2. Test changes on a small sample.
  3. Compare imported records with the original data.

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 →