AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 20 November 2026

Can Vectorize.io handle questions when the answer isn't in the knowledge base?

Vectorize.io signalled that it had nothing for a question its documents do not answer, through low relevance scores rather than an explicit no-match. None of the five passages it returned answers the parental-leave question; the best relevance score was 0.3473 (average 0.0726), against 0.9999542 (average 0.7537) for an answerable question on the same documents.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Reasonable question no document answersPassEvidence
What we sent

“How much paid parental leave does Fenwake give?”

What the tool returned

Copied from Output file (text), lines 2, 4–21, 23–124

Textthe whole file · cited lines 2, 4–21 and 23–124 marked
question: How much paid parental leave does Fenwake give?
average_relevancy=0.0726  ndcg=0.9999

--- rank 1 by relevancy --- similarity=0.7845  relevancy=0.3473  source=A04_employee_handbook.docx
Employee Handbook
Fenwake Instruments Ltd - all locations
1. Working here
This handbook sets out the terms that apply to everyone employed by Fenwake Instruments Ltd, whether based at the Bristol workshop, at the Avonmouth calibration laboratory, or working from a customer site or vessel. It forms part of your contract. Where a term is set out in your written statement of particulars and also here, the written statement governs.
2. Hours of work
Standard hours are 37.5 a week, worked between 08:00 and 18:00, Monday to Friday. Workshop staff work a 07:30 start by agreement with the workshop manager. Anyone rostered to the out-of-hours duty engineer rota is paid a standby allowance for each week on the rota, and an hourly rate for any hour actually worked while on standby.
2.1 Time recording
Hours are recorded against a job number on the day they are worked. A job number is required for chargeable work, for internal projects and for training. Corrections are made by the line manager rather than by editing a submitted week.
3. Annual leave
Full-time employees accrue 26 days of annual leave in each complete leave year, which runs from 1 April to 31 March. Part-time employees accrue pro rata. Leave accrues from the first day of employment and may be taken during the probation period with the line manager's agreement.
3.1 Booking leave
Annual leave is requested in the rota system and confirmed by the line manager. Requests are considered in the order they are received. Service operations will decline a request that would leave the duty engineer rota uncovered, and will say so within five working days so that alternative dates can be chosen.
3.2 Carry-over
Up to five days of untaken annual leave may be carried into the next leave year, and must be taken by 30 June. Anything beyond five days is carried over only where leave could not be taken because of a business requirement, and only with the written agreement of a director.
3.3 Leave on leaving
On termination, accrued and untaken annual leave is paid in the final salary payment. Where more leave has been taken than accrued, the balance is deducted from that payment.
4. Sickness absence

--- rank 2 by relevancy --- similarity=0.7838  relevancy=0.0148  source=A04_employee_handbook.docx
3.3 Leave on leaving
On termination, accrued and untaken annual leave is paid in the final salary payment. Where more leave has been taken than accrued, the balance is deducted from that payment.
4. Sickness absence
Report sickness to your line manager before 09:00 on the first day, by telephone rather than by message. Absence of seven calendar days or fewer is self-certified on return. Longer absence requires a fit note. Company sick pay is paid at normal salary for the first four weeks of a continuous absence and at half salary for the following four weeks, after which statutory sick pay alone applies.
4.1 Return to work
Every absence is followed by a return-to-work conversation with the line manager. The conversation is recorded in one paragraph on the personnel file. Where an absence relates to a condition that affects offshore or diving work, occupational health is consulted before the employee returns to that work.
5. Expenses
Expenses are claimed monthly, with receipts, and reimbursed with the following month's salary. Mileage in a private vehicle is paid at the approved rate. Overnight accommodation is booked through the company travel account wherever possible; where it is not, a room is reimbursed at cost within the regional cap published on the intranet.
6. Notice
During probation, notice is one week on either side. After probation, notice is one month for most roles and three months for directors and for the head of service operations. The company may pay in lieu of notice.
7. Training and certification
Offshore survival and first-aid certification is renewed at company expense before it expires. Time spent in required training counts as working time. Where an employee leaves within twelve months of a discretionary course costing more than two thousand pounds, a proportion is recoverable, as set out in the training agreement signed before the course.
8. Conduct at sea and on customer sites
On a vessel, the master's instructions take precedence over any instruction from Fenwake. On a customer site, the site's permit-to-work system governs. An employee who believes work cannot be done safely is expected to stop it, and will be supported for having done so.
9. Personal data
Personnel records are held for the duration of employment and for six years afterwards. Employees may ask to see their record at any time by writing to the operations director.

--- rank 3 by relevancy --- similarity=0.7202  relevancy=0.0006  source=A01_field_service_policy_and_charges_uk.pdf
Fenwake internal - service operations Page 1

Fenwake Instruments Ltd

