A Wrong Progress Report Can Kill Your Reputation. How to avoid it.

You’d be surprised how fast things can go wrong in Singapore’s professional circles because of one poorly written progress report․

A lot of the time, people submit a report and think it’s “good enough” for the project․. But they forget that it’s not only the project under review‚ it’s themselves too. 

Let me tell you, as I sit here with my tea, this is one of those things that seems small… until it isn’t.

This one little document can literally change how people see you․

What’s the real damage if a progress report is wrong (and who gets blamed)?

In Singapore, a “small” error in a progress report rarely stays small.

If you say a slab is cast when it’s actually formwork-in-progress, or you report 68% completion when the site reality is closer to 55%, you don’t just look a bit off. You trigger real-world consequences like claims, payment disputes, awkward client calls, and a lovely chain of emails where everyone suddenly “needs clarification” (translation: someone’s preparing to defend themselves).

And to our detriment, the blame usually falls on whoever produced the report, even if 10 other people were involved.

In our experience doing construction progress monitoring and PFI work across Singapore, the reputational hit is the worst part. Projects can recover, and schedules can be re-baselined, but once the client thinks your reporting is unreliable, every future report gets read with suspicion.

The kicker is that many wrong reports aren’t caused by “bad intent.” They happen because someone relied on low-quality site photos, rushed walkthrough notes, mismatched dates, or visual estimates with no measurement basis.

Why do progress report and survey prices vary so much in Singapore?

This is one of the most common questions we hear on-site, usually right after someone forwards two quotes with a huge price gap and asks, “Why is this guy so cheap?”

Here’s the answer: pricing varies because scope and risk vary. A proper progress report that stands up in a dispute is not the same thing as a quick photo dump with captions.

These are a few things that legitimately change the cost:

• Site complexity and access: tight sites, heavy-lifting zones, restricted access, night work, or congested traffic marshaling all add time.
• CAAS permissions and constraints: if you’re operating near Changi or Seletar, you can’t just show up and fly. We run CAAS-permitted operations, and where needed, we use a tether system to operate safely and compliantly in sensitive areas. That planning is work.
• Deliverable quality: Are you getting a simple PDF with pictures, or are you getting measured outputs like orthomosaics, annotated elevations, change tracking, and structured progress narratives?
• Accuracy requirements: “Looks about right” is cheap. RTK-linked measurements and repeatable site comparisons are not.
• Turnaround expectations: next-day reporting costs more because it compresses processing and QA time.

We run a lean model, so we can stay competitive without cutting corners, but we’re still not going to pretend all reports are the same.

How accurate are drone surveys for progress reporting (and what’s RTK GPS, really)?

Drone surveys can be extremely accurate if the workflow is built correctly.

A drone is just a camera in the sky; the accuracy comes from georeferencing, good control, and repeatable methods.

When we run RTK (Real-Time Kinematic) GPS, the drone (or base/rover setup) receives correction data so its positioning is far more precise than standard GPS. In practical site terms, RTK helps us produce maps and models that line up properly across time, so Week 3 overlays Week 6 without drifting all over the place.

However, RTK doesn’t magically fix everything. You still need:

• Proper flight planning (overlap, altitude, angles)
• Ground control or known references when required
• Consistent processing settings
• QA checks against site reality

If someone tells you “our drone is RTK so it’s automatically accurate,” that’s like saying “my camera is expensive so the photos are automatically good.” Nice try.

How do airport restrictions and permits in Singapore affect turnaround time?

Singapore is not a “just fly anywhere” place, and ironically, that’s a good thing.

If your site sits in or near controlled zones, you need to factor:

• CAAS permits and operational constraints
• Flight windows and altitude limitations
• Tethered operations where required for safety and compliance
• Extra coordination time (especially for tight reporting deadlines)

We’ve operated near Changi and Seletar using tether systems specifically because it keeps operations controlled, reduces risk, and keeps everyone comfortable from safety officers to project managers.

If a provider shrugs off permits like they’re optional, that’s not “efficient.” That’s a future incident report that can stretch your timeline and your budget.

How do you choose the right provider so your report doesn’t come back to haunt you?

If you want to avoid being the person who issued the wrong report, ask these before hiring:

• How do you ensure accuracy across multiple reporting dates?
• Look for RTK workflows, consistent flight plans, QA processes, and how they control for drift.
• What exactly is included in the deliverable?
• Photos only? Orthomosaic? 3D model? Annotations? Measured quantities? Clarity here prevents disputes later.
• What’s your typical turnaround time, and what causes delays?
• Weather, permits, site access, processing time. A good provider tells you upfront.
• Are you compliant for this location?
• CAAS permissions matter. So do operational methods near airports.
• Do you have the right certifications for the job?
• For certain work, LSB certification and proper professional sign-offs can be relevant. If your job needs it, don’t accept “we can do same-same.”

Also, ask to see a real sample report. Not a curated highlight reel. A real one, with limitations, notes, and all.

Why is turnaround time so critical?

A late progress report doesn’t just arrive late. It breaks downstream decisions.

One delayed report pushes the valuation meeting, which pushes payment certification, which slows procurement, which then magically becomes a “site productivity issue.” Meanwhile, everyone is blaming site teams for not catching up.

Fast turnaround helps when it’s paired with QA. But speed without checks is how you get the infamous wrong report that started this whole article.

Drones usually help here because we can capture a lot of site data quickly without needing scaffolds, boom lifts, or half-day access coordination. Less disruption, more coverage, and a cleaner record of what was actually happening on the day.

This is where drone surveying comes into play. It allows us to gather precise site data rapidly, aiding in faster turnaround times while maintaining quality.

What should a solid progress report include so nobody questions it later?

A good progress report should make it hard for anyone to argue with it. Not because it’s fancy, but because it’s consistent and evidence-based.

In our experience, the most defensible reports include:

• Date-stamped, consistent viewpoints (same angles each visit)
• A site-wide orthomosaic or map layer for context
• Clear annotations: what’s completed, what’s in progress, what’s blocked
• Quantifiable metrics where possible: areas completed, volumes moved, zones handed over
• A short “what changed since last report” summary (so people don’t have to play spot-the-difference)

And yes, sometimes the best report includes a note that says: “This area is behind because access was blocked by XYZ.” Honest reporting protects the site team. Sugar-coating doesn’t.

You can learn more about progress monitoring in Singapore or read about our periodic facade inspection work if that’s also on your radar.