This is very common in technical documentation, specifically things like RFPs (Request for Proposals) <-- Is to state the acromyn the first time, and expand it

This is very common in technical documentation, specifically things like RFPs (Request for Proposals) <-- Is to state the acromyn the first time, and expand it and throughout the RFP you can then use the acronym, the real reason this is important is that RFPs --> $MONEY and thus, will be scrutinized by the "penny pinchers" who will lack a lot of domain knowledge being addressed with an RFP for a project. For example, I, as a Director of OPs was constantly educating our CFO on cloud spend, and would have to kind of train him on technical matters while at the same time explaining where all our costs are etc... Or when designing a huge project (I have worked on many projects with budgets over $1 billion) and going through vendor selection processes, where we review the RFPs with the vendors and the finance holders for the project, there are many times when one has to justify telling Mr. Money Bags why simply accepting the cheapest offer is not sufficient. This was actually a type of work, which at the time felt tedious, but now I realize how much I actually liked this aspect of my career.