A report is not the same thing as a blueprint. A report is a straight read-through in a textual format (usually packaged in Word or PDF files today), like a long articles or a bunch of articles together or an ebook.
A blueprint is a guide, usually of a technical drawing, documenting your program or project, like an engineering design.
With so many tools available today, you can get creative in drawing out your plans and use mind mapping software or PowerPoint slides with shapes, branching out, etc. - - the mapping out of your program or system, for example. Yes, include instructions in textual format to introduce your drawings and feature points about them, steps involved, etc. But don't include the history of all that's involved and all that report / ebook material. That's supplemental stuff if anyone wants it.
Here are neat examples (not an affils. & not my links) :
Type in "blueprints" in Google for tons of examples. Blueprint buyers want to walk away with a plan - -not a report on the history of something, yada, yada, yada. They want to insert their own project info into your plan - -plugging in the info --and run with your system.
Yes, a gazillion videos with it and other bonuses on PPC, etc. may be useful to some buyers. But if people order a blueprint that they want to put into action, and it's not there, well...bonus gifts aren't going to help with the disappointment.
I hope this is clear. If it's not, please speak up, and fellow Warriors, please help out to explain this, if you know what I'm talking about.
Bottom line: if you say you have a system that works, write it out. Period. Skip the bonuses, the entire history of the web and other junk involved. JUST present what you say you have, the system that works : show it. That's plenty.
Anything else is smoke after the fire is out (if it was ever lit to start with...)