Construction schedules that actually work in rural Guatemala

None of those assumptions survive contact with the lake. A construction schedule that works here is built from the ground up against the lake's actual operating conditions. It looks different from a U.S. schedule, it carries a different float, and it is updated against actual progress on a discipline most builders never establish.

This post is about what a realistic schedule looks like, what the most common scheduling mistake at the lake actually is, and how float can be built into a schedule honestly without padding it into a document the client cannot trust.

The lake's working calendar

A realistic Atitlán schedule starts by acknowledging six conditions that a generic schedule ignores.

Rainy season reality. From roughly mid-May through October, afternoon rain is the rule rather than the exception. Concrete pours, exterior plaster, roofing, and exterior earthwork get sequenced into morning windows or shifted out of the rainy months entirely. A schedule that pours slabs in August without acknowledging this will slip — not by days, but by weeks. The rainy season is not an obstacle to plan around. It is a structural feature of the calendar that determines what activities happen when.

Holiday and ceremonial calendar. Semana Santa, Día de los Santos, Christmas through Día de los Reyes, and town-specific patron saint festivals each remove three to seven working days from the calendar. Across a 14-month project these add up to roughly a month of working time that needs to be planned for, not absorbed as slippage. A schedule that does not name these is a schedule that will pretend the project lost time it never had.

Material delivery as a sequence. Imported materials clear Guatemala City customs, transit to a staging location, then move to site by truck and sometimes by boat. Each handoff carries its own timing risk. A serious schedule reflects when material is on site and verified, not when it shipped or when it was promised. We will go deeper on logistics in the next post; for scheduling purposes the principle is that the delivery date on the schedule is the date the material arrives at the site, not the date it leaves the supplier.

Artisan availability. Skilled local trades whether they be master masons, carpenters, plaster specialists, traditional tile setters are not interchangeable and not always available on demand. The schedule blocks their time the way it blocks long-lead materials: in advance, with a deposit if needed. A schedule that assumes any trade can be summoned within a week is a schedule that has not built at the lake.

Permit and inspection windows. OCRET review, municipal inspections, environmental impact study review, INGUAT touchpoints where applicable. These do not move on the project's schedule. The project moves on theirs. Permits at Atitlán typically run four to ten months from submission to issuance. The schedule reflects that range, not an optimistic guess.

Daylight and elevation. Working at 1,500 to 2,000 meters with strong UV, daily wind shifts on the lake, and limited artificial site lighting means productive site hours are shorter than in coastal Guatemala or the U.S. Schedules reflect actual productive hours, not theoretical ones.

A schedule that names these realities is a schedule the owner can trust. A schedule that hides them is a schedule that breaks in month four.

The scheduling mistake nobody admits to

The most common scheduling mistake at the lake and the one that quietly destroys budgets months later is treating the schedule as a sales document instead of a working tool.

The pattern is consistent. A builder hands the owner a clean, optimistic schedule at contract signing. Twelve months, finished by Christmas, ready for the high season. The owner signs partly because the schedule reads as confident. Then the schedule sits in a drawer. Nobody updates it. Nobody compares actual progress against planned progress. By month four the project is six weeks behind, and nobody can say exactly when the slip started because the schedule was never a measurement instrument. It was a sales instrument.

The damage compounds quietly. Without an updated schedule, long-lead materials get ordered late. Trades get sequenced wrong. The owner discovers the delay only when something obvious fails to happen, by which point recovery options are limited and usually expensive. Change orders, rush shipping, expedited fees, and overtime become the only tools left. None of them are cheap.

The fix is structural. A schedule has to be a living document, updated against actual progress every two weeks at minimum, with variances surfaced to the owner in plain language. The honest schedule that shows a three-week slip in month two is infinitely more valuable than the clean schedule that hides a three-month slip until month six.

