--- title: "What Is a Site Intelligence Package and Why Does It Beat a Folder Full of PDFs?" description: "A site intelligence package is a structured pre-construction deliverable combining planning, environmental, transport, topographic, and contextual findings into one shareable report with usable exports." canonical: https://atlasly.app/blog/what-is-a-site-intelligence-package published: 2026-03-28 modified: 2026-03-28 primary_keyword: "site intelligence package" target_query: "what is a site intelligence package" intent: informational --- # What Is a Site Intelligence Package and Why Does It Beat a Folder Full of PDFs? > A site intelligence package is a structured pre-construction deliverable combining planning, environmental, transport, topographic, and contextual findings into one shareable report with usable exports. ## Quick Answer A site intelligence package is a structured pre-construction deliverable that combines planning, environmental, transport, topographic, and contextual findings into one shareable report with usable exports. It is more valuable than loose research files because the whole team can review the same site story and move from analysis into design without rebuilding the evidence. ## Introduction The phrase "site intelligence" sounds like marketing language until you have spent a week chasing the alternative. On most projects, the alternative is a folder. It contains a screenshot from the flood map portal, a PDF from the planning register, a terrain export from a GIS tool, some notes from a site visit, and maybe a consultant's preliminary report that arrived in a format nobody can open in CAD. The folder is technically complete. Every piece of evidence the team needs is somewhere inside it. But it is not a deliverable. It is a filing cabinet. Nobody can review the full site story in one sitting. Nobody can share it with a client and expect them to understand the constraints. And nobody can take that folder and start drawing without first rebuilding the site geometry from scratch. A site intelligence package solves this by structuring the same evidence into a single deliverable: one report, one set of exports, one shareable link. The difference is not the data. It is the assembly. Atlasly's [17-step site intelligence pipeline](/product/site-intelligence-pipeline) produces exactly this kind of package, covering geocoding through to AI synthesis, with CAD-ready exports that survive into downstream design. ## What belongs inside a real site intelligence package? A useful site intelligence package covers the same ground as a thorough manual site assessment, but delivers it in a format that the whole team can review, share, and build from. At minimum, it should include: **Planning and policy context.** Zoning designations, planning history, relevant policy references, and any compliance indicators. Not just what the map shows, but what the policy text says about what can be built. **Environmental constraints.** Flood risk, heritage designations, ecology triggers, noise exposure, and any other constraint that could change the design response or the planning route. Each constraint should be sourced and cited, not summarised from memory. **Physical site conditions.** Topography, elevation profiles, slope analysis, and surrounding building context. This is the data that affects foundation strategy, drainage, access gradients, and massing relationships. **Transport and access.** PTAL scores, walking isochrones, public transport mapping, and street network classification. This drives parking ratios, density arguments, and the transport statement. **Exportable geometry.** DXF, DWG, or GeoJSON files with proper coordinate systems and named layers, so the site context moves into AutoCAD, Revit, or SketchUp without manual redrawing. This is what separates a site intelligence package from a research summary. **A structured narrative.** Not just data layers, but a written synthesis that connects the findings into a site story: what the opportunities are, what the constraints mean for design, and what should be investigated further. Atlasly's automated pipeline produces all of these in a single workflow, generating the full [pre-construction site analysis](/blog/pre-construction-site-analysis-complete-guide) package from a site boundary in minutes. ## Why do loose PDFs and screenshots fail teams? Loose files fail for three reasons that have nothing to do with the quality of the research. **Format fragmentation.** A flood map screenshot, a planning PDF, and a terrain CSV all contain useful information, but they cannot be overlaid, cross-referenced, or viewed in the same spatial context. The architect has to mentally stitch the site story together, which introduces interpretation gaps. **No coordinate integrity.** Screenshots and PDFs do not carry spatial data. When the design team needs to place the flood boundary or the heritage buffer on the CAD drawing, they are estimating positions by eye. That estimate becomes the foundation for massing, setback, and layout decisions. **Sharing breaks the package.** When the project architect sends the folder to a colleague, the client, or a consultant, the recipient has to reconstruct the same mental model. There is no single surface where the whole site story is visible. The result is meetings where everyone is looking at different evidence and drawing different conclusions. A structured site intelligence package solves all three by delivering the evidence in one place, with geometry that carries coordinates, and a narrative that connects the data to design consequences. Atlasly's [shareable site intelligence reports](/blog/shareable-site-intelligence-reports) make the full package accessible via a single link with no login required. ## Which outputs should go to the client, the architect, and the engineer? Different stakeholders need different views of the same site intelligence. **The client** needs the narrative: what the site can support, what the key risks are, and whether the project is worth pursuing. The PDF report and the constraint summary serve this audience. They do not need DXF files or technical layer data. **The project architect** needs everything: the narrative for context, the map layers for spatial understanding, and the CAD exports for design. DXF and DWG files with proper coordinates and named layers are the critical deliverable because they become the base drawing for concept design. **The structural or civil engineer** needs terrain data, elevation profiles, and physical constraint layers. GeoJSON or Shapefile exports serve GIS-native workflows. IFC exports serve BIM coordination. **The planning consultant** needs the policy context, compliance indicators, and planning history. The structured report with cited sources saves them from re-researching constraints they should have been briefed on. The best site intelligence packages are structured so that each stakeholder can extract their view without the project architect having to repackage the data for every audience. Atlasly's export pipeline produces [14 formats](/blog/export-site-analysis-data-to-autocad-and-revit) precisely for this reason. ## How does a site intelligence package change proposals and pre-app meetings? A structured site intelligence package changes two things about how firms win and present work. **Proposals become evidence-based.** When a firm responds to a brief with a site intelligence package attached, the client sees that the team already understands the site. The constraints are identified. The opportunities are mapped. The data is structured and shareable. This is a different proposition from a firm that promises to "carry out a thorough site analysis" after appointment. **Pre-application meetings become productive.** Planning officers respond better when the applicant arrives with structured evidence showing they understand the policy context, the environmental constraints, and the heritage sensitivities. A site intelligence package gives the architect a defensible position from the first meeting, rather than spending the pre-app discovering constraints the officer expected them to know already. In both cases, the package does the same thing: it compresses the "getting to know the site" phase so that design and planning conversations can start from a shared evidence base instead of from assumptions. ## From Practice On a mixed-use scheme in Birmingham, we sent the client our site intelligence package before the first design meeting. It included the flood constraints, the heritage buffer from a nearby conservation area, the PTAL score, and the terrain profile showing a 4-metre level change across the site. The client's previous architect had spent three weeks gathering the same information manually and still missed the conservation area adjacency. We won the project because the client could see we understood the site before we had drawn anything. ## Frequently Asked Questions **What is a site intelligence package?** A site intelligence package is a structured pre-construction deliverable that combines planning, environmental, transport, topographic, and contextual findings into one report with usable exports. It replaces loose PDFs, screenshots, and consultant notes with a single shareable package. **How is a site intelligence package different from a site analysis report?** A traditional site analysis report is typically a PDF document. A site intelligence package includes the report but also provides exportable geometry (DXF, DWG, GeoJSON), interactive maps, cited data sources, and a shareable link. The exports are the key difference because they carry the analysis into downstream design tools. **Who should receive the site intelligence package?** The project architect, client, structural engineer, planning consultant, and any other stakeholder involved in early design decisions. Each can extract the outputs relevant to their role without the architect needing to repackage the data. **Can a site intelligence package replace a consultant's report?** No. It replaces the manual desk research phase and provides a structured evidence base, but specialist reports like formal flood risk assessments, heritage impact assessments, or ecological surveys still require qualified professionals. The package identifies where those specialist inputs are needed. **How long does it take to produce a site intelligence package with Atlasly?** Atlasly's 17-step pipeline produces a complete site intelligence package in under 5 minutes, including CAD exports, PDF report, and AI synthesis. The equivalent manual process typically takes 2-3 working days across multiple data sources. ## Conclusion A folder full of PDFs is evidence. A site intelligence package is a deliverable. The difference matters because teams that start design from a structured, shareable, spatially accurate site package make better early decisions and waste less time rebuilding the evidence base. If your current pre-construction workflow produces a folder instead of a package, Atlasly can change that. Try it on your next site and see how much faster the team moves from analysis to design when the intelligence is already assembled. ## Related Reading - https://atlasly.app/blog/shareable-site-intelligence-reports - https://atlasly.app/blog/pre-construction-due-diligence-for-architects - https://atlasly.app/blog/export-site-analysis-data-to-autocad-and-revit --- Source: https://atlasly.app/blog/what-is-a-site-intelligence-package Platform: Atlasly — AI site intelligence for architects, engineers, and urban planners. https://atlasly.app