Skip to content
Technical design note

Deliverables and release review

An architecture connecting deliverable requirements with execution records, supporting evidence and release review.

SurveyIQ technical note

Technical design notes. Confirm supported product behaviour, configuration and project suitability through technical evaluation.

Abstract

Deliverable review brings together contractual requirements, technical outputs, supporting records and approval. Completion tracking and authorisation to release need to be assessed separately.

Technical field. Delivery

Design considerations

  • A deliverable register needs a defined relationship to scope requirements, revisions and responsible owners.
  • Evidence completeness and technical acceptance require criteria appropriate to the deliverable.
  • Release, recipient access and subsequent revisions require an explicit review and distribution process.

Questions for technical evaluation

  • How are requirements, technical outputs and supporting records associated?
  • Which checks and approvals are required before the proposed release action?
  • How are released revisions, corrections and recipient access controlled?

Scope of this note

This note describes workflow design and evaluation considerations. Supported behaviour, interfaces, controls and limitations need to be demonstrated for the proposed product configuration and intended project.

About this note

SurveyIQ technical note: Deliverables and release review. This editorial edition focuses on architecture and evaluation considerations. Product qualification depends on the intended use and demonstrated configuration.

Evaluate the relevant workflow.

Discuss the data, engineering methods and outputs your project needs.

Request a technical demonstration