Review of AutoCAD Architecture
The connected model made architectural documentation feel more consistent. It let our design work carry walls, doors, windows, and roofs with their real world behaviour, then produce floor plans, elevations, sections, and schedules from one model, which gave the team a clearer route from drafting to usable documents and reduced the sense of repeating the same decisions. That was the part I valued most, although getting comfortable with the specialised workflow took more adjustment than the finished drawings might suggest, and I would have liked permissions to be clearer as we brought more people into the work.
Some of the initial effort sits in understanding how the architectural objects connect to the documentation, and the setup felt less immediate than I hoped, but once that clicked the component library and detailing tools helped keep construction documents orderly; I found it dependable for that purpose, and the automatic schedules were useful without asking the team to rebuild every view by hand.
Review of Square 9
I think the strongest part was how straightforward the document side appeared when I considered the work our office needed to keep moving: storing important files securely, finding them from different locations, and allowing people to work from the same material all address real friction, while the compliance focus and recovery provisions gave me some confidence that the records would not be treated as an afterthought during a digital change.
I still wanted clearer answers about how permissions would be managed in practice, since secure access matters only if the right people can reach the right material without creating extra work for everyone else; for a small education legal team, I would need to understand the setup and confirm that existing processes could continue before I trusted the implementation promise, and I found myself cautiously optimistic rather than fully settled, which is a sensible place for me to pause.