What's new

The latest additions, improvements, and fixes across Auditmark, newest first.

Changes across the admin app, the field app, and reports. Each entry links to the guide that covers the feature in full.

October 2026

New

Fix the answers given at the start of an inspection, such as a mistyped arrival or finish time, after it is completed. Start a correction, change the answer under Start on the Responses tab, and finish. Dashboards show the corrected hours, a new report version is generated, and History shows the old and new value. See Inspections.
Compare several series over time in one chart, such as preventive and corrective work hours per month. Pick Bar or Line, choose a time bucket, and add up to five series that share the bucket and the date range, shown as stacked bars, grouped bars, or lines. See Dashboards.
Keep job titles consistent with your own list of positions. Pick a person's position from a list when you edit their profile, add a new title right from that list, and rename or retire titles for everyone under Positions in Settings. Titles your team already used are on the list from the start. See Users and Settings.
Let inspectors name the entries of a repeating section themselves. Turn on Inspectors can rename entries in the section's settings, and inspectors tap the pencil beside an entry's title in the field app to type its name, which everyone working on the inspection sees. Check Every entry must have a name to require one for each entry. See Templates.
Group questions under a heading inside a section without repeating them. Add a sub-section and click Turn off repeating in its settings; the loop icon on its header makes it repeat again. See Templates.
Reports can say who approved the inspection and when, when it started, and who conducted it. Turn each fact on under Summary on the template's Report tab, where the scheduled date now has its own switch too, so you can leave it out. See Templates.
Draw a thin line between the sections of a report, and print a count of findings at each priority above the flagged items. Turn them on with Line between report sections under Report setup and Count by priority on Flagged items. See Templates.

Improved

Repeating sections and sub-sections share one settings panel: say what each entry is, choose a default title with numbers, letters, or no number, pick the question that names each entry, and set the fewest and most entries. Each setting says whether it shows in the inspection or the report, and a preview shows both. A repeating section placed inside a section is now called a sub-section. See Templates.
Entries are titled the same way everywhere on new inspections: by their name, or else by the entry word and its number or letter, in the field app, on findings, on the inspection's Responses tab, and in the report. Inspections created before this change keep their earlier titles. See Templates.
An inspection's Responses tab shows each entry of a repeating section as its own card with a count of its findings, and keeps entries the inspector removed that still hold answers or a finding, marked Removed entry. See Inspections.
Reports of new inspections print a sub-section where it sits among its section's questions, add a first column of entry titles when a sub-section prints as a table, and say "No entries recorded." for a repeating section with no entries. In PDF and Word reports, an answer that raised a finding is shaded and marked with a flag. Reports of earlier inspections are unchanged. See Templates.
Web reports and shared links now follow your template's current report layout as soon as you change it. PDF and Word files keep the layout they were generated with until you generate a new revision. The PDF preview on an inspection's Report tab says when its file was generated. See Inspections.
A template's Report tab is reorganized so each setting has one place and says what it prints. Report setup holds the settings for the whole report (the line between sections, page breaks, photo placement and image size), the Summary is pinned first with every fact printed under the report title, sections are named for what they print (Start of inspection, Questions and answers, Closing note, Photo appendix), and Score has its own switches for the band, the previous inspection, the section table, and the verdict badge. A ? beside most settings explains what they print. See Templates.
A template that still prints the old summary card keeps its reports as they are until you next change its Report tab. Then the card's facts move into the Summary, its score and verdict badge move onto Score, and its findings count moves onto Flagged items when that section is on. See Templates.
The PDF attached to a report email is named after the inspection and the day it was completed, such as "Site walk - 04-10-2026.pdf", so recipients can tell their reports apart. Every report of a template used to arrive with the same generic name. See Templates.

Fixed

