BasePDH | Course 025 | 2 Professional Development Hours

Digital Design Deliverables as Contract Documents

1. The Contractual Status Decision

1.1 What changes when a file becomes contractual

For several years the New York State Department of Transportation issued its Finish Grade surface to contractors as supplemental information. The surface was accurate, it was useful for survey collectors and machine guidance, and contractors used it. But because it was supplemental, a contractor who relied on it bore the risk of any error inside it, and bore that risk again if the plans indicated something contrary [2]. Issuing the same surface as an electronic file identified as plans moves that risk off the contractor [2]. The file is identical in both cases; what moves is responsibility for an error inside it.

That reallocation is the subject of this course. When a 3D model, a LandXML alignment, or a spreadsheet of superelevation data becomes a contract document, the professional of record's seal stands behind its contents the way it has always stood behind a plan sheet, and the contractor is entitled to build from it. When the same file is delivered as supplemental information, the contractor uses it at its own risk and the 2D sheets remain the governing instrument. Both arrangements are current practice at state DOTs, both are defensible, and the choice between them is a design decision with consequences that surface at the first dispute.

The choice also cannot be made by accident. A standard specification that defines plans as drawings does not admit an electronic file, however carefully modeled, until the definition is amended, and delivering a file to a bidder does not make it contractual [2]. Section 2 covers that mechanism. This section covers the decision itself: what the national practice looks like, the positions agencies have taken, and how the delivery method is scoped to the project.

1.2 Current practice is overwhelmingly two dimensional

The national baseline comes from NCHRP Synthesis 664, a 2026 survey answered by 42 of the 51 state DOTs solicited, an 82% response rate [1]. Two features of the survey govern how its figures may be read. First, percentages are expressed against the respondents to each question rather than the survey population, so the denominator moves from question to question and is reported here with every figure. Second, the respondent pool skews toward design offices: 14 respondents came from highway design and six from BIM or digital delivery units, while construction supplied two and structural design and maintenance none [1]. Answers about construction-phase practice are therefore largely design offices reporting on other people's work.

Asked which media their agency has used to convey design intent for construction, 85% of 41 responding agencies named a 2D PDF plan set with supplemental 3D design files, and 63% named a 2D PDF plan set alone [1]. The two answers in which a 3D model is the primary construction medium drew 12% and 7%, or 5 and 3 agencies [1]. The question allowed multiple selections, so those two rows together represent at most eight agencies, and fewer if any agency selected both. As-built practice is more lopsided still: 90% of 40 responding agencies document as-builts as marked-up 2D PDF plans, against 13% compiling as-built information in a 3D model-based format [1]. The synthesis reads its own results as showing that 2D PDF plan sets remain the dominant medium while agencies make progress with 3D models [1].

The survey also measured how far agencies have gone toward institutionalizing digital delivery, on a three-level scale. The scale's definitions do the work here: at Level 1 an agency has no mandate for 3D deliverables, and only at Level 3 are digital deliverables the main deliverable, with 2D documents minimized [1]. In design, 27 of 40 responding agencies place themselves at Level 2, and 2 of 40, Florida and New York, report Level 3; in construction, no agency reports Level 3 at all [1]. The scale's own Level 2 definition has 2D processes co-existing with digital deliverables. On these figures the common national condition is a dual deliverable: a plan set and a model traveling together, only one of them contractual.

Two further results locate where the contract itself has been touched. Among 41 agencies reporting what they changed to accommodate digital delivery, 76% revised CADD standards, 41% revised project-specific construction contract language such as special notes, and 22%, nine agencies, changed the hierarchy of construction contract documents, the least selected of the seven offered answers [1]. Contract language edited project by project outnumbers structural change to the document hierarchy, which places most current practice at the special-note level rather than at the contract's order-of-precedence clause. And asked how a digital deliverable is authenticated, 57% of 37 responding agencies answered that the question is not applicable to them, 14% rely on a feature of the authoring software, 11%, four agencies, have the engineer seal a memo referencing specific files, and 8% reported blockchain [1]. No method reaches 15%. A practitioner cannot assume a settled national mechanism exists for attaching a seal to a digital file; the two published mechanisms this course examines in Section 3 are exceptions, not examples of a norm.

1.3 Four positions on contractual status

The synthesis interviewed five agencies selected for the maturity of their programs, and their positions on contractual status do not converge [1]. Read together with New York's guidance, they form four distinct answers to the same question.

New York elevates the files to plans. NYSDOT amends the specification definition of plans, project by project, so that designated electronic files are contract plans in the full sense, sealed by the professional of record and standing beside the 2D sheets in the hierarchy [2]. The mechanism is Section 2's subject.