> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/sel-faq/using-the-software/general-operation/a-few-words-regarding-load-com.md). # A Few Words Regarding Load Combinations in SEL Why ENERCALC SEL offers many IBC and ASCE 7 load combination sets and how they differ from the Governing Code setting. ## Why does SEL provide so many options for specifying load combinations? First, you will notice that ENERCALC SEL includes prepopulated load combination sets for IBC and for ASCE 7. Next, you'll notice that the standard load combination sets provided with the program are categorized into sets for the IBC and sets for ASCE 7. This categorization reflects the nuanced differences between the IBC and ASCE 7 load combinations which existed prior to IBC 2024 and ASCE 7-22. For example, one important difference to note is that the ASCE 7 Strength Design load combinations always apply a load factor of 0.2 on Snow Load when combined with Seismic Load, whereas the IBC load combinations apply a factor of either 0.2 or 0.7 on Snow Load when combined with Seismic Load, depending upon whether the roof is of a configuration that *does* or does *not* shed snow. Another subtle difference creeps into the Allowable Stress Design combinations with regard to the percentage of Snow Load to use in combination with Seismic. The IBC load combinations require a factor of 0.75 on Snow Load in combination with Seismic Load when the flat roof Snow Load exceeds 30 psf, but they do not require the use of *any* Snow Load in combination with Seismic when the flat roof snow load is less than 30 psf. This is in contrast to the ASCE 7 Allowable Stress Design combinations which require a factor of 0.75 on Snow Load in combination with Seismic regardless of the magnitude of the snow load. It would seem that the load combinations stipulated in IBC would govern over those set forth in ASCE 7, because IBC is generally the Governing Building Code, which then refers to ASCE 7 as a referenced standard for specific items (such as special load combinations incorporating seismic load effects including overstrength factor). However, the issue gets murkier on two accounts: 1. Not all jurisdictions adopt IBC as their Governing Building Code. So in jurisdictions that have a different Governing Building Code, it is possible that ASCE 7 load combinations *could* be referenced. 2. IBC identifies ACI 318 as a referenced standard. ACI 318 includes its own load combinations (which happen to match ASCE 7 load combinations). IBC does not specifically amend or omit that portion of ACI 318. So in a sense, there is a bit of a contradiction requiring some judgment on the part of the designer. Given the multitude of possibilities, it was decided that we could best serve the user base by providing all of the basic load combination set templates that are likely to be needed. Of course, there is always the ability to edit those templates or create new ones for project-specific needs or to suit office standards. ## What is the Difference Between Load Combination Sets and Governing Codes in ENERCALC? Users should understand that the selected load combination set is a distinct setting, separate from the Governing Code. These two are only superficially related, often sharing similar names but not functionality. ENERCALC does not automatically select a load combination set based on the chosen Governing Code because there is no direct correlation between the two. For example, users might create a custom load combination set like “ABCCoLoads” as an office standard. Therefore, even though some preloaded load combination sets in the program may reference the IBC version they were developed from, this is merely a naming convention. It remains crucial for users to choose the load combination set that best suits their specific calculation needs. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enercalc.com/sel-faq/using-the-software/general-operation/a-few-words-regarding-load-com.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.