Roomcord / Auto-board
A live project board, built from the conversation.
Your team discusses the work in its project room. We’re building Roomcord’s auto-board to turn that context into suggested cards with an owner, a date and a source. People confirm the agreement, then the same board carries it through approval, commitment and follow-up.
What is an auto-board?
An auto-board is a project board assembled from the work a team already discusses: messages, meeting transcripts and shared files. Roomcord’s developing auto-board proposes structured cards instead of leaving every next step buried in a summary. It is designed for project teams that repeatedly reconstruct agreements after meetings or manually copy action items into a tracker.
The board connects five kinds of work. A suggestion is not an accepted assignment, an approval is not a delivery commitment, and a risk is not proof that something has failed.
Five card types, one shared picture
| Card type | Question it answers | Illustrative item |
|---|---|---|
| Decision | What must we settle? | Choose the launch scope after the test review. |
| Approval | Whose permission is needed, by when? | Approve the launch recommendation by Monday noon. |
| Task | What action does one person own? | Claire prepares the test summary by Friday. |
| Milestone | What checkpoint must be reached? | Complete the launch readiness review on Monday. |
| Risk | What could affect the plan? | An unresolved test could change the launch date. |
Each card is intended to carry a type, title, one owner, due date, status, source link and change history. Approval cards also identify the approver. If the source does not establish an owner or date, that field stays unconfirmed and the room agent asks for clarification.
How the board stays connected to the work
- Read the room’s sources. Extract a possible decision or next step from a message, shared file or meeting moment. Keep the supporting quote and source location.
- Suggest a card. Show the proposed type, owner and date. Missing or ambiguous details remain visible for review.
- Confirm the agreement. A person reviews the suggestion and the owner accepts the responsibility and date. Nobody receives an accepted commitment silently.
- Route the next step. Send a decision needing authorization to an approval ballot. Once agreed, ask its action owner for a written commitment and first step.
- Update the same record. Follow-up, changed dates and completion evidence return to the board. The owner confirms completion against the agreed work, rather than treating a generated recap as proof of delivery.
The intended review process flags possible duplicate cards and conflicting owners or dates. People resolve those conflicts against the sources. Manual edits and requests such as “move the launch to November 14” retain who changed what and when; a changed date does not erase the earlier agreement.
Worked example: from a message to a confirmed card
Illustrative scenario, not a customer result or a screenshot of released functionality.
Room message, October 22: “Claire, please prepare the launch test summary by Friday, October 23. We’ll use it for Monday’s scope decision.”
Follow-up: Claire replies, “I can prepare it by Friday. My first step is to check the outstanding test.”
| Field | Proposed record | After owner review |
|---|---|---|
| Type | Task | Task |
| Title | Prepare launch test summary | Prepare launch test summary |
| Owner | Claire, suggested | Claire, accepted |
| Due | October 23, 2026, suggested | October 23, 2026, accepted |
| Source | Room message and Claire’s reply | Both sources remain attached |
| Status | Suggested | Accepted commitment |
| First step | Unconfirmed | Check the outstanding test |
No test result is attached yet, so the board must not report that the launch is ready. The summary can inform a separate scope ballot with a recommendation, named approver and deadline. Protected financial, legal or people decisions still require their designated approval. After acceptance, reminders track the commitment. Completion requires the delivered summary and its owner’s confirmation; the later scope decision keeps its own record.
Where auto-board fits in Roomcord
Auto-board is the structured starting point of Roomcord’s decision engine. Approval ballots resolve the choices. Commit and chase connects accepted work to reminders and escalation. The decision ledger retains the reasoning and changes after a decision closes.
Explore the Roomcord product overview for the complete loop. Bewize Hub and Wize Browser are supporting components; the room and its shared board remain the place where the team sees the agreement.
Availability as of October 21, 2026
Rooms, room chat, shared files and meeting capture form the existing Roomcord foundation. Auto-board extraction, duplicate and conflict review, attributed card editing, ballots and automated commitment follow-up describe the decision engine we are developing. This page announces the intended experience, not general availability of every step or integration. Linked-email intake is also part of the direction; supported sources and access must be confirmed for your first room.Start with one recurring decision
Bring one recurring project meeting and a representative set of messages or notes. Identify the five card types you actually need, agree how owners confirm dates, and choose what counts as completion evidence. Review proposed cards against the originals before relying on the board. For the first review cycle, count incorrect owners or dates, duplicate cards and missing sources. Use those corrections to judge whether the board reduces manual copying without creating more review work.