Supplier directory: knowing who you buy from before you need to
A supplier directory records who you buy from, who owns the relationship and what happens if they stop. What to keep in it, and the questions it should answer in a hurry.
A distribution list outlives the reason it was created and quietly becomes a liability. How to keep them owned, accurate and few — and when an alias is the wrong tool entirely.
Every company has a distribution list created for a project that ended in 2023, still receiving mail, still including two people who left and a contractor nobody remembers engaging. Lists are useful precisely because senders do not have to think about who is on them — which is also why they decay invisibly, and why the decay only becomes visible when something confidential reaches somebody it should not have.
A list whose members were added individually is a snapshot of who was relevant on the day it was made. A list derived from something that changes — the team, the role, the project assignment — updates itself when people move, which is the only mechanism that survives contact with a reorganisation. Where derivation is genuinely impossible, the compensating control is a short review cycle and an owner who is asked rather than reminded.
Audit who can send to an all-company list before you audit who receives it. The receiving side causes embarrassment; the sending side is how a convincing phishing message reaches everybody at once with internal legitimacy.
Three cases. If recipients need to reply to each other, you want a channel rather than an alias — threaded replies on a distribution list are how a hundred people watch two of them negotiate. If the audience is external, you want a mailing tool with consent records and unsubscribe handling, because a list has neither. And if the message is a status update that goes out weekly, you want a written update in a known place; a list guarantees delivery, not attention.
Ettex Contacts holds the register that makes this maintainable: lists with an owner, purpose, membership basis and review date, with external addresses marked as such. Where a list is really a contact segment that gets mailed, the consent and source fields matter more than the membership — which is the distinction a plain alias cannot make.
A named person, usually whoever is accountable for the audience — the team lead, the project manager. A list owned by a department is a list owned by nobody.
Quarterly for anything crossing team boundaries, and immediately after any departure or reorganisation. Derived membership removes most of this work.
Avoid it where you can. Where it is necessary, name the list so that senders can see it reaches outside the company before they press send.
A supplier directory records who you buy from, who owns the relationship and what happens if they stop. What to keep in it, and the questions it should answer in a hurry.
A contact import is the one moment you can fix a list cheaply. What to clean before loading, how to map fields, and why consent and source have to travel with the records.
A stakeholder map sorts the people around a project by influence and interest so attention goes where it changes the outcome. How to build one, and the mistakes that make it decorative.