While we now have mature, proven guidelines (FADGI) which provide solid recommendations on how to create proper master files, beyond targets and the ability to measure them, the cultural heritage community lacks easily consumable, flexible specifications for conducting actual projects. Moreover, there is a general lack of examples of FADGI-compliant Statements of Work, leading to much re-invention of the wheel and even to library and archival personnel deciding to not use FADGI at all. This puts inexperienced users at a decided disadvantage and creates a formidable barrier to entry for new practitioners who want to use the FADGI guidelines on their projects. As discussed in this paper, a DIO (or Digitization Information Object) is a data model encompassing all technical parameters of a still image digitization project. At its core, the DIO schema is intrinsically tied to FADGI, and enforces FADGI compliance through its use. It provides a common, machine-readable instruction set for digitization-facing software programs. This allows consuming applications to be quickly and precisely configured per-project to specify output image parameters, configure post-processing workflows, verify both working files and huge batches of completed content at scale, and even to provide plain-English text for a project's Statement of Work -- all from the same DIO JSON file.