SANJIESAN LICENSING / Review records
A useful design comment names the version and the view
“The label is too close” is difficult to act on when the folder contains several box views and yesterday’s draft. A short comment can be precise without becoming a long report. Attach it to the exact version, identify the relevant view and describe the relationship that needs attention. This method concerns working references rather than any formal acceptance procedure.
Point to the source before describing the change
Name the file or page revision and the view, such as the front panel of proposal B. Use a marked copy or a stable page reference when available, while keeping the editable original separate. A crop can help locate a small issue, but also include enough surrounding context to identify orientation and neighbouring content. Do not let the annotation become a new unlabelled artwork version.
Describe the relationship that is failing
Say that the secondary label competes with the title, or that a border touches a required word in this view. Separate that observation from a suggested solution. “Move the label” might be one option, but the designer may find a better hierarchy adjustment. Keep a fixed requirement explicit so it is not accidentally removed while resolving the visual problem. Avoid vague references such as “same as the one above” when comments may later be exported individually.
Confirm the correction on the revised view
When the revision arrives, open the corresponding view and check the original relationship. Record whether it is resolved or which part remains. Do not close the note simply because the file date changed. If the new version uses a different panel arrangement, update the reference while retaining the reason for the comment. A small record is useful when it lets someone verify the change without reconstructing the entire meeting.