Short Answer
A joint workplan can expose shared dates and handoffs. Separate partner plans can retain the detailed tasks, internal approvals and restricted information each organization needs. Often both are useful: align the shared interface without assuming a shared plan grants authority or requires every internal detail to circulate.
Comparison Table
| Question | Joint workplan | Separate partner plans |
|---|---|---|
| Dependencies | Puts cross-organization handoffs together | Shows local prerequisites; another partner may not see them |
| Authority | Names coordination owners, without creating sign-off powers | Can identify the organization's actual delegation and approval steps |
| Local detail | Keep enough to explain the interface | Retain task sequences, staff capacity and internal constraints |
| Revision control | Shared version and acknowledgment make interface changes visible | Each partner checks and changes its own affected plan through its actual route |
| Privacy of internal detail | Share the minimum needed for coordination | Keep sensitive staffing, finance and other restricted detail in approved local records |
These are OpenAid's design choices, not mandatory plan formats or legal conclusions.
Fictional Handoff: Three Days of Slack Lost
HLN and KCT prepare a youth skills fair on day 60. HLN registration closes day 45 and sends final registration numbers to KCT by day 46. KCT's ten-day print lead time makes day 50 the last order day: 60 - 10 = 50. The original handoff leaves 50 - 46 = four days before ordering.
Proposed joint plan v3 moves the close to day 48. The supplied case rule shifts the final-count handoff one calendar day after closing, to day 49. Slack becomes 50 - 49 = one day: three fewer than before. A final-number handoff for printing is an administrative dependency here, not a method for measuring participant results.
HLN's venue booking also needs its director's actual sign-off. Calling HLN the owner in the joint plan supplies no such approval. The coordinators discuss whether v3 is workable within their actual roles; KCT's authorized approver addresses its local plan change. Do not record either decision before evidence exists.
When to Use Each or Both
Use a joint view when one organization's date changes another's work. Keep separate plans when local sequencing, authority or privacy matters. If using both, give the shared interface a version, preserve each partner's current local reference and record acknowledgment of the affected change. An acknowledgment of receipt is not automatically approval.
This comparison concerns plan products, rather than the agreement discussion or a startup meeting record. Neither plan replaces those decisions or settles legal effect.
Boundary and Source Scope
CC34 (March 7, 2024), Tool10's checklist (January 3, 2011), decision guidance (November 2, 2020) and CC26 (September 16, 2026) inform separate organizations, responsibilities, delegation and risk in England and Wales. ACFID5.2.1's undated Australian membership-code guidance supports discussing shared responsibilities; it does not prescribe these plans. All dates and arithmetic are original fiction. Actual agreements and delegations control; checked November 1, 2026.