I am looking for suggestions on how to document contact lists in Confluence

[Kathy Parker]

The organization has many technical and stakeholder contact lists.  We are trying to transition those documents into Confluence and seeking recommendations for best practices.

[Robert Reiner _smartics_ · Accepted solution]

We have page blueprints for persons, roles, organizations, and stakeholders. Stakeholders map persons to roles for particular projects.

So we have a single document for each person. These have properties so that we can create address lists in tabular form.

I'm a fan of having each thing described in its own document and then having other pages to collect information from those documents (like the organization a stakeholder works for, phone numbers, or homepages) in tabular form.

[Kathy Parker]

Thank you for a prompt reply.  Are the templates you references add-ons?  If you would you be able to provide the Blueprint name?  I am looking through my list and don't see which reflect your description.  

[Robert Reiner _smartics_]

I'm sorry, I thought you are looking for a conceptual approach. Since I know many who prefer to have a long table of information, I wanted to provide a positive view on the one-thing-on-one-page approach. :)

We use our own blueprints which are based on our projectdoc Toolbox. The projectdoc Toolbox is a commercial add-on I am one of the authors (biased alert!).

In Web of Documents we describe the relationship of the document types I mentioned above and provides links to further information.

Maybe you can use some of the ideas for your own blueprints.