Appendix I
CITATIONS AND REFERENCES MANAGEMENT SYSTEM (CRMS)
Business and Technical Requirements
This document is the property of the Council of Europe. It's a part of a consultation service. The supplier will treat this document as strictly confidential. It may not be reproduced or communicated without the author's prior agreement. The content of this document will be disclosed to potential business partners in good faith by the supplier. No part of this document may, in itself, constitute a commitment of the Council of Europe or its staff.
|
Drafted by |
Version |
Date |
Status |
|
Araks Avetyan |
0.5 |
16/06/2025 |
Draft |
|
Araks Avetyan |
1 |
30/06/2025 |
Submitted to CoE and Court of Cassation |
|
Araks Avetyan |
1.1 |
14/07/2025 |
Submitted to CoE |
|
1.2 |
19/07/2025 |
Finalized version submitted to CoE |
|
|
Araks Avetyan |
1.3 |
07/08/2025 |
Reviewed version submitted to CoE |
Presentation of the relevant directorates / departments
Production rollout considerations
Method of requirements capture used
Main functions of the inputting component
Main functions for the advanced search component
Citation handling logic in MS Word
Operational Environment Standards
Hardware and infrastructure requirements
Access modes and security requirements
Service level: availability, performance and support
7. Experience and team composition
Data outputs and reporting requirements
Training Plan and Training Approaches
12. Critical Success Factors (CSF) and measurements
Annex 1 Sample structure of citation
This document presents the detailed business requirements for the Citations and References Management System (CRMS) system for the Cassation Court of the Republic of Armenia that will be delivered by the PGG III: Support to the Justice reform in Armenia project.
Purpose of the Project
The aim of the project is to provide the Court of Cassation of Armenia with an easy-to-use comprehensive electronic search and citation system. The system should enable 4 Chambers of the Court of Cassation of Armenia, including the Civil, Administrative, Criminal and Anti-Corruption, as well as the Legal expertise service to efficiently search and insert legal citations into court decisions and other related documents.
Currently, civil judicial proceedings are conducted through a unified electronic system, while the electronic system for administrative court proceedings is currently under development.
The system will support usage of Microsoft Word through the add-on plugin, which will interact with the system over an API.
Problem being addressed
Given the increasing number of cases reviewed by the Court of Cassation, the workload on court staff, particularly the Legal Expertise Service, has become substantial. The manual process of searching applicable citations is one of the most time and energy consuming parts of drafting court decisions and the staff involved faces significant administrative burdens of citation handling.
The Legal Expertise Service manages the list of all Decisions of Court of Cassation classified alphabetically and by topics. Yet, even though citations are alphabetically and thematically categorized, experts still need to manually search and assess each citation for relevance.
The main problem to be addressed for the Project can be described as following:
“The current citation handling process of the court is time-consuming, inefficient, and contains the risk of inconsistency and possible error in legal documentation.”
Cause of the problem
The main causes of the above formulated problem can be described as following:
1. Absence of a systematized citation library. There is no centralized or standardized repository of legal citations in any format, making it difficult for legal experts to efficiently retrieve or reuse prior references.
2. Lack of supporting software. The court does not operate any software solution that could enable the structured classification and search of required citations.
3. Limited technical resources and capacity. The court, like many other state entities in Armenia, has limited internal technical infrastructure and staffing to support the development or maintenance of such systems.
However, the court staff has a clear understanding of the need for such a solution, and there is strong institutional support from the top leadership, which makes the success of the project easier to achieve.
Project scope and Objectives
The main objective of the project is to increase the speed of documents processing within the Cassation court and at the same time try to make the consistency of these documents even higher. Considering the current business processes, the project’s introduction some routine tasks automation may have a positive impact on internal workflows optimization as well:
|
Objective |
Description |
|
|
1 |
Increase the speed of document processing. |
The tool should enable the court staff and judges to find and use relevant citations much faster than it is done today. The citations inserted from the system will not require further checking, as their appearance at the database implies pre-check and approve procedures. |
|
2 |
Better consistency of the documents. |
The system will allow full-fledged usage of verified and standardized citations for all court documents, reducing uncertainty and mistake probability. |
|
3 |
Optimization of workflows. |
By streamlining the citation process and reducing manual effort, the system may help to optimize internal workflows, if needed. |
It is clear that for achieving the comprehensive results the court needs a full-pledged case management system, nevertheless, the tool developed under the Project will be designed in a way that ensures integration with already existing and future systems, becoming their undividable part.
Considering that the workload of court staff is constantly raising due to the high growth of received cases the early adoption of this tool becomes critical. Even a partial reduction of the burden on staff and judges would provide much-needed relief and should be prioritized.
As a result, judges and the staff of the Cassation Court will spend less time on preparing decisions, and at the same time all stakeholders involved in the cases, including citizens, prosecutors, advocates, and others will experience shorter waiting times for the verdicts. This dual impact is expected to improve internal efficiency and enhance the overall responsiveness of the judicial process contributing to higher public trust and stakeholder satisfaction.
Out of Scope
The Project implies solely the introduction and implementation of new IT tools making the citation process easier and more efficient. However, filling of the core citation database falls out of the Project’s scope.
Presentation of the relevant directorates / departments
The process of preparing decisions of the Court of Cassation involves several departments and follows a multi-stage review procedure. Initially, the draft decisions are prepared by judge assistants and then forwarded to the Legal Expertise Service for a thorough legal review.
Only after these stages are completed are the draft decisions submitted to the judges for final consideration. Throughout this process, the decisions are subject to multiple rounds of review, verification, amendment, and refinement, ensuring both legal accuracy and procedural consistency.
With the introduction of the search and citation system, all above-mentioned parties will experience changes in their workflows, as the new system will influence how legal references are retrieved, verified, and incorporated into draft decisions.
Business processes
The business processes describe the end-to-end workflow for managing legal citations, from initial entry and review to approval and integration within court documents.
Existing (AS IS) processes
The current process of citation usage includes a manual search for relevant materials, including online databases like DataLex.am, official webpage of the Court of Cassation, as well as reviewing locally collected documents stored in alphabetically organized folders.
Future (TO BE) processes
After the introduction of a new system, the Court staff and judges will have the opportunity to quickly find relevant citations by searching based on article, topic, keyword, and other parameters.
Once the search is completed, they can easily select the required citation from a list generated based on the specified search criteria. For even quicker and more convenient future use, users may also tag and save citations to their personal favorites lists.
In cases where the needed citation is not found through the system, the manual process still needs to be applied.
Below is the diagram that illustrates the interaction between users and the Citation Information System along with its Microsoft Word plug-in. It maps out the main use cases, user roles, and system components involved in the citation submission and retrieval process.
Production rollout considerations
As an initial phase of the system rollout, a small-scale pilot should be conducted using a limited number of citations integrated with Microsoft Word. That will allow testing of core functionalities and gathering user feedback.
Following the pilot, the Cassation Court should take the lead in populating the citation database. Once a sufficient volume of content is available, the system may become available to all relevant employees and judges involved in the drafting of verdicts.
To ensure efficiency and usability, access can be configured so that each user group sees only the parts of the citation database relevant to their role or case type. This approach will help avoid information overload and ensure targeted, effective use of the tool.
Method of requirements capture used
To understand and formulate the main business requirements, several methods were employed. These included meetings with the staff of the Cassation Court and the Council of Europe project manager.
A high-level overview of a similar system used by the European Court of Human Rights was shared through a presentation, illustrating the core concept of standardized citations. To gain a deeper understanding, desk research of similar systems was conducted, followed by an online consultation with representatives from the European Court of Human Rights.
The system should have four main components:
- Interface for inputting citations in the database
- Interface for advanced search
- Microsoft Word plug-in to insert and validate citations
- API for citation usage by external systems
Main functions of the inputting component
● The system shall ensure a user friendly interface for filling in the citation in a structured manner. The list of requisite data shall be agreed with the Court of Cassation
● The system shall ensure the approval flow of inputted citation
● The system shall ensure a possibility to categorize citations, add descriptions, themes, keywords etc.
Main functions for the advanced search component
● The system shall provide a possibility to search for content based on predefined criteria
● The advance search functionality of the system should allow searching in text with exact and approximate matching
● For each found citation, the tree path of that specific citation should be presented
● For each citation there should be logs, indicating the dates of creation, publication, last modification and last insertion, marking as disabled.
● The user should be able to easily copy and mark the existing citations as favorite
● The user shall have a separate section with all favorite citations
● The user should receive notifications about changes in citations marked as favorite
● The user should have access to informative content, including manuals, instructions
● The user should have a separate section about statistics about the citations.
Main functions of the Microsoft Word plug-in
● The plug-in shall be visible in the ribbon of MS Word document as a separate tab named “Court tools” (should be compatible with Microsoft Word starting from version 2010 and equivalent versions for macOS).
● Search and insertion of the citation directly in MS Word document with clear indication of the citation being inserted from the system.
● It shall be possible to perform the insertion with numeric references. The plugin should provide functionality to configure numbering settings.
● The plug-in shall ensure that editing or making changes in the inserted citation are recognizable. Each change should result in the removal of the verified status of the citation. The Supplier is expected to propose options that enable not only the detection of citation changes, but also the clear presentation of the specific parts of the citation that have been edited or removed.
● The plug-in shall ensure the verification of already inserted citation by cross-check with the system’s data. If changes to the inserted citations are detected, a relevant message should be shown and color differentiation should indicate the validation results (e.g. green if not changed, rose if there are changes).
● The plug-in shall ensure the notification if the newer version of already inserted citation is available.
● The plug-in should include a “Publish” button that converts all citations and references into plain text and triggers a “Save As…” dialog to create a separate instance of the document. This functionality is essential to ensure smooth viewing and compatibility in Microsoft Word editors outside the Court environment, particularly where the citation plug-in is not installed.
● The plugin should provide the option to choose between two citation referencing types: concatenation or footnoting.
● The exact view of citation inserted in MS Word should be agreed with the Beneficiary.
API requirements
The system must provide an API that enables secure access to citation data and supports the following core functionalities:
● Search endpoint to retrieve a list of citations based on search criteria (keywords, article number, etc.)
● Get citation by ID, including full text, metadata, and references
● Retrieve citation version history
● Provide citation hash to verify content integrity and detect changes
● Access to approved/public citations only for Microsoft Word plug-in developed for the Project.
Citation structure
The citation structure includes key elements such as the citation text for insertion, legal or case references, metadata, version history, and classification. Other elements might be added based on discussions with the Court staff.
Annex 1 provides a sample structure for citations, however it is solely for informational purposes. The contractor is expected to propose and implement a final structure that ensures smooth and efficient operation of the system with consultation with the Court of Cassation on required data.
Citation handling logic in MS Word
First use
When a citation is inserted in the document for the first time, it should include the full citation and the corresponding reference concatenated by …(տե՛ս ...) structure.
|
Citation |
(…) [Ի] տարբերություն օրինական ուժի մեջ չմտած դատական ակտերի` օրինական ուժի մեջ մտած դատական ակտերը կարող են վերանայվել բացառապես նյութական կամ դատավարական իրավունքի հիմնարար խախտման (կամ նոր երևան եկած կամ նոր հանգամանքների) հիմքով: Նման իրավակարգավորումը բխում է իրավաչափ այն գաղափարից, որ օրինական ուժի մեջ մտած դատական ակտերի վերանայումը ընդհանուր կանոնից բացառություն է և, որպես այդպիսին, ենթադրում է բողոքարկման բացառիկ հիմքերի առկայություն: Հարկ է ընդգծել, որ «հիմնարար խախտումը» ենթադրում է խախտման առավել ծանր բնույթ, քան քրեական օրենքի սխալ կիրառումը կամ քրեադատավարական օրենքի էական խախտումը (ՀՀ քրեական դատավարության օրենսգրքի 397-398-րդ հոդվածներ): Հիմնարար խախտման էությունը դրսևորվում է նրանում, որ այն ի սկզբանե կանխորոշում է քրեական գործի քննության ոչ ճիշտ ընթացքը, բովանդակազրկում դրա նշանակությունը` դրանով իսկ վկայելով անօրինական և չհիմնավորված դատական ակտ կայացված լինելու մասին (…) |
|
Reference |
Վճռաբեկ դատարանի` Մկրտիչ Սարգսյանի գործով 2015 թվականի հունիսի 5-ի թիվ ԵՄԴ/0020/01/14 որոշման 18-19-րդ կետերը: |
|
Referencing option 1 - Footnoting |
The superscript number should be placed immediately after the citation text, indicating the corresponding footnote. The footnote should begin with “Տե՛ս” followed by the reference text. |
|
Referencing option 2 - Concatenation |
the reference text is inserted inline in parentheses following the citation. … (տե՛ս …) |
Subsequent uses - shortened reference:
If the same citation is used again later in the same document, it should automatically switch to a shortened reference form, such as: “Տե՛ս” or ”տե՛ս”, depending on referencing option, and shortened reference text. Example: Տե՛ս Վճռաբեկ դատարանի՝ Արևիկ Սահակյանի և Ծովինար Սահակյանի գործով վերը նշված որոշումը.
Deletion logic - reversion to full citation:
If the first (full) citation is deleted from the document, the next remaining instance of that citation should automatically be updated to become a full citation, maintaining clarity and reference completeness.
The above mentioned is for example only. The exact format of citations, including wordings, bolds, italics, etc. should be discussed with the Court of Cassation.
Interface requirements
The website should follow the principles of universal design:
● Equitable use: The design is useful and marketable to people with diverse abilities.
● Flexibility in use: The design accommodates a wide range of individual preferences and abilities.
● Simple and intuitive use: The design is easy to understand, regardless of the user’s experience, knowledge, language skills, or current concentration level.
● Perceptible information: The design communicates necessary information effectively to the user, regardless of ambient conditions or the user’s sensory abilities.
● Tolerance for error: The design minimizes hazards and the adverse consequences of accidental or unintended actions.
● Low physical and cognitive effort: The design can be used efficiently and comfortably and with minimum fatigue.
● Size and space for approach and use: The design provides appropriate sizing and spacing of elements, allowing the user to interact successfully.
● The website should follow the web accessibility principles, on which level AA WCAG is based.
The main accessibility principles are the following:
● Perceivable: Information and user interface components must be presentable to users in ways they can perceive.
● Operable: User interface components and navigation must be operable.
● Understandable: Information and the operation of the user interface must be understandable.
● Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
During the acceptance, the website should be checked against the WCAG using relevant tools.
User profiles
The system should implement role-based access control (RBAC) to ensure that users can only access functionalities and data appropriate to their assigned roles.
The system should have user based access control ensuring distinguished roles between the users who input information, the users that approve the input and the final users that get access to the inputted data.
|
User |
Description |
|
|
1 |
Administrator |
Manages user accounts and system configurations. This user is responsible for creating and assigning roles to other users, ensuring appropriate access levels and workflow permissions across the platform. |
|
2 |
Data entry user |
Inputs and edits citations and all required metadata (e.g., keywords, legal references, descriptions). This user prepares the information for review but cannot publish it independently. |
|
3 |
Approver |
Reviews the submitted citations and their metadata for accuracy and completeness. Upon approval, the data becomes officially available within the system for search and use. |
|
4 |
Viewer |
Can search the platform for citations and metadata and insert selected content into MS Word documents or integrated systems. This user has read-only access and cannot modify any content. |
Operational Environment Standards
The system must meet the following operational environment standards to ensure compliance, security, interoperability, and long-term maintainability.
Compliance Requirements
The system must comply with the RA Government Decision N 1093-N dated 2015, which defines minimum security requirements and interoperability standards for state information systems.
Operating System
The system must operate on a Unix-based or other open-source operating system, ensuring stability, security, and cost-efficiency.
Database
The system must use PostgreSQL or an equivalent open-source relational database that supports complex queries, indexing, and scalability.
Web Browser Compatibility
The system should fully support all modern web browsers, including but not limited to:
● Google Chrome (latest versions)
● Mozilla Firefox
● Microsoft Edge
● Safari (for macOS)
Security Protocols
All data transmission must be encrypted using HTTPS (TLS 1.2 or higher).
Exceptions
Any required deviations must be justified, reviewed, and approved by the client before implementation.
Source code
After official handover of the system and the launch, the source code is the property of the Court of Cassation.
Hardware and infrastructure requirements
The system must be hosted in a secure cloud environment that ensures:
● High availability and scalability
● Regular data backups
● Monitoring and logging of system activity
The Beneficiary must not incur any hosting-related costs including development phase and a period of 24 months following project acceptance. All hosting and maintenance costs for this period must be fully covered by the Contractor and clearly presented as a separate line item in the financial offer.
Upon completion of the 24-month period, the Contractor shall submit a migration strategy for approval by the Court of Cassation and ensure the system is successfully migrated to the hosting environment designated by the Court of Cassation.
Preferably, the cloud service provider should ensure that all data is hosted within the territory of Armenia.
The hosting shall be compliant with the requirements set out in the Government Decree N884-L, dated 14.06.2024.
Access modes and security requirements
Strong passwords with two-factor authentication (2FA) methods should be available and configurable for the Administrator user role to enhance security and protect against unauthorized access.
Data entry users and Approvers should enter the system solely through YesEm National identification portal as specified in 572-N Government Decree, dated 25.05.2017.
Operational Security
All actions performed by Administrator, Data Entry Users and Approvers must be logged to ensure traceability and support future audits. The logging mechanism should be built-in to the system (no external third party tools are acceptable for logging) at a minimum record the following events:
● User logins and logouts
● Citation submissions for approval
● Approval or rejection of citations
● Edits or updates to existing citations and metadata
● Role and permission changes
The system must also provide a user-friendly audit log viewing interface, enabling searching, filtering, and exporting of log data without the need for any external tools or software. This functionality should be accessible only to authorized users in accordance with their roles and permissions.
Backup and Archiving
Incremental backups should be implemented on a daily basis to capture changes since the last full backup, which should be implemented on a weekly basis, reducing storage needs and speeding up the process.
Encryption: The backup data should be encrypted during the transit and at rest to ensure protection of sensitive data.
Regular Testing: The supplier should regularly test backup files to ensure that they can be restored accurately and within maximum 24 hours.
Lifecycle management: The Supplier should develop the backup lifecycle management plan, including the proposal for back-up storage media to be utilized and submit for the Court’s approval.
In addition, the system should include functionality to export and import the entire database, including citations, metadata, user roles, and other critical configuration settings. This capability is essential for effective disaster recovery and system restoration in case of data loss, corruption, or system failure.
Service level: availability, performance and support
After the official handover of the platform to the Court of Cassation, the Supplier should provide 12 months of technical support.
The hosting of the platform shall be envisaged for 2 years. Within this support, upgrades and releases should be submitted to correct the errors and bugs.
In case of detecting incompliance, those should be eliminated by the Supplier and at the Supplier’s expense.
The Supplier should establish a help desk for submitting the issues over the email and phone line available on working days from at least 10:00 to 17:00. The response to the recorded issue should be provided within maximum in 1 hour, indicating estimated timelines for the elimination of the issue.
Incident handling
Incident: any event that is not part of the normal operation of the applications, causing or likely to cause an interruption in service or a deterioration in its quality (as defined in the service agreement).
· Critical Incident: type of incident defined as such by the Customer or, failing this, resulting in the total loss of service.
· Major Incident: type of incident defined as such by the Customer or, failing this, resulting in the deterioration of the service.
· Minor Incident: type of incident defined as such by the Customer or, failing this, representing a fault without affecting the service.
|
Minor incident |
Timeframe for the service provider to take care of the incident: Less than 24 hours |
Expected resolution time: |
Penalty: 0.1% of Contract price per 1 day delay in resolving the incident |
|
Major incident |
Timeframe for the service provider to take care of the incident: Less than 4 hours |
Expected resolution time : |
Penalty: 0.2% of Contract price per day late in resolving the incident |
|
Critical incident
|
Timeframe for the service provider to take care of the incident: |
Expected resolution time : |
Penalty: 0.5% of Contract price per day late delay in resolving the incident |
The response time indicated takes effect as soon as the Beneficiary has informed the Supplier of the malfunction, by email or telephone. The email address is provided by the service provider; the service provider will be deemed to have received the email informing them of the malfunction as soon as it is sent by the Beneficiary, unless an error message is returned, in which case the Council will notify the service provider by telephone.
The above terms and conditions apply in the absence of a detailed personalised proposal from the service provider.
Changes
The Supplier shall take into account that during this time period the Court of Cassation may request changes in the platform for up to 15 (fifteen) percent of the total scope of works.
System Documentation
The following documentation should be delivered to ensure proper system deployment, integration, usage, and maintenance throughout the project lifecycle.
1 Detailed functional specifications must be provided, describing all system features, user roles, and permissions, as well as workflows. This documentation should serve as the basis for testing and user training.
2 Detailed system description must be provided, including the overall system architecture, key components, data flow, integration points, and technology stack. The documentation should support both technical understanding and future maintenance.
3 Detailed user manuals must be available within the system’s web interface for each user type. The Viewer User Guide must also be accessible in the Microsoft Word plug-in.
4 Detailed system installation guide must be provided covering step-by-step instructions necessary for deploying the system and setup the database, as well as operational system and network configurations.
5 Detailed export/import guide must be provided to ensure that system administrators can perform full or partial restores as needed.
6 API documentation and integration guides must be provided to support seamless interoperability with external systems and services.
7 Test scenarios must be developed to cover all functional and non-functional requirements. These should include user role-based actions, data validation and integration points. All the scenarios must be used during system acceptance testing.
8 The source code of the application should be delivered by the Supplier in an appropriate, reusable and documented form.
9 Prior to the official launch of the system, the Supplier shall prepare and submit a detailed Compliance Report confirming that the developed solution adheres to the requirements of the following international standards:
● ISO/IEC 5055: Software quality measurement model
● ISO/IEC 25001: Quality requirements and evaluation for system and software product quality
The report shall outline the methodology used for evaluation, reference the specific criteria met under each standard, and provide evidence of conformity. This deliverable is a precondition for final system acceptance.
The table below outlines the key actions, corresponding deliverables (in bold), and the estimated timelines for their completion.
|
N |
Actions and deliverables |
Estimated timeline |
|
Phase 1: Inception |
||
|
1 |
Kick off meeting |
Within 1 week after Contract enters into force |
|
2 |
Desk review and interviews with the Beneficiary |
2 weeks after Contract enters into force |
|
Submission of the project plan for approval |
2 weeks after Contract enters into force |
|
|
3 |
Development of detailed system specifications |
4 weeks after Contract enters into force |
|
4 |
System interface design development |
5 weeks after Contract enters into force |
|
System Requirements including business process models, data requirements, user roles, and software design |
6 weeks after Contract enters into force |
|
|
Phase 2: Development and testing |
||
|
5 |
Development of the system |
20 weeks after Contract enters into force |
|
6 |
Development of the plug-in for Microsoft Word |
20 weeks after Contract enters into force |
|
7 |
APIs for integration |
24 weeks after Contract enters into force |
|
8 |
Testing of the system, including pilot and user acceptance testing |
28 weeks after Contract enters into force |
|
Demonstration of the final system and submission of testing results |
29 weeks after Contract enters into force |
|
|
Phase 3: Training and launch |
||
|
9 |
Training of the staff of the Court of Cassation |
32 weeks after Contract enters into force |
|
10 |
Development of system documentation, including user manuals |
33 weeks after Contract enters into force |
|
Official launch of the system |
34 weeks after Contract enters into force |
|
|
Support period |
12 months after the official launch |
|
The organization should demonstrate experience in developing comparable systems. A comparable system is defined as one that includes the following features: workflow management, role-based user access and permissions, a database, advanced search capabilities, a reporting module, and APIs that enable integration with external systems.
Within the last five years, the Supplier must have implemented at least three comparable systems, at least one of which had a contract value equal to or exceeding the amount specified in the financial proposal for this Project.
The Supplier shall present a project approach with team composition that ensures full coverage of all key functional areas, including project management, business analysis, UX/UI design, software development (front-end, back-end, DevOps, and MS Word plug-in), quality assurance, technical documentation, training, and user support.
Assumptions
● The Court will assign a designated focal point to provide detailed explanations related to citation processes and workflows. Additionally, the authors of the Terms of Reference will remain available to respond to clarification requests during both the tendering phase and the subsequent system development process.
● The Court of Cassation will define a standard for citations, which must be used in all documents. The standard shall define the citation structure, including the required format and the data fields for unified referencing and consistency across all entries.
● The filling in of the content into the system will remain the responsibility of the Court of Cassation.
● The Court will provide the list of necessary structured reports on system usage or approve Contractors respective suggestions.
Constraints
There are no identifiable constraints at this stage that would prevent the successful implementation of the Project.
Risks
|
RISK |
Explanation |
Impact |
Mitigation |
|
Absence of legal act formulating citation standard. |
Based on the practice of the European Court of Human Rights the citation in the document is placed as a single paragraph containing citation and the reference in brackets. In Armenia different court documents use various citation formats, such as parentheses, quotation marks (or their absence), italics, footnotes, and so on, yet the MS Word tools should support only one standard which may be “unacceptable” causing resistance. |
Mode-rate |
Training explaining why a single standard is needed. Internal circulars or orders stating the citation structure. |
|
Inability to form a dedicated working group for data entry prior to or during the early stages of the support period |
Although the delay in forming the working group will not hinder the technical development of the system, the training may be disrupted. Moreover, it may negatively impact the sense of ownership and engagement among the actual end users. |
High |
Develop comprehensive documentation Conduct targeted consulting |
Data inputs
All data is expected to be entered manually by a dedicated working group of the Court of Cassation. No automated data migration or import is planned at this stage.
Data outputs and reporting requirements
The system shall ensure the ability to create different reports based on the data collected (number of filled in citations, number of approved citations, most popular searches, most cited decisions, etc.). A dashboard with filtering and drill-down functionality should be available targeted for different users. The content of dashboards and reports should be discussed with the Beneficiary.
The system should provide APIs for integration of citation embedding, validating functionality with other systems
The aim of the training is to provide comprehensive information about the general operation of the system, structure, knowledge and skills.
Training Plan and Training Approaches
● Before starting training courses, the Supplier should prepare a training plan for different groups of users of the system
● The training shall be conducted in Armenian language.
● The Supplier should assess the training needs associated with the use of the system before it is fully operational.
● The training methods may, without limitation, include presentations for the trainees, intensive classroom activities during which manuals and other technical literature will be handed over, briefings, on-site workshops.
● The training should be conducted in the premises of the Court of Cassation. At the request of the beneficiary, training can be held in hybrid mode as well.
● The Supplier should organize training on system use for around 30 users (TBC by the Court of Cassation).
● The supplier should envisage separate training for administrators. During this training, the Supplier shall perform a one-day training course for the administrators. The topics of this training shall include the installation, operation, and maintenance of the system.
● As part of the training, a copy of the source code with code explanations should be provided.
Privacy Requirements
For administrators, data entry users, and approvers, it is essential that all actions are auditable and clearly linked to the individual user who performed them. This includes logins, data edits, approvals, and other critical operations.
In contrast, for viewer users, privacy must be strictly preserved: no identifiable information should be stored or exposed regarding which user searched for or inserted specific citations.
All users subject to auditing (administrators, data entry users, and approvers) must be explicitly informed and must provide consent to the conditions of activity logging prior to using the system.
Legislation
This chapter will be excluded from a Call for Tender document
Completing the database is a critical component of the system and will require significant time and effort from the Court. This process may involve the establishment of a dedicated working group composed of internal staff and, where necessary, external experts.
It is important to note that launching the tool while the database is still limited carries the risk that users may not find relevant content and could lose trust in the system. To mitigate this, targeted communication efforts and awareness-raising workshops will be necessary to inform potential users about the phased implementation approach and manage expectations regarding the system’s capabilities during its initial stages.
Annex 1 Sample structure of citation
JSON
{
"citation_id": "CIT-2025-000123",
"title": "Interpretation of Article 12: Import Tariff Flexibility",
"text": "(…) [Ի] տարբերություն օրինական ուժի մեջ չմտած դատական ակտերի` օրինական ուժի մեջ մտած դատական ակտերը կարող են վերանայվել բացառապես նյութական կամ դատավարական իրավունքի հիմնարար խախտման (կամ նոր երևան եկած կամ նոր հանգամանքների) հիմքով: Նման իրավակարգավորումը բխում է իրավաչափ այն գաղափարից, որ օրինական ուժի մեջ մտած դատական ակտերի վերանայումը ընդհանուր կանոնից բացառություն է և, որպես այդպիսին, ենթադրում է բողոքարկման բացառիկ հիմքերի առկայություն: Հարկ է ընդգծել, որ «հիմնարար խախտումը» ենթադրում է խախտման առավել ծանր բնույթ, քան քրեական օրենքի սխալ կիրառումը կամ քրեադատավարական օրենքի էական խախտումը (ՀՀ քրեական դատավարության օրենսգրքի 397-398-րդ հոդվածներ): Հիմնարար խախտման էությունը դրսևորվում է նրանում, որ այն ի սկզբանե կանխորոշում է քրեական գործի քննության ոչ ճիշտ ընթացքը, բովանդակազրկում դրա նշանակությունը` դրանով իսկ վկայելով անօրինական և չհիմնավորված դատական ակտ կայացված լինելու մասին (…)",
"references": [
{
"type": "case",
"text": " Վճռաբեկ դատարանի` Մկրտիչ Սարգսյանի գործով 2015 թվականի հունիսի 5-ի թիվ ԵՄԴ/0020/01/14 որոշման 18-19-րդ կետերը:",
"shortened text": "Վճռաբեկ դատարանի՝ Արևիկ Սահակյանի և Ծովինար Սահակյանի գործով վերը նշված որոշումը",
"case_number": "ՎԴ/2659/05/22",
"court": "ՀՀ Վճռաբեկ դատարան",
"decision_date": "2023-09-21",
"volume": "",
"reference_url": "https://courts.am/decisions/2023-015"
}
],
"keywords": ["վնաս", "զգալի վնաս", "հիմնավոր կասկած", "import"],
"article": "ՀՀ վարչական դատավարության օրենսգրքի 83-րդ հոդված"
"type": "Քրեական",
"language": "հայ",
"created_by": "Լեոնիդ Ավետիսյան 1610700069",
"created_at": "2025-06-12T15:23:00Z",
"approved_by": "Արաքս Ավետյան 6211920527",
"approved_at": "2025-06-13T09:45:00Z",
"status": "approved",
"hierarchy": {
"level_1": "Վնաս",
"level_2": "Զգալի վնաս",
},
"revision_history": [
{
"version": 1,
"date": "2025-06-12",
"changed_by": "Արաքս Ավետյան 6211920527",
"change_note": "Initial entry"
"hash": "a3b5f1b77e8d97a925e59c905a3ff473fbc8d8df0ef69ea2e43d9e5148652e36"
}
]
}