Project Charter developing tools

It really depends on the information itself - some might be automatically generated (e.g. forecast based on past performance) and some might be visually rendered whereas other information might purely exist in document form.

Circumstances have forced me to move away from a simple charter to a detailed document that boils down all elements to their nuts and bolts.

My charters are structured like a textbook (and my TOC alone usually takes up two pages!).

I use the charter like a user manual for the project for new/ replacement team members - it saves a lot of time and gets them up to speed quickly.

Yes, if the surroundings were different, I would go for a fairly simple charter.