Pillar 01 · Digital Foundations
Build the digital foundations
your organisation can grow on.
Most organisations are not short of information. They are short of information they can find, trust and connect. We put the foundations in place before anything is built on top of them.
Capture the record.
Structure the data.
Then make it answerable.
The problem
The information exists. It just cannot be used.
Years of records end up in places that do not talk to each other. Paper files in a cabinet. Spreadsheets on individual laptops. Email threads. Chat messages. Invoices in a folder someone named “misc”. And the memory of the person who has been there longest.
Some organisations have no reliable record at all. Others have plenty of information and still cannot retrieve it, reconcile it, or prove that it is correct. Both problems cost money quietly. A decision is delayed. A customer is asked for the same detail twice. A report is rebuilt by hand every month because nobody trusts the last one.
A missing file is obvious. A filing system nobody can search is the more expensive problem, because everyone works around it and nobody counts what the workaround costs.
What we do
Four foundations, built in the order that works.
We do not start with a document management product and work backwards. We establish what information exists, how it needs to be used, and which of these foundations is actually missing.
Document Digitisation
Paper is not the problem by itself. The problem is paper that cannot be searched, shared or audited. We convert physical and scanned records into structured digital files, then check the output instead of assuming the scanner got it right.
- Physical document scanning and digitisation
- OCR and text extraction
- Document classification and categorisation
- Metadata extraction
- Indexing and searchable archives
- Document quality assurance
- Bulk legacy-record digitisation
Digital Records Management
A shared drive is storage, not records management. We establish where a document lives, who is allowed to open it, which version is current, and what happens to it when it is no longer needed.
- Electronic document management systems
- Centralised digital repositories
- Document organisation and retrieval
- Access permissions and role-based access
- Version control where the platform supports it
- Audit trails and records governance
- Document retention and archival workflows
Data Infrastructure and Organisation
The spreadsheet holding a department together is usually a database that was never designed. We build the structure the work actually needs, migrate what is worth keeping, and standardise it so reporting stops being a manual exercise.
- Database design and implementation
- Structured data capture
- Data consolidation and standardisation
- Spreadsheet and legacy-data migration
- Integration of fragmented information sources
- Establishment of appropriate organisational data sources
- Reporting-ready data structures
Organisational Knowledge Systems
When knowledge lives in one person’s head, the organisation is one resignation away from losing it. We build repositories that hold what the organisation knows and answer questions from approved material, with the source attached.
- Private organisational knowledge repositories
- Searchable institutional knowledge
- Document-grounded AI assistants
- Source-referenced question answering
- Internal knowledge retrieval
- Intelligent document processing
Flagship capability
JML Document Intelligence
Document Intelligence is our end-to-end records and knowledge capability. It is not a scanner, and it is not a chatbot. It is the pipeline that turns a room of records into an organisation that can answer questions about them.
Input: physical records and existing digital files, wherever they currently sit.
Records and information assessment
What exists, in what state, how it is used today, and what is worth carrying forward.
Physical document digitisation
Capture at a quality that survives extraction later, with the pages and volumes logged.
OCR and text extraction
Turning image into text, including the parts a scanner misses: tables, stamps, handwriting, marginal notes.
Classification and metadata organisation
So the archive can be filtered and governed, not just full-text searched.
Searchable digital records repository
One place to find a record, with permissions applied to it.
Organisational knowledge assistant
Questions answered from approved records, with the passage that supports the answer.
Ongoing ingestion and management
New records keep arriving. The system is designed to survive that, not to be finished once.
The seven stages run in order because each one depends on the one before it. Classification applied to poor extraction produces a well-organised archive of the wrong thing.
Output: a permissioned repository, and an assistant that answers from it, feeding the operational workflows that depend on those records.
What the assistant will and will not do
- It answers from the documents it has been given access to, and shows the passage it used.
- It respects the permissions of the person asking. A user cannot retrieve what they are not cleared to see.
- It says when the records do not contain an answer, or when the answer is uncertain.
- It does not understand every document perfectly. Extraction quality depends on the source, and we test it rather than assume it.
Scanning a document does not make the scan a legally authoritative replacement for the original. Retention, ownership, security and any applicable regulatory requirement are established with you for each implementation.
Architecture
Where information goes, and why the components are not interchangeable.
A document repository, an operational database and an analytical data warehouse are different components. They can be integrated. They cannot be substituted for one another.
The distinction that matters
- A repository stores and retrieves files, with permissions and a record of who opened what.
- An operational database runs a process. It holds the current state of work: requests, cases, customers, stock.
- A data warehouse supports analysis across history. It is built from the other two, not instead of them.
Choosing the wrong one is a common and expensive mistake. A repository forced to run a workflow becomes a folder structure nobody follows. A database asked to store scanned documents becomes an unusable archive.
Governance
Records carry obligations, not just content.
A digitisation project is also a decision about who can see what, for how long, and what happens when someone asks for it to be deleted.
- Access granted by role, reviewed with you rather than assumed.
- An audit trail of who opened, changed or exported a record.
- Retention and deletion rules agreed before the archive is built.
- Data ownership remaining with your organisation. You are not handing over your records to use the system.
- Where an AI provider is involved, its data handling documented, and processing kept within an agreed boundary where required.
- Applicable regulatory requirements reviewed for each implementation, with qualified advice where the obligation is legal rather than technical.
We do not make blanket claims about security or about how a third-party provider handles data. What we will do is tell you exactly what is in place for your implementation, and what is not.
What improves
The point of the work.
Records you can find
A document is retrieved in seconds instead of a phone call to the person who might still have it.
Decisions you can defend
Reports and answers trace back to a record, not to somebody’s recollection of it.
Knowledge that stays
What the organisation knows survives staff changes, because it is held somewhere other than memory.
Digital Foundations
Start with the records
you cannot find today.
Tell us what you hold, how it is stored and who needs access. We will tell you what is worth doing first, and what is not worth digitising at all.