FileVision

Team reviewing paper documents beside laptops at a shared desk

Choose the Required Index Fields Your Team Will Actually Complete

A shared drive becomes searchable only when the people who file documents agree on a short list of required fields. Before you expand an index, decide which fields your team will actually complete on every new file.

This checklist supports a FileVision document-management conversation. It does not replace legal hold or records-retention policy.

Start with retrieval questions, not every possible field

List the questions staff already ask: whose project, which property, which year, which document type. Fields that never answer a real question become empty optional clutter. Cap the required set so it is trainable in one sitting.

Name owners for each required field

If nobody is responsible for “project code,” it will not be entered consistently. Write the role, not only the field label. Indexing work should match those owners rather than assuming every user fills every box.

Separate security tags from descriptive tags

Access control fields and descriptive keywords solve different problems. Mixing them encourages people to skip the hard field or to overshare in the easy one. Keep a one-page field dictionary beside training so new hires do not invent synonyms.

Pilot on one document type before rolling out widely

Choose a high-volume type, measure completion for two weeks, then adjust labels. A failed pilot is cheaper than a firm-wide empty index. Tell people what to do when a required field is unknown at filing time — a documented “unknown + follow-up owner” process beats silent blanks.

  • Document classes in scope for this phase
  • Retention owners named in writing
  • Saved searches staff will actually use
  • Audit-trail fields required at approval

FileVision’s document management and data capture solutions and the ALFO document management platform are the reference pages for how those fields show up in day-to-day filing.