{"id":8646,"date":"2026-11-17T11:09:55","date_gmt":"2026-11-17T11:09:55","guid":{"rendered":"https:\/\/blog.filio.io\/?p=8646"},"modified":"2026-11-17T11:09:58","modified_gmt":"2026-11-17T11:09:58","slug":"as-planned-as-built-spatial-review","status":"publish","type":"post","link":"https:\/\/blog.filio.io\/as-planned-as-built-spatial-review\/","title":{"rendered":"As-Planned vs. As-Built: Review Spatial Evidence Before Calling a Deviation"},"content":{"rendered":"\n<div id=\"blog-101-reader\">\n<p>Before calling something a deviation, confirm the reference revision, the identity of the observed element, the spatial relationship between the datasets and the evidence needed for the decision. Otherwise, a mismatch on screen may be a reference problem rather than a construction problem.<\/p>\n<figure class=\"wp-block-image size-full\" id=\"vis-101-01\"><picture><source media=\"(max-width:600px)\" srcset=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v1M-review.png\" width=\"390\" height=\"864\"><img loading=\"lazy\" src=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v1D-review.png\" width=\"1200\" height=\"820\" alt=\"Four review stages connect a drawing reference and field evidence to interpretation and responsible verification.\" loading=\"lazy\" decoding=\"async\" style=\"width:100%;height:auto\"><\/picture><figcaption>A review is traceable only when the source, comparison basis and decision owner remain connected.<\/figcaption><\/figure>\n<h2 id=\"establish-which-planned-condition-governs-the-question\">Establish which planned condition governs the question<\/h2>\n<p>\u201cCompare with the plan\u201d is incomplete. Record the drawing or model identifier, revision, relevant level or zone and the particular detail or requirement under review. Check whether an approved change affects the comparison.<\/p>\n<p>Keep the record&#8217;s date distinct from the reference&#8217;s revision date. A capture may be valid evidence of a condition at that time even when a later design revision changes what the team expects. Do not overwrite that history to make the images appear to match the latest drawing.<\/p>\n<p>The review also needs a defined question. \u201cDoes this view identify the partition location?\u201d is different from \u201cDoes the installed partition comply with the design?\u201d The second may require dimensions, concealed details, performance evidence and an authorized technical decision.<\/p>\n<h2 id=\"align-the-references-before-interpreting-the-difference\">Align the references before interpreting the difference<\/h2>\n<p>Registration relates datasets through an identified spatial transformation. It is not the same as dragging two views until they look similar. Confirm the units, scale, axes or coordinate convention, and the basis used to associate the observed scene with the planned one.<\/p>\n<p>Research on <a href=\"https:\/\/isprs-archives.copernicus.org\/articles\/XLVIII-G-2025\/1455\/2025\/isprs-archives-XLVIII-G-2025-1455-2025.html\" target=\"_blank\" rel=\"noopener\">scan-vs-BIM registration<\/a> identifies repeated and symmetric building geometry as a challenge when finding correspondences. A similar column or doorway is not necessarily the same reference feature.<\/p>\n<p>For a dimensional comparison, ask what independent evidence checks the alignment and what uncertainty is material to the decision. Do not report an offset from a screen overlay when scale or registration has not been established.<\/p>\n<p>Plans themselves can differ from built conditions. The research paper <a href=\"https:\/\/arxiv.org\/abs\/2408.01737\" target=\"_blank\" rel=\"noopener\">Tightly Coupled SLAM With Imprecise Architectural Plans<\/a> studies a particular method that accounts for this issue while estimating alignment and deviations. It does not make ordinary plan overlays self-validating, and it is not evidence of a Filio capability.<\/p>\n<h2 id=\"keep-observation-discrepancy-and-acceptance-separate\">Keep observation, discrepancy and acceptance separate<\/h2>\n<p>An observation describes what a source shows: \u201cThe captured view shows the partition return beside column C4.\u201d<\/p>\n<p>A discrepancy is a difference identified against an applicable reference after the comparison basis is established. If that basis is uncertain, use \u201capparent mismatch\u201d or describe the unresolved reference instead of asserting a measured deviation.<\/p>\n<p>Technical acceptance is a decision made by the responsible authority using the project&#8217;s requirements and sufficient evidence. The person assembling a photo package may not be the person entitled to make that decision.<\/p>\n<p>A visible surface can support an observation without proving what is behind it. An absent object in a partial scan is not necessarily absent from the site. Keep \u201cnot observed,\u201d \u201cnot supplied\u201d and \u201cconfirmed absent\u201d separate.<\/p>\n<h2 id=\"worked-example-a-partition-return-beside-a-riser\">Worked example: a partition return beside a riser<\/h2>\n<p>Consider a fictional commercial fit-out. An off-site coordinator receives photographs P-21 and P-22 and a model-view screenshot showing a partition return near riser R-04. The capture package names drawing A-203 revision C. The coordination meeting is using revision D.<\/p>\n<p>The screen comparison appears to put the partition on a different line. No registration report, control references or independently checked dimensions are included. Part of the junction is obscured by stored materials. This is enough to open a focused question, not enough to declare the installation wrong.<\/p>\n<p>The coordinator first asks the document controller to confirm the governing revision and any relevant approved change. Next, the capture lead identifies the source dataset, capture date, level, units and basis for the displayed alignment. Only then can the responsible design or survey professional determine whether a dimensional comparison is valid and what further evidence is needed.<\/p>\n<p>The stored materials create a separate coverage limit. Resolving the drawing revision will not reveal the concealed junction. Any additional observation must follow the project&#8217;s authorized access and safety arrangements.<\/p>\n<figure class=\"wp-block-image size-full\" id=\"vis-101-02\"><picture><source media=\"(max-width:600px)\" srcset=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v2M-review.png\" width=\"390\" height=\"742\"><img loading=\"lazy\" src=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v2D-review.png\" width=\"1200\" height=\"722\" alt=\"Fictional revision and source-photo references leave alignment and an obscured junction unresolved.\" loading=\"lazy\" decoding=\"async\" style=\"width:100%;height:auto\"><\/picture><figcaption>The fictional example separates a revision question from missing coverage; neither is a measured deviation.<\/figcaption><\/figure>\n<h3 id=\"record-the-review-without-compressing-it-into-pass-or-fail\">Record the review without compressing it into \u201cpass\u201d or \u201cfail\u201d<\/h3>\n<figure class=\"wp-block-table\" role=\"region\" tabindex=\"0\" aria-label=\"Spatial evidence review decision record\"><table><thead><tr><th scope=\"col\"><strong>Review item<\/strong><\/th><th scope=\"col\"><strong>Evidence available<\/strong><\/th><th scope=\"col\"><strong>Unresolved point<\/strong><\/th><th scope=\"col\"><strong>Responsible follow-up<\/strong><\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Planned reference<\/th><td>Capture package cites A-203 C; meeting uses D.<\/td><td>Which revision and approved change govern this question?<\/td><td>Document controller confirms the reference; technical reviewer interprets it.<\/td><\/tr><tr><th scope=\"row\">Element identity<\/th><td>P-21\/P-22 show the partition near the stated riser.<\/td><td>Whether the subject and level association are sufficiently established.<\/td><td>Capture lead supplies the source context and identifying view.<\/td><\/tr><tr><th scope=\"row\">Spatial comparison<\/th><td>A model-view screenshot suggests a different line.<\/td><td>Units, scale, alignment basis and quality checks are not supplied.<\/td><td>Capture\/survey specialist confirms whether a dimensional comparison is valid.<\/td><\/tr><tr><th scope=\"row\">Coverage<\/th><td>Stored materials obscure part of the junction.<\/td><td>Condition of the hidden portion.<\/td><td>Responsible reviewer identifies the needed evidence and authorized safe-access route.<\/td><\/tr><tr><th scope=\"row\">Decision<\/th><td>An apparent mismatch has been recorded.<\/td><td>No measured deviation or technical acceptance is established.<\/td><td>Authorized professional records the conclusion, evidence and any remaining condition.<\/td><\/tr><\/tbody><\/table><figcaption>Fictional review record; no measured deviation or technical acceptance is established.<\/figcaption><\/figure>\n<p>This is a human decision record, not an automated assessment or a Filio software screen. It gives each unresolved issue a specific route without pretending that every question requires another photograph.<\/p>\n<h2 id=\"ask-for-the-evidence-that-could-change-the-decision\">Ask for the evidence that could change the decision<\/h2>\n<p>A useful request names the source, the unresolved relationship and the required response. For this example:<\/p>\n<p>\u201cPlease confirm whether A-203 revision C or D governs the R-04 partition comparison and identify the relevant approved change, if any. Provide the source and alignment basis for the model-view screenshot. The junction is obscured in P-21\/P-22; identify whether an existing authorized record shows it. No dimensional deviation or installation acceptance has been established in this review.\u201d<\/p>\n<p>This wording preserves the useful images while preventing an unsupported conclusion. It also allows a response other than a new scan: an existing change record or a corrected reference may answer part of the question.<\/p>\n<p>Where an alleged deviation affects a dependent activity, use the project&#8217;s established RFI, issue or technical-review process. Record who owns the decision and the agreed return point. Do not treat a closed message thread, uploaded image or report approval button as evidence that construction has been technically accepted.<\/p>\n<h2 id=\"preserve-the-chain-from-source-to-finding\">Preserve the chain from source to finding<\/h2>\n<p>Retain the original source references and the version used in the review. If the capture is processed again or the reference changes, identify the new version and explain which conclusion, if any, changed.<\/p>\n<p>A compact review package should connect the location and element, the planned reference, the observed source, the comparison basis, the finding&#8217;s limits and the responsible response. It should let a colleague reconstruct why the question was raised without relying on memory.<\/p>\n<p>For a purely photographic assessment, the <a href=\"https:\/\/www.filio.io\/blog\/remote-construction-photo-review\" target=\"_blank\" rel=\"noopener\">remote construction photo-review guide<\/a> provides a simpler Visible \/ Unknown \/ Next Action worksheet. A spatial comparison adds another requirement: validating the relationship between the planned and observed references.<\/p>\n<p>When capture context is uncertain, consult the <a href=\"https:\/\/www.filio.io\/blog\/construction-photo-metadata-review\" target=\"_blank\" rel=\"noopener\">photo metadata review guide<\/a>. When the resulting issue becomes a defined correction item, the <a href=\"https:\/\/www.filio.io\/blog\/punch-list-photos\" target=\"_blank\" rel=\"noopener\">punch-list photo guide<\/a> addresses documenting that item and its response. Neither substitutes for confirming the governing technical requirement.<\/p>\n<h2 id=\"use-filio-for-the-connected-record-not-an-invented-verdict\">Use Filio for the connected record, not an invented verdict<\/h2>\n<figure class=\"wp-block-image size-full\" id=\"vis-101-03\"><picture><source media=\"(max-width:600px)\" srcset=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v3M-review.png\" width=\"390\" height=\"1128\"><img loading=\"lazy\" src=\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101v3D-review.png\" width=\"1200\" height=\"1139\" alt=\"A Filio sample record shows a window photograph and existing Measure and Sheet 1 tags.\" loading=\"lazy\" decoding=\"async\" style=\"width:100%;height:auto\"><\/picture><figcaption>Authentic Filio Web App sample record, separate from the fictional R-04 scenario. It illustrates record review, not automatic comparison, alignment or technical acceptance.<\/figcaption><\/figure>\n<p>Filio&#8217;s verified project organization, tags, contextual fields, retrieval and reporting can help keep selected field records available for review. Use those capabilities to connect relevant evidence and explain the question in the project&#8217;s existing process.<\/p>\n<p>A completed Filio 3D model can also be inspected using the documented viewer and supported measurement interactions. The <a href=\"https:\/\/www.filio.io\/academy\/how-do-i-review-and-measure-a-3d-model-in-filio\" target=\"_blank\" rel=\"noopener\">3D review and measurement guide<\/a> explains that visible geometry and displayed values still need interpretation in context.<\/p>\n<p>Do not describe this as automatic BIM deviation detection, certified registration, survey validation or as-built acceptance. A plan-associated photo and a measured point cloud have different evidential roles; using both in a discussion does not make them equivalent.<\/p>\n<p>If selected records are assembled into a report, make sure the reference revision and unresolved questions remain clear in the version the recipient receives. The <a href=\"https:\/\/www.filio.io\/academy\/how-to-create-a-report-in-filio-web-app\" target=\"_blank\" rel=\"noopener\">Filio report-creation guide<\/a> covers assembly, not the technical authority to approve construction.<\/p>\n<h2 id=\"close-the-comparison-that-is-supported\">Close the comparison that is supported<\/h2>\n<p>Suppose the revision check shows that D intentionally changed the partition return. The coordinator can close the revision mismatch and retain that explanation with the source references. That does not resolve the obscured junction or validate dimensions that were never checked.<\/p>\n<p>Alternatively, if an apparent difference remains after the references are reconciled, the responsible professional can specify the next measurement, inspection or design response. The initial record should remain an accurate account of what was known at the time.<\/p>\n<p>The aim is not to avoid conclusions. It is to make conclusions traceable to the correct reference, sufficient evidence and the person responsible for deciding. A clear boundary between those three is more useful than a confident overlay.<\/p>\n<p>Reader note: R-04, A-203 and the photo references are fictional teaching examples. This is a documentation-review framework, not a survey method, tolerance standard, inspection instruction or authorization to accept work.<\/p>\n<\/div>\n<style>#blog-101-reader h2[id],#blog-101-reader h3[id]{scroll-margin-top:210px}#blog-101-reader .wp-block-table{max-width:100%;overflow-x:auto}#blog-101-reader table{border-collapse:collapse;width:100%;min-width:640px}#blog-101-reader th,#blog-101-reader td{vertical-align:top;overflow-wrap:normal;word-break:normal;padding:12px;border:1px solid #ddd}#blog-101-reader th[scope=\"row\"]{min-width:150px}#blog-101-reader figure{margin:32px 0}#blog-101-reader picture{display:block}#blog-101-reader figcaption{font-size:14px;line-height:1.5;margin-top:10px}.elementor-element-c67bacb picture{display:block;width:84%;margin-inline:auto}#blog-101-reader figure:is(#vis-101-01,#vis-101-02){width:90%;margin-inline:auto}@media(max-width:600px){.elementor-element-c67bacb picture{width:92%}#blog-101-reader figure:is(#vis-101-01,#vis-101-02){width:96%}}<\/style>\n<script>\n(function(){\nfunction init(){\nif(!document.getElementById('blog-101-reader'))return;\nvar content=document.querySelector('.elementor-widget-theme-post-content');\nvar hero=document.querySelector('.elementor-element-c67bacb img');\nif(hero&&!hero.closest('picture')){\nvar picture=document.createElement('picture'),source=document.createElement('source');\nsource.media='(max-width:600px)';source.srcset='https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/10\/BLOG-101heroM-review.png';source.width=390;source.height=802;\nhero.parentNode.insertBefore(picture,hero);picture.appendChild(source);picture.appendChild(hero);\nvar caption=document.createElement('p');caption.className='wp-element-caption';caption.textContent='Illustrative comparison: confirm the reference before interpreting an apparent difference. No measured deviation is shown.';picture.parentNode.appendChild(caption);\n}\nfunction move(target,smooth){\nvar header=document.querySelector('header'),bar=document.getElementById('wpadminbar');\nvar clearance=Math.max(header?header.getBoundingClientRect().bottom:0,bar?bar.getBoundingClientRect().bottom:0,0)+20;\nwindow.scrollTo({top:Math.max(0,window.scrollY+target.getBoundingClientRect().top-clearance),behavior:smooth&&!window.matchMedia('(prefers-reduced-motion:reduce)').matches?'smooth':'instant'});\n}\ndocument.querySelectorAll('.elementor-widget-table-of-contents').forEach(function(toc){\ntoc.addEventListener('click',function(e){\nvar a=e.target.closest('a[href*=\"#\"]');if(!a||!content)return;\nvar url=new URL(a.href,location.href);if(url.pathname!==location.pathname||!url.hash)return;\nvar target=document.getElementById(decodeURIComponent(url.hash.slice(1)));\nif(!target||!content.contains(target))return;\ne.preventDefault();e.stopImmediatePropagation();history.pushState(null,'',url.hash);move(target,true);\n},true);\n});\nfunction fragment(){if(!location.hash||!content)return;var target=document.getElementById(decodeURIComponent(location.hash.slice(1)));if(target&&content.contains(target))move(target,false);}\nwindow.addEventListener('popstate',fragment);window.addEventListener('hashchange',fragment);window.addEventListener('load',fragment);\n}\nif(document.readyState==='loading')document.addEventListener('DOMContentLoaded',init);else init();\n})();\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>As-planned information describes the intended work in a particular drawing, model or approved change. As-built information describes recorded conditions after work has occurred. A photograph or scan can contribute to that record, but does not automatically establish a verified as-built condition.<\/p>\n","protected":false},"author":2,"featured_media":8637,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[38],"tags":[],"class_list":["post-8646","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-construction"],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/posts\/8646","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/comments?post=8646"}],"version-history":[{"count":6,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/posts\/8646\/revisions"}],"predecessor-version":[{"id":8734,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/posts\/8646\/revisions\/8734"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/media\/8637"}],"wp:attachment":[{"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/media?parent=8646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/categories?post=8646"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.filio.io\/wp-json\/wp\/v2\/tags?post=8646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}