Field Service Policy and Charges
United Kingdom operations

1. Purpose
This document states what a customer holding a support contract with Fenwake Instruments Ltd may
expect when an instrument fails in service, what the service desk in Bristol is obliged to do in response,
and what is charged for work that falls outside cover. It applies to the Tolvan A3, the Tolvan C5 and the
Brannoc telemetry gateway, on every cover level.

2. Scope
Part A covers fault handling: acknowledgement, attendance, spares and escalation. Part B sets out the
charges that apply outside cover. Neither part describes the goods warranty carried by a new instrument.

3. Fault priorities
Every ticket is given a priority when it is raised. The priority is set by the effect on the customer's
operation, not by which component failed.

• Priority 1 - a deployed instrument is not returning data, or is returning data known to be invalid, and no
spare is rigged.

• Priority 2 - an instrument is degraded but usable, or a spare has been rigged and the primary unit is
down.

• Priority 3 - a question, a configuration change, or a fault with no operational effect.

A priority may be raised by the duty engineer at any point. It is lowered only with the customer's
agreement, recorded on the ticket.


Fenwake Instruments Ltd - Field Service Policy and Charges (United Kingdom)

Fenwake internal - service operations Page 2

4. Acknowledgement during business hours
Business hours are 08:00 to 18:00, Monday to Friday, excluding statutory non-working days in England
and Wales. Within those hours the service desk is staffed continuously and the targets below are measured
from the moment the ticket is raised, by telephone or through the portal, whichever is earlier.

Priority Acknowledgement target Measured from

Priority 1 30 minutes Ticket raised

Priority 2 4 working hours Ticket raised

Priority 3 The next working day Ticket raised

An acknowledgement is a named engineer taking ownership of the ticket and telling the customer what
happens next. An automatic reply from the ticketing system is not an acknowledgement and does not stop
the clock.

--- rank 4 by relevancy --- similarity=0.7224  relevancy=0.0002  source=A08_warranty_terms_sales_pack.pdf
Fenwake Instruments Ltd - Warranty Terms

Sales pack Page 2

5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data,
loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not
that failure is covered.

6. Statutory rights
Nothing in these terms affects a consumer's statutory rights. The instruments described here are sold for
commercial use, and the terms are written on that basis.

--- rank 5 by relevancy --- similarity=0.7160  relevancy=0.0001  source=A09_warranty_statement_service_pack.pdf
Fenwake Instruments Ltd - Warranty Terms

Service pack Page 2

review is open.

5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data,
loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not
that failure is covered.

6. Statutory rights
Nothing in these terms affects a consumer's statutory rights. The instruments described here are sold for
commercial use, and the terms are written on that basis.

Retrieval results: all five returned passages with their relevance scores and source documents

Open the text file ↗
Expected vs. Found
✓Expected: Show that nothing answers the question: an empty result, relevance scores clearly apart from an answerable question's, or an explicit no-match.Found: Five passages came back, none about parental leave. The top relevance score was 0.3473 (an annual-leave section), the rest 0.0148 or below; an answerable question scored 0.9999542.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the retrieval request and the top match with its relevance score
Open original ↗
Why this result

The tool had to show it had nothing: an empty result, an explicit no-match, or scores clearly apart from a real hit. It is a Pass because its relevance scores for this question sat far below those of an answerable question asked with the same settings.

Also observed in this test case

Similarity score did not flag it. The top passage, the employee handbook's annual-leave section, had a vector similarity of 0.7845, almost the same as the unrelated second result's 0.7838; similarity alone would not have signalled the miss.

Ranking metric stayed near perfect. The result set's ranking quality metric (nDCG) was reported as 0.9999 even though nothing relevant was returned, so that metric does not signal a missing answer.

Tested by Vivek Tomar · evidence dated 16 September 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
Vectorize.io
Build or version
v1 (Beta)
Surface
API
Set up before the run
The question asked how much paid parental leave Fenwake gives; none of the Fenwake documents in the knowledge base could contain or imply the answer, though the question stays in their subject area.
Number of results
5
Tested
16 September 2026 · Vivek Tomar

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

LevelNameScope
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityRetrieval →
ScenarioAnswer is not available in the knowledge base →
ToolVectorize.io →

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
20 November 2026First publishedManaged RAG v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/managed-rag/results/vectorize-io/answer-is-not-available-in-the-knowledge-base · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-20

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Output file (text) ↗text/plain; charset=utf-8 · 8 KB
Proof 1 · Screenshot ↗image/png · 422 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Output file (text)594177b51fe1c513c63f8c2129341cb2531e49fc7ba4e5d5fbc62971d68a7994
Proof 1 · Screenshot0eb4ef0aae6d9c50ee34ae54d38528f357afbd0852a071dfb556d08c64952aec