Systems Review

Understand the work before choosing the project.

An optional paid, fixed-fee assessment for decisions about IT and business systems that need investigation. We examine the agreed systems and process, explain what we find and recommend what to do first. The materials belong to you, to use with KGS, your own team or another provider.

The review provides findings and recommendations. Implementation is scoped separately. If you already know the support or project you need, we can discuss it directly.

When a Systems Review makes sense

When you need to investigate before deciding.

A review helps you decide what work to commission. These are some of the situations it can address.

  • The same problem keeps returning, and several people or providers are involved.
  • You are considering new software and need to understand the current process before choosing it.
  • Staff spend too much time on manual steps, but you are unsure whether to change the process, connect applications or automate it.
  • A report takes too long to prepare, or the numbers are hard to trust because they come from several places.
  • Providers disagree about the cause of a problem, and you need someone to look across the systems involved.
  • You want to automate a task or use AI, but need to check the process, data and safeguards first.
  • Growth, a change of leadership or an upcoming project has exposed gaps in the documentation.
What KGS looks at

Look at the process and the systems behind it.

We agree what to examine before the review begins. That may include interviews, process notes, settings and sample records or reports, along with the responsibilities of your staff and providers.

Access is agreed in advance and should be limited to what the review needs.

  • The current workflow, including common exceptions
  • The applications and configurations involved
  • Where information enters, changes, or has to be entered again
  • Approvals, handoffs, ownership, and escalation
  • Reporting and how leaders currently establish status
  • Documentation and process knowledge
  • Vendor responsibilities and dependencies
  • Access, security, or data handling constraints relevant to the work
What you receive

Findings, options and a plan for the next decisions.

The depth depends on the agreed scope. The review is expected to explain the findings, recommend an order of work and give you a way to judge later changes.

Current process map

A map of how the work happens today: the tools involved, who handles each step and where the usual process changes.

Illustrative ownership map (PDF)

A separate fictional field-service example, showing who handles each step. No client findings or measured results.

Issues and dependencies

The problems worth addressing first, what they depend on and the questions that still need answers.

Recommended quick fixes

Low-risk changes to consider first, with the proposed owner and any dependencies. Implementation is scoped separately.

90-day priorities

What to tackle over the next 90 days, in order, and what can wait.

Implementation options

Options for carrying out the recommendations, with tradeoffs and a reason to keep or replace the tools you have.

Measurement plan

What to measure before and after a change so you can judge whether it helped.

Fictional example. Not a client case study.

Explore the hospitality service-request example.

View the sample Systems Review
How the Systems Review works

From the initial question to the recommendations.

  1. 01

    Scope the question

    Agree the question the review needs to answer, which systems or processes to examine, who to involve and what access is needed.

  2. 02

    See the work

    Talk to the people doing the work and examine the relevant tools and records. Check what happens in practice, including the workarounds.

  3. 03

    Put the picture together

    Map the process, check the likely causes and identify what to address first. Separate quick-fix recommendations from changes that need more planning.

  4. 04

    Review the decisions

    Explain the findings and options, answer questions and discuss the order of work and who could carry it out.

Preparing for the review

Help KGS see the real process.

Involve someone who can approve the work and the people who use or support the systems. We will agree which documents, reports, sample records, settings, contracts or interviews are needed before collecting information. Permission to inspect them must cover the agreed scope.

Passwords and credentials should never be sent through the public website form or ordinary email.

FAQ

Questions about the Systems Review.

Do I need a Systems Review for ongoing IT support or a defined project?

No. We can discuss ongoing support or a specific project directly. A review is useful when you need to investigate the cause before deciding what work to commission.

Is the first call free?

Yes. The first call is to see whether KGS is a fit for the review. We discuss the problem, who needs to be involved, timing and access, then decide whether to propose a paid review.

What does the Systems Review include?

The Systems Review covers the agreed investigation, findings and recommendations. It does not include implementing fixes. After the free fit call, the proposal sets out the scope, fee and deliverables before work begins. Any implementation is scoped separately.

Does KGS have to implement the recommendations?

No. The assessment materials belong to you. You can act on them with your own staff or an existing provider, discuss a separate project with KGS, or decide that no project is needed.

Can a Systems Review cover an AI or automation idea?

Yes. We can check whether the task is ready to automate, what data it needs, which errors matter and who would review the output. The review also sets out how to measure whether the change helps.

Do you need access to sensitive data?

Not automatically. We look for the smallest useful set of information. Redacted records, samples, metadata, settings or interviews may answer part of the question. Any access to sensitive material should be agreed in the scope and handled under the engagement terms.

What if the review shows our current software is fine?

We may recommend changing a setting, simplifying the process, assigning an owner or asking your provider for a specific change. Better use of the software you have can be the right answer.

What do you need to understand before making a decision?

Describe the problem and why you want to address it now. If the work looks like a fit, we will suggest a short conversation.

Discuss a Systems Review