The defining of a standard is more important than what the standard actually states. The end result is consistency. In large organisations it can be difficult, the key is to involve everyone in the discussions. You want to come to a common consensus and then implement it rapidly. It might take a long time to reach a consensus, but lots of interesting things will come up. Also it is important to make it clear that the guys doing the coding are responsible for defining the standards, the manaqers should act as trainer and enablers making sure new recruits are aware of their role to maintain, follow and help develop those standards. You must make it clear that you are not trying to tell people how to code! Any decent programmer should secretly love the thought of working with and developing standards even if they oppose resistance to it initially. The key is to highlight the fact that they are responsible for the definitions, its not going to be a management decision forced upon them. A good way to start is to have some collaboration perhaps on a wiki. Thus allowing flexibility in the generation of the standards and also to help get people involved. Ultimately 1 person has to be accountable and responsible for managing the "released" standards. Also it is good to start with something. Find a good general standard and get peoples feedback on it, then try to implement it. Well I hope that gives you a few ideas. It is more of a cultural shift you are trying to achieve. Working from, maintaining and constantly improving standards is a hugely powerful way of working. It is imperative for any company to focus large amounts of time working ON the way they do things rather than constantly firefighting - working in it. The "we just haven't got time now, we're too busy" scenario never ends. The key is to offset the short term, with a much longer term vision! Steve O'Brien A successful person isn't necessarily better than her less successful peers at solving problems; her pattern-recognition facilities have just learned what problems are worth solving. www.newicon.net