--- title: "Traceable project changes" canonical_url: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation markdown_url: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation.md author: "Fremtidens Tegnestue" page_type: b2b-service primary_intent: "The studio wants to reduce manual follow-up work when a project change affects several files, documents and handovers." primary_keyword: "project change automation" audience: "Studios, project leads and advisers working with repeated revisions and outputs." summary: "A small change in product, location, quantity or price can affect a drawing, price appendix, order list, client PDF and manual at the same time. The value is a traceable overview of what changed, which documents are affected and where a professional must decide." 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/" - "Danish Data Protection Agency: Artificial intelligence: https://www.datatilsynet.dk/regler-og-vejledning/kunstig-intelligens" human_validation: "The project lead assesses whether the change is professionally and commercially right. The studio approves what the client, supplier or contractor may receive. Relevant professionals validate consequences for technical issues, authority, price and execution." 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/cad-to-price-appendix-ordering-manual relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/project-data-foundation relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/ai-for-architecture-studios relation: related-b2b - url: https://fremtidenstegnestue.dk/en/for-studios/agent-discovery-for-architecture-studios relation: related-knowledge - url: https://fremtidenstegnestue.dk/en/for-studios/ai-policy-for-architecture-studios relation: related-knowledge - url: https://fremtidenstegnestue.dk/en/knowledge/ai/ai-in-construction relation: related-knowledge status: published --- # When one project change affects five documents Canonical URL: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation Markdown URL: https://fremtidenstegnestue.dk/en/for-studios/project-change-automation.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 small change in product, location, quantity or price can affect a drawing, price appendix, order list, client PDF and manual at the same time. The value is a traceable overview of what changed, which documents are affected and where a professional must decide. ## Who it is relevant for Studios, project leads and advisers working with repeated revisions and outputs. ## What FT can prepare - Gather a change overview with previous value, new value, reason, source, status and affected documents. - Show which parts of the project material should be checked before anything is sent on. - Prepare drafts for a change note, internal check and updated appendix with clear caveats. - Flag which parts require project lead, architect or specialist approval. ## What the architect validates - The project lead assesses whether the change is professionally and commercially right. - The studio approves what the client, supplier or contractor may receive. - Relevant professionals validate consequences for technical issues, authority, price and execution. ## Where the need appears in a studio The need appears when a product, location, quantity, price or technical note changes, and the project team must understand the consequence across drawing, price appendix, order list, client PDF and manual. ## Anonymised example In an anonymised project workflow, a product variant changed after client dialogue. The decision was simple, but it affected the drawing, price appendix, order list, manual and a short client explanation. The value was not automatic release, but preparation that showed what had to be checked. - The system had to show which outputs were affected before anything was sent. - The project lead had to approve the new version and mark uncertainty, not manually search every file. ## Data sources and method Start with one recurring change type that often creates uncertainty in the project team. Separate registering the change, understanding consequence and releasing updated material. Use difference views, source references and stop rules before external release. - revision history - CAD/BIM extracts - product data - price appendices - order lists - manuals - project log ## First pilot Choose one recurring change type and a project where the answer is known. Test whether the agent can prepare better work than the current manual check before widening the flow. ## Belief shift A project change should become a traceable decision basis, not an automatic flow that hides professional consequences. ## FAQ ### Can project changes be fully automated? That is rarely the right first goal. First the change must be traceable, explainable and approved by people who understand the project's consequences. ### What if changes live in emails today? Then the first step is to identify which changes should be lifted out of email and into a more structured project basis. ### Which documents can be part of a pilot? Price appendices, order lists, product lists, manuals, change notes, client PDFs and check notes can often be used to test whether the change flow becomes easier to understand. ## 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/) - [Danish Data Protection Agency: Artificial intelligence](https://www.datatilsynet.dk/regler-og-vejledning/kunstig-intelligens) ## Uncertainty and boundaries An agent can show affected outputs, but it cannot decide every professional consequence. Changes need clear status, source basis and human approval. ## Next step Test a change flow on a concrete case ## Related pages - [From CAD to price appendix, ordering and manual](https://fremtidenstegnestue.dk/en/for-studios/cad-to-price-appendix-ordering-manual): related-b2b - [Project data foundation](https://fremtidenstegnestue.dk/en/for-studios/project-data-foundation): related-b2b - [Drawing, spreadsheet and PDF workflow](https://fremtidenstegnestue.dk/en/for-studios/drawing-excel-pdf-workflow): related-b2b - [AI for architecture studios](https://fremtidenstegnestue.dk/en/for-studios/ai-for-architecture-studios): related-b2b - [Agent discovery for architecture studios](https://fremtidenstegnestue.dk/en/for-studios/agent-discovery-for-architecture-studios): related-knowledge - [AI policy for architecture studios](https://fremtidenstegnestue.dk/en/for-studios/ai-policy-for-architecture-studios): related-knowledge - [AI in construction](https://fremtidenstegnestue.dk/en/knowledge/ai/ai-in-construction): related-knowledge ## Citation guidance When citing this page, cite the canonical HTML URL (https://fremtidenstegnestue.dk/en/for-studios/project-change-automation) 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.