Use role contacts without inventing people
The original fictional directory below uses example.com addresses for demonstration. Extension labels are invented display values, not numbers to call. It contains no real employees, personal phones, home addresses, or emergency and medical information.
| Role ID / work need | Department | Demonstration work channel | Last confirmed | Update responsibility / status |
|---|---|---|---|---|
| FD01 / Room booking | Front desk | booking@example.com; demo extension 101 | October 12, 2026 | Office coordinator; confirmed in fictional notes. |
| IT01 / System access | IT | access@example.com; demo extension 202 | October 13, 2026 | IT coordinator; confirmed in fictional notes. |
| ED01 / Copy review | Editorial | review@example.com; demo extension 303 | October 9, 2026 | Managing editor; confirmed in fictional notes. |
| FA01 / Facilities request | Facilities | [REPLACEMENT CHANNEL TO CONFIRM] | Previous holder departed; current contact unconfirmed | Office coordinator must confirm replacement. |
The Smartsheet employee-contact description allows fields such as department, job title, and location. This work-need routing design is original. Use only fields appropriate for your approved work directory; a different emergency-contact form is a separate record.
Keep identity, channel, and responsibility distinct
FD01 identifies a role; it does not identify whoever currently answers the shared booking inbox. In a real employee directory, give each person a stable identity too, and record the relationship between person and role using confirmed information. A staffing change should not silently leave a departed person as the current owner.
A work channel may be shared by a team. Label that fact rather than implying every address belongs to an individual. Keep update responsibility separate from the contact itself: the person who maintains the directory may not handle the work request.
Make no-match and stale entries useful
Filtering for system access should return IT01, not an editorial address with a similar-looking name. Filtering for a work need absent from the supplied directory should return No confirmed matching contact and identify how to request a correction through the existing approved process.
For facilities, retain the replacement-to-confirm state. Do not manufacture facilities@example.com to make the row look complete. A last-confirmed date helps someone inspect freshness, but define your actual review policy before calling an old date invalid.
If you build a local prototype, use filter/reset and entry-detail controls to inspect the supplied rows. Do not provide a demonstration button that claims to call, message, save a live directory change, or synchronize personnel records.
Copy a work-contact planning prompt
Draft an employee work-contact directory in US English.
Approved work needs and departments: [inputs]
Confirmed role/person IDs and relationships: [inputs]
Permitted work channels and whether shared or personal work channels: [inputs]
Last-confirmed dates, update owners, and known staffing changes: [inputs]
Directory review policy and approved original format: [inputs]
Organize entries so a colleague can find a contact by task or department. Keep stable identity, role, channel, last-confirmed date, update responsibility, and confirmation status distinct. Show missing replacements and no-match states without inventing people or addresses. Do not treat an old date as invalid without the supplied policy. Specify optional local filters/detail/reset with keyboard and text-state access; do not claim live calling, messaging, saving, or synchronization.
Use only authorized work information. Exclude home/personal/emergency/medical data from this work-directory example. For a public demonstration use fictional labels and example.com channels, never actual personnel records. Mark gaps [NEEDED: input]. Return the required maintained-directory format with any sanitized prototype explicitly separate.
Confirm the facilities replacement with the responsible owner and update the approved directory. Test one work need against its entry and one absent need against the no-match state. A useful contact list routes an actual question without disguising missing coverage as a complete record.
Optional: review a sanitized prototype in NOS
NOS can save and render a prepared HTML directory prototype with fictional work channels. Use that review to inspect task-to-contact routing; retain actual personnel data and updates in the approved directory or spreadsheet.