Technical dossier
Expediente técnico para comités de aprobación municipal
Qué documentos revisan los consejos y en qué orden
A technical dossier is not a sales folder. When a municipal council or a public works committee opens the file, they are not looking for a pitch. They want to know whether the project is justified, whether the design holds up, and what it costs the treasury in each budget year. If the descriptive report is missing, or the civil works drawings do not match the field survey, the file goes back to the desk. That return can cost a full quarter.
We organize the documents in four blocks. The order matters because committees read in sequence, and each block answers the question the previous one raises.
1. Context and demand
Population served, current connectivity gaps, projected subscribers, and the specific municipal services the network will support. Include the field survey with coordinates and photographs.
2. Network design
Topology, node locations, fiber routes, equipment specifications, and capacity calculations. Drawings must reference the same coordinates used in the survey.
3. Permits and easements
Land tenure, right-of-way requests, environmental notes, and any agreements with private landowners. Missing easements are the most common cause of delay after approval.
4. Schedule and budget by phase
Phased deployment with verifiable milestones, annual budget impact, and a note on assumptions. The committee needs to see what remains unconfirmed.
Each block carries verifiable annexes. A capacity model without the underlying subscriber data is just a number. A civil works plan without the survey reference is a drawing. Committees notice the difference, and they ask about it in session.
The assumptions note is not a weakness. It tells the committee exactly which items still need confirmation, which reduces the back-and-forth between technical staff and council members. In our experience, files that include this note move through review faster than files that present everything as settled.
