Skip to main content
For architectural accessibility audits

Nautil Arch building audits from walkthrough to report

An Android phone app and a browser panel in which Nautil’s auditors carry out our building accessibility audits. The auditor walks through the building with a phone, rates the requirements and takes photos — even without signal. Once the audit is sent, the Word report, with numbering, photos and recommendations, puts itself together and lands in Google Drive.

The app and panel in action

See what an audit looks like in practice

Six short recordings: three from the demo version of the app and three from the panel. Building names, addresses and authors are examples. The recordings have no sound, and below each one we describe what it shows.

Building walkthrough

  1. New audit. Starting a new audit from the app’s dashboard and choosing a template: an administrative building, a hospital or a bank branch.
  2. Audit details. The building’s name and address, the contractor and the report date.
  3. Area name. The entrance area category gets its own name: “Brama B”.
  4. Rating. Requirements rated YES or NO. For the unmet requirement on the manoeuvring space in front of the entrance — the standard recommendation from the norm and a note with the measurement “130 x 140 cm”.
  5. Second area. Cloning the category adds another entrance area with blank ratings — for example, for a second entrance to the building.

Working without signal

  1. No network. The dashboard shows a connection error, and the audit already started waits saved on the phone, ready to continue.
  2. Rating offline. In the external stairs category, requirements are rated as usual.
  3. Sending attempt. Finishing and sending the audit — the app tries to send it with the photos.
  4. Weak signal. A message: the audit was not sent, but the data is saved on the phone and has not been lost — it just needs to be sent again somewhere with a better signal.

Sending and the report

  1. Reminder. The dashboard shows the audit that could not be sent, with a button to open it and send it again.
  2. Copy on the server. The audit shows when its backup copy was last saved.
  3. Sending. Finishing and sending — the audit and photos go to the server.
  4. Report. The audit is sent, and on the dashboard its status changes from generating the report to ready — the report is in Google Drive.

Corrections in the panel

  1. List of audits. Search and filters; the demo audit “Budynek biurowy A” (office building A).
  2. Categories. Each with the number it will have in the report, rating progress, photos and a clone button.
  3. Changing a rating. The threshold in front of the entrance changed from YES to NO, with the comment “Próg ok. 4 cm, bez ściętego klina.” (threshold about 4 cm, no bevel) — the panel saves the changes by itself.
  4. Classification. Recommendation, type, cost level and time for this one audit — the template stays unchanged.
  5. New report. In the Report tab, choosing the document layout and regenerating — the report in Google Drive is updated.

Barrier removal schedule

  1. Report tab. The audit “Budynek biurowy A” (office building A) with a finished report, still without a schedule.
  2. Generating the schedule. An AI model groups the unmet requirements into actions (the wait is cut from the recording).
  3. Sheet in Google Drive. The barrier removal schedule for office building A: 16 actions in a Google Sheet.
  4. Columns. Priority (critical, important, recommended), action, accessibility type, estimated cost, alternative access and the report points the action comes from.

Building templates

  1. List of templates. Building types — from a student residence and a swimming pool to a bank branch — with the number of categories, requirements and audits.
  2. Administrative building. 14 categories, from the surroundings to information and communication solutions; a category can be added or imported from another template.
  3. Subcategories. Passenger lifts, and within them the lift car.
  4. Requirement. “The lift car doors are at least 90 cm wide”: a short criterion for the post-audit recommendations, the recommendation, type, high cost, long time, the groups the barrier affects and the option to always show it in the report.
Screenshots

This is what the app and panel look like

  • App dashboard
  • A category with photos
  • Rating a requirement with a recommendation and a measurement
  • Panel dashboard
  • List of audits
  • Corrections in an audit
  • The report in Google Drive
  • Template editor
  • Barrier removal schedule
Sound familiar?

Audit on paper, photos in the gallery, report in Word

Many building accessibility audits look the same: a paper checklist and hundreds of photos on the phone on site, then evenings in Word — retyping ratings, pasting photos, numbering points and recommendations. Rebuilding costs are estimated by eye, and every correction means another version of the file.

  • A paper checklist

    Ratings and measurements written down by hand, then retyped on a computer — with room for mistakes.

  • Photos in no order

    Hundreds of photos in the phone gallery that later have to be matched to the right points.

  • A report put together by hand

    Rating tables, point numbering and recommendations pasted into Word for every audit.

  • Costs and a plan from scratch

    The client asks where to start and how much it will cost, and the answer has to be worked out from the beginning.

Illustration: a paper checklist on a clipboard and a pencil, a phone gallery with 312 photos, the fifth version of a report with a crookedly pasted photo and the point number “3.2.?”, a sticky note with the cost “? zł” and a laptop with the report in a text editor, with one point number marked in red.
After the rollout

From walkthrough to report in one tool

The auditor rates a requirement and takes a photo once — on the phone, on site. The rating, photos and recommendation go into the report by themselves, and corrections are made in the panel without putting the document together again.

  • Audits on site

    The building template on the phone: requirements rated YES, NO or N/A, photos for each category, measurements in notes and further areas cloned with a single tap. Nothing is lost without signal.

  • A report that puts itself together

    Title page, audit details, numbered rating tables, photos and recommendations — a Word document in Google Drive a few minutes after the audit is sent.

  • Barrier removal plan

    A schedule in Google Sheets built from unmet requirements — actions with priority, estimated cost and alternative access — plus “Conclusions” and “Barrier removal plan” chapters in the report.

  • Your brand and your data

    An app with your name, colours and icon, the report in your layout, a separate database and server, and licences with limits for auditors.

Scope

App and panel features