Finding next to an answer and View source answer on a finding now open each other, in the exact entry of a repeating section, and each finding names the question it was raised on. Approvers get the same links when they review an inspection. See Inspections.
Each entry of a repeating section shows its own photos in the report. The first entry could print photos taken in the other entries. See Templates.
Removing an entry in the field app clears its answers and photos, and an entry that holds a finding can't be removed until the finding is. A removal that reaches an inspection already finished, such as one made offline, is refused, so its photos stay on the report. See Templates.
In the field app, a section's progress counts the questions inside its sub-sections, and tapping a row under Needs attention, in Sections, or on a corrective action opens the exact entry instead of the first copy of the question. See Templates.
Reports leave the client or location line out of the header when the inspection has none, instead of printing a dash. See Templates.
On an inspection's Report tab, each version's View, Download, and Email buttons wrap onto their own line, so Email is no longer cut off in the side column. See Inspections.
Report emails show the date the inspection was completed. The date variable used to read the scheduled date, so most emails went out with it blank. Pick Start date or Completed date from the variable list; templates that used the old date variable now show the completed date. The template and inspection title variables also show the template's real name instead of "Inspection Report". See Templates.
Skipping or moving a schedule's next run now takes effect. A skipped run is not created, a moved run is created once at its new time, and pausing and resuming the schedule keeps the skip. See Schedules.
Archiving or deleting a template, or removing a client, pauses the schedules that use it. Those schedules used to keep creating inspections. See Schedules.
Saving changes to a paused schedule keeps it paused; it used to start running again. A schedule paused because its template was archived or its client removed can't be resumed by mistake, and says why. See Schedules.
Inviting someone as an Approver works. Approver invites used to fail with an error. See Users.
A response set that lists the people in your organization can be created straight away. You used to have to pick another provider and switch back before Test source and Create worked. See Response sets.
The field app's Today list follows the phone's own day. Inspections early in the morning used to count as yesterday's, and Overdue and Upcoming could be a day off. See Onboarding your inspectors.

September 2026

New

Score whole inspections. In a template's Scoring settings, choose Points, Section average, or Deduction, decide how N/A answers count, and color the result with your own bands; weight questions and choose which sections count in the Build editor. The score is saved when the inspection is submitted and shows with its band, the previous inspection's score, and a table of section scores on the inspection and in the report. See Templates.
Skip the other scored answers when a question is answered N/A. The field app hides them, names what it skipped in the question, and asks for none of their photos or notes; changing the answer back brings them back as they were. See Templates.
Start a template from a library of published inspection checklists drawn from public sources, then edit the copy however you like. Browse by category, preview the questions, and create your draft in one step. No AI credits are used, and the source credit travels with the copy. See Templates.
Split time-tracking hours by what an inspection answered, so you can see which kind of work costs the most rather than only which site does. See Dashboard.
Compare up to five measures in one bar chart, side by side or stacked, for example inspections and findings for each location. See Dashboard.
Start a template from what you already have: import a spreadsheet checklist (.xlsx or .csv) or describe the template in plain language and let AI draft it, then review and finish in the editor. Turn it on under Settings, AI features. See Templates.
Send a sample of any webhook event from Settings, Webhooks, so you can set up your receiving system with real event data before the first event arrives. Samples are marked as tests. See Webhooks.
Every site now has its own page instead of a side panel: an Overview with open actions, inspection count, last score and last completed date, plus full tabs for inspection history, corrective actions, and contacts. Start an inspection for the site from its header, and return to the list you came from with your filters intact. See Locations.
Inspectors can see the sites they work on. Sites, under More in the field app, shows each site's inspections, what is still to do there, which corrective actions are still open, and who to call, and it works with no connection. See Onboarding your inspectors.
Inspectors can fix a corrective action from the field app instead of asking an admin: change its priority, due date, assignee or resolution notes, and file a photo as proof the work was done. It all queues offline and syncs, and every change is named in the action's activity timeline. See Onboarding your inspectors.
Inspectors can correct a finding they already raised while the inspection is still in progress, including its title, description, priority and label. The photos the finding already carries are shown, so nothing gets photographed twice. See Onboarding your inspectors.

Improved

