Architectural grids organize columns, walls, cores, and bays, but editing them safely requires more than moving lines on a drawing. Snaptrude’s checklist explains how teams can evaluate whether grid geometry, labels, visibility, and dependent model elements remain coordinated throughout a design workflow.
The article separates grid behavior into four areas: model location, view extent, annotation, and interaction. Each needs testing, followed by checks of their connections. Moving a datum should produce predictable changes across the model, while shortening its appearance in one view should follow defined display rules.
Initial tests cover grid creation, naming, insertion, and deletion. Teams should establish whether labels remain attached to objects or change with spatial order. Numeric spacing edits must identify which line moves and which stays fixed. Invalid values should trigger clear feedback while preserving the last valid state.
Direct manipulation deserves attention. Lines, endpoints, bubbles, and spacing handles should be distinguishable, with snapping that supports the intended action. Selection should remain predictable at building, bay, and detail scales, even when walls, columns, dimensions, and controls overlap.
Using Revit documentation as an example, the article distinguishes model-wide grid extents from presentation changes limited to individual views. Teams should record coordinates, object identities, visible extents, and affected views before and after edits, rather than relying only on screenshots.
Downstream testing includes checking bay dimensions, constrained elements, plans, elevations, and three-dimensional views. Undo, redo, saving, reopening, and relevant exports must preserve the expected model and documentation states.
Acceptance records should document setup, actions, expected outcomes, actual results, recovery, and evidence. Outcomes are classified as pass, conditional, or fail; destructive errors should block the affected workflow.
The checklist also applies to Snaptrude, but its modeling capabilities do not establish specific grid behavior. Teams must test their intended operations on representative models before approving them for project use.
