If you don't request a map, the specific diversity details might not actually get into the hands of the people engineering the circuit/service. It's very common for the order to be entered into some system and the actual service order document to only be looked at by people who don't even really understand the language around diversity requirements.
However, if you request a map and (if needed) raise a stink, someone on the sales/order management side has to get in touch with someone in Engineering. When I was in network engineering I would always go to great lengths to wring actual signed service orders out of order management. Usually I'd be told that I didn't need it a few times before I got it. Pretty often I'd find something that wasn't put into the order database, like a diversity requirement or some technical requirement like supporting 9000+ byte frames or transparent to double-tagged traffic. Sometimes I'd find out that the OC192 was actually 10GigE or vice versa.
Ask for maps, trigger that Engineering involvement.