Design production controls: inputs, versions, QA and approval

Astratto uses a documented production-control standard for new engagements scoped on or after August 22, 2026. The standard records which inputs control the work, what is included, how files are labeled, what was reviewed, which questions remain open, and who approves the next stage.

This process does not promise that nothing will change or that errors cannot occur. It creates a traceable record so changes, assumptions, and downstream responsibilities are visible.

1. Inputs are registered

The engagement record identifies the plans, measurements, surveys, sketches, models, reference images, templates, product information, standards, and constraints supplied for the project. Each input is recorded as supplied, client-verified, unverified, or superseded.

Missing or conflicting information is flagged rather than silently treated as fact. Field conditions, code requirements, engineering information, product availability, and other project facts remain unverified unless the responsible party confirms them.

2. Scope is confirmed in writing

Before production begins, the accepted scope identifies the deliverables, quantities, formats, milestones, dependencies, timing, fee, review or revision allowance, and explicit exclusions. It also records the responsibilities that remain with the client firm and the appropriate licensed professionals, contractor, fabricator, vendor, or end client.

Only the deliverables listed in the accepted scope are included. If the requested input, quantity, design direction, output, or schedule changes, that change is recorded before additional work proceeds.

3. Files and versions are traceable

Issued files carry a project identifier, deliverable identifier, status, revision, and date. Work-in-progress, review, approved, final-for-scope, and superseded material are distinguishable.

“Final” means final for Astratto's accepted deliverable scope. It does not mean stamped, permit-ready, engineered, fabrication-approved, field-verified, or approved for every downstream use.

4. Questions and assumptions stay visible

Questions, conflicts, and assumptions are recorded with their potential impact, owner, response, and status. An accepted assumption identifies who accepted it and where that decision was recorded.

5. Review checks match the deliverable

Checks are selected for the actual scope and may include:

  • Alignment with the accepted brief and latest controlling input.
  • Drawing, room, sheet, and reference consistency.
  • Consistency among plans, elevations, schedules, and renderings.
  • Material and FF&E identifiers.
  • Client-template, title-block, naming, and output-format requirements.
  • Missing-input, assumption, and responsibility flags.
  • Correct revision, file status, and delivery index.

The review record identifies the reviewer, date, deliverable revision, open exceptions, and release decision.

6. Approvals and changes are recorded

Review decisions are tied to the named deliverable and revision. Silence is not treated as approval unless a signed agreement expressly says otherwise. A request outside the accepted scope is documented with any fee or schedule effect before it proceeds.

White-label and confidentiality boundary

Direct end-client contact is excluded unless the accepted written scope authorizes it. NDA review is available before confidential project information is shared. Branding, attribution, publication, portfolio use, deliverable ownership, source-file transfer, and usage rights follow the signed agreement and project record.

A third party's identity, testimonial, files, or results are not used publicly without the required permission.

Product, site and construction boundary

Product information is dated when checked because price, stock, lead time, dimensions, finish, and suitability can change. Renderings and drawings communicate design intent based on the supplied and approved inputs.

Field measurement, site verification, code compliance, engineering, stamping, permitting, shop drawings, fabrication verification, and construction execution remain with the appropriately responsible party unless lawfully and explicitly contracted.

Start with a bounded scope

See white-label design assistance, how the engagement works, pricing and quote inputs, or the 60+ project case study.