Porches and attached buildings counted correctly

Every porch, lean-to and attached building on a SmartBuild job is parsed with its own dimensions, and an enclosed attached building counts as building square footage rather than porch area.

What it is

Structured parsing of SmartBuild's Sheds array: side, depth, run, corner wrap, leg square footage, an enclosed flag and a nested flag. Open structures sum into the customer-facing porch area; enclosed ones sum into building square footage.

Also called: porch square footage · attached building · wraparound porch area · sheds array

See it
Porches and attached buildings counted correctly
Area
Integrations
Group
Estimating
System
SmartBuild Integration
Solves
3 named problems
01Shed Type 0 is a solid-walled attached building; Types 1 and 2 are open porches or lean-tos — verified against real jobs, where Type-0 records carry zero open-wall sections and Type-1/2 carry dozens.
02An attached building carries its OWN porches in a nested Sheds array, so the parser recurses even past an invalid parent or they vanish from every total.
03Leg square footage is deliberately the SAFE lower bound: each leg counted once, and a wraparound's shared corner never auto-added, because both adjacent legs report the same corner and it cannot be derived without double counting. The corner is left to a builder-confirmed override.
Job detail listing each attached structure with its side, dimensions and leg square footage, with enclosed ones marked and totalled separately. Sample data — no customer information appears here.
How it works
  1. 1Shed Type 0 is a solid-walled attached building; Types 1 and 2 are open porches or lean-tos — verified against real jobs, where Type-0 records carry zero open-wall sections and Type-1/2 carry dozens.
  2. 2An attached building carries its OWN porches in a nested Sheds array, so the parser recurses even past an invalid parent or they vanish from every total.
  3. 3Leg square footage is deliberately the SAFE lower bound: each leg counted once, and a wraparound's shared corner never auto-added, because both adjacent legs report the same corner and it cannot be derived without double counting. The corner is left to a builder-confirmed override.
  4. 4Float noise from the API is rounded to two places.
Why we built it

Porches and attached structures were not counted at all: the square footage read fields that do not exist on real jobs and came back zero every time, so every porch a shop had ever sold was missing from its own totals. The correction then swung the other way and treated every attached structure as a porch, which dropped a 28x42 enclosed attached building into the porch total. Attached structures are now read from the real job data and classified by what they actually are, so square footage and porch area are each right on their own terms.

The problem
  • Porch and attached-building areas silently reading zero.
  • Enclosed structures inflating the porch total.
  • Wraparound corners double-counted or ignored without a decision.
Sound familiar?
What you get
Porch and building square footage are separated correctly.
Nested porches on attached buildings are included.
Wraparound corners are a builder decision, not a guess.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →