NEN 2767 inspection app development
NEN 2767 makes the condition of a building measurable: each defect is assessed on severity, extent and intensity, resulting in a condition score for each building or installation component. Appfront builds the app in which the inspector records that assessment on site, so the multi-year maintenance plan is based on observations rather than an estimate after the fact.
What condition assessment under NEN 2767 involves
The standard provides a method for objectively determining the technical condition of building and installation components. The inspector does not assess the element as a whole but the defects they see, and weighs them on three points: how serious the defect is, how much of the element it covers, and how intensively it occurs. These three produce a condition score on a scale from 1 to 6, where 1 is excellent and 6 is very poor.
The value of this approach lies in comparability. Because two inspectors follow the same assessment method, scores can be compared between buildings and over the years. That makes condition assessment a suitable basis for a multi-year maintenance plan and for budget discussions, because a score of 4 on the facade of one property means the same as on another.
In practice, it all depends on how the data is created. We still often see an inspector walking through a property with a paper form or a spreadsheet and writing up the findings afterwards. Photos sit in a separate folder and have to be matched to the right element later. What happens then is that the nuance disappears: the defect is reduced to a score, and at the next assessment it is no longer possible to trace why that score was given.
Sewerage has its own series of standards with its own condition coding. We cover that on the page about the sewer inspection app and the pumping station round.
How we build your condition assessment app
We start with the decomposition of your property portfolio. If it doesn't match how you manage, the scores will be objective but not usable for your planning.
How you divide a building into parts: by building component, by element, by installation. If that matches your existing property administration, scores and maintenance measures can be linked to each other. If it differs, every report requires translation work.
For each element type, the defects that can occur, together with the rating method. The inspector picks from a list instead of typing freely, because that is what keeps scores comparable across inspectors.
We work in sprints and start with the on-site inspection. Your inspectors take part and run a real measurement early on with an interim version; only then do you find out whether the pace is achievable in a building where you have set aside a day.
The scores have to go somewhere: into your multi-year maintenance plan or your management system. We set up that handover and then hand over to your management organisation.
What the app actually does
Six components that turn an inspection round into a usable file. What you need depends on the size of your portfolio.
Decomposition per building
The building broken down into components and elements, with the previous score and the defects found at that time for each element. The inspector works through that tree instead of a list, and can see along the way what they have not yet covered.
Defects by severity, extent and intensity
For each defect, the three assessments the standard requires, from which the condition score follows. The inspector assesses and the system calculates, so a score can always be traced back to the observations beneath it.
Photo per element
Images are attached to the element and the defect, not to the visit. At the next measurement, last year's photo sits alongside, making deterioration visible instead of something to argue about.
Cycle per building
The measurement cycle differs per building and sometimes per element type. The system plans ahead, groups what is in the same neighbourhood or complex, and flags which buildings are due.
From score to action
A score on its own is not a plan. We link scores to proposed actions with an urgency, so the outcome of a round can be translated directly into a multi-year maintenance plan instead of first being retyped.
Portfolio overview
Across buildings: where the worst scores are, which element types consistently score poorly, and how condition is developing. That is the conversation a manager has with their board.
Who we build for
Four types of organisation. The difference lies in whether you measure for your own portfolio or on behalf of third parties.
Property managers and housing associations
Large portfolios where condition measurement drives the budget. If this connects to your property management software, the decomposition does not need to exist twice.
Healthcare, education and government
Own property with an in-house technical department, where the measurement mainly serves to substantiate investment decisions to the board or municipal council.
Inspection firms and advisers
You measure on behalf of third parties and deliver the report. What matters to you is turnaround time per building and a report your client can use directly in their own system.
Commercial property managers
Distribution centres, shops or offices, where condition measurement goes hand in hand with facility management and sustainability plans.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
What we use follows from how you work. Crawl spaces, roofs and technical rooms rarely have coverage, so offline working is a prerequisite. Usability outweighs functionality: an inspector who is out all day should lose seconds per element, not minutes.
If you also want to code the building components in your inspections and maintenance plans according to the NL-SfB classification, take a look at our NL-SfB integration.
If you also want to use the results of the inspection in your budget and maintenance planning, read more about our MJOP integration.
For investigating the foundation itself, with inspection pits, measurements and a report per building, there is our reporting software for foundation investigation.
Why Appfront
The score follows from the observation
We let the inspector assess what they see and let the system do the calculating. A score that is entered directly cannot be explained at the next measurement.
Comparability is the whole point
The value of the standard lies in being able to compare buildings and years side by side. That requires fixed defect lists and a decomposition that does not change from one round to the next.
The scores have to go somewhere
A measurement that gets stuck in a report changes nothing. We build the bridge to your multi-year maintenance plan or management system through integrations.
We join you on a round
Before we design anything, we spend a day inspecting alongside you. The difference between an app that keeps up and one that slows you down lies in the number of actions per element.
Security and privacy
A condition measurement contains little personal data, but it does record which inspector gave which assessment. That is traceable to an individual and it is sensitive, because scores are a judgement and inspectors differ. We use that record to safeguard quality, not to produce output figures per inspector, and we focus reporting on the property.
More significant is that condition scores have financial consequences. They steer budgets, they play a role in purchases and sales, and in rentals they can become part of a dispute. That is why reliability is no formality here: a finalised measurement cannot be changed silently, a correction is visible as a correction, and photos are timestamped. If you measure on behalf of third parties, access is strictly per client so that nobody sees anyone else's portfolio. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.
Frequently asked questions about condition measurement
The scale runs from 1, excellent, to 6, very poor. More important than the number is how it comes about: the inspector assesses the defects they see on severity, extent and intensity, and the score follows from that. This means a score can always be traced back to observations. That is why we build the app so that the inspector records defects and the system calculates the score, not the other way round.
There is no general legal obligation. In practice it is the standard method for property management organisations with a real estate portfolio, and it is regularly required contractually: for tendered maintenance, performance contracts and sometimes financing. The reason to do it is usually internal: without an objective method, a maintenance budget is a debate between opinions.
That is up to you and it differs per portfolio. Many managers use a cycle of a few years per building, with fast-ageing components coming up more often than the load-bearing structure. Because that cycle can differ per building and per element type, we make it configurable and let the system plan ahead so that a round can be organised efficiently.
Condition assessment establishes where things stand; maintenance software carries out the work that follows from it. They belong together but are not the same: the assessment is a periodic review by an inspector, while maintenance is a continuous process of reports, work orders and planning. We build the assessment so that the outcome flows into your maintenance planning without retyping.
By using fixed defect lists per element type and having the score calculated rather than entered. It also helps to require a photo for every defect, so that an assessment can be checked afterwards. Two inspectors will never score exactly the same, because it remains skilled work; what you can achieve is that differences are explainable rather than arbitrary.
Yes. Crawl spaces, roofs, plant rooms and vacant buildings rarely have coverage, and those are exactly the places you inspect. The app stores data locally, including photos, and syncs as soon as there is a connection. A day of inspecting quickly adds up to hundreds of captures, so we explicitly design how these are handled without filling up the device.
That is the aim. We link scores to proposed measures with an urgency level, and build the export or integration to the system that holds your long-term maintenance plan. What is possible exactly depends on that system; we establish this in the discovery phase. Where an integration is not possible, we deliver an export in the format your planner uses.
That depends on the size of your portfolio, how detailed you want the decomposition to be, and whether an integration with your management system is involved. The inspection app is usually the quickest to become usable. Setting up the defect lists per element type is the most preparatory work, and we do that together with your inspectors. We give a substantiated estimate after the discovery phase.
Ready to build a condition assessment app?
Tell us how large your portfolio is and how the assessment is currently carried out, and we will help you think through the decomposition, the defect lists and the bridge to your maintenance planning. We build this as a standalone app and as part of a broader project involving custom software or an app. For new builds in consequence class 1, the Wkb file comes first; see competent authority file.