01
Operating context
A defined role in the project
The work begins with the project brief, the information available, and the people who will receive the result. That context helps define a useful production or review scope without confusing delivery support with project design authority.
02
Operating context
Inputs before assumptions
Source files, revisions, coordinate references, intended use, and acceptance expectations shape what can reasonably be produced. Missing or uncertain information should remain visible for the team to resolve.
- Identify the source models, drawings, or survey information
- Set areas, elements, review boundaries, and exclusions
- Agree file formats, information needs, and receiving roles
03
Operating context
Work that supports a next decision
A model, detail package, or issue record is useful when its limits and context travel with it. Design decisions, field verification, technical approval, and acceptance remain with the professionals appointed to the project.