JC Project Managers
Company Tracker action: implementation-setup-jc-project-managers
Milestone: Job Cost / Module Setup (milestone_id=5, core_milestone_id=2)
Order: 4
Estimated duration: 0.5 hours
Typical owner: Controller
Purpose
Maintain the Job Cost project-manager list used on jobs for assignment, report filtering, and cost-projection initialization by PM. This is a JC-only master, not a Payroll employee validation list.
Prerequisites
- Know which managers will be assigned on go-live jobs.
- Contact details ready if the client wants phone / email on the master (optional for posting).
- Agree whether historical / inactive PMs are needed for reporting or only active go-live names.
Vista configuration article
See the detailed Vista guide:
Setting Up JC Project Managers
Field meanings and form steps live there. Do not restate them on this page.
Implementation guidance
Decide (client / kickoff)
- PM list scope: load active go-live project managers (the ones assigned to jobs). Historical names are optional for report continuity; they are not the default starter.
- Numbering: stable codes the client will recognize on jobs and projections (up to 10 digits).
- Contact fields: typically populate name and email. Phone is optional.
Load / accept (implementation defaults)
- Load PMs as a JC-only list. They are not validated against or synced from Payroll employees. PR changes do not update this list — keep ownership clear.
- Assignment is informational for report filter and cost-projection init by PM. It does not drive AP, PR, or other posting by itself.
- Recommended starter: active go-live PMs with name + email; add phone if the client wants it; defer historical names unless reporting needs them.
- Accept means owners confirm names and codes used on go-live jobs before job load.
Tips and gotchas
- PM list: active go-live first; name + email are the usual contact fields (phone optional). Historical PMs only when reports need them.
- JC Project Managers are a separate JC-only list — not validated against Payroll and not synced from it. PR edits never flow here.
- Missing PM on a job breaks PM-filtered reports and projection init by manager, not cost posting.
- Restrict who can edit the list if codes are referenced heavily in job imports.
Done when
- Active go-live project managers exist with accepted codes, names, and typical contact fields (name + email).
- List is ready to assign on JC Jobs.