Define the core project information that will be inherited by all Work Packages.

Pick the key project leaders from the people assigned to this project. Choosing a user account (rather than typing a name) is what lets the Work Package Creator offer them as an owner and lets the suite email them — so add anyone missing to the project first, in the Admin Console.

Two roles are required on every package. They default to Superintendent and Foreman — rename either to fit your project (e.g. a BIM SOP uses BIM Coordinator and Construction Lead). Add more below.

Enable the WP types your project will use. Add any special rules and the roles required to approve WO completion. Spec Section is filled onto every work package of that type automatically, so nobody types it per package.

Define how Work Packages are formatted, sized, and issued on this project. The choices here decide how the Work Package Creator behaves for every package.

Decide whether a single package can carry more than one discipline (e.g. a chiller skid needing Mechanical install + Electrical wire-pull + Tech terminations), or whether each discipline gets its own package. This drives whether the Creator shows per-discipline scope sections and the Split by Discipline button.

A Work Package should be a manageable, trackable chunk of work — typically a 1–2 week assignment. The Creator warns the planner when a package exceeds the ceiling so it can be broken down.

Establish project-wide quality expectations that cascade to every Work Package.

Select the tools used for construction tracking and commissioning. These can be the same or different systems.

Comes pre-sequenced with a typical install flow. Drag the ⠿ handle to reorder steps, edit labels inline, add a QC hold gate, or remove any step.

Constraints are readiness items that must be cleared before a WP can be issued.

Link to key documents and systems that WP authors will reference.

Building, floor and sector for this project. The shape of a location differs per job — on some, floors within one building behave like separate buildings and are the unit of both execution and cost tracking — so it is configured here rather than assumed. Work packages pick from this list, and cost rolls up by it.

Turn off the parts of a work package this project does not use. A section that is off does not appear in the creation form, in the work package itself, or in the PDF export. Nothing is deleted. Anything already captured stays on the package and comes back intact if the section is turned on again — which is what makes this different from removing a field.