Informe De Supervisor De Obra

How The Site Supervisor Report Actually Works In Practice

The Informe De Supervisor De Obra is a mandatory daily document required by most Spanish-language construction regulatory frameworks. It tracks what happens on site each day: workers present, materials delivered, work completed, delays, safety incidents, and weather conditions. The form varies slightly between countries, but the core structure is nearly identical across Spain, Mexico, Colombia, and other jurisdictions that require it. I started filling these out for an architecture firm in Mexico City around 2009. The first version was handwritten in a spiral notebook. Within two years every major contractor on my projects was using structured PDF templates that had to be uploaded to the client portal weekly. The shift wasn't just organizational. It changed how supervisors treated the document, moving it from something filed at the end of the month to something that actually influenced decisions in real time.

Where To Get The Informe De Supervisor De Obra Template

You can find valid templates from several sources depending on your country and the type of project. For Mexico, CONSTRUCTORES.org publishes a free downloadable version formatted to current NOM standards. In Spain, the Colegio Oficial de Arquitectos de Madrid provides a template compatible with the CODIFICACIÓN TÉCNICA DE LA EDIFICACIÓN requirements. Colombia's INCOPOR provides theirs through their member portal, which requires registration but gives you access to versions tailored to different project sizes. For general Latin American use, the World Bank's procurement documentation portal hosts a multilingual version that works across multiple jurisdictions if you are managing cross-border projects. Most of these are free PDFs or Word documents you can edit directly. Here is the practical method I use now that cuts the daily filing time to roughly fifteen minutes. I fill the header fields first: date, project name, location, supervisor name, and contract number. These never change mid-project except for the date, so once you have a master file with those locked in, you just open a fresh copy each morning. Next I write the labor count by trade. This is the section most supervisors rush through, and it is also the section that causes the most problems later. If you write "20 workers" and a dispute comes up about whether you actually had enough crew on a concrete pour day, you need to know exactly how many were there and what they were doing. I break it down by trade: carpenters, rebar workers, masons, electricians, helpers. Even if the breakdown feels tedious, it saves hours during claims review. The materials section comes next. I log deliveries only when they arrive, with quantity, supplier name, and intended use. This creates a paper trail that matches your invoicing schedule. Miss this step and you will have no way to verify whether a charge on a monthly payment application actually corresponds to material that was delivered and stored on site. The work completed section is where the template often falls short. Most standard forms have a single text box labeled "Avance de obra" or "Progress achieved." A proper entry needs to reference the specific activity code from the CPM schedule, not a vague description. Instead of writing "continued structural work," I write "Activity 3.2.1 - Column castings, Level 2, 6 of 12 units completed per schedule reference CPS-REV4." That references the exact line item your scheduler uses and makes it trivial to cross-check progress claims against the baseline.

Delays and incidents get their own section. I log weather separately from delays because they are not the same thing. Rain did not cause a delay if the crew was working indoors that day and the schedule had float built in. I learned this distinction the hard way on a warehouse project in Querétaro where a three-day rain event was attributed to us as a delay cause, but the schedule showed we had fourteen days of float at that point in the work. The counterargument was bulletproof once I could point to the weather data and the float analysis side by side. Both belonged in the report, but clearly separated.

A Specific Problem I Encountered And How I Fixed It

On a hospital renovation project in Guadalajara, the municipal inspector refused to sign off on the Informe De Supervisor De Obra because the template we were using did not include a field for environmental compliance data, which a 2018 regulation amendment had added as mandatory. The form from our professional college was the 2016 version. We had been submitting it for eight months without issue until the final inspection cycle, when the inspector flagged every single submission as non-compliant. This meant roughly two hundred daily reports needed to be corrected and resubmitted, which would have delayed the certificate of completion by weeks. The workaround was not to redo all two hundred reports. I pulled the revised template, identified which sections the new regulation actually affected (only the environmental and waste disposal fields), and created an addendum sheet that we attached to each past report going forward. The addendum referenced the original report number, date, and the specific compliance data that was now required. We submitted the addendum package to the inspector along with a brief cover letter citing the regulation number and amendment date. The inspector accepted it. The key was that the original reports were not invalid, they were simply incomplete under the newer standard. Adding the missing fields prospectively satisfied the requirement without invalidating the entire submission history. This approach only works if your original reports were at least internally consistent and legible. If the early reports were scribbled on notebook paper with missing dates, you are out of luck and will need to reconstruct them from attendance records and delivery invoices, which is significantly more work.

Counter-Intuitive Details Beginners Miss

Most people treating this document as a compliance checkbox miss two things that matter later. First, the signature block is not administrative paperwork. In a payment dispute, the supervisor's signed daily report is primary evidence of what was actually accomplished on a given date. An unsigned or retrospectively signed report loses most of its weight in arbitration. I have seen reports signed on Friday for the entire week, which is fine for convenience but opens you to a challenge that any particular day's entries were fabricated. The safest practice is to sign each report on the day it covers, even if you fill it out the following morning before heading back to site. Second, the progress percentages in the report must align with your monthly payment applications. I once caught a discrepancy where the daily report showed sixty percent structural completion by mid-month, but the payment request claimed eighty-five percent. The gap existed because the scheduling software and the daily report template were using different activity definitions. The client's quantity surveyor caught it during review, which triggered a full audit of the month's submissions. Aligning the report template with your scheduling software's activity codes at the project outset prevents this kind of problem entirely. It takes about an hour of setup at project mobilization and saves days of dispute resolution later.

Where This Process Breaks Down

The daily report system fails when the site supervisor treats it as someone else's responsibility. In larger projects the superintendent or a junior engineer may fill it out while the licensed supervisor signs without reviewing the entries. This creates a document that looks complete but contains factual errors, like listing materials as delivered when they were only ordered, or reporting work completed on activities that were actually delayed. The report then becomes a liability rather than a protection. There is no technical enforcement mechanism that prevents this. It relies on the supervisor actually reading and verifying the entries before signing, which means treating the report as a management tool rather than an administrative formality. The system also breaks down when projects run long enough that the template gets updated mid-construction. If your contract references a specific template version and the regulating authority releases a new one, you need to establish whether the new version applies retroactively or only to submissions made after the effective date. I found this ambiguity on a federal infrastructure project where the answer depended on which level of government had jurisdiction, and the contract documents did not specify. The workaround was to use both templates simultaneously, noting which version governed each submission, and get the client's representation in writing confirming acceptance of the hybrid approach before proceeding.

Downloading The Standard Informe De Supervisor De Obra Template

The most widely used template in Mexico is available through CONSTRUCTORES.org under their free resources section. The file is a fillable PDF formatted to current SCT standards and includes all required fields for federal and state projects. For Spain, the downloadable version from the Colegio Oficial de Arquitectos de Madrid covers the basic COE requirements but may need supplementation depending on your regional federation's additional obligations. If you are working across multiple countries on the same project, the World Bank template is the closest to a universal format, though you should still verify local regulatory additions before relying on it as your primary document. All three sources link directly from their respective homepages without requiring paid subscriptions, though some Colombian resources do require free registration before access. The practical value of this document depends entirely on how carefully it is maintained. A well-kept daily report will resolve a dispute in fifteen minutes. A neglected one will generate months of correspondence and possibly litigation. The effort required to keep it accurate is small compared to the cost of getting it wrong.