Software Genuine Management System and Responsibility System Sample

Key points of this article

The management system governs the "how": scope, responsibilities, procurement, ledgers, installation and inspection processes must be written in enforceable terms.
The assessment and evaluation system governs "how well done": indicators must be verifiable, evaluation procedures must be in place, and results must have a destination.
The responsibility system governs "who is responsible and what to do if something goes wrong": responsibility must be assigned to the position, and accountability situations and accountability procedures must be clearly written.
The three systems can be written separately, but the terminology, responsibilities and clause numbers must be consistent.
Using Word's title style and multi-level list layout, the numbering and table of contents can be automatically updated after modifying the terms.

When many units promote the legalization of software, they have work plans and annual summaries in hand, but they lack a set of institutional documents that can be implemented over the long term. The plan explains "what to do" and summarizes and reviews "what has been done". The system answers "what rules should be followed and what should be done if it is not done well". This is exactly the problem that documents such as "Software Genuine Work Management System", "Software Genuine Work Assessment and Evaluation System" and "Software Genuine Work Responsibility System" are to solve.

This article is written for office, information or asset managers responsible for drafting systems. After reading it, you can get the chapter structure of the three-part system, what to write in each part, how to express the terms, and how to arrange it into a formal document in Word. The content in this article is a general framework. Please adjust the specific terms according to the organizational structure of your unit and the requirements of your superiors.

How to split the system? One sentence conclusion

Each of the three systems deals with one thing. It is recommended that they be written separately and reference each other, rather than pile all the requirements into one long document. The table below illustrates common practices in different situations.

your situation	Recommended practices	reason
The unit is small, with only one information technology position	The management system and responsibility system are merged into one, and the assessment and evaluation are listed separately.	The number of documents is small, and the assessment remains independent, making it easy to review.
Multiple departments each have software purchasing rights	Separate into three parts, the responsibility system lists responsibilities by department.	When responsibilities are dispersed, a checklist allows each department to know what it is responsible for
Superiors require submission of system text	The master document of the management system, ledger format and indicator table are attached.	The text structure is complete and attachments can be updated along with the software list.
There is an old system and the content is outdated	Keep the original numbering system, revise it item by item and record the revision date	Clearly compare the old and new documents to avoid conflicts between the two sets of documents.
The system is used for internal assessment	Indicators are written as verifiable factual items, and reviewers and procedures are specified	When indicators cannot be verified, reviews tend to become just a formality

Template structure overview

part	what to write	Space suggestion
Management System·General Principles	Purpose, scope of application, basis, definition of terms	1–2 paragraphs
Management system·division of responsibilities	The respective responsibilities of the leadership group, responsible departments, and user departments	3–5 items
Management system·Procurement and ledger	Procurement approval, registration requirements, ledger fields, update cycle	5–8 items
Management system·Installation and inspection	Installation permissions, regular verification, and exception handling	3–5 items
Assessment and evaluation system	Assessment objects, assessment indicators, evaluation procedures, and application of results	6–10 items
Responsibility system	Responsible subjects, responsibility list, accountability situations, accountability procedures	5–8 items
By-laws and Attachments	Implementation date, interpretation department, revision record, appendix	2–3 items

How to write part by part

General principles and division of responsibilities

The general principles should clearly state why the system was established, which equipment and personnel it manages, and which superior documents it is based on. The "scope of application" should be specific to the department and office equipment type, and avoid just writing "all employees".

The division of responsibilities is usually divided into three levels: the leadership group coordinates decision-making, the responsible department is responsible for organizing implementation and summarizing the list, and the user department is responsible for the daily self-examination of the department. Example: "[The responsible department] is responsible for organizing the legalization of software throughout the unit, and compiles a software list every [cycle] and submits it to the [leading group] for review."

Purchase approval and software ledger

This part should stipulate that newly purchased software must be approved before purchasing, and explain the registration scope and update cycle of the ledger. Suggested ledger fields include: software name, version, authorization quantity, authorization type, license or contract number, usage department, custodian, and expiration time.

Example: "To add or renew software, the using department should fill out the "Software Procurement Application Form". The purchase can only be made after approval by [Approval Position]. After the purchase is completed, it will be entered into the ledger within [time limit]."

Installation and inspection

Installation permissions should be managed centrally, and individuals are not allowed to install unregistered software without authorization. Inspections are divided into two categories: regular inspections and random inspections. During the inspection, the ledger will be compared with the actual installation situation.

Example: "If unregistered software is found during the verification, the [responsible department] should complete the verification within [time limit] and submit processing instructions to the [responsible department]."

