Method evidence / no invented portfolioPATTERNS / 09

Project patterns, shown without pretending they are case studies.

Until a named project is approved for publication, credibility comes from explaining how a responsible method changes with the environment. Anonymous logos, unsupported metrics, and stock-photo success stories are not evidence.

DISCLOSURE

What is represented here?

These are planning archetypes based on common reality-capture constraints. They demonstrate scope logic. They are not customer testimonials, completed-project claims, or evidence that a particular site was scanned.

01 / METHODS

Constraint → response

How the same equipment can require a different plan.

01

Congested plant room

Decision: route and fit new work among existing systems. Plan: short lines of sight, redundant scan relationships, reflective-surface review, equipment-state notes, and a tightly bounded model scope.

02

Occupied high-rise renovation

Decision: establish floor and core conditions while operations continue. Plan: phased access, privacy controls, repeated-geometry discipline, coordinate strategy, and floor-by-floor coverage records.

03

Large venue back-of-house

Decision: coordinate interventions across long travel paths and elevation changes. Plan: survey/control integration where required, explicit zones, vertical connections, data segmentation, and staged handoff.

04

Maritime retrofit

Decision: evaluate fit in a moving, confined, highly occluded environment. Plan: motion and access review, dense station placement, interface prioritization, coordinate-basis agreement, and project-specific safety controls.

Publication standard

What a future case study must disclose.

Permission
Named client or site information is published only with authorization.
Scope
The decision, accessible capture boundary, coordinate basis, and agreed deliverable are stated.
Method
Equipment and software roles are described without implying they alone produced the result.
Evidence
Any schedule, quantity, accuracy, or outcome is tied to project records and the conditions under which it was measured.

Next coordinatePROJECT / SCOPE

Bring the real constraints. Build the right method.

Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.