Skip to main content
Share / Export

Configuring PM Document Types

PM Document Types creates and maintains document types that classify documents inside a document category (for example Field Order under Pending Change Order). Types drive sorting/filtering on forms and reports, and for PCOs they default impact, add-ons, pricing, projection inclusion, and which dates are tracked.

Default document templates and distribution defaults are assigned from related Create & Send forms (Assign a Project Template; PM Assign Distribution Defaults), not as fields on this form. Numbering is not covered on these help topics.

Before you start​

  • Know which categories you need (Pending Change Order, Submittal, RFI, Other Documents, etc.).
  • For PCO types: decide projection inclusion, default add-ons/markups, pricing method, and Estimate / SL / PO / Contract defaults.
  • Projection inclusion also depends on the PCO’s Status ID Projections Option in Configuring PM Status IDs.

Steps​

  1. Open PM Document Types.
  2. Enter Document Type (up to 10 characters) and Description (up to 30).
  3. Select Document Category. Choose Pending Change Order only for types used on PCOs — that enables PCO-only fields.
  4. Check Active so the type can be assigned to new records (RFIs, PCOs, etc.). Clearing Active does not stop processing documents already using the type; lookups on PM Document Tracking / History / Transmittals hide inactive types, but history still includes them and transmittals can still attach existing docs of those types.
  5. For PCO types, set:
    • Include in Cost Projections (About page may say “Include in JC Projections”)
    • Include Default Add-ons and Markups
    • Pricing Method (defaults the PCO Info tab)
    • Estimate, SL, PO, Contract checkboxes (defaults on the PCO Info tab; About page may say Budget / Subcontract / Purchase Order)
  6. For PCO types, name header dates (PCO Date 1/2/3) and item dates (Item Date 1/2/3) up to 30 characters each, and set Show in Grid. Blank description with Show on shows as Date 1 / Date 2 / Date 3.
  7. Save. Use Other Documents for miscellaneous types (letters, contracts, POs, blueprints).

Example types: FO Field Orders (PCO); SHOP / SAMPLE (Submittal); CONT / PO (Other Documents); COMPACT / ELECT (Test / Inspection Logs); SITE / STRUCT (Drawing Logs). PCO examples: ICO (owner/architect), RCO (contractor/sub), FO (field order — often approved into an ACO after work).

PCO projection and add-on rules​

  • Include in Cost Projections: if the status’s Projections Option is None, the PCO is excluded from JC Projection Future CO / JC Revenue Future CO even when this box is checked. If the option is Display in Projections or Display & Calculate in Projections, this box must also be checked. Unchecked excludes the type from cost and revenue projections. When included, PCOs appear on Future COs in PM Cost Projection Editor and related JC Future CO columns (units/amounts).
  • Include Default Add-ons and Markups checked: a new PCO with Estimate, SL, or PO checked pulls project add-ons from PM Project Add-ons plus markups for cost types on the CO. Unchecked: an internal PCO only gets add-ons if Contract is checked; markups start at 0.00.
  • Estimate / SL / PO / Contract / Pricing Method are defaults only — users can change them on the PCO.

Category notes​

  • RFQ category applies only to the enhanced PM Request For Quote form (not RFQ created on PM Request For Quote - 6.6).
  • Submittals - 6.5 is for PM Submittals - 6.5; types created before 6.6 were auto-assigned that category.

Notes​