Two ideas run through every system we build: one organisation must never see another organisation’s data, and every change must be attributable to somebody. This page is about how we design for that – and about which of it is a commitment and which is already measured.
These are rules we hold ourselves to, not certificates. An interface that forgets to filter is a bug; a database that enforces the boundary is a control.
The boundary between one organisation’s records and another’s is enforced where the data is, not only in the screen that asks for it, so a missing filter in an interface is not the only thing standing between them.
Changes are written down at the point they are made, with the values as they were before the change, so the answer to “who changed this and when” does not depend on anybody remembering.
Roles, permissions, categories and terminology are held as records rather than written into code, so changing what your business calls something does not require a release.
Deliberately small and deliberately ordinary, chosen so that it can be run without a specialist and handed over without one.
A product that stores a compliance status is not a compliance certificate, and a design commitment held across a company is not evidence that every product has already reached it. So this page does not tell you that our products enforce row-level isolation, revoke anonymous access or keep an append-only audit log.
Those are properties of a specific system at a specific version, and they belong with that system, stated with the evidence that shows it. Ask us about a product and you will get that product’s answer, including where it has not got there yet.
The products are at genuinely different stages: thirteen of the fourteen are running today and one is not yet, and the stage each one is at is shown below.
We will show you what exists today, tell you what is still being built, and let you judge whether the difference matters for your operation.
Hosting region, backup schedule and data-processing terms are agreed in writing before any live data is loaded, not assumed.
Every line below is the recorded result of a request that was actually made. It says what answered and how; it is not a claim about anything we have not measured.
Live — accounts on request
Running at pascoesproperty.uk.
Last checked 12 Sep 2026.
Private pilot
Running at siteledger.uk.
Last checked 12 Sep 2026.
Private pilot
Running at accounts.pascoesystems.co.uk.
Last checked 16 Sep 2026.
Private pilot
Running at pbsfieldservice.co.uk.
Last checked 12 Sep 2026.
Private pilot
Running at policies.pascoesystems.co.uk. It opens on a sign-in screen; access is arranged with us.
Last checked 1 Oct 2026.
Live — accounts on request
Running at pbsfarmstock.uk.
Last checked 12 Sep 2026.
Demonstration only
Running at livestock.pascoesystems.co.uk.
Last checked 13 Sep 2026.
Demonstration only
Running at farmshop.pascoesystems.co.uk. It opens on a sign-in screen; access is arranged with us.
Last checked 26 Sep 2026.
Demonstration only
Running at aircon.pascoesystems.co.uk.
Last checked 13 Sep 2026.
Demonstration only
Running at demo.pbscare.uk.
Last checked 12 Sep 2026.
Private pilot
Running at delivery.pascoesystems.co.uk.
Last checked 29 Sep 2026.
Private pilot
Running at minutes.pascoesystems.co.uk.
Last checked 29 Sep 2026.
In development
Nothing is deployed, so there is no running system to measure and nothing here describes one.
Free tool
Running at tools.pascoesystems.co.uk.
Last checked 12 Sep 2026.
If you have a security questionnaire, send it. We would rather answer it properly at the start than discover a mismatch after migration.