[JerrodM]

My partner and I find it difficult to keep track of the latest version of our ever-changing system. I have no experience with Google Docs, but think it might work. I envision a structure something like this:

Current Agreements Folder. Overview plus individual files/folders for each opening bid (etc), each flagged with the latest date. Includes a master file tracking changes.

Proposals folder. Discussions of ideas not yet dismissed or accepted.

Rejected ideas folder. Ideas considered and rejected.

Any suggestions would be appreciated. Thanks in advance.

[hrothgar]

I recall that folks used to say good things about the following


http://www.hcs-usa.com/sysnotes.htm

[helene_t]

I think I would prefer to have suggestions and the actual agreements in the same document. You can use "suggest edits" which you or your partner can accept or reject.

For vague thoughts which you don't yet have a suggested wording for, you can use comments.

[shyams]

At the risk of suggesting a useless software, there is an app called Obsidian notes which a close family member uses (for an entirely different thing). I was told that it has a good indexing and cross-referencing feature.

You may want to check it, if you wish to do so.

Note: I have never used the software. My recommendation is based on what I heard from my kin.

[mycroft]

This is the kind of thing that I've always thought mind-map software would be useful for, if you're the type to visualize that way. I haven't got down to it myself after several tries, but I'm investigating Obsidian these days to see if it works for "throw a bunch of ideas at the wall, link them together as they will, then pull it all out sequentially."

Like any development project, revision control (and versioning, if you are comfortable with that) is critical. Branches can be made for "suggestions", and they don't have to be pruned if they are rejected, so you can see it. But being able to point to "it used to be <this>, but we agreed in december that it's now <that>" is very helpful, as is "well, we looked at this idea, but it didn't fit for <reason>, so it was shelved."

[edit: heh, snap]