--- title: "Shareable Site Intelligence Reports: How to Package and Distribute Pre-Construction Analysis" description: "How architects can create comprehensive site intelligence packages with automated research pipelines, shareable links, and multi-format exports to streamline client communication and win more projects." canonical: https://atlasly.app/blog/shareable-site-intelligence-reports published: 2026-03-28 modified: 2026-03-28 primary_keyword: "site intelligence report" target_query: "how to create and share site analysis reports with clients and team" intent: commercial --- # Shareable Site Intelligence Reports: How to Package and Distribute Pre-Construction Analysis > How architects can create comprehensive site intelligence packages with automated research pipelines, shareable links, and multi-format exports to streamline client communication and win more projects. ## Quick Answer A shareable site intelligence report packages the full pre-construction analysis of a site, including planning, environmental, transport, topographic, and contextual findings, into a structured document that can be shared via public link or exported in multiple formats. Automated research pipelines replace manual data gathering, and share links allow clients and team members to review the analysis without requiring software access. ## Introduction The quality of pre-construction analysis has improved dramatically in recent years. Architects now have access to planning data, flood mapping, terrain models, transport scoring, and walkability analysis that would have required weeks of manual research a decade ago. But there is a persistent gap between having the analysis and communicating it. Too often, the site intelligence lives in the analyst's browser, scattered across tabs, map views, and downloaded files. When the client asks for a summary, someone has to manually compile a document. When a team member needs the flood data, they ask the person who ran the analysis. When the project moves to a new phase, the research has to be reconstructed because it was never packaged properly. Atlasly's Site Intelligence Package solves this by running the [17-step site intelligence pipeline](/product/site-intelligence-pipeline), compiling the results into a structured report, and providing share links that give anyone access to the findings without requiring a login. Combined with exports in DXF, GeoJSON, Shapefile, SVG, CSV, and PDF, the package serves every downstream workflow from client presentations to CAD integration. ## Why is packaged site intelligence better than loose research files? Loose research files create five problems that packaged intelligence solves. **Fragmentation**: When the flood data is in one PDF, the planning context is in a browser bookmark, the transport scoring is in a screenshot, and the topography is in a downloaded file, no one has the complete picture. Each team member works from a partial view of the site story. **Version confusion**: When research is updated, which files are current? If the flood mapping was re-checked after the initial review, does everyone have the new version? Loose files have no built-in versioning or currency indicator. **Communication overhead**: Every time a new team member, consultant, or client stakeholder needs the research, someone has to find, compile, and send it. That overhead is pure waste. It adds no analytical value and consumes time that could be spent on design. **Presentation quality**: A collection of screenshots and downloaded files does not communicate professional competence. A structured report with consistent formatting, clear findings, and a logical narrative demonstrates that the analysis was thorough and the team is organised. **Loss over time**: When a project pauses and resumes months later, loose files may have been deleted, moved, or forgotten. A packaged report with a persistent share link survives project interruptions. Atlasly's Site Intelligence Package addresses all five problems by automating the compilation, structuring the output, and providing persistent access. The 17-step research pipeline ensures completeness. The report format ensures consistency. The share link ensures distribution. ## What does the 17-step automated research pipeline cover? The pipeline is structured to produce a comprehensive site picture without manual data gathering. Each step targets a specific aspect of pre-construction intelligence: The pipeline covers planning context and policy designations, environmental and flood risk indicators, topographic and elevation analysis, transport accessibility and public transport scoring, walkability and 15-minute city metrics, surrounding built context including building heights and uses, street-level conditions, solar orientation and shadow considerations, demographic and census context, land ownership indicators, historic planning application records, conservation and heritage designations, ecological and green infrastructure context, utilities and infrastructure proximity, noise and air quality indicators, site photographs and street imagery, and a synthesis summary that brings the key findings together. Each step draws from the data layers available in Atlasly's platform and produces a structured output that feeds into the final report. The automation matters because it eliminates the selection bias that affects manual research. When an architect researches manually, they tend to focus on the factors they are most concerned about and may overlook less familiar issues. The automated pipeline checks everything, regardless of the researcher's assumptions about what will matter. The synthesis step is particularly important. Raw data from 17 research areas is not useful in itself. The synthesis summarises the key findings, highlights risks and opportunities, and frames the analysis in terms that a client or decision-maker can act on. This is where the report becomes intelligence rather than information. For architects using the pipeline as part of a fee proposal or competition entry, the speed is the decisive advantage. A comprehensive site intelligence package that would take two to three days of manual research can be generated in minutes. That means the analysis can be included in every proposal, not just the ones with enough fee to justify the research time. ## How do share links work for client and team distribution? Atlasly's share links create a public URL that gives anyone access to the site intelligence package without requiring a login or subscription. The link opens the full report in a browser, with all maps, data layers, and findings visible in the same structured format. This design decision reflects how site analysis is actually consumed in practice. The architect who runs the analysis is rarely the only person who needs to see it. The client principal needs it for the board meeting. The planning consultant needs the policy summary. The cost consultant needs the site conditions overview. The project architect joining the team next week needs the full picture. Without share links, each of those stakeholders requires a separate communication: an email with attachments, a meeting to walk through the findings, or access to the platform itself. Share links collapse that distribution into a single URL that can be sent in an email, dropped into a project management tool, or included in a fee proposal. The links carry a 30-day expiry, which serves two purposes. First, it ensures that the report is consumed while it is current. Site conditions and planning context can change, and a report from six months ago should not be treated as current intelligence. Second, it provides a natural refresh point. If the project continues beyond 30 days, regenerating the package ensures the team is working from up-to-date information. For practices that manage multiple projects simultaneously, the share link model also creates a lightweight audit trail. Each shared package has a URL that records what was shared, when, and what the analysis contained at that point. If a client later questions whether a constraint was identified during feasibility, the share link provides evidence. ## Which export formats serve which workflows? The value of a site intelligence package depends on whether it can move into the workflows where work actually happens. Different team members and different project stages require different formats. **PDF** is the universal distribution format. Every client, consultant, and committee member can open a PDF. The site intelligence report in PDF format is the primary deliverable for client presentations, fee proposals, planning pre-application meetings, and internal design reviews. It should contain the narrative summary, key maps, scored findings, and constraint highlights in a format that can be printed, emailed, or projected. **DXF** serves the CAD workflow. When the architect needs to import the site boundary, constraint layers, and context geometry into AutoCAD or similar software, DXF preserves the coordinate reference system and layer structure. This is the bridge between analysis and design: the site boundary arrives in the drawing at the correct location, oriented correctly, with constraint layers that can be toggled on and off. **GeoJSON** serves GIS and web mapping workflows. For teams that maintain project GIS databases, planning consultants who work in QGIS, or digital teams building project websites with interactive maps, GeoJSON provides the structured spatial data with attributes intact. **Shapefile** serves the traditional GIS community. Many local authorities, environmental consultants, and infrastructure planners still work with Shapefile format. Exporting in this format ensures compatibility with established GIS workflows without requiring format conversion. **SVG** serves graphic design and presentation workflows. When the site plan, constraint map, or analysis diagram needs to be included in a designed document, pitch deck, or publication, SVG provides scalable vector graphics that can be edited in Illustrator, Figma, or similar tools. **CSV** serves data analysis workflows. When the underlying data, such as transport scores, amenity distances, or compliance results, needs to be loaded into a spreadsheet for custom analysis, CSV provides the simplest data transfer format. Atlasly's export pipeline supports all six formats from the same intelligence package. This means the architect exports the PDF for the client, the DXF for the design team, and the GeoJSON for the planning consultant from a single analysis session. No reformatting, no manual conversion, no coordinate system confusion. The full scope of what that package should contain is set out in the [pre-construction site analysis complete guide](/blog/pre-construction-site-analysis-complete-guide). ## From Practice We were competing for a residential commission against two other practices. The client had given all three teams the same site and the same brief. Instead of leading with design ideas in our pitch, we led with a site intelligence report that we shared via link 48 hours before the interview. The report covered planning context, flood risk, transport scoring, walkability, and a feasibility summary. The client told us afterward that we were the only team that demonstrated we understood the site before trying to design on it. We won the project. The intelligence package took less than an hour to produce. ## Frequently Asked Questions **What is a site intelligence report?** It is a structured package of pre-construction findings covering planning, environmental, transport, topographic, and contextual analysis for a specific site, compiled into a shareable format with maps, scores, and actionable summaries. **Who can access a shared site intelligence link?** Anyone with the URL can access the report without needing a login or subscription. The link opens the full report in a browser with all maps, data, and findings visible. **How long do share links remain active?** Share links carry a 30-day expiry to ensure the report is consumed while current. If the project continues, the package can be regenerated with updated data and a fresh link issued. **Can the site intelligence package be exported into CAD software?** Yes. DXF export preserves the site boundary, constraint layers, and context geometry with coordinate reference system integrity for direct import into AutoCAD, Revit, and similar tools. **How does a site intelligence package differ from a site visit report?** A site intelligence package is a data-driven analysis covering planning, environmental, transport, and contextual factors from desk research. A site visit report records physical observations from an in-person visit. Both are valuable, but the intelligence package is faster and more comprehensive for the desk-research component. ## Conclusion The gap between having site intelligence and being able to share it effectively is where projects lose time, miscommunicate, and sometimes lose commissions. A packaged, shareable site intelligence report with automated research, structured findings, and multi-format exports closes that gap. If you want to produce and share comprehensive site intelligence on your next project, try Atlasly's Site Intelligence Package and see how much faster the analysis reaches the people who need it. ## Related Reading - https://atlasly.app/blog/export-site-analysis-data-to-autocad-and-revit - https://atlasly.app/blog/pre-construction-due-diligence-for-architects - https://atlasly.app/blog/ai-site-analysis-vs-manual-research --- Source: https://atlasly.app/blog/shareable-site-intelligence-reports Platform: Atlasly — AI site intelligence for architects, engineers, and urban planners. https://atlasly.app