Assessment and evaluation system

Assessment and review should answer four questions: who is assessed, what is assessed, how to evaluate, and how to use the results.

Assessment indicators should be written as items that can be verified with facts, such as "whether the ledger is updated on schedule", "whether the verification issues are rectified within the deadline", and "whether the procurement approval records are complete", to avoid expressions such as "the work has achieved significant results" that cannot be judged. The evaluation method can be department self-evaluation, verification by the responsible department, and evaluation by the leadership group when necessary. The application of results can be connected with the department's annual work evaluation, and the specific method is determined by the unit.

Example: "The assessment results are divided into [grades], determined by the [evaluation agency], and announced within [range] for [duration]."

Responsibility system

The focus of the responsibility system is to assign responsibilities to positions. Responsible subjects usually include the person in charge of the unit, the person in charge of the responsible department, the person in charge of the using department and the software custodian. Each subject corresponds to a list of responsibilities, indicating "what to do" and "what will happen if you don't do it."

Accountability situations can list common problems, such as purchasing without approval, ledgers not being updated for a long time, verification problems not being rectified, and concealing problems. The accountability procedure should include several steps: verification, notification, listening to the opinions of the parties, handling, and keeping records.

Example: "[Position] failed to update the ledger as required. After verification, the [processing agency] will conduct an interview and order rectification within [time limit]."

Supplementary Provisions and Revision Records

The supplementary provisions state the date of implementation, interpreting department and abolished old documents. It is recommended that the revision record table include four columns: version number, date, revision content, and approver, so that each change can be traced later.

Layout in the editor

Use Word's "Heading 1" to set the chapter name, "Heading 2" to set the section name, and use normal paragraph or list style for the body clauses to make the structure clearly visible in the navigation pane.
Set up multi-level list automatic numbering for clauses, and the format can be set to "Article X". After deleting or adding an item in this way, the subsequent clause numbers will be automatically extended, and there is no need to manually change the numbers.
Insert a table of contents at the beginning of the text. As long as the title style is set correctly, the table of contents can be updated with one click.
Write the name of the system in the header, and add the page number in the format of "Page
Use tables to format revision records and signature columns, and set the tables not to break across pages. Export PDF for filing or signing after finalization. If you need to add a signature to a PDF or fill out a form, you can do it in the PDF editor of the OmniDoc desktop client; if you need multiple people to collaborate online to modify a Word file, you can open it in the UniDoc web editor (app.unidoc.top) and export it to Word after editing.

Common writing problems

The terms only say "strengthen management" and "timely processing", lacking the subject, action and time limit.
Responsibilities are written to "relevant departments" and are not assigned to specific positions.
The assessment indicators cannot be verified and can only be scored based on impressions during evaluation.
Terms such as "software ledger" and "software assets" are used interchangeably in the three systems, and there is no unified definition.
The accountability situation in the liability system does not match the obligation provisions of the management system.
After revision, only the main text is corrected, and the ledger fields and revision records of the attachment are not updated simultaneously.

❓ Frequently Asked Questions (FAQ)

1. What is the difference between the software legalization work management system and the work plan?

The tasks and time arrangements in the plan writing stage have clear completion nodes; the system writes long-term applicable rules, responsibilities and procedures, and generally does not set a specific completion date.

2. Does the three-part system have to be written separately?

Not required. Smaller units can merge the management system and responsibility system, but the assessment and evaluation should be listed separately so that the evaluation process can operate independently.

3. Can the liability system only say "relevant personnel bear joint and several liability"?

General statements are not recommended. A list of responsibilities and accountability situations should be listed by position; whether joint and several liability applies, please refer to the unit's regulations and superiors' regulations.

4. How to determine the time limit and quantity in the system?

Placeholders are used when drafting, and are determined by the unit based on actual workload and superior requirements. It is not appropriate to directly copy figures from other units.

5. Can foreign language reference templates be directly translated and used?

You can translate it first for reference, but you need to check the terminology and legal expressions item by item. Upload a Word file on omnidoc.top and select bilingual comparison or translation only to quickly get a draft of the translation; the results of machine translation require manual verification, especially the responsibilities and time limit clauses.

📝 Summary

The software legalization work management system, assessment and evaluation system, and responsibility system each have their own division of labor. If the scope, responsibilities, procedures, and responsible entities are clearly stated, an executable system can be formed. First, set up the framework according to the structure of this article, then use placeholders to fill in the actual situation of the unit, and finally finalize it in Word using title style and automatic numbering.

Open OmniDoc, edit and export documents online