Authority concept · Field Ratio Architecture + Engineering

A room list counts spaces. A program explains how they need to work together.

Useful programming connects people, activities, workflows, adjacencies, shared resources, growth/change, equipment, schedule, and area assumptions. That information can reveal whether the stated project is the right project.
Exposed structural and building-service zone showing duct, conduit, and access relationships.

Questions to carry forward

  • users and activities
  • flows and adjacencies
  • shared versus dedicated space
  • equipment/storage/support
  • growth/change assumptions
  • area and utilization assumptions

Use the question to test the project

The value of the exercise is not a universal answer. It is making criteria, assumptions, responsibilities, and unknowns explicit enough that the next phase can respond to them.

Professional boundary

This fictional article demonstrates communication strategy, not licensed architectural/engineering advice for a real project. Jurisdictional, code, engineering, healthcare, environmental, and specialist decisions require qualified professionals.

What changes when activities replace labels

Two rooms with the same name can require different adjacency, acoustic, equipment, supervision, storage, daylight, service, or circulation relationships. A program becomes useful when it describes those relationships and tests how much space they actually require.

That richer brief can reveal opportunities to share space, reduce duplication, separate conflicting flows, or challenge a requested area before the project treats it as fixed.

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