I'm not sure I understand your term "add-ins". Our templates do not take much space at all as we don't save the spreadsheet for each and every use. For example, when starting up a new project, we need to calculate the required wind loads that the particular building code requires. We bring up the previously created spreadsheet template (which has specified areas of required input such as wind speed, exposure, etc.). We enter the input, the built-in functions calculate the relevent wind loads for walls, roofs, towers, etc. and we print it out to include in our calculations.
In this case, there is no standard "table", just a series of equations, if-then checks, and a nice display of the input/output.
Another sheet we use calculates the capacity of a standard double angle connection using AISC tables 9-2, 9-3 and 9-4. We didn't enter the AISC tabular capacity values. Instead, we designed the spreadsheet to actually do the calculations for each type of beam/angle combination. The beam data is on an attached worksheet that includes all the relevent shape data. Again, this doesn't take up a lot of space on the disk as we don't save repeated copies of the template. By printing out the template for each use, and including all the input data, we can re-create the same sheet later, if needed.
One other valuable benefit from using this spreadsheet template that I didn't mention before: To actually write a spreadsheet (or a program) one must have a very exhaustive understanding of the function you are trying to develop. In writing a wind load template, for example, I came away from the effort with a much better knowledge base of the required code provisions and design processes. This is because the template must apply to a number of different uses, condition, input values, etc., and therefore must be written to encompass the full logical process required. All of the what-ifs, if-thens, must be understood. Great self-learning tool!