At Atitlán Build, schedule updates are part of the standard reporting rhythm. Every two weeks the project's actual progress is measured against the baseline, variances are flagged, recovery options are identified, and the next two weeks of activities are confirmed. The schedule is never a static document. If it is not changing, it is not being used.

How honest float works

Every realistic schedule carries float. The question is whether float is shown or hidden.

Hidden float reads as either dishonest or amateur. A schedule with two months of mystery buffer at the end tells the owner that the builder either does not understand the project's risks or does not want to name them. Either way, the owner cannot tell what the buffer is protecting against, cannot tell when it is being consumed, and cannot tell when it is being recovered.

Honest float is named. We carry float in three explicit places, each labeled for what it is.

Weather float against rainy season activities. We name the activity, name the weather risk, and assign visible buffer days. If a slab pour is scheduled for September, the buffer is on the schedule with the reason attached. If the pour completes before the buffer is consumed, the float becomes recovered time visible to the owner. If the buffer is fully consumed, the owner sees which risk materialized and why.

Logistics float on long-lead and imported materials. The schedule shows the supplier's promised delivery date, then adds a logistics buffer for customs, transport, and site delivery. If the material arrives early, the buffer becomes early float on downstream activities. The owner sees the math. The buffer is not a guess; it is a named exposure with a named duration.

Coordination float between trade handoffs. Sequencing rough framing into roofing, into plaster, into finishes is where most projects lose time at Atitlán. Each handoff gets a small explicit buffer rather than one big mystery contingency at the end of the schedule. The buffers are individually small, sometimes a few days, sometimes a week — but together they account for the friction that always appears at handoffs between trades, in any project, anywhere.

Naming float does two things at once. It tells the owner the schedule is realistic, because realistic schedules acknowledge real risks. And it removes the temptation to pad invisibly, because every buffer is accountable to a reason. If a buffer goes unused, that recovery time is visible to everyone. If a buffer gets consumed, the owner sees which risk materialized and can ask why.

The contrast with hidden padding is what builds trust. A schedule with twelve named buffer items reading "rainy season — slab pour" and "customs clearance — imported tile" and "trade handoff — framing to roofing" reads as the work of someone who has built here before. A schedule with two months of unexplained float at the end reads as either inexperience or deception. Owners learn the difference quickly.

A small example of what scheduling discipline prevents

A retreat-center project at the back of one of the lake valleys gives a clear illustration of what happens when scheduling and logistics are not integrated. The builder underestimated the labor required to haul material to the jobsite, which had no road access for the final stretch. The cost premium for transport was real and could have been planned for. Instead, it surfaced during construction as an unbudgeted expense the owner had to absorb. The contractor, a talented architect, by all accounts, ended up spending roughly 70 percent of his time coordinating material movement rather than building. The project did not reach the first floor of a three-story retreat center before the budget ran out.

The schedule and the procurement plan would have caught this. A properly built schedule names the labor required to move material as a separate activity, with a duration and a cost. A properly built procurement plan flags any project where the final logistics segment exceeds normal site access conditions and prices it accordingly. Neither document is exotic. Both are skipped routinely at the lake. The cost is borne by the owner.

The schedule and the SOV: how they connect

The schedule does not stand alone. It is the time dimension of the same project the Schedule of Values describes in dollars. Every SOV line item has a place on the schedule, and every schedule activity has a corresponding SOV value. Together they answer the two questions every owner cares about: how much, and when.

When the schedule slips, the SOV's draw curve slips with it. When a line item completes early, the SOV recognizes the work earlier. When a buffer is consumed, the owner sees both the time impact and the financial implications in the same reporting cycle. The schedule and the SOV are designed to be read together, in the same monthly report, against the same set of facts on the ground.

This is what integrated reporting looks like. Not a single big document, but two documents that reference each other and update on the same rhythm. The owner sees the project in two dimensions at once — time and cost and can trace any change in either back to a specific event on site.

In the next post we will look at the third dimension that makes the lake unlike anywhere else: material logistics at 1,500 meters with no road access.