Good Low Level Designs

I work for a small MSP in Europe that helps customers build network infrastructure. We have our Low Level Designs, that we hand over to the customer. I've been asked to redesign the template for them by our senior network engineer. I'm looking at building it like this:

1. Project Overview (Problem, Requirements, Constraints, Scope)
2. Hardware (Hardware, Features, Hardware-Location)
3. Standards (How we normally lay out a data center, remote site, whatever we're building. Lists Physical cable layout, Layer 2, Layer 3, HA, etc)
4. Sites (Anything that deviates from the standards. So, it'll be a table for IP ranges and device names. If we used 2 cables between the routers and switches instead of 3... It'll be documented here. Otherwise, if it conforms to the standards. Nothing changes).
5. Management and Operations (Anything extra about management of the solution)

Thoughts?

Are there any specific comments or feedback that you have around what you like/dislike about LLDs from MSPs? What is good to include in an LLD?