Supervising a Philippine Build From Abroad, my Three-Layer Setup That Actually Works

How I Supervise a Philippine Build From the Other Side of the World

Hey, Daniel here!

A few people have asked how I’m running supervision on this build given that I work in the UAE and my architect isn’t on site either. Short answer: a daily site documenter, three messenger groups, and a clear escalation path. It’s surprisingly simple once you set it up, and so far it has caught every issue we’ve had before it got buried in concrete.

Here’s the actual setup.

The Person on the Ground

The foundation of the whole thing is one hire: an independent person who goes to the site every single day. He’s not on the contractor’s payroll. He reports to me.

His job description, intentionally narrow:

• Walk the active work areas
• Take photos and short videos of everything in progress
• Take measurements when asked
• Push everything into the shared messenger group
• Follow my architect’s instructions, nothing more, nothing less

He has some construction knowledge, not a lot, but enough to know what to point the camera at. He’s not making engineering judgments. He’s the eyes and the tape measure on site. That’s exactly what I need and exactly what I pay him for.

He does excellent work because the role is scoped and clear. He doesn’t have to argue with the contractor, doesn’t have to call shots, doesn’t have to interpret drawings. He photographs, measures, and posts.

How the Architect Actually Supervises

This is the part most people miss: my architect is also not on site.

He’s the main supervisor on this project, but he supervises remotely from another location, asynchronously. He reviews the daily photos and videos, takes notes, marks up images with arrows and annotations, asks targeted questions, and drives the weekly call.

When he marks up a photo, it looks like this:

That’s a column cage with three issues called out at once: stirrup hook either too small or not fixed properly, missing pour level mark, and concrete spacers needed on all 4 sides. All flagged remotely from a desk, all visible to the contractor, all actionable before the next pour.

He references the code when needed. Things like seismic stirrup hook detailing get spelled out with a diagram and the exact dimension required:

This is the difference between “fix it” and “fix it to this specification.” The contractor’s foreman sees the same diagram I do. There’s no ambiguity to negotiate later.

The Three Messenger Groups

This is where most people overcomplicate things or, worse, dump everything into one chat where nothing gets resolved. I run three separate groups, each with a clear purpose.

Group 1: Internal Supervision (me, the architect, the documenter)

This is where raw site photos and videos land first. We discuss things internally before saying anything to the contractor. The architect makes notes, I ask questions, we agree on what’s a real issue versus what’s just a normal site mess.

This is the filter. Not everything that looks weird in a photo is actually wrong. We figure that out here before involving anyone on the contractor side.

Group 2: Day-to-Day Site Issues (with the contractor’s construction engineer)

Once we’ve decided something is a real issue, this is where it gets discussed with the contractor’s site engineer. Urgent technical matters, approvals before pours, RFI-type questions, daily progress confirmations.

Fast turnaround chat, technical level, decisions get made and documented. Some short examples of what gets resolved here:

That’s a real example. The contractor reported a 20cm level difference. We measured from the photo and it was 12cm. Real number on the record, not a guess. That kind of dialogue happens in this group every day.

Group 3: Owner-to-Owner (with the contractor’s company owner)

Strategic stuff only. Important decisions, scope changes, escalations when the day-to-day group isn’t moving fast enough, and the weekly call logistics.

This group stays quiet most of the time, which is how it should be. When it activates, everyone knows it matters. Keeping the company owner out of daily noise means when I do reach out, the response is fast and serious.

The Weekly Call

One scheduled call per week. The architect drives it. He shows up with the notes he has been collecting all week from the daily photos, organized by topic and grid line, with the photos pulled up.

We walk through:

• Outstanding issues from previous calls and whether they were closed
• New issues spotted in the past week
• Upcoming pours and approvals needed
• Schedule and cost variations
• Action items, owner, and deadline for the coming week

The contractor’s engineer and owner are both on the call. Action items get written down and posted in the relevant group afterward. The next call starts by closing out those items.

This is not innovative. It’s just disciplined.

Why This Works

A few honest observations after running this for several months:

1. The independent documenter changes contractor behavior. When everyone knows there will be daily photos in a group with the architect, “we’ll fix it later” stops being a viable answer.
2. Async beats live. The architect’s value is in careful review, not in standing on site shouting. Photos he reviews at 9 PM with coffee are more thorough than rushed site visits in the heat.
3. Three groups, not one. Mixing strategic conversations with day-to-day approvals dilutes both. Each group has a job. People only get notified about what’s relevant to them.
4. The architect drives the weekly call, not me. He has the technical depth and the notes. I’m there to make business decisions, not to interpret rebar drawings live on a Zoom call.
5. Costs less than being on site. Total cost of this setup is a fraction of what flying back to the Philippines monthly would cost, and the coverage is better than monthly visits would give me.

What This Doesn’t Replace

To be fair, this setup has limits.

• It doesn’t replace a structural engineer signing off on as-built repairs or design changes. For those, we get the engineer on site in person.
• It doesn’t replace a final acceptance walk-through. Eventually somebody has to physically inspect the finished house. That’s still on the to-do list.
• It depends on having an architect who’s willing to work this way. Some traditional architects want to be on site or not involved at all. The async-supervision model needs someone comfortable with daily-photo reviews and remote dialogue.

A Few Practical Notes If You Want to Copy This

• Hire the documenter on a fixed daily rate, not by the hour. You want them on site every day at roughly the same time, not stretching their day.
• Give them a simple shot list: every active formwork, every rebar cage, every connection, every ongoing trade. Same shots every day. New issues become obvious by comparison.
• Use a messaging app the contractor’s team already uses. Don’t make them learn a new platform. Whatever the team uses for personal chat is fine.
• Time-stamp everything. Photos with EXIF, screenshots with timestamps. When something becomes a dispute, the timeline matters.
• Back it up. Phones get lost. Pull the photos into cloud storage weekly so you have a permanent record of how the build was actually executed.

Bottom Line

I’m not on site. My architect is not on site. The build is being supervised better than most projects where the owner is physically present every day, because the structure forces visibility and discipline that a single owner-on-site rarely maintains.

The total kit:

• One independent documenter on site daily
• One architect supervising remotely
• Three focused messenger groups
• One weekly call

That’s it. No fancy software, no dashboards, no project management tool. Just clear roles, daily evidence, and disciplined communication.

Want to set up the same process for your own build? If you’re managing a Philippine build from abroad (or even from another city) and you’d like help putting this kind of supervision setup in place - the documenter brief, the group structure, the weekly-call template, the kind of architect to look for - give me a shout. Happy to share what’s working and what I’d do differently.