Ask AI answers show their tables, lists, and bold text formatted rather than as raw symbols, and Copy gives you plain text. Ask AI, and Describe it with AI on a dashboard, now find sites, clients, templates, and questions beyond the first hundred of each, and an answer that is cut short says so and uses no credit. See Ask AI.
Importing a spreadsheet or describing a template to AI now handles long checklists, up to 250 questions, by drafting them in parts at the same time. A sheet over 400 rows, or a checklist that would add more than 30 new response sets, gets a message telling you to split the file, instead of being cut short or failing with a general error. See Templates.
In Chapter flow, the field app brings inspectors back to where they were in the section list and in each chapter, instead of the top. In Chapter and Tabs flow, tapping a row under Needs attention on the finalize screen now opens its section. See Templates.
The failed items summary email is written in your template's language, in the email body as well as in the PDF, and a Hebrew summary reads right to left. The email body used to be in English whatever the template's language. See Templates.
On the inspections list, the progress bar and percentage now sit beneath the status pill in one Status column. On an inspection's Responses tab, every answer leads with a chip naming its type (Yes/No, Selection), instructions no longer appear, and the score card's Sections table no longer lists each section's band, which the report still prints. See Inspections.
Scores read to one decimal on the inspections list, the inspection page, a site's page, dashboard inspection lists, and reports, and an inspection still open or reopened for a correction reads "Score pending" rather than a score it no longer has. See Inspections.
Publishing a template with scoring on checks every score against the scoring mode and lists what to fix, including when you republish a template first published before the scoring settings existed. See Templates.
A report's title follows your terminology, for example "Audit report", and the PDF attached to report emails carries the same name. See Templates.
Sign-off checks every entry of a repeatable section for the corrective actions its rules require, and no longer asks for one on an answer hidden by logic or skipped by N/A. See Templates.
A template's Appearance rail starts from your workspace theme and names it. Turn on Customize this template's appearance to give the template its own theme, cover page, or page size, and turn it off to go back. See Templates.
A template's Report tab shows its save status in the top bar, beside Form settings, and tells you when a change is still waiting to be sent. A change you make just before switching to the Build tab or opening another page is saved instead of dropped. See Templates.
A template's reports always carry your organization logo, which you change under Settings, General. The Appearance rail no longer offers a separate logo per template. See Templates.
Choose which dates a report states about itself. The template's Report tab now carries a Report header group with a switch for the client or site line, the date the inspection was completed, and the date the report was generated. Reports no longer print the generation time unless you ask for it, and the completion date is new. See Templates.
The inspections list shows when work started and when it finished as two columns, Date started and Date completed, instead of one Date column that changed meaning by status. An inspection that has not started shows its due date in the first column. Each column sorts by its own date. See Inspections.
Report design is one workspace under Settings, Branding: pick a theme in the rail, edit it while it saves as you go, and watch the real report preview beside it. See Report design.
Importing a brand from a PDF walks you through Upload and Review, where you choose the role each detected color plays before the theme is created. See Report design.
A site's report contacts are people, not just addresses: each one carries a name, a role, an email, and a phone number. See Locations.
Monday site sync can map a contact's name, role, and phone from your subitem columns, not only the email. Clearing the mapping now warns you first that the next sync strips those contacts. See Marketplace.
The failed items summary email is a formatted message: one card per failed item with its priority, status, where it was raised, and the inspector's notes, in priority order. It no longer lists corrective actions, which have their own email. See Templates.
The Failed items summary card on a template's Report tab now lists its recipient addresses, so you can see who receives the summary without opening Manage recipients. See Templates.
Choose how the failed items summary arrives: in the email body, or as a PDF of the report showing only the flagged items. Either way it is drawn in your template's report colors and typeface, so the summary and the report no longer look like two unrelated documents. Set it under Manage recipients on the template's Report tab. See Templates.
Edit with AI on the Build tab handles big requests: large edits are proposed in pages, the panel shows the page and the changes so far with a Stop button, and one combined list of every change waits for you at the end. Each page that returns changes uses one credit. See Templates.
AI credits are used only for actions that deliver a result. An AI action that fails, is refused, or is rejected before you see it no longer uses a credit, whether it is a template edit, an import, a report layout change, a photo check, or an Ask AI question the AI could not answer. See Ask AI.
Site contacts you enter in the admin now reach your inspectors: they read on the site's screen in the field app, where a tap calls the number or starts an email. See Locations.
The inspections list has a filter row you choose. A Filters button beside Columns opens a checklist of nine filters, including Client, Template, and Template tag, and the ones you tick stay on the toolbar as pills holding their own value. Every pill with a list has a search box, Due date, Start date, and Completion date are three separate filters with rolling ranges or a custom one open at either end, and the set of pills you keep is saved to your account. See Inspections.
Dashboard scores read to one decimal with a percent sign, as on the inspection page, on every kind of widget and in the widget previews. When none of your published templates has scoring settings yet, an empty score widget says so and links to the Templates guide instead of reading "No data for these filters". See Dashboard.
The inspections list's Score filter follows the Score column. Its five options are "90 and above", "75 up to 90", "Below 75", "Score pending", and "No score", so an open inspection no longer lands in a band by the score it held before. Sorting by Score leaves every inspection showing a dash at the end. See Inspections.
A Word export shows the score the way the PDF does: "Score pending", "No score", or the score with its band and the previous inspection's score with the change, followed by the table of section scores. See Templates.
Select Previous on an inspection's score card to open the inspection it compares against. See Inspections.
The Build tab's live preview skips the other scored answers when a question is answered N/A, as the field app does, so you can try the setting before you publish. An answer whose options come from a response set cannot be set to N/A in the preview yet, because the preview does not load those options. See Templates.
The preview on a template's Report tab shows the Score block in the published template's own color bands, with a sample previous score and section table, instead of a plain score. See Templates.
A question with several answers reads the same everywhere: its first answer carries the question text, never an instruction placed first, and each other answer is labelled with its type in your template's language, in the field app, on the inspection page, in reports, and in emails. Reports no longer print the question text twice when it starts with an instruction. See Templates.

