Of course, you realize, that you have to be a good writer in the first place.  You also need to have passion and conviction to write exciting reviews.  Please note, that you do not have to follow these guidelines, perfectly, it is just to give you some inspiration, that will improve your own style.    
 
Anyways, here are my initial ideas, and I would like to get some advice on making this format a little more robust.  Expanding on each section would be a primary goal.  Specifically, what do each of these sections need to include?  Are there any sub-sections that need to be injected?  Re-ordering and adding / deleting sections are definitely, open.  
 
If I follow the normal format for technical report writing, the review would look something like this:
 

• Abstract or Overview
  
• Introduction
  
• Body with Headings and Graphics if possible
  
• Tables and Informative Data
  
• Conclusion
  
• Appendices
  
• Sources and Citations
  
• Acknowledgements
  

 
 

---

 
EXPLANATIONS and EXAMPLES

---

Abstract or Overview:  Brief eye catcher, this is what people see before they click on your review.
 
Example:  This is a game that will remain a cherished part of your collection for many years to come!
 

---

 
Introduction:  Put highlights here, including important features, likes, dislikes, and recommendations.  (condensed)
 
Example:  Both the graphics and gameplay are amazing!  The sound is good and the story keeps you on the edge of your seat till the end.  On the other hand, the controls are a bit awkward, but it's really not that noticeable, once you get going.  (add more as you see fit, you really need to make your views of the game shine here).
 
Some things that you should include in the introduction are:
 

• Grab the attention of the reader.
  
• Mention the length of the main story.
  
• Introduce the main characters.
  
• Describe scenes and environments.
  
• A few game basics.
  
• Replay Value.
  

 
These are primers for the main body, which would include the same elements, but in greater detail.
 

---

 
Body with Headings and Graphics if possible:  Use bold headings for the different areas you want to talk about and include some thumbnail graphics, if possible, to accent your presentation. Include numbered citations, where needed.  (Full, Vigorously Detailed Review)
 
The Good:  
Describe the good points of this game. (Summary)
 
The Bad:  
Describe the bad points about this game. (Summary)
 
Example:  Any sub-section suggestions?  (Indent / double indent these)

• Gameplay
  -          Example:
  
• Fun Factor
  -          Example:
  
• Difficulty
   -          Example:
  
• Modes of Play
   -          Example:
  
• Re-playability
  -           Example:
  
• Depth and Length of Game
   -          Example:
  
• Game Controls
   -          Example:
  
• Physics
  -           Example:
  
• Graphics
  -           Example:
  
• Audio
   -          Example:
  *****  Voice Acting
  -----------  Give your thoughts about this aspect
  *****  Creature Sounds
  -----------  Give your thoughts about this aspect
  *****  Atmosphere
  -----------  Give your thoughts about this aspect
  
• Movie Sequences
  -           Example:
  
• Manuals
  -           Example:
   
  More Categories
  *****      More sub-categories
  ----------  Give your thoughts about this aspect
  

---

 
Tables and informative data:  Performance data, and system requirements.  How did the game perform on your system, and specify what components your rig is made up of.  If it is a console release, specify which one.  Multi-platform?
 
(Cite this info with a  number.   Also, include it in the citation section of the review, matching numbers, of course. ²⁾ (normally these would be super / sub script.)
 
Example:  
System requirements ²:  
Win98SE/2000/ME/XP
Pentium III 1Ghz or greater
512mb RAM
DirectX 9 compatible video card with 64mb texture memory
DirectSound compatible audio hardware
 
Include your system specs here (if PC: AMD Athalon XP 2200 +, etc.
Benchmark results with your system here (if PC):
Detail framerates and performance with different quality settings.
Any noticeable graphical or sound anomalies?
 
Or just detail how it runs on your console.
 

---

 
 
Conclusion:  With all that said, post your final say on the game quality.  Is it good? How many entertainment hours are there?  Re-playable?  Is it worth the money, etc.?
 
Example:  In conclusion, I must say that I am very happy with the quality of this game.  Give some reasons, mention value, expected gameplay hours, and any other recommendations, be it negative or positive.
 

---

 
Appendices:  System Specs, minimum and recommended. Any other data not included in the body of the review. (More detailed)
 
Example:  Repeat above and add the "Recommended Specs".  Large scale diagrams and raw data and other specifications.
 

---

 
Sources and Citations:  If you quoted any information, include the sources here.
 
Example:  Use numbered citations with the following format (Of course, you will have to number them in the body of your review, as well):
 
(normally these would be super / sub script.)
¹ http://www.nvidia.com/details.html  
²  http://www.ati.com/  
 
if this is where you got your information.
 

---

 
Acknowledgements:  If anyone helped you with the review, mention them here.
 
Example:  
Bob Shlowmo  ***  Bob performed the benchmark tests that were included in this review.
 
Jill Shlowmo  ***  Jill performed the editing and finalizing of the entire project.
 
Many thanks to both of them!
 

---

 
In conclusion, I am hoping that I can entice some of you kind folks out there to share your experience on the development of these guidelines.  I believe that it will not only help me, but others, to write great reviews for the games they love so much.  Mostly, though, it will help all of the game players out there, that are seeking advice on whether or not a game will be fun for them.
 
Thanks for reading!
 
Hamarabi