Detailed hospitality interior coordination for Lume in Phuket

Designing a project in Thailand from abroad

← All insights

The premise

Remote clients need fewer assumptions, clearer approval gates and a shared decision record—not a constant stream of disconnected messages.

01 / Begin with roles, time zones and decision authority

Before design accelerates, identify the client decision-makers, local representatives, architect, consultants, contractor and suppliers. Record who recommends, who verifies and who approves each class of information.

A predictable review rhythm is more effective than permanent availability. It gives the team time to prepare complete questions and gives the client a clear window for decisions.

  • Named approvers
  • Responsibility matrix
  • Shared file location
  • Meeting and response rhythm

02 / Use visual approval packages

Plans, marked views, samples, mock-ups and concise option comparisons allow decisions to be understood without relying on memory from a call. Each issue should show context, consequence and the date by which it affects the project.

A decision log should distinguish approved direction, pending information and items returned for revision. Chat can alert the team; it should not be the only project record.

03 / Make samples and site evidence travel

Material appearance changes with scale, daylight, adjacent finishes and local workmanship. Physical samples, calibrated photography, video review and site mock-ups reduce—but do not entirely remove—the gap between screen and reality.

Critical milestones may justify an in-person review. The useful question is not whether the client can avoid every trip, but which decisions gain enough value from being experienced directly.

  • Reference scale and neutral light
  • Label sample code and supplier
  • Show adjacent materials
  • Record acceptance and conditions

04 / Control substitutions as design changes

Availability and site conditions can require alternatives. Every substitution should be evaluated against performance, dimensions, appearance, lead time, cost effect and its relationship to the complete palette.

Remote delivery becomes fragile when many locally reasonable substitutions accumulate without a central design review. A single approval trail keeps the project coherent.

The useful conclusion

Distance is manageable when the project has one source of truth: defined roles, visual decisions, scheduled reviews, sample control and an explicit record of what changed.
See the related project Client pathwaysStart a project Discuss your project

Questions before you move forward

01Can the whole project be designed remotely?+

Many design and approval activities can be organised remotely, but site information, local specialist input, samples, construction review and selected physical milestones may still require local or in-person action.

02How often should client reviews happen?+

The rhythm depends on stage and programme. A predictable agenda-based review is usually more useful than continuous fragmented messaging.

03What is the source of truth?+

A shared, version-controlled location for approved drawings, schedules, decisions, samples and open questions—not one person’s message history.

04How are language differences handled?+

Key decisions should use clear drawings, references and written records. Project-specific translation or local coordination should be agreed where required.

05Can Arch Unique supervise construction?+

Design supervision can be scoped according to project, location, stage and delivery team. It does not replace the contractor’s or statutory parties’ responsibilities.

06When should the client visit?+

Visits are most valuable when decisions depend on physical space, critical mock-ups, material groups or final composition. The exact milestones should be planned early.

Continue reading · Villa delivery · Decision strategy

The decisions that become expensive when made late

Next field note ↗