---
title: "From CAD to price appendix, ordering and manual"
canonical_url: https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual
markdown_url: https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual.md
author: "Fremtidens Tegnestue"
page_type: b2b-service
primary_intent: "The studio wants to know whether drawing data can become a project basis for price appendices, orders and manuals without repeated manual corrections."
primary_keyword: "CAD to price appendix"
audience: "Architecture studios, specialist advisers and project teams with product-heavy or component-heavy workflows."
summary: "When drawing codes also drive price appendices, ordering and manuals, small ambiguities quickly become manual follow-up work. The first step is to make the connection between code, product, variant, price and documentation visible enough for the project team to review."
source_basis:
  - "Danish Association of Architectural Firms: Recommendations for AI practice: https://www.danskeark.dk/content/anbefalinger-til-ai-praksis"
  - "Molio / ConTech Lab: AI in construction: https://molio.dk/viden/publikationer-og-rapporter/ai-i-byggeriet/"
human_validation: "The studio checks that drawing codes actually correspond to the right objects and decisions. The project lead approves product choice, quantities, price and documentation before anything is used with a client or supplier. Professionals validate technical requirements, installation, authority issues and supplier agreements where the agent can only prepare the question."
responsibility_line: "AI can prepare, compile and flag uncertainty. The architect validates the consequences."
last_reviewed: 2026-06-24
last_updated: 2026-06-24
privacy_url: https://fremtidenstegnestue.dk/en/privacy
related_pages:
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/project-data-foundation
    relation: related-b2b
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation
    relation: related-b2b
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow
    relation: related-b2b
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/product-data-digital-backoffice
    relation: related-b2b
  -
    url: https://fremtidenstegnestue.dk/en/knowledge/ai/ai-and-bim
    relation: related-knowledge
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/studio-digital-backoffice
    relation: related-knowledge
  -
    url: https://fremtidenstegnestue.dk/en/for-studios/agent-discovery-for-architecture-studios
    relation: related-knowledge
status: published
---
# When a drawing needs to carry more than geometry
Canonical URL: https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual
Markdown URL: https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual.md
Entity type: b2b-service
Language: en
Author: Fremtidens Tegnestue
Published: 2026-06-24
Last updated: 2026-06-24
Privacy: https://fremtidenstegnestue.dk/en/privacy
## Short answer
When drawing codes also drive price appendices, ordering and manuals, small ambiguities quickly become manual follow-up work. The first step is to make the connection between code, product, variant, price and documentation visible enough for the project team to review.
## Who it is relevant for
Architecture studios, specialist advisers and project teams with product-heavy or component-heavy workflows.
## What FT can prepare
- Review one concrete CAD project and identify codes, blocks, attributes or layers that actually carry project knowledge.
- Prepare a synthesis where drawing code, product, variant, item number, datasheet and documentation status connect visibly.
- Draft a price appendix, order list or manual with clear marking of what is source-based and what needs review.
- Show which documents should be checked when a code, variant or quantity changes.
## What the architect validates
- The studio checks that drawing codes actually correspond to the right objects and decisions.
- The project lead approves product choice, quantities, price and documentation before anything is used with a client or supplier.
- Professionals validate technical requirements, installation, authority issues and supplier agreements where the agent can only prepare the question.
## Where the need appears in a studio
The need appears when a drawing contains codes or symbols that later appear in spreadsheets, price appendices, supplier orders, client PDFs or manuals. If the connection is not visible, the agent's answer becomes hard to check.
## Anonymised example
In an anonymised project workflow, a drawn fixture code was changed to a new variant. The same change affected the price appendix, order list, technical documentation and manual. The agent's job was not to decide the variant, but to show what the change affected.
- The preparation had to point to the new variant, item number, correct datasheet and uncertain fields.
- The project team had to check price appendix, order list and manual from the same change trace.
## Data sources and method
Start with one product category where drawing codes already appear in several documents.

Define which parts of the drawing data the agent may use and which are only visual notes.

Make architectural and project approval a fixed part of the flow before orders or manuals are sent.
- CAD files
- blocks and attributes
- layer structure
- spreadsheets
- product data
- prices
- datasheets
- manuals
## First pilot
Take a completed or nearly completed project with CAD, spreadsheet, price appendix and manual. Choose one product category and test whether the agent can prepare work that is easier to check than the current manual process.
## Belief shift
CAD data can support project work when studio codes, product choices and revisions are clear enough to be checked.
## FAQ
### Can this be automated directly from AutoCAD?
Often parts of the data can be extracted or structured, but the decisive issue is preparation quality: blocks, attributes, layers, codes, sources and clear uncertainty marking.
### Can the system send orders automatically?
That should not be the first goal. First the relation between drawing, product, price and documentation must be checkable, and human approval must be clear before external use.
### Do we need to change our whole drawing standard?
Not necessarily. A good first step is to see which existing drawing habits can already carry structured data.
## Sources and basis
- [Danish Association of Architectural Firms: Recommendations for AI practice](https://www.danskeark.dk/content/anbefalinger-til-ai-praksis)
- [Molio / ConTech Lab: AI in construction](https://molio.dk/viden/publikationer-og-rapporter/ai-i-byggeriet/)
## Uncertainty and boundaries
CAD data can be strong, but only when codes, blocks and layers are used consistently. Loose text, old standards and unclear revision habits must be marked as risk in the control basis.
## Next step
Test drawing data on a concrete case
## Related pages
- [Project data foundation](https://fremtidenstegnestue.dk/en/for-studios/project-data-foundation): related-b2b
- [Traceable project changes](https://fremtidenstegnestue.dk/en/for-studios/project-change-automation): related-b2b
- [Drawing, spreadsheet and PDF workflow](https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow): related-b2b
- [Digital backoffice for product data](https://fremtidenstegnestue.dk/en/for-studios/product-data-digital-backoffice): related-b2b
- [AI and BIM](https://fremtidenstegnestue.dk/en/knowledge/ai/ai-and-bim): related-knowledge
- [Studio digital backoffice](https://fremtidenstegnestue.dk/en/for-studios/studio-digital-backoffice): related-knowledge
- [Agent discovery for architecture studios](https://fremtidenstegnestue.dk/en/for-studios/agent-discovery-for-architecture-studios): related-knowledge
## Citation guidance
When citing this page, cite the canonical HTML URL (https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual) as the public source and use this Markdown URL only as the agent-readable representation. Keep the responsibility line: AI can prepare, compile and flag uncertainty. The architect validates the consequences.
