Systems
What should happen, who takes part and what must move between applications? Define the process before specifying its parts.
Follow the workflow ↗Systems / Records / Retrieval
Make information
work from
the start.
Computer systems and information services for organisations with data to organise, applications to support and information to retrieve.
A useful starting point is a concrete task: bring inconsistent records into order, define an application or make a collection easier to search.
Discuss your projectIncoming informationDefined structureUsable result
Areas of work
Start with what
needs to work.
The requirement comes first. Each area answers a different question about the relationship between people, software and information.
Data
What do the records mean, and what shape must they take? Establish structure, consistency and rules for their next use.
Read the record ↗Infrastructure
Where will the service operate? Identify the environment, dependencies and responsibilities needed to support it.
See the layers ↗Retrieval
How will someone find the right material? Connect collection structure and descriptive information to useful results.
Trace the source ↗Computer systems design
Define the system
around the task.
Start with users, decisions and the information that moves between them. Identify how records enter, which steps require approval and what another application must receive.
A project brief can specify workflow diagrams, functional requirements, interface definitions, data models and acceptance criteria. The right combination gives the intended system a shared, reviewable description.
Data processing & preparation
Give records a
usable structure.
Organise supplied information, map fields between formats and apply agreed transformation rules. Establish the source, destination and meaning of important fields before processing begins.
Illustrative field mapping — example values only
Source recordTreatmentPrepared field
Record ref: A–017Preserve identifierrecord_id: A–017
Entry date: 8 April 2026Agree date conventionentry_date: 2026-04-08
Category: [blank]Flag for reviewException recorded
Ambiguity needs an agreed treatment. A blank value should not silently become a guess.
The rules travel with the output.
Potential deliverables include a field mapping, processed dataset, exception report and description of applied rules. Import preparation also needs decisions about required values and duplicate handling.
Hosting & computing infrastructure
An environment.
Clear responsibilities.
Establish what will run, how it will be accessed and which supporting services it depends on. Capacity, deployment, configuration and recovery requirements belong in the same discussion.
Application
What runs, and who maintains its code?
Runtime
Which configurations and dependencies are required?
Storage
What information persists, and what recovery is required?
Access & network
Who supplies accounts and authorises changes?
Information retrieval & web resources
A useful result begins
with its source.
Begin with the available collection and the questions readers need to answer. Consistent titles, descriptive fields, categories and version distinctions can make material easier to navigate.
Possible outputs include a collection structure, metadata specification, indexing requirements and search-result presentation rules. A result should explain its subject, source and relevance before someone opens it.
Illustrative query
“Import requirements”
Preparing records for import
Required fields, date conventions and exception handling are described in the collection’s import guidance.
Connected commissions
One outcome.
Several kinds of work.
These illustrative scenarios show how services can fit together. Each needs defined starting materials, outputs and handover conditions.
A record migration
Existing records → field mapping and preparation → import-ready information with documented exceptions.
Possible deliverables
Source assessment, mapping rules, prepared data and agreed import requirements.
A web information resource
A collection → structure and retrieval requirements → a defined publishing and hosting brief.
Possible deliverables
Metadata specification, result presentation rules, environment requirements and responsibility schedule.
An application handover
An existing application → system and environment documentation → a clearer basis for continued operation.
Possible deliverables
Workflow documentation, dependency record, access arrangements and acceptance criteria.
A reviewable approach
Leave a record
of the decisions.
Brief
Describe the current situation, available materials, intended users and required outcome. Identify constraints that could affect the work.
Scope
Set out deliverables, dependencies, responsibilities and acceptance criteria in writing, with review points suited to the commission.
Review
Use representative material to expose unclear rules or technical constraints. Record decisions that change the agreed approach.
Handover
Assess outputs against the stated criteria and identify the documentation and access arrangements needed for continued use.
Commissioning questions
Before the first
conversation.
- What belongs in an initial brief?
- The task, current tools, available information and result you need. A description is enough to begin; avoid sending passwords or confidential datasets.
- Can existing systems stay involved?
- Identify them early so compatibility, dependencies and access requirements can be assessed as part of the scope.
- Who resolves unclear records?
- Agree both the treatment rules and the person responsible for deciding exceptions before those decisions affect an output.
- What affects an estimate?
- Scope, technical dependencies, access, data condition and review requirements. Confirm any ongoing support separately in the agreed scope.
Begin with the requirement
Put your next
requirement into words.
Describe the work, the material involved and any technical constraints. Include your preferred way to continue the conversation.
Emailgrecegun@gmail.com
Telephone+447846659863
Company address37 Barrow Road Quorn LOUGHBOROUGH - LE12 8DH United Kingdom (GB)