I do suggest you to introduce a new type of mandatory field which would become active (become mandatory) based on rules and conditions such as blueprint status, field values, time counts, correspondence count, etc. For example a field used to classify solution proposals shouldn't be mandatory when the ticket has been received (New ticket) but become mandatory on certain statuses of the blueprint.