The app and the panel are one product: you get all the features below — the same ones Nautil’s auditors work with.

  1. Building templates

    An audit starts with choosing the building type: categories, subcategories and requirements with recommendations. Templates are edited in the panel, and a category can be imported from another template.

  2. Rating requirements

    Every requirement: YES, NO or N/A and the auditor’s comment, for example a measured value. The standard recommendation from the norm can be viewed next to the requirement.

  3. Evidence photos

    Photos from the camera or the gallery for each category and subcategory, with a limit per point. They go into the report and into the audit folder in Google Drive.

  4. Additional areas

    A second staircase, another entrance, one more toilet — a category cloned with blank ratings and its own name. In the panel, clones can be added and removed.

  5. Working without signal

    The audit and photos are saved on the phone. If sending fails, nothing is lost: the app resumes from where it stopped, and a copy of the audit waits on the server. Logging in and downloading templates require internet access.

  6. Word report

    Once the audit is sent, the server puts the report together: title page, audit details, chapters with rating tables, point numbering, photos and recommendations. The file goes to Google Drive, and its status is visible in the app and in the panel.

  7. Recommendations with cost and time

    For each requirement: the recommendation type (basic, additional or recommended), cost level, time needed and the groups the barrier affects — people with mobility, visual and hearing impairments and carers with children.

  8. Barrier removal schedule

    Unmet requirements become a Google Sheet next to the report: actions with priority, accessibility type, estimated cost and alternative access. The actions, amounts and alternative access are proposed by an AI model based on the recommendations and cost levels in the template — a proposal for the auditor to check, not a cost estimate.

  9. Corrections and a new report

    After the audit is sent, ratings, comments, recommendations and photos are corrected in the panel and the report is generated again. In the app, the audit can be corrected and sent again, within the regeneration limit of the licence.

  10. Report layout

    A header and footer from the client’s letterhead — for example, a university with the logos of an EU-funded project. The layout is chosen for each audit; the report content stays the same.

  11. Statistics

    The number of audits over time and in the current month, statuses, template usage and the ten most common non-conformities across all audits.

  12. Licences and accounts

    Auditor accounts and limits: audits per month and per year, report regenerations, photos per point and an account tied to a phone. The counter of used audits is shown in the app.

In everyday use

We carry out our building audits in this app

Since May 2026 we have used it to audit university buildings and student residences, administrative buildings, bank branches, swimming pools, libraries, a hospital and a sports hall. The figures below come from our installation (November 2026).

  • 100+ building audits with a finished report
  • 15,000+ rated requirements
  • 8,000+ evidence photos
  • 5,500+ non-conformities with recommendations in reports

97% of the buildings we rated have an entrance without automatic doors.

The most common non-conformity in Nautil’s audits: the requirement “The entrance doors are automatic” was not met in 63 of the 65 buildings where the auditor rated it. Automatic doors let a wheelchair user, a person on crutches or someone with a pushchair enter on their own.
First rollout

Running at Wielkopolska Grupa Prawnicza

Wielkopolska Grupa Prawnicza was the first company to roll out the app — it has used it since March 2026 in its own installation. WGPR’s auditors carry out architectural audits of branches with their own template and work on phones with a licence tied to the device, and the Word report in the WGPR layout goes to a Google Drive folder together with the photos.

Logo of Wielkopolska Grupa Prawnicza (WGPR)
  • 33 audits with a finished report
  • 2,700+ rated requirements
  • 1,100+ non-conformities with recommendations in reports
  • 4 auditors with their own accounts

The same app — under the WGPR brand.

WGPR’s auditors work in the “WGPR Audyt” app with the company’s name, icon, colours and typeface. The reports use the WGPR layout, and the data sits in a separate database on a separate server.
Rollout

From contract to launch — 3 to 5 weeks

Below is the process for the full scope: your own installation with your brand. With a smaller scope, the rollout is shorter. The first 60 days after launch are a support period — configuration fixes and the team’s questions are free of charge.

  1. Analysis and templates

    A kick-off meeting, a review of your checklists and turning them into building templates.

  2. Your own installation

    A separate database and server, auditor accounts, licences and limits.

  3. Report and brand

    The report template in your layout and the app with your name, colours and icon.

  4. Testing and training

    A trial audit in a building, acceptance tests and online training for auditors — included in the rollout.

  5. Launch

    The app on your auditors’ phones, the panel under your domain, the official launch and 60 days of post-rollout support.

    60 days of support
    at no extra cost

What the rollout includes

  • Your own installation: a separate database and server.
  • An Android app with your name, colours and icon.
  • Building templates prepared from your checklists.
  • A Word report template in your layout.
  • The panel under your domain or subdomain, with an SSL certificate.
  • Auditor accounts, licences and limits.
  • Online training for the team of auditors.
  • 60 days of free fixes after launch.

What annual support includes

  • Hosting of the database, server and panel, monitoring and daily backups.
  • Updates to the app and panel, and security patches.
  • E-mail and phone support for auditors.
  • Minor changes to templates and configuration.
  • A licence to use the app and panel during the support period.

We agree the scope and price after a conversation. We send the full price list in an individual offer.

Another Nautil product Nautil Control

Do you also audit websites and apps?

Nautil Control is a panel for digital accessibility audits of websites, mobile apps and files. AI fills in error descriptions and fix guidance, and the report is generated from a template.

Discover Nautil Control

See how it works

The simplest way to assess Nautil Arch is a short online consultation. We will show you the app and the panel live and agree together how to roll them out in your company.

International project

AIMused – accessibility and artificial intelligence in museums

Nautil is the technology partner in a project in which, together with institutions from Poland, Germany, Denmark, Sweden and Lithuania, we are building AI-based solutions that make museums and tourist attractions accessible to everyone.

More about the AIMused project
Interreg South Baltic. Co-funded by the European Union

Project co-funded by the European Regional Development Fund under the Interreg South Baltic 2021–2027 programme.