Building a requirements management program can be a daunting task. If someone we to ask you to establish such a program on a large project, how would you go about it? What would the program have to do address the challenges that are typically faced on a project? When I was asked to develop two such programs for a project (one to manage technical requirements and one to manage programmatic requirements), I turned to the literature expecting to find a paper or book on establishing a coherent program. The literature is full of writings about the attributes of good requirements and managing databases. There is ample information about a few other subtopics such as requirements elicitation and analysis. However, there is little information about how to specify and develop an entire program that is integrated with development processes. This paper describes the challenge of building a requirements management program from scratch and proposes a standard list of program functions necessary for an effective program.