Skip to content

Contribution Onboarding Packet

Onboarding document — instantiates Net-Additive Contribution Intake

The written working agreement handed to an accepted contributor — scope, ownership, support, credit, and exit terms — so the relationship runs on stated expectations rather than assumed ones.

An accepted contribution is the start of a relationship, and relationships fail on the expectations no one wrote down: what the contributor may touch, who supports them, what they get credited for, and how it ends. Contribution Onboarding Packet is the artifact that makes those terms explicit before work begins. It is handed to a newly accepted contributor and states, in one place, the scope and standards of the work, the access limits, the support and communication cadence they can rely on, how their contribution is credited, and — crucially — how the arrangement is maintained and gracefully wound down. Its defining purpose is to convert an implicit, assumed bargain into a stated one, protecting the contributor from exploitation and the system from a contributor who understood the deal differently. It governs the how of an accepted contribution, not the whether — the accept decision is already made when the packet is issued.

Example

An academic journal recruits a new volunteer peer reviewer. Enthusiasm is high and the terms are entirely unstated — the classic setup for a reviewer who is over-assigned, ghosted by the editors, and never told how their work is used. The onboarding packet forestalls all of it. It states the scope (which subject areas, roughly how many reviews per year), the standards (the rubric, the turnaround window, the tone expected), the access limits (manuscripts are confidential, not to be shared or used), the support (a named handling editor, a response-time promise), the credit (annual public recognition; reviewer credits on record), and the exit terms (how to pause, decline an assignment, or step down without burning the relationship).

The result is a reviewer who knows exactly what they signed up for and a journal that can rely on it. When the reviewer's availability drops a year later, the exit terms are already written — they step down cleanly, with thanks, instead of silently vanishing mid-assignment and leaving papers stranded. The packet is what turned goodwill into a durable, fair working relationship.

How it works

  • State the working terms up front. Scope, standards, access limits, and support cadence are written and shared before the first contribution, so both sides operate from the same document instead of divergent assumptions.
  • Name ownership and the handoff. The packet fixes who owns the contribution, who the contributor's point of contact is, and how work is handed over — so nothing depends on a single unrecorded understanding.
  • Make the exit routine. How to pause, hand back, or leave is specified while the relationship is healthy, so winding down later is a documented step rather than an awkward improvisation or a silent disappearance.
  • Guard dignity explicitly. Credit, fair workload, privacy, and non-exploitation are stated as terms the system owes the contributor, not favors it may grant.

Tuning parameters

  • Formality — a one-page welcome versus a signed agreement. Heavier packets set clearer expectations and travel better under dispute, but can feel bureaucratic to a small-stakes volunteer and deter casual help.
  • Scope tightness — how narrowly the work is bounded. Tight scope prevents mission creep and over-ask; too tight wastes a capable contributor and reads as distrust.
  • Credit generosity — how visibly the contribution is recognized. Generous credit builds a durable contributor base but can create expectations the system must keep honoring.
  • Exit-term prominence — how plainly the graceful-exit path is stated. Foregrounding it lowers the cost of leaving (and so of joining); burying it produces contributors who ghost rather than resign.

When it helps, and when it misleads

Its strength is that it makes the psychological contract[1] explicit — the unwritten mutual expectations that otherwise surface only when they're broken. It protects a contributor from being quietly over-asked or uncredited, and protects the system from a contributor operating on terms it never agreed to. Stated exit terms in particular convert the most relationship-damaging moment — someone leaving — into a routine, dignified step.

It misleads when the document becomes a shield instead of an agreement: a packet written to extract maximum contribution while minimizing the system's obligations is exploitation with better paperwork, and contributors read that quickly. It can also over-formalize a light, generous relationship into something transactional, deterring exactly the casual help it meant to welcome. And a packet is only as good as its practice — promised support and credit that never materialize damage trust more than silence would. The discipline that keeps it honest is to write the packet as a genuine two-way agreement, weighted toward what the system owes the contributor, and to hold the system to the support and credit it states.

How it implements the components

Contribution Onboarding Packet realizes the working-agreement components of the archetype — the terms an accepted contribution runs under:

  • ownership_and_handoff_rule — states who owns the contribution, who supports the contributor, and how work is handed over, so the arrangement doesn't rest on an unrecorded understanding.
  • maintenance_and_exit_obligation — documents how the contribution is kept up and how the relationship is paused or ended, making a clean, graceful exit a written default.
  • contributor_dignity_and_non_exploitation_guardrail — sets credit, fair workload, privacy, and non-exploitation as stated terms the system owes the contributor.

It does not decide whether to accept the contribution (Contribution Net-Value Review), secure the named owner and budget behind the acceptance (Sponsor-Required Acceptance Protocol), or test an uncertain contribution before committing (Bounded Contribution Pilot).

References

[1] The psychological contract is the set of unwritten, mutual expectations each party believes governs a working relationship — obligations neither side stated but both assume. Its breaches are felt as broken promises even when nothing formal was violated. An onboarding packet works by moving as much of that contract as possible from assumed to written, so the expectations can be met on purpose instead of discovered in the breach. ↩