> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/lams/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/lams/tools/doku.md).

# Doc Collaboration (doKu)

### <img src="/files/-MUvE03t3Tiu5bFsjGcb" alt="" data-size="original"> Intro

**doKu is a real-time collaborative document editor** in LAMS that allows students to work together simultaneously on a shared document. As students type, edit, and contribute content, all team members can see changes happening live, creating a highly interactive and collaborative learning experience.

Unlike traditional assignment tools where students work individually and submit separate files, doKu enables learners to **co-create knowledge together**, discuss ideas through writing, and collaboratively shape responses, reports, plans, or case analyses in real time.

One of the most powerful aspects of doKu is that it allows you to **see the full history of the collaborative process**, from the very first word typed through to the final submitted document. This provides valuable insight into how students think, collaborate, negotiate ideas, contribute to group work, and develop their understanding over time.

Doku also supports **rich content creation**, allowing students to create:

* **Tables**
* **Embedded images**
* **PDFs and uploaded files**
* **Embedded web resources**
* **Formatted collaborative reports and assignments**

### Why would you use doKu as an educational activity?

You can use doKu for a **wide range of collaborative learning activities**, including:

* **Collaborative assignments**
* **Case study responses**
* **Group reports**
* **Research planning**
* **Problem-solving exercises**
* **Clinical reasoning activities**
* **Brainstorming sessions**
* **Collaborative note-taking**
* **Project planning**
* **Policy drafting**
* **Reflection activities**
* **Peer review exercises**
* **Group revision summaries**
* **Knowledge synthesis activities**
* **Application Exercises in TBL**

For example, **in a medical education** setting, you could provide students with a patient case and ask teams to collaboratively develop:

* **A differential diagnosis**
* **A treatment plan**
* **A patient management strategy**
* **A reflective clinical summary**

**In business education**, teams could collaboratively produce:

* **A market analysis**
* **A CSR evaluation**
* **A strategic proposal**
* **A risk assessment document**

### Insight into Students' learning and collaboration

doKu is particularly valuable because it **makes the learning process visible, not just the final answer**.&#x20;

You can observe:

* Who contributed
* When they contributed
* How ideas evolved
* How teams negotiated meaning
* Which students led or supported the discussion
* Where misconceptions or confusion emerged

**This gives you an exceptional level of insight into student collaboration and learning behaviour.**

{% hint style="success" %}
**Educational Insight**

Allowing teachers to see how collaborative assignments were created, from the first letter that was typed until the moment the assigned was submitted, gives an incredible insight to the students collaboration and learning process
{% endhint %}

### What can I use doKu for?

Assignments, case responses, collaborative writing, brainstorming sessions, general text based collaboration, planning, etc.

doKu supports a wide range of pedagogical approaches, including:

* **Team-Based Learning (TBL)**
* **Problem-Based Learning (PBL)**&#x20;
* **Case-Based Learning**
* **Process Oriented Guided Inquiry Learning (POGIL)**
* **Jigsaw activities**
* **Just-in-Time Teaching**
* **Collaborative writing and peer learning approaches**

### How does it work? <a href="#how-does-it-work" id="how-does-it-work"></a>

You create a doKu activity and provide students with:

* **Instructions**
* **A scenario or case**
* **Questions or prompts**
* Optionally, a **document base/template** to guide their response

Students then work collaboratively within the shared document environment.

If the activity uses groups or teams, students collaborate together within their assigned team document. Multiple students can edit the document at the same time, with updates appearing live for everyone in the group.

Optionally:

* You can assign a **team leader/scribe** who edits on behalf of the group
* You can **allow teams to review and evaluate each other’s work** through a Gallery Walk
* You can **monitor each team’s progress live while they work**
* You can **intervene in real time** when guidance or clarification is needed

After students complete their work, they submit the document for review.

One of the most valuable features is the document history and playback functionality, which allows you to:

* **View the full editing history**
* See who **contributed specific content**
* **Understand how the document evolved over time**
* **Analyse student collaboration patterns**
* Review the **learning and reasoning process**, not just the final submission

Because doKu supports rich formatting and embedded content, **students can collaboratively create sophisticated and engaging outputs**.

### <i class="fa-brain-circuit" style="color:$primary;">:brain-circuit:</i> AI Features&#x20;

#### Learning Outcomes Alignment

doKu includes AI-powered Learning Outcomes Alignment analysis.

This feature **compares each team’s doKu document against the learning objectives** you define for the activity and provides a real-time overview of how closely the teams’ work aligns with those objectives.

For each learning objective, teams receive an **alignment score from 0 to 5**:

* 0 = Response is significantly off track
* 5 = Strong alignment with the learning outcome

This allows you to:

* **Identify groups that may need clarification or redirection**
* **Provide timely intervention while students are still working**
* **Monitor conceptual understanding across teams**
* **Support instructional decision-making during live activities**

The automated scores and feedback are indicative only and are designed to support, not replace, academic judgement.

#### Concepts Analysis

The Concepts Analysis feature uses AI to analyse all team doKu submissions and identify:

* Frequently repeated concepts
* Dominant themes
* Shared patterns of thinking
* Missing or underdeveloped ideas

This gives you a rapid overview of:

* **Strong conceptual convergence across groups**
* **Misconceptions or gaps in understanding**
* **Themes suitable for whole-class discussion**
* **Areas requiring further clarification**

This is particularly valuable during live facilitation, as it helps you quickly understand what students collectively understand and where additional teaching may be required.

#### AI Personas

doKu also supports AI Personas to create authentic learning experience where students can interact with AI characters that you create to&#x20;

You can create AI-driven personas or characters for students to interact with during the activity. These personas can simulate:

* **Patients**
* **Clients**
* **Stakeholders**
* **Historical figures**
* **Business representatives**
* **Subject matter experts**

This allows you to create highly interactive and immersive learning experiences where students collaboratively engage with simulated scenarios while documenting and discussing their responses inside doKu.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lamsfoundation.org/lams/tools/doku.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.