Create a Resource Directory Verification Checklist
Use a repeatable checklist to track who provides a service, whom it serves, and when details were last checked.
Build a record for each service
A directory entry should help a person decide what to do next. Record the provider’s name, service description, location or service area, contact method, and hours. Add eligibility information only when it is available from a reliable source, and identify whether it is confirmed or awaiting a check. For a service that operates across multiple locations, distinguish the main office from the place where assistance is delivered. A clear record prevents a phone number or mailing address from being mistaken for a walk-in site.
Track the source and date
Every changeable detail should have a source and a date checked. A provider’s own current page or direct confirmation may support hours, while a public directory may be helpful for discovering a program. Record the exact page, phone contact, or other method used, along with the date and the person or role that completed the check if appropriate. For example, note “hours checked on provider page, March 4” rather than simply labeling them “current.” A date gives later reviewers a sensible starting point.
Flag uncertainty clearly
Use simple status labels such as confirmed, needs follow-up, or not stated. If a listing omits eligibility details, do not translate that absence into “everyone eligible.” If a call goes unanswered, record that the contact attempt did not confirm the information. Separate verified facts from helpful but unconfirmed notes. This distinction matters when a reader may travel across town or rely on a service for an urgent need. Avoid wording that suggests certainty when the underlying source is incomplete, old, or indirect.
Set a review routine
Choose a review interval that fits the directory’s purpose and the rate at which details tend to change. Establish a consistent process: select entries due for review, check the listed source, contact the provider if needed, record the result, and update the public version. Keep a change log so reviewers can see what moved and when. When a service closes or pauses, mark the entry clearly rather than deleting the record without explanation. A reliable checklist turns maintenance into a manageable task instead of a last-minute cleanup.
Spotted something we should look at? Suggest a correction.