Blueprints are reusable workflow definitions that orchestrate multiple templates and define the end-to-end process for document generation, collaboration, and e-signatures. They serve as process blueprints that can be instantiated into workflows with specific data and participants.

Each blueprint contains documents (references to templates), entity slots (structured data requirements across all documents), roles (participants needed), and steps (the orchestrated process flow). Steps are organized in a tree-based hierarchy starting from a root step. Group steps can have child steps that execute in parallel or sequentially, participant steps define where users interact with documents, and you can add conditional logic to control the flow. For example, a real estate closing blueprint might have a root group with parallel branches for buyer and seller document reviews, followed by sequential steps for escrow processing and final signatures.

Blueprints follow the standard SignStack resource lifecycle: iterate in a draft, then publish to an immutable semver. Published versions are frozen so existing workflows keep running against the exact shape they were instantiated from; to make changes, edit the draft and publish again.

Blueprints can be previewed directly within Signstack using scenarios with realistic entity data, and can be instantiated into workflows with actual participants and data for execution.