Axisware InsightTrack is coming soon. This first article introduces the management problem it is being built to address and the principles behind its approach.
An operational concern rarely arrives as a neat, self-contained case. It may begin as a customer complaint, a quality deviation, a safety observation, a supplier failure, a service breakdown, an audit finding or a concern raised by a member of staff. The first record can be brief, the facts may be incomplete and several people may need to contribute before the organisation understands what happened.
The management challenge is not simply recording that the concern exists. It is maintaining a clear line from the initial report through triage, investigation, decisions, actions, evidence, review and authorised closure. When that line is broken, managers lose confidence in status reports, action owners receive unclear requests, evidence becomes scattered and an issue can be marked closed before the underlying risk is controlled.
Axisware is preparing Axisware InsightTrack to help SMEs and larger enterprises manage that complete lifecycle. It brings issue management, investigation, action planning, risk and assurance into a configurable, accountable workflow, with carefully governed AI assistance where it can improve consistency and reduce administrative effort.
The management problem is fragmentation, not a lack of data
Most organisations already have information about their operational issues. The difficulty is that the information is often distributed across shared inboxes, spreadsheets, meeting notes, document folders, task lists and specialist systems. Each tool may serve a local purpose, but the combined process leaves important management questions difficult to answer.
Who owns the next decision? Which response or investigation timescale applies? What evidence supports the current finding? Are actions overdue? Has an independent reviewer challenged the conclusion? Does this event resemble another concern raised elsewhere? Has the residual risk been accepted by someone with the authority to do so?
A spreadsheet can list cases, but it is weak at enforcing role-based transitions, maintaining a dependable chronology and connecting actions to the evidence needed for approval. Email can communicate quickly, but messages are easily separated from the record that gives them context. Documents can explain a detailed investigation, but without structured status and ownership they do not provide a reliable live management view.
This is why the value of workflow automation is not limited to saving clicks. A well-designed workflow makes responsibility, due dates, required evidence and approval points explicit. It gives people a common operating process while retaining the detail needed for serious investigation.
Controlled closure is more than changing a status
Closing an issue should represent a management judgement supported by evidence. It should not mean that the record has become old, the discussion has moved to another channel or the original reporter has stopped asking for an update.
A defensible issue lifecycle normally includes several distinct decisions:
- Capture and triage: record the concern, immediate controls, affected area, severity and people who need to respond.
- Investigation: gather relevant information, test assumptions, distinguish observations from conclusions and identify contributing or root causes.
- Findings and decisions: explain what the evidence supports, what remains uncertain and which controls or corrective measures are required.
- Action planning: assign specific work to named owners with due dates, expected evidence and review requirements.
- Verification: confirm that actions were completed and assess whether they achieved the intended result rather than merely producing activity.
- Authorised sign-off: require an appropriate person to accept the evidence, residual exposure and closure decision.
The UK Health and Safety Executive’s HSG245 investigation guide is specific to health and safety, but its progression is useful more widely: gather information, analyse it, identify control measures, then create and implement an action plan. The wider lesson is that an investigation only creates value when learning is converted into controlled action.
InsightTrack is being designed around this distinction. A case can move through configured stages, but progression can be governed by required fields, evidence, assigned responsibilities and sign-off rules. Different issue types can use different routes instead of forcing every concern into one generic ticket process.
Accountability needs chronology, timescales and role clarity
Senior management needs a concise view of progress, while investigators and action owners need the underlying detail. Both depend on the same foundations: a dependable chronology, explicit responsibility and agreed timescales.
InsightTrack maintains chronology throughout the issue lifecycle. Reports, status changes, investigation notes, findings, actions, evidence, messages, reviews, reminders and sign-off events can remain connected to the relevant record. This reduces the need to reconstruct the history from inboxes when a case is reviewed, escalated or audited.
Timescales also need to reflect business context. A critical safety concern should not inherit the same response target as a low-impact administrative error. The planned configuration supports separate response, investigation and resolution targets based on issue type and severity. Workflow updates, follow-ups, reminders and escalation can then use those targets consistently.
Role hierarchy is equally important. Staff may be permitted to raise an issue without being able to investigate it. An investigator may record findings without having authority to approve the final risk position. A manager may sign off a closure while a specialist reviews a particular technical or regulatory aspect. Clear role routes preserve separation of responsibility without hiding the case from people who need to contribute.
Usability matters here. A control system that is technically rigorous but difficult to navigate will encourage workarounds. Axisware’s existing guidance on familiar interfaces and software adoption applies directly: people are more likely to follow the intended process when lists, detail views, actions and navigation match the way they work.
Action plans should create evidence-backed work
An investigation report can be thorough and still fail to improve the organisation if its recommendations are vague. “Review the process”, “provide training” or “monitor the situation” do not tell an owner what evidence will demonstrate completion or who must decide whether the response was adequate.
InsightTrack action plans are intended to turn findings into accountable work. From an issue, investigation or risk assessment, an authorised user can create an action, assign it to a named person, set a due date and explain what further investigation, review or evidence is required. The owner can then update the action, provide evidence and return it for review.
Completion and approval are separate concepts. Uploading a document or ticking a task does not necessarily demonstrate that a control is operating. A reviewer may need to challenge the evidence, request further work or confirm effectiveness after an agreed period. That review becomes part of the chronology rather than an informal exchange outside the system.
This approach also improves communication. Messages can be generated from relevant objects so that the recipient receives useful context, while the communication remains connected to the issue, action or assessment that caused it. Workflow-generated updates and reminders can support follow-up without replacing professional judgement.
Recurring issues should inform risk and assurance
Managing each issue in isolation can conceal an important organisational pattern. A minor failure repeated across sites, teams, suppliers or products may represent a more significant control weakness than any single record suggests.
InsightTrack includes planned AI assistance to compare newly raised issues with existing records, identify potential similarity and highlight recurrence for human review. The purpose is not to merge cases automatically or declare a root cause. It is to help investigators and managers notice relationships that warrant examination, while preserving the evidence and decisions associated with each case.
Where an issue indicates material uncertainty or control weakness, users can raise a related risk assessment. The optional risk and assurance module supports configurable criteria, flexible scoring, controls, treatment actions, reviews and a risk register. It can operate alongside issue management or independently for organisations that need a dedicated risk solution.
The current ISO 31000:2018 risk management guidance describes an organisation-wide approach to identifying, analysing, evaluating, treating, monitoring and communicating risk. It does not certify organisations, and software cannot confer compliance. InsightTrack is instead being designed so that organisations can configure workflows and records to support appropriate, ISO-aligned practices.
For a public-sector example, HM Treasury’s updated Orange Book emphasises governance, clear accountability, treatment, monitoring, useful reporting and continual learning. Its formal requirements apply to its stated government audience, but the management questions are relevant more broadly: are responsibilities clear, is information reliable and do decisions lead to effective control?
Management visibility should retain operational detail
Leadership reporting often fails in one of two ways. It can expose so much operational detail that priorities disappear, or compress complex cases into headline counts that managers cannot interrogate. InsightTrack is intended to support a management overview with drill-through to the underlying authorised records.
Custom Razor dashboards, report suites and server-optimised data views can present open issues, ageing, overdue responses, investigation progress, actions, recurrence, risk exposure and sign-off status. Interactive kanban views make permitted stage movement visible. Calendars bring response dates, investigation milestones, action deadlines, reviews and follow-ups into one operational schedule.
Server-side filtering, sorting and paging will be used wherever the data source permits, with client processing reserved for cases where it is genuinely necessary. This matters for larger organisations: a management interface should remain responsive as the volume of issues, evidence and chronology grows.
The reporting approach also supports detailed reports, scheduled management packs, drill-through and export. The objective is a shared view of performance and exposure, not a second reporting process maintained separately from live records. Axisware’s data and analytics work provides the wider context for turning structured operational records into useful management information.
AI assistance must operate inside governance
InsightTrack is planned with separate AI assistants for raising, triage, investigation, resolution, action planning, messages, documentation and risk assessment. This separation is deliberate: each task has different evidence, permissions and review requirements.
AI may help a reporter structure a clear initial account, suggest keywords and a concise summary, identify missing investigation questions, compare similar cases or turn approved findings into a draft action plan. It may also help prepare SOPs, controlled documents and risk assessments using approved company examples, terminology, corporate styling and layout.
These outputs remain drafts or recommendations. They must be reviewed by an authorised person, and source material must be appropriate for the user’s role. AI should not invent evidence, decide whether an allegation is true, approve its own recommendation or replace accountable sign-off. Organisations will need policies covering permitted use, data handling, model configuration, review and record retention.
Used within those boundaries, AI can reduce avoidable administrative work and improve consistency. The management benefit comes from helping people prepare better records and notice relevant information, not from removing people from decisions that require context, authority and professional judgement.
Introducing Axisware InsightTrack
Axisware InsightTrack is being prepared for release for SMEs and larger enterprises that need a clearer way to manage operational issues, investigations, actions, evidence, risk and assurance. It is designed to support configurable terminology, issue types, custom fields, severity models, timescales and organisational roles rather than imposing one sector’s process on every customer.
The planned solution includes dashboards, lists, detail views, interactive kanban, calendars, chronology, workflow automation, a full reporting suite and a maintained API. Deployment options are intended to include Axisware-hosted and customer-hosted environments. Risk and assurance can be added to issue management or operated as an independent module.
Our aim is straightforward: give managers a dependable line from concern to controlled closure, while giving investigators, action owners, reviewers and staff a practical interface for doing the work properly.
Preparing for a private management preview
Organisations considering a preview can start by selecting one real issue type and mapping its current lifecycle. Identify who can raise it, who triages severity, which timescales apply, who investigates, what evidence is expected, how actions are approved and who has authority to close. Note where the present process moves between systems or becomes dependent on manual follow-up.
That example provides a useful basis for evaluating InsightTrack because it tests configuration, responsibility, evidence and management reporting together. It also keeps a preview focused on an operational outcome rather than a generic feature demonstration.
Axisware InsightTrack is coming soon. To register interest in a private management preview and discuss how your organisation currently manages issues, investigations, actions, evidence, risk and sign-off, contact the Axisware team.
