Authority concept · Field Ratio Architecture + Engineering

Test the premise before optimizing the plan.

Programming is not a room list and feasibility is not a decorative concept. The work frames operations, areas, adjacency, site/building constraints, structural/systems implications, phasing, schedule, and cost assumptions so an owner can decide what project to pursue.

Existing masonry, concrete, and steel window junction documented in the field.

Questions this practice carries

A useful brief addresses owner goals and decision criteria, users/workflows, area and adjacency, site/existing-building fit, technical constraints, and phasing/schedule/budget assumptions.

Coordination responsibility

The page should show where this discipline changes decisions elsewhere. It should not read like an isolated menu of deliverables.

Professional boundary

This is a fictional TruePoint concept. No real architect/engineer licenses, seals, registrations, professional liability coverage, or jurisdictional authority are claimed. A real project requires appropriately licensed professionals.

Where this changes the project

A feasibility effort can reveal that the requested square footage is not the real problem, that adjacency matters more than total area, that an existing facility can absorb growth through reorganization, or that a technical constraint makes one option disproportionately expensive.

The value is the ability to compare premises while they are still inexpensive to change. That is why this practice page links directly to owner insights rather than presenting programming as a fixed deliverables list.

TruePoint concept · fictional A/E practice · Built for Aster