Working with the panel, the programmer solicits and advises broad goal statements which will guide the rest of the programming process. Each one of the following categories is a goal that should be addressed:

* Organizational Goals: What are the goals of the owner? Where do they see their organization headed? How will this architectural project fit into this broad picture?

* Form and Image Goals: What really should be the cultured and psychological impact of the design? How should it relate to the environment? Should its image be like or distinct from its neighbours from other buildings belonging to the owner that are found somewhere else? Are there significant cultural and context implications?

* Function Goals: What major functions will occur in the building? How many folks are going to be housed in the building? How might the building design augment or impact occupant interactions?

* Industrial Goals: what's the total project budget? What's the disposition toward primary costs against long-range operating and upkeep costs? What level of quality is desired? What's the approach toward conservation of resources and supportability (energy, water, and so on)?

* Time Goals: When is the project occupied? What kinds of changes are anticipated over the next five, ten, fifteen, and twenty years?

* Management Goals: These goals aren't so much a problem of the character of the project as they're the circumstances of the owner, clients, programmer, or architect. For instance, maybe the schematic design must be finished in time for a judicial request application cut-off point.