LAP reports in Inspector365

LAP reports went live on Inspector365 just over a week ago—and we’re pleased to share that things are off to a smooth start. As of today, 9 reports have already been published to the website, with another 36 currently in progress.

Aside from one minor 'daylight saving' hiccup (now resolved), there have been no reported issues. The system is stable and performing well.

From now on, we’ll be using this newsletter to highlight key product updates and share anything else we think might be useful to you.

As always, if you spot a bug, have an idea for a new feature, or just want to share some feedback, we’d love to hear from you. Drop us a line at contact@axistwelve.com with the subject Inspector365.

What’s new in v1.01

Security patch
We applied a routine security update to the underlying platform. This is standard maintenance to ensure Inspector365 remains secure and up to date.

Timestamp fix
We corrected an issue where audit event timestamps were off by one hour (due to daylight saving). This only affected internal admin logs and is now resolved.

Word template tweak
The downloadable Word template has been updated to better match the layout of the final PDF version. We know many inspectors are using it for note-taking, peer reviews, and other pre-publication tasks—so this should make it even more useful.

Real-time status updates
Previously, section statuses (Not started, In progress, Complete) didn’t update unless you refreshed the page. These now update dynamically without the need for a page refresh.

View published report content
We’ve made a change so that you can now view published reports in read-only mode directly in the browser. Editing is still locked (as intended), but you’ll be able to see the contents of the report without having to download a PDF version.

As we discussed in last week's post we recently enabled the autocreate feature in Inspector365 to speed up the process of creating new LAP reports in Regulatory Platform (RP). This week we share some of the benefits that functionality has delivered.

Manually creating records in RP was holding up testing

In order for Inspector365 to publish an assessment, a LAP record had to be first manually created in RP by the testers or the Ops team. Setting up a record manually is a complex and time-consuming process, and threatened to limit the scope of what could be tested within the UAT time window.

The decision to enable autocreate in Inspector365 has meant that LAP records are automatically setup in RP based on the assessment criteria that the user enters through the Inspector365 interface.

This automation has helped the test team publish over 70 reports to the Regulatory Platform over the past week, enabling broader test coverage and faster confirmation that all mapping is 100% accurate.

Assessors can now create a full assessment report outline in Inspector365 in minutes and proceed directly to filling out the report and testing its publication.

Since the tool's release, feedback has been extremely positive, with some users commenting how being able to create reports without having to set them up in RP has shaved hours of the process of authoring.

What's next?

The team continues to monitor the process for further optimisation opportunities. Consideration is currently taking place as to whether the autocreate feature should be enabled in Production as well.

In our next post we'll share with you some continual improvements we are working on in response to feedback from Assessors.

We'll provide additional updates as testing progresses and welcome any feedback from stakeholders.

One of the more time consuming tasks faced by the test teams and inspectors, has been the need to set up LAP records in Regulatory Platform in preparation for i365 publishing. Previously, setting up a record in Regulatory Platform manually involved numerous screens/steps, required a lot of the user's time and was prone to error. With the large number of records that needed to be tested as part of functional testing and UAT, this process demanded a significant amount of the team’s time and was threatening to impact the go-live date later this month.

This time-consuming manual process has now been virtually eliminated using i365’s auto-create feature which creates the LAP and associated AP records in Regulatory Platform at the click of a button.

i365's auto-create feature lets users set up reports in Regulatory Platform in under a minute.

By using i365’s auto-create feature for testing, new LAP & AP records are created in Dynamics from the source i365 report - instantly. This advancement has allowed the team to significantly reduce the time required to test a new inspection end-to-end, and has also led to an increase in data accuracy.

Benefits

Faster test cycles:

Auto-creation of LAP and AP record stubs in Regulatory Platform speeds up the testing process, allowing for more tests to be performed in less time.

Improved accuracy:

Eliminating manual entry reduces human error eliminating any chance of misalignment between i365 and RP thereby ensuring 100% consistency between the inspection tool and the backend system.

Streamlined workflow:

Testers can now execute scenarios without switching between systems, simplifying the process and reducing oversight.

Potential to streamline the assessment process in Production

Because auto-create is one of i365’s core features, it could be just as effective in Production as it has proved to be in the test environments. It would help inspectors save time, reduce manual tasks, and ensure more accurate and efficient publishing.

What’s next?

UAT is scheduled for completion by the end of next week. Following that we will be going through operational readiness steps in preparation for go-live.

We’ve reached the final stage in developing the LAP template — the instant creation of perfectly formatted PDFs for the factual accuracy process. These PDFs are crucial, as they’ll be sent to providers for review. To ensure these documents are professional, consistent and accessible, Inspector365 utilises PrinceXML, a powerful tool bundled in the core assessment platform.

About PrinceXML

PrinceXML is a robust tool that transforms HTML documents into high-quality PDFs. It ensures that our LAP reports are concise, easy to read and accurate. PrinceXML conforms to ISO 14289, (the International Standard for accessible PDF technology) that can be used by people with assistive technologies.

PDF Layout

The layout of the PDF differs slightly from the online version of the LAP, but this was designed intentionally to enhance readability. The overall ratings for the location and key questions are brought to the top of the report, giving readers an immediate overview. Each ASG begins on its own section, allowing for clearer organisation.

