An honest baseline
A clear score across process, coverage, tooling and defects, based on evidence rather than opinion.
[ Why audit & documentation ]
You can’t improve a QA process you can’t see.
Most teams test hard but can’t say how well. An audit gives you an honest baseline: what you test, what you miss, what it costs and where bugs really come from. Good documentation then keeps the improvements in place, so quality doesn’t depend on who happens to be on the team.
Want ongoing guidance after the audit? See QA consulting →
Fixes in the right order
A prioritised roadmap with quick wins first, so effort goes where it removes the most risk.
Documents you keep
Strategy, plans, test cases and traceability written in your tools and owned by your team.
Ready for any audit
Clear evidence of what was tested and why, for auditors, regulators and enterprise clients.
[ What we test ]
Ten ways to see and fix your QA
Use them on their own or together. Each one lists what we review or write, when you need it and the problem it prevents.
QA process audit
Health checkA structured review of how your team plans, runs and reports testing today, measured against good practice and your own goals.
What we test
- Interviews with developers, testers and product owners
- Review of test plans, cases and reports
- Release and sign-off process mapped end to end
- QA maturity scored across ten areas
When you need it
When releases feel risky, bugs keep escaping or nobody can say how good the testing really is.
The problem it preventsSpending more on testing without getting fewer bugs
Test coverage analysis
Find the gapsWe map your requirements, features and risks against the tests you actually run, so you can see what is checked and what is not.
What we test
- Features and user journeys mapped to tests
- Untested and over-tested areas highlighted
- A risk-based view of what to cover first
- Manual and automated coverage shown side by side
When you need it
Before a big release or an audit, or when you inherit a test suite you didn’t write.
The problem it preventsCritical flows that nobody is actually testing
Defect & release analysis
Data-ledYour bug history shows where quality breaks. We analyse it to find patterns, root causes and the bugs that keep reaching production.
What we test
- Escaped bugs traced back to their cause
- Defect trends by area, severity and release
- Triage and bug-report quality reviewed
- Release readiness criteria checked
When you need it
When the same kinds of bugs keep coming back after release.
The problem it preventsFixing symptoms while the cause stays in place
Automation & tooling review
Stack reviewAn honest look at your automation framework, CI/CD pipelines and test tools: what works, what is flaky and what is worth the upkeep.
What we test
- Framework design and code quality reviewed
- Flaky and slow tests identified
- Pipeline and test-environment setup checked
- Tool licences and overlaps reviewed
When you need it
When automation costs a lot to maintain but nobody trusts the results.
The problem it preventsPaying to maintain tests that never catch bugs
Test strategy
DirectionOne clear document that sets out what you test, how, by whom and when, so everyone works to the same plan.
What we test
- Scope, test levels and test types agreed
- Manual and automation split defined
- Environments, test data and tools set out
- Entry, exit and release criteria
When you need it
For new products and growing teams, or when an audit shows there is no shared approach.
The problem it preventsEvery tester working to a different idea of done
Test plans
Per releasePractical plans for each release or project that turn the strategy into scope, schedule, people and risks.
What we test
- Scope and out-of-scope items listed
- Schedule, people and environments
- Risks and how they will be handled
- Sign-off criteria agreed in advance
When you need it
For major releases, launches and anything with a fixed date.
The problem it preventsTesting that starts late and gets cut short
Test case writing & clean-up
StructuredWe write the missing test cases and tidy the ones you have, removing duplicates and gaps so the suite is easy to run and maintain.
What we test
- Clear steps, test data and expected results
- Duplicates and outdated cases removed
- Cases grouped into smoke, regression and full runs
- Ready to automate where it makes sense
When you need it
When the test suite is out of date, inconsistent or only lives in one person’s head.
The problem it preventsA regression suite nobody trusts or wants to run
Traceability matrix (RTM)
Audit-readyA traceability matrix that links every requirement to its tests and their latest result, so coverage is never a guess.
What we test
- Requirements linked to test cases
- Latest results and open defects shown
- Gaps flagged before each release
- Kept in your test management tool
When you need it
For regulated products, client audits or any team that must prove what was tested.
The problem it preventsFailing an audit because coverage can’t be shown
QA metrics & reporting
VisibilitySimple reporting standards and dashboards that show quality at a glance, for engineers and for leadership.
What we test
- A small set of meaningful QA metrics
- Execution and defect report templates
- A release sign-off summary format
- Dashboards in the tools you already use
When you need it
When leadership asks “are we ready to release?” and nobody has a clear answer.
The problem it preventsRelease decisions made on gut feel
Compliance-ready QA documentation
ISO, SOC 2, FDAQA documentation structured to stand up to auditors, regulators and enterprise customers.
What we test
- Evidence mapped to the standard you follow
- Test records and approvals kept in order
- Validation and verification documents
- Gap review before the external audit
When you need it
Before an ISO, SOC 2, HIPAA, GDPR or FDA audit, or an enterprise security review.
The problem it preventsLast-minute scrambles for evidence before an audit
[ What you receive ]
Findings you can act on, documents you keep
Six deliverables, written into your tools. And every finding is written up like the one on the right.
- 01QA maturity assessmentA scored view of your QA across process, coverage, tooling, defects and reporting.
- 02Gap and risk reportEvery finding with its evidence, its impact and the risk it creates.
- 03Improvement roadmapPhased actions with owners, effort and quick wins, ready to plan into sprints.
- 04Test strategy and plansHow you test, by whom and when, agreed and written down.
- 05Test cases and RTMStructured test cases linked to requirements and their latest results.
- 06Reporting templatesExecution, defect and release sign-off reports your team can reuse.
Sample audit findingHigh · fix first
- Title
- Checkout regression is not covered on mobile
- Area
- Regression suite · releases 4.8 to 4.12 · iOS and Android
- Observation
- 38% of checkout test cases run on desktop only. 3 of the last 5 production bugs were mobile checkout failures.
- Risk
- Payment problems on phones reach customers before anyone notices
- Recommendation
- Add 12 mobile checkout cases to the regression run and the smoke check
- Impact / effort
- High / low · about 2 days of work
- Evidence
- Coverage map, defect log, release notes
Example only. Real findings are shared in your audit report.
[ How we work ]
Six steps from kick-off to a roadmap you can run
You see each finding as it comes up. Every document is written in your tools and belongs to you.
-
Step 1 of 6
Kick-off and access
Goals, scope and people agreed, with read-only access to your tracker, test tools and pipelines.
You get -
Step 2 of 6
Review how you test
We read your test cases, plans and reports and interview developers, testers and product owners.
You get -
Step 3 of 6
Analyse the data
Defect history, escaped bugs, coverage and pipeline results measured against good practice.
You get -
Step 4 of 6
Share the findings
A workshop with your team to walk through every finding and agree priorities.
You get -
Step 5 of 6
Write the documents
Strategy, plans, test cases and traceability written or rebuilt in your tools.
You get -
Step 6 of 6
Hand over the roadmap
A phased improvement plan with owners, effort and quick wins, plus a follow-up review.
You get
- Free one-week POCWe review one area of your QA for a week, so you can judge our findings first.
- In your toolsDocuments and test cases are written in your Jira, Confluence or test management tool, not ours.
- NDA before accessWe sign your NDA first and use test accounts and test data by default.
[ Tools ]
The tools we review and write in
17 tools across four jobs. We audit and document inside whatever your team already uses.
Test management
Plans, cases and results in one place.
- TestRailTest cases & runs
- ZephyrTesting inside Jira
- XrayJira test management
- qTestEnterprise test management
- PractiTestEnd-to-end test management
- TestLinkOpen-source test management
Bug tracking & workflow
Where your team already works.
- JiraBugs & sprints
- Azure DevOpsBoards & test plans
- ConfluenceDocs & reports
- SlackDaily updates
CI/CD & code quality
Where tests run and coverage is measured.
- JenkinsPipeline runs
- GitHub ActionsWorkflow checks
- SonarQubeCode quality & coverage
Reporting & dashboards
Metrics your team can read.
- Power BIQA dashboards
- Looker StudioShared reports
- Allure ReportTest run reports
- Google SheetsCoverage maps & RTM
See every tool we use on our technology stack page →
[ Case Studies ]
Teams whose QA we’ve reviewed and rebuilt
Each one links to the full write-up by the engineers who ran it.
[ Ways to work ]
Six ways to run your audit
A one-off audit, ongoing guidance or a team that puts the roadmap into practice. You can switch as you grow.
01Dedicated QA teamChoose it when you want a team to put the roadmap into practice every sprint.02Managed testingChoose it when you want the improved process run and reported for you.03Fixed-price projectChoose it for a one-off audit with a fixed scope, date and price.04On-demand testingChoose it for a quick health check before a big release or a due-diligence review.05Staff augmentationChoose it when you need a QA lead or testers to carry out the changes.06QA consultingChoose it for an expert review plus ongoing advice as you improve.
Not sure which fits? Find your model in four questions or compare all six.
[ FAQ ]
QA audit and documentation questions, answered
{{ f.a }}
[ Contact us ]
Get a QA audit plan for your team
✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day