--- title: "Drawing, spreadsheet and PDF workflow" canonical_url: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow markdown_url: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow.md author: "Fremtidens Tegnestue" page_type: b2b-service primary_intent: "The studio wants to keep spreadsheets, PDFs and drawings as practical formats without letting them become separate truths." primary_keyword: "drawing spreadsheet PDF workflow" audience: "Studios and project teams where spreadsheets have become an unofficial project management system." summary: "A spreadsheet is often the system no one formally chose. It can be a good working view, but when drawing, spreadsheet and PDF carry the same project knowledge without visible connection, it becomes hard to see which fact is current. The goal is to make relations and uncertainty clear enough for professional 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 decides which spreadsheet habits actually work and should remain. The project lead checks that relations between drawing, price, product and PDF are correct. The team approves which outputs can be used and which still require manual review." 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/cad-to-price-appendix-ordering-manual relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/studio-knowledge-foundation relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/studio-digital-backoffice relation: related-knowledge - url: https://fremtidenstegnestue.dk/en/for-studios/ai-strategy-for-architecture-studios relation: related-knowledge - url: https://fremtidenstegnestue.dk/en/contact relation: related-knowledge status: published --- # When spreadsheets are useful but should not be the only truth Canonical URL: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow Markdown URL: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow.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 A spreadsheet is often the system no one formally chose. It can be a good working view, but when drawing, spreadsheet and PDF carry the same project knowledge without visible connection, it becomes hard to see which fact is current. The goal is to make relations and uncertainty clear enough for professional review. ## Who it is relevant for Studios and project teams where spreadsheets have become an unofficial project management system. ## What FT can prepare - Review the spreadsheets that effectively function as the project's working basis. - Distinguish columns that are project data, working notes, calculations and temporary assessments. - Prepare a synthesis where data fields can be traced to drawing, PDF output, price appendix, ordering and manual. - Flag which relations the agent can use and which require clarification with the team. ## What the architect validates - The studio decides which spreadsheet habits actually work and should remain. - The project lead checks that relations between drawing, price, product and PDF are correct. - The team approves which outputs can be used and which still require manual review. ## Where the need appears in a studio The need appears when a spreadsheet is used as product list, price basis, order basis, client PDF and source for manuals, while drawings and PDFs do not show the same status. ## Anonymised example In an anonymised project workflow, a spreadsheet acted as product list, price basis and internal order overview. The PDF was sent to the client, while the drawing showed the codes. When a variant changed, several formats had to be edited and checked manually. - The spreadsheet could remain a working view, but not the only truth. - PDF, order list and manual had to be checked from the same relation between code, product and status. ## Data sources and method Start with the spreadsheet everyone uses but no one fully owns. Keep spreadsheets as a view or export when they still help the team. Make critical relations visible enough for an agent to explain them and an architect to check them. - spreadsheets - CAD/BIM data - PDF output - price appendices - order lists - manuals - project folders ## First pilot Choose the most used spreadsheet and a project where it has already created follow-up work. Test whether the agent can prepare one checkable output without removing the spreadsheet as a working view. ## Belief shift Spreadsheets can still be useful, but they should not alone carry the relation between drawing, product, price, status and output. ## FAQ ### Do we have to stop using spreadsheets? Not necessarily. A spreadsheet can be a useful working view. The problem appears when it is the only place where critical project data is connected. ### How can the agent help with PDFs? In many cases a PDF draft can be prepared from a structured project basis, but it should still be quality checked before sending. ### Where should we start? Start with the most used spreadsheet and one concrete case where a change previously had to be corrected in several places. ## 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 A new project basis only helps if the spreadsheet's meaning is understood correctly. Unclear columns, old tabs and local habits must be clarified before an agent may use them as a basis. ## Next step Review a concrete workflow ## Related pages - [Project data foundation](https://fremtidenstegnestue.dk/en/for-studios/project-data-foundation): related-b2b - [From CAD to price appendix, ordering and manual](https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual): related-b2b - [Traceable project changes](https://fremtidenstegnestue.dk/en/for-studios/project-change-automation): related-b2b - [The studio knowledge foundation](https://fremtidenstegnestue.dk/en/for-studios/studio-knowledge-foundation): related-b2b - [Studio digital backoffice](https://fremtidenstegnestue.dk/en/for-studios/studio-digital-backoffice): related-knowledge - [AI strategy for architecture studios](https://fremtidenstegnestue.dk/en/for-studios/ai-strategy-for-architecture-studios): related-knowledge - [Contact](https://fremtidenstegnestue.dk/en/contact): related-knowledge ## Citation guidance When citing this page, cite the canonical HTML URL (https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow) 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.