Many software architecture and delivery questions can be reviewed effectively remotely. Documentation, source material, infrastructure configuration and focused conversations can provide enough evidence for a technical health check.
An onsite review becomes more valuable when the technology is closely tied to physical operations, connected products, manufacturing workflows or several stakeholder groups whose work is difficult to understand from documents alone.
Choose based on the question
A remote review is often the efficient starting point for maintainability, cloud infrastructure, scalability or supplier-delivery concerns. It keeps the engagement focused and reduces disruption.
An onsite review makes sense when observing the operation changes the quality of the evidence. Seeing how systems are used, where workarounds occur and how software interacts with equipment can expose constraints that would otherwise remain hidden.
The scope should follow the decision that needs to be made. When the right approach is not obvious, an initial discussion can determine whether being onsite will materially improve the findings.