Deliverables and contributions

A deliverable is an output being produced. A contribution is a submission made against one. All workspace activity is organised around this pair.

A workspace: deliverables, contributions, files and its own wikiOpen /w/ in the app

×

File uploads require connected storage. A workspace without a Google Drive connection displays a notice, and deliverables cannot accept file attachments until storage is configured in the workspace’s settings. Contributions can still be submitted as text or a link, so an unconnected workspace remains usable for everything except files.

A deliverable is an output, not a task

“Module 3: Conflict Resolution” is a deliverable; “Write section 3” is not. The submit-and-review pipeline handles completed outputs, which is why it contains no sub-task concept. Work breakdown below this level belongs in the partner’s own tooling.

Adding deliverables

Deliverables can be created manually, edited, and reordered. The order determines how partners read the work, so it should be set deliberately rather than left in creation order.

Two further routes are available:

Suggested from the workspace’s origin. A workspace created from an opportunity, a project or a connection can propose the deliverables that follow from it.

Suggested from an uploaded document. Supplying the funder’s call or a partner agreement produces the deliverables that document implies.

Both produce suggestions for acceptance or rejection rather than a finished plan.

The six states

Draft → in progress → in review → approved → done → published.

The board displays five as columns — draft, in progress, in review, approved, published. A List view is available alongside the Kanban.

Three of the states are readily conflated and have distinct meanings:

Approved	The reviewer’s verdict on the work
Done	Work on the item is complete
Published	The item has left the workspace

A deliverable may remain approved and unpublished for an extended period; this is not an error state.

Contribution outcomes

A contribution is submitted as a file, text, or a link. A link is a valid submission, so work held in another system does not need to be re-uploaded.

Outcome	Means
Accepted	Taken as it is
Revision requested	Sent back with changes
Needs discussion	Neither acceptance nor rejection; requires discussion first
(submitted)	Awaiting review

Needs discussion is frequently overlooked. It exists to avoid a specific outcome: rejecting a contribution that required only clarification, which tends to disengage the partner. It allows a reviewer to avoid choosing between accepting uncertain work and returning it.

Deleting a contribution is permanent and restricted to coordinators. Deliverables are archived and can be restored; submitted contributions cannot.

WorkspacesWorkspaces