Understand today's work
We review intake, routing, completion and storage. We look for steps where people improvise, re-enter information or work around a process that does not suit their needs.
Practical records management advice
Improve procedures, prepare requirements or plan a new system. We combine records management and technical expertise to help you decide what to do next.
Clear procedures and responsibilities
We recommend changes to policies, roles and the handling of different document types. The aim is guidance that both staff and system administrators can use.
Requirements for selecting a system
We turn findings into requirements covering functions, integration, migration, security and operations. Concrete scenarios make it easier to compare proposals and accept the finished system.
Support during implementation
Working on your side, we review the design and readiness of individual stages. The service does not require ELO or DEPO and can support another vendor's implementation.
Current situation → Analysis → Methodology → Requirements and brief → Implementation oversight → Operation and development. Conceptual diagram · not a fixed product configuration
Frequently asked questions
Can you advise on another vendor's system?
Yes. Guidance, analysis and assessments do not require ELO or DEPO. We focus on your processes and requirements. Changes to another vendor's product need to be agreed with that supplier.
What information is needed for an assessment?
Usually internal procedures, a system description, application and interface lists, and representative work examples. Access is agreed in advance. Sensitive documents should not be sent through a public enquiry form.
What will the assessment deliver?
Findings with impact, priority and recommendations. Depending on scope, it also includes an action plan, responsibilities and follow-up checks. The aim is to support practical change, not just list shortcomings.
Must every application go live at once?
No. A DMS can often start with one application. Statutory records management also needs continuity of registration and operation. Plan stages around those duties and dependencies, not just screens.
What affects implementation cost and timing?
Applications, users, interfaces, data quality and customisation all matter. A proposal should distinguish licences, implementation, migration and support. A useful schedule also accounts for the customer's preparation and participation.
How should users prepare for the change?
Training should follow their roles and real tasks. A pilot group, short guides and a clear support contact help. Administrators and records staff need their own training, not just an end-user demonstration.