SQL Server might complain if reducing the size of the field would delete data already in the column. Is there some reason why you can't just create a new column, copy & convert the field data with an UPDATE statement, then remove the old column?
It sounds like an odd request; nvarchar is a flexible data type that also supports nulls. Maybe you need to put on your "change management" hat ![]()