What the document is for
A partnership document has two jobs, and they pull in different directions. It records what was agreed, so that people who were not in the room can act on it. And it settles in advance what happens when things go wrong, so that a disagreement has a route out that is not litigation or resentment.
The first job rewards clarity and brevity. The second rewards thoroughness about unpleasant possibilities. Documents that do only the first read well and fail under pressure; documents that do only the second are unreadable by the people who have to operate them. The usual answer is a short operative agreement with the detailed working arrangements in schedules that can be updated without renegotiating the whole thing.
Scope
Scope is the description of the overlap: what the parties are doing together, and by implication everything they are not. It is the most commonly under-specified part of a partnership document and the source of the largest share of later argument.
Good scope is written in the language of activity rather than intention. "The parties will collaborate in the industrial sector" is not scope. "Party A will supply units of the specified type, Party B will install and support them for buyers in the named territory" is. Where the arrangement is expected to grow, scope is often written narrowly with a named process for extending it, which is far safer than writing it broadly and hoping restraint prevails.
Exclusivity
Exclusivity is a promise not to do the same thing with somebody else. It is valuable, it is frequently asked for early, and it is the term most likely to be granted too widely.
Where it appears, it is normally bounded on four axes at once: territory, market segment or customer type, product line, and time. It is also frequently made conditional on performance, so that a party which asked to be the only route into a market keeps that position only while it is actually delivering volume. An unconditional, unbounded exclusivity is the term most likely to be regretted, because it removes the producer's options precisely when the relationship stops working.
Arrangements between parties who might otherwise compete also sit within competition law, which differs by jurisdiction and is not a matter for general description. This is one of several reasons why partnership documents are drafted with proper professional input rather than from a template.
Money
The money clauses answer four questions: who pays whom, on what basis, when, and what happens if the basis stops making sense. Margin, commission, fee, contribution and share of results are all just answers to the second question.
Two provisions do a lot of quiet work. One is a definition of the amount the percentage applies to, precise enough that neither party can reasonably compute a different figure — the arguments here are almost always about what is deducted before the split. The other is a review mechanism: a stated occasion on which the commercial terms are looked at again. Without one, a rate that made sense at signature persists for years past its usefulness and becomes a grievance.
Ownership of what is made jointly
If the parties will produce something together — software, a design, research, a body of material, a customer list — the document needs to say who owns it and what the other party may do with it afterwards. This is separate from, and more important than, who owns the things each party brought in.
Common patterns are: each party keeps what it brought and licenses it for the purpose of the arrangement; jointly created work is owned by one party with a lasting licence to the other; or jointly created work is jointly owned, which sounds fair and is the hardest to administer. What matters is that a decision exists in writing, because the question only ever gets asked at the end, when the parties have stopped agreeing.
Term and exit
Term says how long it runs and whether it renews on its own. Exit says how it stops. Most documents cover ending for a breach; fewer cover ending because a party simply no longer wants to continue, which is the far more common reason.
The provisions that reduce damage are practical ones: adequate notice, sized to how long it would take the other party to arrange an alternative; what happens to work already in progress and to customers already served; how long licences survive; what each side may say publicly about the ending. These do not make an ending pleasant, but they make it survivable, and knowing that makes both parties readier to commit while it lasts.
Where this leads
A document is a record of an agreement, not a mechanism for running one. The mechanism is governance.