# Officer search results are non-deterministic and miss out results

**URL:** <http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246>\
**Category:** API Issues\
**Created:** [December 21, 2023, 3:48pm UTC](http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246 "2023-12-21T15:48:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcniboc](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/j/f6c823/32.png) [@jcniboc](http://forum.companieshouse.gov.uk/u/jcniboc)\
**Post date:** [December 21, 2023, 3:48pm UTC](http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246/1 "2023-12-21T15:48:40Z")

</div>

I’ve noticed what appears to be an issue when searching for officers, both with the API and the web search. I was wondering whether this is indeed an issue, and if so whether it is a known issue and whether there is a work around.

The issue is that when searching for a given name in the officers search, there are certain officers who will only appear in the search results say 1 in 10 times. Take as an example the well-known UK businessman Richard Branson: [Richard Charles Nicholas BRANSON personal appointments - Find and update company information - GOV.UK](https://find-and-update.company-information.service.gov.uk/officers/fPsul1-gLgzfRlgRvGBL14iNV3c/appointments)

If you search for Richard Branson under officers, you will get the result seen below only about 1 in 10 times. The majority of the time however, this result does not appear in the search results. Notably, this result has Sir in the title, and those without Sir in the title do not seem to suffer from this problem. This means it’s obviously quite difficult to find individuals you’re looking for - especially when it often is the individual with honorific titles that are of interest.

![image](http://discourselive.s3.dualstack.eu-west-1.amazonaws.com/original/2X/0/0bfc139ed9ed0a14de488db6215c5d3cef28d129.png)

What would people suggest here?

---

<div class="post-metadata">

**Author:** ![MArkWilliams](http://forum.companieshouse.gov.uk/user_avatar/forum.companieshouse.gov.uk/markwilliams/32/194_2.png) [@MArkWilliams](http://forum.companieshouse.gov.uk/u/MArkWilliams)\
**Post date:** [January 9, 2024, 12:55pm UTC](http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246/2 "2024-01-09T12:55:09Z")

</div>

Thank you for taking the time to report this.  
We have found the issue and corrected it.  
It was to do with older resigned dates affecting the ‘score’ so the match was way down on the order list.

---

<div class="post-metadata">

**Author:** ![jcniboc](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/j/f6c823/32.png) [@jcniboc](http://forum.companieshouse.gov.uk/u/jcniboc)\
**Post date:** [January 10, 2024, 5:11pm UTC](http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246/3 "2024-01-10T17:11:10Z")

</div>

Hi there - the situation seems to be fixed for Richard Branson, but I’m seeing similar problems for other names.

For example: [Brian COLLETT personal appointments - Find and update company information - GOV.UK](https://find-and-update.company-information.service.gov.uk/officers/m6QSF-C7zZmY541n0aPUGY9v3jQ/appointments)

This individual Brian Collett has 435 total appointments, of which 2 are current. But the individual does not come up at all in the first 1000 results when you search Brian Collett. Could you advise what is going on here?

Thanks so much

---

<div class="post-metadata">

**Author:** ![DevCat](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/d/898d66/32.png) [@DevCat](http://forum.companieshouse.gov.uk/u/DevCat)\
**Post date:** [January 30, 2025, 3:06pm UTC](http://forum.companieshouse.gov.uk/t/officer-search-results-are-non-deterministic-and-miss-out-results/7246/4 "2025-01-30T15:06:46Z")

</div>

Hello, was this issue resolved?
