Tasks in Brusnika.LMS: Checklists, Assignments and Review
Maria Ivanova
Analyst
Integrations mentioned in this article
Tasks in Brusnika.LMS are practical assignments with deadlines. They help organize specific actions that employees need to complete as part of learning, development, onboarding, or other structured activities.
A task can have one of two formats: a checklist or an assignment requiring review. With a checklist, the employee marks completed items themselves. With an assignment, the employee submits an answer and, when required, a file. A reviewer then accepts the work or returns it for revision.
Tasks are stored in a task catalog. They can be assigned directly to employees and included in learning programs and learning paths.
What the Tasks module allows
In Brusnika.LMS, users can:
- create tasks with a title, description, and deadline;
- attach files from an upload or the media library;
- show a task in the task catalog or hide it;
- create checklist-based tasks;
- create assignments that require a submitted response;
- add individual items to a checklist;
- mark a checklist item as requiring a result for review;
- assign tasks to employees;
- include tasks in learning programs and learning paths;
- access assigned tasks through the employee task sections;
- review submitted answers;
- accept assignments or return them for revision;
- view the previous answer when an assignment is returned;
- identify overdue and incomplete tasks;
- review task completion reports;
- export task data to Excel and PDF.
How tasks work
A moderator creates a task and defines its main parameters directly in the task card. There is no separate task settings screen.
A task can contain:
- a title;
- a description;
- a deadline;
- files;
- the Show in catalog option.
After creation, the task can be assigned to employees or included in a learning program or learning path.
The employee sees assigned tasks in the relevant sections of Brusnika.LMS and completes them by the specified deadline.
Two task formats
Brusnika.LMS supports two task formats.
| Format | How it works |
|---|---|
| Checklist | The employee completes individual items and marks them in the task card |
| Assignment | The employee submits a written answer and, when required, a file for review |
Checklists
A checklist is useful when a task consists of several actions that need to be completed and tracked individually.
When creating a checklist, the moderator adds its items. Employees mark completed items directly in the task card, and changes are saved automatically.
An individual checklist item can be marked as requiring a result for review. In that case, the employee cannot close the item independently. The result must be accepted by a reviewer.
This makes it possible to combine self-completed checklist items with items that require confirmation from another person.
Assignments with review
The Assignment format is designed for situations where an employee needs to submit a concrete work result rather than simply mark an action as complete.
The employee:
- receives the assignment description;
- completes the work;
- writes an answer;
- attaches a file when required;
- submits the result for review.
A file can be made mandatory. A reviewer is required for an assignment, so an assignment cannot be saved without selecting a reviewer.
An assignment can have the following statuses:
- not submitted yet;
- submitted and awaiting review;
- accepted;
- returned for revision.
When an assignment is returned for revision, the previous answer remains visible.
Submitted answers are delivered to the reviewer in Review Answers and Assignments.
Assigning tasks
Tasks can be assigned directly from the task catalog. They can also be included in learning programs and learning paths.
A task does not have to be visible in the catalog to be used elsewhere. If Show in catalog is disabled, the task can still be assigned and added to a program or learning path.
Task catalog
The task catalog is used to manage created tasks.
Available actions include:
- search;
- assign;
- share;
- copy a link;
- delete a task.
The catalog therefore serves as a central place for storing and managing tasks that can later be assigned individually or included in structured learning scenarios.
Where employees see their tasks
Assigned tasks are available in:
- Learning → My Tasks;
- Tests, Surveys and Assignments → My Assignments.
For checklists, employees complete items directly in the task card. Changes are saved automatically.
For assignments, employees submit their answers, which are then sent for review.
Overdue tasks are marked accordingly. The number of incomplete tasks is also displayed on the corresponding menu tile.
Tasks in Bitrix24
When Brusnika.LMS is used with Bitrix24, an assigned LMS task can be created as a task in the Bitrix24 portal. This allows employees to see the task alongside their other work.
Task status changes are synchronized between the LMS and the portal, so status updates made in the portal are transferred back to Brusnika.LMS.
When an assignment is removed, the corresponding task is closed in the portal.
Brusnika.LMS does not delete tasks from the portal. Events created in Brusnika.LMS also do not become Bitrix24 tasks.
The availability of specific LMS functionality inside Bitrix24 depends on the implementation of the relevant integration.
Reporting and analytics
Task results are available under Activity Reports → Tasks.
The task report can show:
- which employees completed tasks;
- which employees have tasks in progress;
- checklist completion by department;
- completion-time breakdowns.
The report also includes Nika.AI insights.
Task data can be exported to:
- Excel;
- PDF.
How tasks connect with other Brusnika.LMS features
Tasks can be used as part of broader learning and employee development scenarios.
Assignments
A task can be assigned directly to an employee from the task catalog.
Learning programs
Tasks can be included in learning programs. Completion can be counted based on the task type: a checklist is counted when it is completed, while an assignment is counted based on the reviewer's assessment.
Learning paths
Tasks can also be included in learning paths. The same completion logic applies: checklists are counted by completion, while assignments are counted based on the reviewer's assessment.
Answer and assignment review
Submitted assignment responses and checklist items that require review are delivered to Review Answers and Assignments.
Individual Development Plans
Brusnika.LMS includes its own task checklist within an Individual Development Plan (IDP), allowing practical actions to form part of an employee's development plan.
Gamification
Points awarded for tasks are configured in the gamification module.
Notifications
Task notification texts are configured in the notification settings.
Use cases
Onboarding checklist
A task can be used as a structured sequence of actions for a new employee.
For example, a First Week task may include:
- obtaining an access pass;
- completing an induction briefing;
- meeting the mentor.
The task can be assigned to new employees with a deadline. Employees mark items as they complete them.
Practical assignment with review
When a concrete work result needs to be submitted, the Assignment format can be used.
For example:
- create an assignment and describe the work;
- make a file mandatory;
- select a reviewer;
- the employee completes the work and submits an answer with the file;
- the reviewer accepts the result or returns it for revision.
This format is useful when simply marking an activity as completed is not enough and the result needs to be reviewed.
Limitations and important details
The following conditions apply to tasks:
- an assignment cannot be saved without a reviewer;
- an attached file can be made mandatory for an assignment;
- a checklist item marked as requiring a result for review cannot be closed by the employee independently;
- there is no separate task settings screen; the main parameters are configured in the task itself;
- task points are configured through gamification;
- notification texts are configured separately in notification settings;
- a task can be hidden from the catalog while still being assignable and available in programs and learning paths;
- when integrated with Bitrix24, task statuses are synchronized, but Brusnika.LMS does not delete portal tasks;
- Brusnika.LMS events do not become Bitrix24 tasks.
Frequently asked questions
What are tasks in Brusnika.LMS?
Tasks are practical assignments with deadlines. They can be checklists or assignments that require a submitted result to be reviewed.
What is the difference between a checklist and an assignment?
With a checklist, the employee marks completed items. With an assignment, the employee submits an answer, and a reviewer accepts it or returns it for revision.
Can a checklist item require review?
Yes. An individual item can be marked as requiring a result for review. Such an item must be accepted by a reviewer.
Can an assignment require a file?
Yes. A file attachment can be made mandatory for an assignment.
Can tasks be included in learning programs?
Yes. Tasks can be added to learning programs, and their completion can count toward the program.
Can tasks be used in learning paths?
Yes. Tasks can be included in learning paths. Checklists are counted by completion, while assignments are counted based on the reviewer's assessment.
Where can employees see assigned tasks?
Assigned tasks are available under Learning → My Tasks and Tests, Surveys and Assignments → My Assignments.
Can tasks be used in Bitrix24?
Yes. With the relevant integration, an assigned LMS task can appear as a task in the Bitrix24 portal, with status changes synchronized back to Brusnika.LMS.
Can Brusnika.LMS delete a task from Bitrix24?
No. When an assignment is removed, the portal task is closed, but Brusnika.LMS does not delete it.
Is there task reporting?
Yes. The Tasks tab under Activity Reports provides information about completion, work in progress, checklist completion by department, and completion-time breakdowns. Nika.AI insights and Excel/PDF exports are also available.