Non-Standard Options

About Non-Standard Options

A non-standard option (NSO) is a change requested by a buyer that is not offered on a published option list. For a non-standard option to be built, one of the following may be required:

  • A deletion in quantity and/or material from the base house takeoff

  • An addition in quantity and/or material to the base house takeoff

  • Both deletions and additions in quantity and/or material to the base house takeoff

Whenever possible, maintain full and complete takeoffs for non-standard options in the same way that plan takeoffs, community takeoffs, and standard option takeoffs are maintained. This allows a user to:

  • Create purchase orders or Schedule Cs that correctly reflect the material and/or labor associated with the NSO.

  • Historically document quantities and materials used to build a NSO for field audits.

  • Uniformly estimate and price duplicate NSOs that may be requested by multiple buyers.

  • Easily add the NSO to the standard option list if it is profitable and proves to have a buyer perceived value.

Note

While BuilderZen will allow you to enter a non-standard option in a lump sum, turnkey type entry at the job budget level, this method is not recommended.

Rules for Managing Non-Standard Options

Follow these rules for managing non-standard options:

  1. In the Master Data section of the system, create a Choice Category named "NSO" and a Choice named "Non-Standard Option."

Note

The naming must be able to be used across all NSOs. It may be necessary to create more than one NSO if the retail multiplier is applied and can change from one option to the next.

  1. Each non-standard option takeoff should be maintained in its own layer.

  2. Users should have a logical naming and layering scheme for NSOs.

Naming and Layering for Non-Standard Options

There are two strategies for layering non-standard options:

1. Layer NSOs in a Single Plan

A user can name a plan NSO and layer all NSOs within a single plan, enabling all NSOs to be viewed in one location. Layers must be named in a consistent manner so that, as the number of records increases, it is easy to locate specific NSOs.

Example

NSO (Plan Name) Layers:

  • Structural-Rear Extension 2 Ft.-Plan 2000
  • Structural-Rear Extension 2 Ft.-Plan 2500
  • Structural-Bay Window -General

2. Layer NSOs by Plan Type

Place plan-specific NSO layers in the specified plan and non-specific NSO layers in the Plan General. This strategy requires the user to open each plan to view the NSOs for that plan; however, the number of NSOs that must be filtered or sorted is smaller.

Example

Plan 2000

  • Layer: Structural-Rear Extension 2 Ft.-Plan 2000

Plan 2500

  • Layer: Structural-Rear Extension 2 Ft.-Plan 2500

Plan General

  • Layer: Structural-Bay Window.-General

Creating Takeoffs for Non-Standard Options

The takeoffs for NSOs are entered using the same steps as plan takeoffs or community takeoffs. By building NSOs in this way, purchase orders, Schedule Cs for Options, and Option Floorplans can be produced with that itemize specific material and labor costs. Follow the rules for entering takeoff items, but enter the items directly into the NSO layer.

Last Updated: 9/28/2018, 7:06:42 PM