1. Why can I not Margin Industries I once was able to apply Margins to?

The only marginable industries are Retail and Wholesale Industries.  You are no longer be able to margin non-retail/wholesale industries because the margins that were being used were simply for the Industry’s margin on its “primary Commodity.” This change is to ensure more accuracy. Now, when the item purchased is known, a Commodity Output Event should be modeled using the purchased item as the Specification and Margins can be applied if appropriate. 


2. Where Margins can be applied, how do I apply Margins?

The options for applying Margins or not applying Margins are now labeled “Total Revenue” and “Marginal Revenue”, respectively. More information can be found in the article Margins & Deflators.


3. Why are my Induced results different in the newest release of IMPLAN?

Seeing differing Induced Effects when comparing the results of the same Impact on the same geography and year of data in the new release of IMPLAN to past versions, is due to methodology improvements to the IMPLAN Social Accounting Matrix (SAM). One of the largest changes we've incorporated is to use gross commuting flows as opposed to net commuting flows. This means for all regions where there is both in-commuters and out-commuters, the In-Commuting Rate will be larger in the current version of IMPLAN (app.implan.com), reducing Induced Effects in the Impact Results.

This is because in these cases, total in-commuting dollars is always larger than net in-commuting dollars because net in-commuting dollars = total in-commuting dollars - out-commuting dollars.

Previously, net in-commuting dollars were divided by total Employee Compensation (EC) in the region to calculate an In-Commuting Rate. Now total in-commuting dollars are divided by total EC to generate an In-Commuting Rate. For single-region analysis, the In-Commuting Rate is applied as a reduction, along with the Payroll Tax reduction, to any Employee Compensation value (in any Event that generates Employee Compensation to the region) before it is run through the region as Household Income. This reduction represents the assumed leakage from workers in the Study Area leaving the Region to go home, where they spend their money. Some of the other SAM changes could have a positive effect on Induced Effects, so the overall effect won't always be a reduction in Induced Effects.

Multi-Regional Input-Output (MRIO) analysis uses commuting data to track where in-commuters live so there is no change to the way MRIO results are calculated.

Other SAM changes include:

Previously, sub-national SAMs consolidated all commuting in the Domestic Trade account. Now, foreign commuting stays in the Foreign Trade account. Some payments to government have been reclassified, e.g., rents and royalties are paid from Other Property Income (OPI) to government, rather than from Taxes on Production and Imports (TOPI) to government. Such changes serve to align IMPLAN SAMs with the Bureau of Economic Analysis’s (BEA) National Income and Product Accounts (NIPAs) and to improve the quality of tax impact results.


4. How do I import Events from Excel?

The feature to import the Event Template into IMPLAN is outlined in the article Using the Event Template


5. How do I search for my Industry using a NAICS code or description?

Currently you can search for Industries by NAICS codes and descriptions using this Excel file


6. I recently ran an MRIO analysis that is identical to one I have run before. But, this time I got different results. Why?

When using MRIO, there is a less burdensome (but still realistic) assumption on the system with regard to trade between regions. Specifically, the threshold at which an MRIO analysis in IMPLAN considers the dollars of Commodities and/or Employee Compensation being traded between regions to be sufficiently small and subsequently stops processing any further rounds of calculations. Explicitly, we changed this threshold from $0.01 (one penny) to $100 (one hundred dollars).

This is to say, for example, that if the effects of trade between Region A and Region B are being calculated, IMPLAN will stop processing calculations once it reaches the point at which less than $100 of Commodities and/or Employee Compensation are transferring between them.

This means that you will see more conservative estimates. In instances in which this change does affect a study’s results, how big will the difference in them be? Well, we ran back-to-back MRIO analyses to find out; one prior to changing the threshold, and one afterwards. We ran two hypothetical 3-region MRIO analyses in which a $10 million change in total Output was modeled. The difference in results between the first and second analysis equated to < 0.5% (less than one half of one percent).

We recognize that some analysts may still ask, "Well, my Direct Effects are far less than $10 million. Wouldn't the observed change in results be greater in scenarios where Direct Effects (in this case, a change in total Output) are smaller?" Well, we ran back-to-back MRIO analyses to test this as well. We ran two more hypothetical MRIO analyses (with 2 regions this time) in which a $190,000 change in total Output was modeled. In this instance, the difference in results between the first and second analysis equated to approximately 0.5% (again, one half of one percent).



An MRIO study requires a much higher number of calculations than non-MRIO studies as the trade of all the sectors are analyzed between regions. As such, we expect these types of studies to take longer to finish than non-MRIO studies. The amount of time it takes to finish will depend on the number of events and the number of groups that the user has entered. The expected time for an MRIO analysis to finish can range between a few minutes for smaller studies to several hours for larger studies.

The best practice for MRIO and other larger studies is to leave yourself lots of time to run the analysis! Keep an eye on the Progress Panel in the lower right corner of the Impact screen that will provide notification of the progress of the study. Notification will be provided if the study has timed out. That can happen for various reasons with the most common being that the size of the study exceeds our processing limits. While we have made great strides in increasing the processing power, you still may see longer wait times. That said, in order to minimize wait times or potential for "timing out" with regard to processing performance, we suggest limiting your MRIO analyses to a) include a maximum of ten Events and b) limit your number of combined Groups to four or five. If your MRIO analysis absolutely must include more than ten Events or Groups which contain more than three Combined Regions, we suggest that you contact your Customer Success Manager support@implan.com to personally discuss potential strategies for managing the size and/or complexity of your study. 



Groups with more than 250 events may not complete or may take a long time to complete. We are still exploring, testing, and discovering the current limits of the tool's processing power and the amounts of data that it can communicate to our servers at any one time. That said, in order to minimize wait times or potential for "timing out" with regard to large studies, we recommend keeping the number of Events in your Groups to less than 250. If your study requires more, contact your Customer Success Manager by emailing support@implan.com to personally discuss potential strategies for managing the size and/or complexity of your study.



The user kicks off a large study and wants to run a second study while the first is processing. Even if the second study is a small study, it doesn't finish in the expected time frame. The best practice for larger studies, including MRIO that we expect to take longer, is to plan ahead. Run smaller studies first since studies that are kicked off after a large study get placed in queue and will not start until the large study has completed. This is to prevent too much data hitting the server at once and crashing the system. The second study analysis will automatically begin without any further action from the user.

Updated March 11, 2022