BYstudio. CRM acceptance issue log
21 October 2026. Fill-in template.
Source: https://bystudio.ru/en/solutions/crm-implementation-acceptance/
One record describes one finding. Copy the block for each issue.
Use anonymised data; exclude keys, tokens and customer records.

Project and phase:
Date, environment and tested version:
Acceptance owner:

Issue reference:
Short title:
Type: agreed requirement not met / clarification / new function
Requirement reference:
User role:
Starting data and test record:
Reproduction steps:
Expected result:
Actual behavior:
Evidence without customer data:
Workflow and launch impact:
Fix owner:
Agreed date:
Status: open / reported fixed / retested / closed
Supplier change description:
Retest date, environment and version:
Repeated steps and affected checks:
Actual result after the fix:
Confirmation owner and basis for closing:

ILLUSTRATIVE A-01
Role: manager. Order: safe test example.
Action: move to Confirmed.
Expected: delivery preparation activity by the agreed specification and time.
Actual: no activity after that time.
Next: check conditions and permissions, then repeat the same scenario.
This is an example, not a discovered Krest-NN or DOROGA defect.

OUTCOME
Open findings:
Untested requirements:
Agreed exclusions and new requests:
Phase decision and launch conditions: