The board's annual plan on Bitrix24 instead of an Excel file
The board's annual plan was kept in an Excel file: deadlines, postponements and results were edited by hand, the approval history of postponements was not stored in the file, and the table was prepared separately for each board meeting.
Management was used to the look of the file — the registry had to look "like the plan". The approved deadline must not be lost through postponements, and the current deadline could be changed only via approval.
- A plan line is a smart-process item: the stock card, kanban and timeline with no second data store
- A custom registry "like the plan file": a table with numbers and completion criteria, a board summary, an approval queue
- A deadline postponement is a business process with two sign-offs and a mandatory justification; the postponement counter and current deadline change only after sign-off
- A result is required when submitting and closing a line; the approved deadline and plan details are locked against manual editing
- Overdue and acceptance reminders, a weekly summary to the board in a single message
- Exporting the plan for a board meeting to Word and PDF with one button from the registry
The board plan moved from Excel into the portal: each line shows the approved and current deadline, the postponement history with sign-offs and justifications, and the completion result. The rules for postponements, sign-off routing and export are covered by unit tests.
Related services and solutions
Bitrix24 D7: boxed development and stabilization
I work not only with interface settings, but at the level of the box, the code and internal APIs.
Business process automation
When employees transfer data manually, reconcile spreadsheets, lose requests or repeat the same actions — I turn the routine into code.