As we recognise that some reports may be quite extensive, we’ve introduced a repeating section header at the top of each page. This header shows the reader exactly which section they’re on, helping to prevent disorientation and ensure smooth navigation through the report. Additionally, we’ve included the location name, LAP ID, and page numbers in the footer for easy reference.

A detailed table of contents will be added to the PDF in the future to further enhance user experience.

Testing: Functional, Accessibility, and Integration

With the application now fully complete, we’ve entered the testing phase — including functional, accessibility, and integration testing. Initial tests have shown no functional defects, with only minor labelling tweaks needed (which have already been addressed and deployed).

Integration testing, which focuses on ensuring the integrity of the data sent from Inspector365 to the Regulatory platform, is ongoing. So far, no issues have been found, and we’re confident we’ll meet all proposed deadlines.

User Acceptance Testing (UAT)

The LAP template has now been handed over to a CQC test team for final User Acceptance Testing (UAT). After several days of testing, no bugs have been reported yet.

What's next?

Next week, we’ll wrap up all remaining testing, and, pending any defects reported by the CQC team, we’ll consider the first phase of our LAP work complete. At that point, the template will be production-ready from our perspective.

Below are some images of a sample PDF report produced by i365.

Last week, we hit a major milestone as per our schedule: successfully integrating our platform with CQC's Dynamics instance.

This integration automates the flow of inspection report data into CQC's Dynamics’ Dataverse, but we’ve gone beyond basic connectivity. Our goal was simple: ensure data integrity, enhance visibility, and minimise downtime.

Here's how we’ve done it:

Uncompromising focus on Data Integrity

Data is only valuable if it’s accurate. Before sending any data to Dynamics, we built a multi-layered validation process within i365. Each piece of data is checked for consistency and compliance with business rules. We created a “digital twin” of the Dynamics' inspection report model inside i365, constantly validating that data remains in sync.

Smart Error Handling

We’ve designed the integration to be self-healing. We have built in robust operational alerting and health checks to ensure issues are quickly resolved - through automation where possible. If something critical downstream fails we hold data securely in a queue, ensuring nothing is lost and processes resume as soon as possible.

User Transparency

A seamless backend is only effective if users can trust it. We’ve made the process clear and intuitive for end-users, with real-time status updates that show exactly where each report is in the workflow. If delays occur, users get plain-language explanations, not error codes. The result should be less frustration and fewer support requests.

Why This Matters

By ensuring data integrity, minimising downtime, and offering complete transparency, we’re empowering CQC to:

• Trust the data: Giving you confidence that what you see in Dynamics matches i365.
• Minimise disruptions: Automated fixes ensure workflows stay on track.
• Increase productivity: Clear visibility means less time spent troubleshooting.

Looking Ahead

This week we began work on the final sprint - PDF production and production readiness. Stay tuned for further updates!

This week, we made significant progress on the new template in i365, building it based on the wireframes and visual designs shared in our previous updates. By the end of the week, both the front-end and back-end development for the new template were largely completed with only minor changes and tweaks to incorporate based on further user testing.

We wrapped up the week with a demonstration to the CQC project team, along with other stakeholders and inspectors. The feedback was overwhelmingly positive, and we received some excellent suggestions for improvement. Some of these ideas will be incorporated into the initial release, while others are being considered for future updates.

Looking ahead, we aim to complete the Dynamics integration next week, which will enable the seamless posting of inspection data to the Regulatory Platform.

Stay tuned for more updates!

This week, we’ve been hard at work refining and testing the visual design for the new LAP report structure.

The screen grabs below show how closely the visual design aligns with the black-and-white wireframes we previously iterated. Each page has been carefully designed to meet AA accessibility standards and is fully responsive across three screen types: phone, tablet, and desktop.

The design is now 99% complete, with only a few minor tweaks remaining. As a sneak preview, we’ve included a few more of the latest designs below. We’re excited to hear your thoughts!

Make sure you subscribe so you don't miss out on future updates.

This week, we made significant strides in refining our prototypes and designs. The big challenge came with the new LAP + ASG report template. Unlike existing Dynamics 365 reports, this one introduces a deeper structure with an extra layer of hierarchy. While we anticipated some friction, we quickly realized the existing UX—designed over four years ago—wasn't equipped to handle this added complexity. Navigating through so many layers could severely impact usability, so we focused on reworking the information architecture (IA).

We kicked things off with wireframes and user testing to find a solution that maintained the core functionality inspectors rely on in I365, while making navigation more intuitive. A key insight came from our work with legacy Trust reports, which often left users feeling "lost" due to their sprawling multi-section layouts. The existing interface struggled to keep users oriented, so we knew we had to improve this experience.

After several rounds of testing, we found that displaying the entire report layout on a single landing page, with input screens sliding in from the right as drawers, solved the problem beautifully. This design not only made it easier for users to know where they were, but also kept the interface sleek and user-friendly.

Here’s a sneak peek at some wireframes showing the new interface improvements.

In addition to the wireframing work, investigations begun on Dynamics integration as well as the final visual design. We'll be sharing more on those topics next week.