Most HVAC software still sizes ducts wrong. Here is what right looks like.
A 5-inch duct for 110 CFM is not a typo. It is what velocity-only sizing produces. Why rule-of-thumb duct sizing keeps failing, and what ACCA Manual J and Manual D require instead.
Ask a typical contractor platform to size a duct and it will usually do one of two things: look the answer up on a friction chart, or work it out from air velocity alone. Either can produce a result like a 5-inch duct for 110 CFM. That specification looks fine on a screen and leads to callbacks in the field.
Duct sizing is one of the few engineering tasks that HVAC software is well placed to get right. Most of it does not.
Velocity is not the whole story
“Size by velocity” is the shortcut most people learn: choose a target air speed and work back to a duct size. It is quick, and it is wrong often enough to matter.
Velocity describes how fast air moves through one duct. It says nothing about whether the system as a whole can deliver the required airflow to every room. Two runs at the same velocity behave very differently once length, fittings and the static pressure the equipment must overcome are taken into account.
Airflow is a pressure budget
Sizing ducts correctly means treating the whole system as a pressure budget.
It starts with the load. A Manual J calculation establishes how much heating and cooling each room needs, and therefore how much airflow. It works from real inputs: window U-factor and solar heat gain, orientation, insulation and infiltration.
Ducts are then sized to a friction rate, not a velocity. The equal-friction method in Manual D spreads the available static pressure across the whole duct system so that every run receives its share. A velocity cap is applied so that air never moves fast enough to become noise.
Total static pressure is counted. Every elbow, boot and length of duct costs pressure. If that is ignored, the fan cannot deliver the airflow the load calculation called for, and the rooms furthest from the air handler are short of air.
The two approaches compare as follows:
| Velocity-only rule of thumb | Manual J and Manual D | |
|---|---|---|
| Sizes from | A target air speed | Each room’s heating and cooling load |
| Run length and fittings | Ignored | Included |
| Total static pressure | Ignored | Included |
| Noise control | Incidental | Explicit velocity cap |
| Airflow to every room | Not assured | By design |
| Can the numbers be checked? | No, the result is taken on trust | Yes, with printed calculations and automated tests |
Why most software avoids it
It is difficult. A real Manual J and Manual D engine is a substantial piece of engineering, not a chart lookup. Most contractor platforms handle quotes and invoices and leave sizing to a rule of thumb or a separate tool. They run the business but not the work.
What doing it properly looks like
We built this into a contractor platform:
- A Manual J load calculation for each room.
- An equal-friction Manual D engine with a velocity cap and total system static pressure.
- An automated test suite and PDF calculation sheets, so the numbers can be checked instead of trusted.
- Automatic routing. The user places the air handler and the supply boots, and the system produces a correctly sized trunk-and-branch layout for supply and return.
The engineering stays behind the interface. The person using it sees a clean design. In the example above, the 110 CFM room receives a 7-inch duct instead of a 5-inch one. The build is described in the HVAC platform case study.
What to ask your HVAC software
If you are evaluating a platform, the sizing questions matter more than the feature list:
- Does it run a real Manual J load calculation per room, using window U-factor, solar gain, orientation and infiltration, or does it apply a rule of thumb?
- Does it size ducts by Manual D equal friction using total system static pressure, or by velocity alone?
- Does it apply a velocity cap so that runs do not become noisy?
- Can it show its work with numbers you can check?
- Does it route a usable trunk-and-branch layout, or only return a single figure?
In our experience, most platforms cannot say yes to the first four. That gap is where the callbacks come from.
The cost shows up as callbacks
Correct sizing is not an academic concern. It is the difference between a system that is quiet and comfortable and one that produces complaints, warranty visits and a back bedroom that is always hot. Each of those costs a contractor time and trust.
The methods are not a secret. ACCA published them decades ago. The rule of thumb survives because building the real thing is harder, not because it works.
Working on something in this territory?
If any of this sounds like the problem in front of you, tell us where you are and where you'd like to be. We'll come back with a plan within two business days.