The recurring-work problem behind JOC
The concept was developed in the early 1980s by U.S. Army engineers at Supreme Headquarters Allied Powers Europe, known as SHAPE, and is credited to Harry Mellon. It addressed a backlog of small, recurring facility projects. Arranging a separate contract for each small job was cumbersome.[1][2][3][4]
The Army tested JOC from 1985 to 1989 and approved it for general Army use. The Navy and Air Force developed their own programs. JOC was later adopted by public, nonmilitary organizations at federal, state and local levels.
The design connects a common contract framework with individual work packages. A shared price book and contractor bid coefficient provide the pricing basis, while the particular scope and quantities identify each job. Recurring work can share a framework without becoming one indistinct scope.
Turn the backlog into described needs
Start with a location-based inventory rather than a list of vague requests. For each need, name the facility area, observed condition and intended result. Keep a request such as “fix corridor finishes” open until the surfaces and work boundaries are identified.
Separate observations from proposed instructions. A note that ceiling tiles are damaged describes a condition; a decision to replace specified tiles describes intended work. Ask the facility representative to confirm the desired result before turning the condition into an estimating task.
Retain relevant photographs, drawings and access notes with the need record. Identify information that still requires a site visit or an owner decision. An inventory entry should show what is known and the next action, not make an unverified quantity look ready for pricing.
- Location: use the building and area names the facility team recognizes.
- Condition: describe what was observed without guessing its cause.
- Result: state what the owner wants changed or restored.
- Information: attach available records and flag missing details.
- Action: assign the site visit or decision needed to define the scope.
Group work around a coherent scope
As practical planning guidance, consider whether needs share a location, access arrangement or coordinated work window. Those connections can help you evaluate a potential job package. Do not group unrelated tasks solely because they are on the same backlog list.
Check whether the proposed grouping can be described clearly. Identify its physical limits, included tasks and exclusions. If the package depends on an unresolved design choice or unknown condition, identify that decision before presenting it as a settled scope.
Consider whether separate packages would make responsibilities and review clearer. A large, unique or highly designed task may need a different procurement approach under your agency’s rules. Refer that question to the responsible design and procurement reviewers rather than using the backlog label as the answer.
| Planning question | What to establish |
|---|---|
| Do the tasks belong together? | Shared location, access or coordination reason, with clear task boundaries. |
| Is the work defined? | Known conditions, intended results and decisions still needed. |
| Can the work be priced? | Scope tasks, supporting measurements and applicable pricing instructions. |
| Who owns the next step? | Facility contact, scope participants, reviewers and authorized issuer. |
Develop the job, not just the backlog label
JOC is a competitively bid, firm-fixed-price IDIQ delivery method for repair, maintenance, renovation and minor construction. Its scope of use does not supply the details of a particular maintenance task. A work package still needs site information, intended work and supported quantities.[3][4][5]
Hold the joint scope meeting around the proposed package. Walk the locations, record measurements and discuss working hours, access and staging. Identify which questions affect the task description and which affect pricing category selection.
A price book lists tasks, units and unit prices; each selected line amount multiplies unit price by quantity and contractor coefficient. Keep measurements attached to the scope so the proposal reviewer can trace the quantities. Identify any task not represented in the book for review under the applicable instructions.
Update the record as decisions are made
Track each need as a defined work record with a responsible person and current next action. Distinguish a proposed package, a submitted proposal and an issued job order. A productive site meeting does not replace the authorization required before work begins.
When a scope changes, update the description and supporting measurements before revising pricing. Keep the matching scope and proposal versions together. If a need is excluded from the issued work, retain it as a separate unresolved item rather than letting it disappear from the facility record.
At closeout, compare completed tasks with the issued scope and collect the required completion records. Update the backlog to distinguish the work completed from remaining needs. This keeps future planning based on specific conditions and decisions rather than an old request whose status is unclear.
Programs vary; check your agency’s rules, solicitation and contract for applicable requirements.
Sources
- U.S. Army Corps of Engineers, Transatlantic Middle East District, "Old contracting tool leads to new successes in Kuwait"
- Associated Schools of Construction, "Job-Order-Contracting for Facility Owners" (2006)
- Cassell and Gilday, "Improving the Army's Job Order Contracting Program" (1997)
- Arizona State University, "Job Order Contracting Performance" (2015 report)
- Army Federal Acquisition Regulation Supplement (AFARS), "Subpart 5117.90 - Job Order Contracts"