I like that players have defined the standard of what NAPs should be, but I'd like to work some of that into the game itself to rid ourselves of the delays involved with back-and-forth messaging regarding NAP terms.  Life would be much easier if we didn't have to chase down unresponsive or forgetful leaders.

What I envision is an extension of the current relations page nap controls.  Rather than being a simple dropdown of families with a dropdown of duration, I see a more clear process that allows families the ability to draft terms and core-lists amongst themselves and allies before actually sending any offer over.  It would provide more explicit control over what exactly families want to offer.  Less room for miscommunication and mistakes.

Bear with me here, because this would be a big change over the current ingame naps.

Scenario 1: Family to Family NAP proposal (Simple)

At the beginning of the round, family A decides on their core.  A's leader is able to save this list of systems in-game, outside of just the map.  He can name it what he wants so he calls it "Family A's Core". (this feature doesn't yet exist).

A's leader decides he is interested in proposing a NAP to family Z.  He goes to the new NAP proposal page and is presented with the following:

[BEGIN DRAFT A NAP PROPOSAL PAGE]
What is the length of the proposed NAP? (24) (48) (72) (Permanent)
He chooses 48.

What, if any, systems are proposed as restricted for your family? [dropdown of system lists, with "none" as the default]
He clicks the dropdown menu and chooses "Family A's Core".  This has no actual in-game effect, it is purely informational.

Will system intrusion violations require compensation for clearing? (Yes) (No)
He clicks "no", meaning he wants a NAP in which if Z gets into A's core, they can be cleared without A having "trade" them out.

Any additional notes? [large text field]

Does this NAP involve any allies? (Family B) (none)
He chooses "none".

For which family is this offer intended? [dropdown of non-allied and non-NAPped families]
He chooses Family Z.

Submit Button: Send this proposal to Family Z.
This saves this particular draft with a NAP ID, and sends it over to Family Z's leader.  Family Z's leader gets a notification similar to NEW MESSAGES.
[END DRAFT A NAP PROPOSAL PAGE]

Z's leader get's the notification and clicks on a link that would take him to a similar page, where he has more control than just "accept" or "decline":

[BEGIN RESPOND TO NAP PROPOSAL PAGE]
Family A has proposed the following NAP with your family:

Length: 48 weeks (change)

System intrusion violations will NOT require compensation for clearing. (change)

Family A restricted systems: [link to system list, which would allow Family Z to see the actual systems proposed]

Additional notes: [whatever notes A's leader wrote in]

What, if any, systems are proposed as restricted for your family? [dropdown of system lists, with "none" as the default]
He clicks the dropdown menu and chooses "Family Z's Core"

Any additional notes? [large text field]

Submit Button: Return draft to Family A.
This modifies the original NAP and sends it back to A's leader.  There is no signing happening yet, as they are just proposing cores at this point.  This is the only option if anything has been added or changed.

OR

Submit Button: No changes, sign NAP.
If for some reason Z's leader didn't want any cores he could just sign and accept.  Obviously nobody would really do this, but the ability is important for the next step.  This is the only option if nothing has been added or changed.
[END RESPOND TO NAP PROPOSAL PAGE]

Now, modifications can continue back and forth if the two families keep tweaking the terms.  At some point though, one family will say "ok cool" and confirm whatever the latest terms are.  When that happens they are simply signing the latest terms agreed upon, making the NAP official.

So let's say Family A is fine with Z's cores and is ready to go.  He gets a page that is exactly the same above, but *this* is where it makes sense to say "No changes, sign NAP."

With all that done, the NAP is signed and there is a NAP ID that can be referenced by any member involved from either family.  This would be linked to from the current relations page, instead of just the "break the pact" link.

As a bonus, the systems involved in this agreement could also now show up within the new map.  Family A would see something like "Fam Z NAP cores" in their map-system list.  This would allow them to more easily reference any systems they might want to avoid as per the agreement.

I have a much more in depth process that extends this for alliance NAPs (Scenario 2), but I will hold off on that for now.  What are your guys thoughts on the above?  It takes much longer to explain that it would actually take to use.  It's actually incredibly easy in my mind, but I'd like to hear if anybody sees any potential problems.