Skip to main content
Share / Export

JC Jobs

Company Tracker action: implementation-setup-jc-jobs Milestone: Job Cost / Module Setup (milestone_id=5, core_milestone_id=2) Order: 10 Estimated duration: 2 hours Typical owner: Controller

Purpose​

Create JC jobs with contract link, project manager, liability / insurance / fixed-rate templates, phase lock, compliance, reviewer, and optional Analytics, Roles, and Workflow. Soft/hard close is controlled on Contract Close and Company Parameters, not as day-to-day fields here.

Prerequisites​

  • Contracts and related masters ready (JC Contracts, JC Project Managers, liability / insurance / fixed-rate templates as used).
  • If using Analytics, configure HQ Project Structure Types first. If using job Roles, set up HQ Roles first.
  • Price escalation needs HQ Escalation Index / Materials when MS oil-price tracking is in use.
  • Job numbering settled in Code Format Design; phase-lock policy agreed before load.

Vista configuration article​

See the detailed Vista guide:

Setting Up JC Jobs

Field meanings and form steps live there. Do not restate them on this page.

Implementation guidance​

Decide (client / kickoff)​

  • Load scope (hard rule): all open jobs and any job with activity in the year (with its contract) so WIP ties to GL. See JC Contracts.
  • Job numbering: follow the scheme already decided in Code Format Design (do not re-litigate it here).
  • Purge: do not purge JC job data. There is no good implementation reason to purge; keep history.
  • Phase lock: use Locked when the client wants to stop people from posting to phases that are not on the original budget / estimate. Locked limits transaction posting to phases already on the job (Job Phases, Original Estimates, PM, or previously used). Unlocked allows any phase from JC Phases.
    • Locked does not fully block adding phases on Job Phases, but the intended way to introduce new phases is a change order (pending CO, approved CO, or a CO entered directly in Job Cost) — not ad-hoc posting to new phase codes.
  • Templates on the job:
    • Liability: required. Every job needs a liability template — at least one company All Jobs template. Add alternate liability templates when rates differ by state or type of work.
    • Insurance: only when phase-based insurance calculation is in use.
    • Fixed Rate: only when fixed rates must differ by which job is charged (see Fixed Rate Template).
  • Compliance / invoice reviewer groups when in scope.
  • Analytics include/exclude, Roles, Workflow (job-level Workflow overrides company / module defaults), and Material Sales escalators when in scope.

Load / accept (implementation defaults)​

  • Load jobs linked to contracts; set PM, templates, compliance, and reviewer as in scope.
  • Prefer TAD for bulk job bring-live when volumes are large. Use Job Copy for similar jobs after one gold job exists.
  • Once a job has activity, deletion generally requires JC Contract Purge. Unposted jobs can be deleted only after related phases, cost types, and estimates are removed. Deleting a job also removes related PM records.
  • Job numbering lives in the Code Format Design playbook — link there. Do not purge job history.
  • Accept means each go-live job has the correct contract link and controls before phase / estimate load.

Tips and gotchas​

  • Job bring-live pack order: Contracts → Jobs → Job Phases → Original Estimates → Contract Items (open + year-activity scope).
  • Phase lock Locked: keep posting on the original estimate list; new phases should arrive via change order, not on-the-fly posting.
  • Job templates: Liability always (All Jobs + variants for state/work); Insurance only if phase-based; Fixed Rate only if rates differ by job.
  • Load all open jobs and any with year activity so WIP ties to GL; same rule as contracts.
  • Exclude from Analytics must be set explicitly when a job should stay out of Analytics.
  • Phase lock surprises field users who expected free posting to any master phase. Document the policy in training.
  • Job-level Workflow silently overrides company defaults. Audit a few go-live jobs before cutover.
  • Soft/hard close status is not maintained as a casual setup field here. Point close process owners to Contract Close.

Done when​

  • In-scope jobs exist with contract links and accepted PM / template / lock settings.
  • Ready for JC Job Phases and estimate load.