Fixed

A report too large to attach to its email now goes out as a link. Reports just under the size limit used to be refused and never arrived. See Inspections.
A report's AI summary is now written for large inspections too. An inspection with many findings used to get no summary, and one that failed before is written the next time its report is generated. See Templates.
On an inspection's Responses and History tabs, a Yes / No answered N/A reads as its N/A label instead of No. See Inspections.
In the web version of a report, each section's score band sits under the section title, so a long title no longer squeezes the band to one letter per line on a phone. See Templates.
In the field app, an option's color dot shows the color chosen for it in the response set. Some colors showed no dot at all, or a different shade. See Response sets.
PDF reports make better use of the page. The Image size you pick on the Report tab now sets how large photos print in the PDF and the Word export, not only how sharp they are, with Medium matching the size reports had before. The results also start on page 1 instead of leaving it to the header alone, and turning off Page break between sections takes effect. See Templates.
When a corrective action is reassigned, the person it moved away from now gets a notification that says so, under the bell in the admin app and in the field app. It used to read "You have a new notification" in the admin app and did not appear in the field app at all. See Account.
In the field app, a photo taken while logging a corrective action no longer turns into a broken image on the question, and a question's Required mark clears as soon as the photo or note it asks for is added. See Onboarding your inspectors.
The field app keeps its place. The form no longer jumps to the top while another inspector works on the same inspection, a completed inspection's report scrolls instead of snapping back to the top, and the label and assignee lists on a finding scroll with a swipe. See Onboarding your inspectors.
A question with several answers asks for its corrective action once, under the answer the rule names, instead of under every answer, and sign-off asks for exactly the actions the field app asked for, reading every condition of the rule. See Templates.
A question with several answers has one note and photo area, at the end of the question, instead of one under each answer. A note or photo on any of its answers meets the question's note or photo requirement, in the field app and at sign-off. See Templates.
On an inspection's Responses tab, a question that starts with an instruction now shows all of its answers, and list answers show their option name rather than a code, there and in the history. See Inspections.
The PDF report prints a Yes / No answered N/A as its N/A label, not the raw value "na". See Templates.
Templates now follow the workspace theme you set as the default in Report design. A template without a theme of its own used the built-in look instead, whatever the default was, so its reports switch to your workspace theme the next time they are generated. See Templates.
A cover image upload on a template's Report tab says so when it fails, and keeps its result when you move to another rail section while it uploads. See Templates.
People you have deactivated are no longer offered where you assign work. That covers the approver on an inspection and on the calendar, a schedule's default approver and default inspectors, and the recipients of a notice. Picking one used to fail on save, and a schedule could keep handing work to someone who can no longer sign in. See Inspections.
Requesting changes or rejecting an inspection without a comment now tells you a comment is needed, before the decision is sent. It used to fail with a message that did not say what was wrong, and discard what you had typed. See Inspections.
The report footer's Page numbers and Running title switches now apply to the PDF, and turning the running title on or off saves. Before, page numbers always printed, the running title never did, and a theme with that switch touched could not be saved at all. See Report design.
On a phone, a long name or address no longer pushes a list card sideways off the screen. This affects the card layout on every admin list. See Locations.
In the field app, a corrective action that has been closed no longer counts as open. Open-action counts on inspections and sites drop to match, and a closed action past its due date now reads under Resolved rather than Overdue. See Onboarding your inspectors.
Two sites that share a name no longer share a filter in the field app. Filtering inspections or actions by site now picks exactly one site, the filter shows the client account beside a name that repeats, and an action raised on an inspection with no site is no longer listed under a site of its own, matching the rule the inspections list already follows. See Onboarding your inspectors.
In the field app, a Yes / No's N/A option shows its own label, or the template language's word for N/A when it has none (for example "S.O." in a French template), the same word the report prints. See Templates.
In the field app, a repeatable section with no minimum asks for nothing until its first entry is added. An empty one used to count toward progress and could hold up moving on or submitting. See Templates.
An answer hidden by logic, or skipped because its question is answered N/A, no longer carries an AI flag from a compliance check. See Inspections.
In the PDF report, a long answer with no spaces, such as a link or a serial number, wraps inside its table cell instead of running off the page. See Inspections.

