Is this table designed properly
Either way could be correct.  

Choose 1 table if you want to make it difficult to change the number of reviews possible.  It may be counter-intuitive to want to make something difficult, but if it would actually be a bad idea to make it 1:n, then building in some pain to make the change has some logic.

But, you almost certainly want to go with two tables for long term flexibility.  If it was me, I'd put a trigger on there to enforce the 'one review per methodology statement' rule.  If that changes, just modify or drop the trigger.

One question to keep in mind, though:  if you go to multiple reviews, how would you resolve status codes that conflict?  For instance, what if you had one code 4 and one code 5 for the same methodology statement?

UPDATE:

...or you can do the much better thing and use a unique constraint as @Max Vernon suggests.