Where JOC came from

Small jobs, a recurring backlog

The concept behind Job Order Contracting was developed in the early 1980s by U.S. Army engineers at Supreme Headquarters Allied Powers Europe, known as SHAPE. It is credited to Harry Mellon. The engineers faced a backlog of small, recurring facility projects, with a cumbersome new-contract-per-small-job approach.^[1][2]

The problem connected two different needs: a way to contract for recurring work and a way to define each particular job. Repeating a contracting exercise for every small project addressed the second need without providing a common framework for the first. JOC put individual work packages inside a competitively bid contract framework.

That distinction is central to the design. The contract framework provides the common basis for job orders, while each order describes and prices a particular package of work. The framework does not make the jobs identical: their selected tasks and quantities still depend on the work being ordered.

A contract framework for separate work packages

JOC is described as a competitively bid, firm-fixed-price, indefinite delivery / indefinite quantity construction delivery method. The IDIQ framework and individual job orders belong to the same arrangement. They are not competing descriptions: one describes the contracting method, and the other identifies work within it.^[3][4]

Its stated uses are repair, maintenance, renovation and minor construction. Those categories fit the original problem of small, recurring facility projects. The design connects the recurring need for work to individual scopes rather than requiring the contract framework itself to describe every job as one combined project.

A particular job still needs a defined scope. Its location, tasks and quantities supply the job-specific information that a shared framework cannot provide. The contract and the order therefore do different work: a common contracting basis on one side, a particular construction package on the other.

A common book and a bid factor

A unit price book supplies construction tasks, units of measure and unit prices. Those prices include direct material, labor and equipment costs, but not indirect costs or profit. The shared book gives the parties a common reference for selecting and pricing work rather than treating each task description as an unrelated quotation.^[5][4][1]

Contractors bid a coefficient or coefficients. The coefficient covers costs outside the book’s unit prices, including general and administrative and other overhead, insurance and bonding. It connects the common book to the contractor’s bid factor without replacing the task descriptions or the quantities for a job.

For each selected line item, the calculation is unit price multiplied by quantity and the contractor’s coefficient. The selected task and its quantity identify the individual work; the book price and bid coefficient connect it to the shared pricing framework. This is how a common basis produces prices for different work packages.

Because both parties price from the same book, negotiation is mostly about line-item selection and quantities. The design directs the job-specific discussion toward which tasks represent the scope and how much work is included. A shared pricing reference can be reused while those decisions remain specific to each order.

Army testing and wider adoption

The Army tested JOC from 1985 to 1989 and approved it for general Army use. The Navy and Air Force developed their own programs. The sequence moved the concept from its early development into military programs beyond its original setting.^[1][2][3]

JOC was later adopted by public, nonmilitary organizations at federal, state and local levels. Its history is therefore not confined to military facility work. The verified milestones are its Army origins, testing and approval, the other services’ programs and subsequent public-sector adoption.

The design joins a competitively bid framework, a shared price book and contractor bid coefficients with individually scoped job orders. That combination addressed the original contracting problem without removing the need to describe and quantify each small job. The recurring framework and the particular scope remain distinct parts of the same method.