A working draft is not the tabled proposal
Teams need room to prepare ideas, compare language and test costing before committing to an exchange. Personal drafts serve that preparation. Reviewed wording versions and immutable packages serve a different purpose: identifying exactly what was approved or exchanged. A shared document name cannot reliably carry all of those meanings.
UnionStack’s bargaining workspace separates these stages and retains issue, proposal and exchange context. Each immutable wording version has one language. Teams must review any translation deliberately; the workflow does not create an automatically paired bilingual legal text.
Retain the exact exchange evidence
Before tabling or recording an exchange, compare the approved wording with the package being used. Keep the counterparty, timing and evidence attached to that exact package. Costing and comparables support negotiation decisions, while restricted meeting links preserve the round’s access boundary.
Ask a reviewer to reconstruct one issue after several drafts and an external offer. They should identify the current reviewed version without relying on a participant’s memory or overwriting previous evidence.
Settlement creates further responsibilities
Settlement and ratification evidence belongs in append-only records. Recording an outcome does not automatically publish or activate the successor agreement. Agreement administration and any approved member update remain explicit next steps with their own authority and audience.
A useful demonstration ends by tracing one issue from draft to exchange, recorded outcome and the remaining publication work. It should make unfinished responsibilities visible instead of presenting a settlement status as the end of the whole process.