When spreadsheets are useful but should not be the only truth
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.
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.
AI can prepare, compile and flag uncertainty. The architect validates consequence, judgement and responsibility.
Here, architecture does not mean software architecture. We mean the built environment: architecture studios, renovation, local plans, BR18, materials, building data and architectural decisions.
What must the team be able to trust?
Before agent output enters project work, the team must see sources, assumptions, gaps and the next control point. Otherwise AI becomes one more place where project knowledge can turn unclear.
Source-fixed extraction
A useful output for drawing spreadsheet PDF workflow should show which information comes from spreadsheets, CAD/BIM data, PDF output, price appendices, and which points are based on project assumptions.
Professional sorting
The agent should not only reproduce text. It should help the studio sort what matters for the case, what can wait and what requires human assessment.
Validation track
The output should point to who checks the next step. In this workflow, that especially means that the studio decides which spreadsheet habits actually work and should remain.
Decision log
Important findings should be traceable to source, status and next action. At minimum, the team should see why a recommendation was included or rejected.
How to test without making AI the answer.
The first goal is to test whether the system can review the spreadsheets that effectively function as the project's working basis, while the studio checks whether the output actually improves the workflow.
- 01
Start with a real case where the studio knows enough of the answer to assess quality.
- 02
Compare the first output with your manual workflow, and note where it saves time, misses something or becomes too certain.
- 03
Keep the pilot scope narrow: start with the spreadsheet everyone uses but no one fully owns.
- 04
End the test with a decision about where the workflow should enter practice, and which parts are still owned by architect, adviser or leadership.
Where does the need appear in the 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.
What can the agent prepare?
- check_circle Review the spreadsheets that effectively function as the project's working basis.
- check_circle Distinguish columns that are project data, working notes, calculations and temporary assessments.
- check_circle Prepare a synthesis where data fields can be traced to drawing, PDF output, price appendix, ordering and manual.
- check_circle Flag which relations the agent can use and which require clarification with the team.
What must the architect validate?
- verified The studio decides which spreadsheet habits actually work and should remain.
- verified The project lead checks that relations between drawing, price, product and PDF are correct.
- verified The team approves which outputs can be used and which still require manual review.
When the spreadsheet has become the unofficial engine
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.
- sync_alt The spreadsheet could remain a working view, but not the only truth.
- sync_alt PDF, order list and manual had to be checked from the same relation between code, product and status.
Data sources and uncertainty
The source basis must be visible so the studio can distinguish between data, interpretation and decision.
Data that can be included
- spreadsheets
- CAD/BIM data
- PDF output
- price appendices
- order lists
- manuals
- project folders
Working 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.
Uncertainty and responsibility
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.
Visible source basis
Sources should make it possible to check what is documented and what still requires professional judgement.
Start with one concrete case.
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.
Frequently asked questions
Do we have to stop using spreadsheets?
add
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?
add
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?
add
Start with the most used spreadsheet and one concrete case where a change previously had to be corrected in several places.
Project data foundation
Connect drawings, spreadsheets, product choices and revisions so the studio can review agent drafts from one shared basis.
CAD and outputsFrom CAD to price appendix, ordering and manual
Connect drawing codes, product data and documentation so price appendices, orders and manuals can be checked from the same basis.
RevisionsTraceable project changes
Make project changes traceable so an agent can prepare overview, control points and drafts before the architect approves.
Knowledge layerThe studio knowledge foundation
A studio knowledge foundation makes cases, sources, standards and decisions easier to reuse without losing responsibility.
Related knowledge