August 2026

New

Choose how completed reports are emailed for your whole organization, as a secure web link or a PDF attachment, and name the people who always receive one. Set it under Settings, Email notifications, Report delivery. See Settings.
Download any dashboard widget as a CSV file, an Excel workbook, or a PNG image, with the dashboard's filters applied. See Dashboard.
A repeating section placed inside a section can now name each entry from one of its answers, or number its entries with numbers or letters, as a whole repeating section can. The name heads the entry in the field app, on its findings, and in the report, and entries keep the order they were added in everywhere. See Templates.
Correct a completed inspection without losing the audit trail: reopen with a reason, edit answers inline, and every change is recorded in the new History tab. See Inspections.
Export any report as a Word document alongside the PDF, on the Premium and Enterprise plans. See Inspections.
Share a report with people outside Auditmark through an expiring public link, once sharing is enabled for your organization. See Inspections.
The integrations page became a Marketplace: browse vendors by category, connect more than one account, and follow every sync in one activity feed. See Marketplace.
Ask AI answers now stream in live, and each answer keeps its verifiable step trace. See Ask AI.
Weight time-tracking dashboards by a numeric field, for totals like staff hours. See Dashboard.
Manage people outside your organization who receive site and corrective-action assignments as guests. See External assignees.

Improved

The dashboard filter row takes several locations or several templates at once, and Custom range sets exact dates, for the whole dashboard or for a single widget. See Dashboard.
In the field app, a date question has a Today button and a time or date-and-time question a Now button, so inspectors fill them in with one tap. Default to today now applies to date questions only, so a time question never starts out holding a date. See Templates.
Signing in tells you what is wrong when it cannot finish. Someone without an invitation is asked to open their invitation email or ask an administrator, and when the app cannot load your workspace it says so and offers Try again, instead of a loading bar that never ends. See Getting started.
Inspection creation is a guided four-step wizard: site, template, people, and timing, with site-assigned templates listed first. See Inspections.
The inspections list gained saved filters for site, assignee, score bands, and dates, all shareable through the page URL. See Inspections.
Locations picked up status tabs, bulk actions, per-site template assignment with pinning, and report contacts that prefill report emails. See Locations.
Settings grew dedicated sections for plan and usage, finding labels, corrective-action closure policy, email notifications, AI features, and sharing controls. See Settings.
Response sets sourced from Monday.com can now drill into nested board items, and keep a synced copy of their options so field forms work offline. See Response sets.
The template editor's conditional logic reads as a sentence and can require corrective actions, notes, photos, or trigger a follow-up form. See Templates.

Fixed

Photos taken in the field app keep their detail. They were saved at a low resolution, so photos in reports looked soft even at a large image size. See Templates.
Template changes stay in the editor and its preview when you leave the template and come back, including changes made with Edit with AI. They used to disappear from view until you reloaded the page. See Templates.
Report deep links and heading anchors across the documentation were re-verified end to end, and the docs site now carries a full-text search, topic pages, and this changelog. See Getting started.

Earlier

The documentation was fully reconciled against the shipped product in June 2026; changes before then predate this changelog. For API-level changes, see the developer changelog.