Contract team assignment
How a contract is assigned to its contract specialist, contracting officer and COR — proposals, designation evidence, confirmation and what each role can then do (CT05).
Contract specialist · Contracting Officer · COR · Branch Chief · User Access Admin
/pdcc/acquisitions/contracts/CT-DEMO-012/teamEvery managed contract has a team bound to that contract. Assigning someone here binds a contract-specific responsibility; it is separate from app roles and from legal authority. The Team assignments page (step 4.7) manages the key government and support roles for the contract.
The three required roles
| Role | Who | Authority comes from |
|---|---|---|
| Contract Specialist (CS) | Prepares packages and coordinates work (e.g. Jordan Lee). | App role only — no implied warrant. |
| Contracting Officer (CO) | Makes contracting decisions (e.g. Casey Park / Parker Quinn). | A verified CO warrant: scope, dollar limit and effective dates. |
| Contracting Officer's Representative (COR) | Surveillance and designated technical review (e.g. Morgan Reed / Sydney Ward). | A verified COR designation for this contract and appointment period. |
All three are required. A branch chief is not a contracting officer — naming one in the CO field is rejected with *Name the warranted contracting officer for this contract*.
Team assignments table
- Role
- CS, CO or COR.
- Assigned person
- The named individual.
- Source
- Where the assignment comes from (e.g. *SAP export* for CS and CO).
- Status
- *Confirmed* or *Proposed*.
- Effective date
- When the responsibility starts (*On confirmation* for a new COR).
Tabs: Assignments, Access (what each assignment allows) and History (all assignment requests and decisions).
Assign or change the COR
- 1
Open Team
Contract › Team (
/pdcc/acquisitions/contracts/CT-DEMO-012/team) or *Review appointment* from readiness. - 2
Select the proposed COR
In the Proposed COR panel choose the person. Selecting a person only proposes the assignment.
- 3
Save proposal
Saves CS, CO and COR together with designation evidence (e.g.
Designation_Morgan_Reed.pdf (awaiting review)) and effective period *On confirmation*. The response reads *designation: pending verification*. - 4
Track the request
You land on Assignment request detail (step 4.10, e.g.
ASG-042) showing requested person, role, requested effective date, submitted by, date submitted and the responsible reviewer. - 5
Configured reviewer confirms
The reviewer examines the designation evidence and confirms the COR designation for this contract and period.
- 6
Assigned user notified
The COR receives a New COR assignment briefing and a first contract briefing.
Assignment progress (four stages)
1. Proposal saved
The COR is proposed; no access is created.
2. Evidence review
Designation evidence awaits the configured reviewer.
3. Source confirmation
The appointment is confirmed against its source for this contract and period.
4. Assigned user notified
The COR is told; briefing is available.
Request reassignment or update
Use Request reassignment on the team page or Request update on the request detail to change an assignment. The request routes to the same review; the current confirmed assignment stays in force until a new one is confirmed.
After confirmation
- New COR assignment briefing — shown only after a confirmed appointment; it is not itself an appointment or expanded authority.
- First contract briefing — acknowledging it is separate from accepting deliverables or modifying terms; the designation evidence link is retained.
- COR work plan — suggested COR jobs become tasks only after you select them and authority is validated. No unsupported contractual dates are invented.
- The COR now sees the contract in Deliverable Reviews and on My Day.
Where else assignment is managed
| What | Where |
|---|---|
| Warrants and designations (authority records) | Administration › role assignments and authority (UA03) — a role label never establishes legal authority. |
| Individual tasks on the contract | Tasks: reassign and delegate. |
| Workload rebalancing across a team | Team & Portfolio › Team Workload. |
| Evidence-gap owners | Assign an evidence gap (EV06). |
Related guides
Readiness and managed work
Review mandatory checks, select suggested jobs, and move the contract into managed work with a receipt (CT06, CT07).
Role assignments and authority
Keep application roles separate from contract-specific warrants and designations; record and validate authority (UA03).
Tasks: create, reassign, delegate, reschedule and complete
How tasks are created and owned, and the exact rules for reassigning, delegating, changing due dates and completing them.
Deliverables and acceptance review
Track contractor submissions and government decisions separately; review acceptance test results and request missing evidence (CT08, CT09).