> ## Documentation Index
> Fetch the complete documentation index at: https://reconco.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://reconco.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://reconco.manicule.dev/api/mcp.
> Every agent surface: https://reconco.manicule.dev/.well-known/llms-manifest.json

# Collaboration and Team Workflows (/documentation/using-reconco/collaboration-and-team-workflows)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 902 · updated: 2026-11-22 -->
Related: [Team Documentation Use Cases](/documentation/using-reconco/team-documentation-use-cases.md), [Evaluating Reconco](/documentation/using-reconco/evaluating-reconco.md)

Assess Reconco against a documentation change your team actually needs to make. Define who is responsible for that change, then test whether the web app supports the handoffs your team requires. The collaboration capabilities discussed below are checks to perform, not confirmed Reconco features.

## Define ownership and contributions

Give each document an accountable owner who can judge whether it is still accurate. Decide who contributes changes and who checks them before readers rely on the result. These are team responsibilities, not Reconco permission roles.

For example, consider a document explaining a service your team maintains. A developer changing the service could draft the documentation update, while another developer checks that the instructions match the new behavior. The document owner remains responsible for resolving questions and making sure the update reaches readers.

Before testing that arrangement, decide whether contributors should be able to change a document directly or must submit changes for review. Then confirm whether Reconco's access controls can support the distinction your team needs. Do not assume that separate responsibilities imply separate product permissions.

If you have not selected a representative document, use [team documentation use cases](/team-documentation-use-cases) to choose one.

## Check how changes are reviewed

Test the required handoff in the web app with the people who would perform it. For the service document, have the contributor propose a change and the reviewer check it. Establish how the reviewer would request a correction and how the team would know the change is ready for readers.

Confirm the capabilities that affect that handoff:

* If contributors may edit at the same time, test what happens when their changes overlap and whether either person's work can be lost.
* If review discussion must stay beside the document, check whether comments are available and whether the team can tell which feedback remains unresolved.
* If mistakes must be reversible, check whether revision history exists and whether an earlier version can be restored.
* If approval must happen before a change reaches readers, check whether Reconco can enforce that requirement. An agreement to ask for review does not establish an enforced approval step.

Record any process that must happen outside Reconco. A manual handoff may meet your needs when review is informal; it does not meet a requirement for product-enforced approval. Judge the result against the requirement you set before the test.

## Plan how documents stay current

Connect documentation maintenance to changes in the product or service it describes. In the service example, the document owner should be involved when a behavior change affects the instructions. Make updating the document, or confirming that no update is needed, part of completing that change.

Also decide when the owner will check documents that have not recently changed. Use those checks to identify outdated instructions, and assign a new owner when responsibility for the service moves to another team. A named owner is useful only if that person knows which documents they maintain and what should trigger a check.

Choose how your team will track those checks without assuming Reconco provides reminders, notifications, or integrations. If your process depends on any of those capabilities, confirm it in the web app before committing to the process.

Carry the required handoffs, confirmed capabilities, and remaining manual work into your [overall Reconco evaluation](/evaluating-reconco).
