Woub vs email: how do you keep project agreements, tasks and conversations together?

Why do agreements disappear into personal inboxes?

The problem is usually not that an email cannot be found. It is that the full answer becomes scattered across several people and communication channels. One colleague has the supplier's email, another received a phone call, and only the site manager has the latest photo. Nobody automatically sees the whole sequence.

Putting everyone in CC helps distribute the same email, but does not make clear who acts. Once someone answers by phone, the visible email exchange stops while the agreement continues changing. A read message is not a completed action either.

Practical example: the owner becomes the relay

At Heldoorn Restauraties & Gevelwerken, project details arrived through WhatsApp, email and phone calls. Frederik Heldoorn then collected documents and photos into his folder structure in the evenings and at weekends. He subsequently had to share the information himself. In the customer story, he describes how the team accesses project information independently with Woub and records photos directly within the project.

The lesson: a carefully maintained office archive can still depend on one person. For site teams, information needs to be available within the work, even when the owner is travelling or absent. This is Heldoorn's described experience, rather than measured time savings for every business.

A colour change that did not reach production

Also, Beentjes Hekwerk & Toegangstechniek describes fragmentation between calls, email and WhatsApp. A colour changed by phone was not passed on centrally, so a gate was delivered in the old colour. The business now uses an internal team chat and an external client chat for each project, among other things.

This shows why a better mailbox alone is not the whole solution: agreements arising outside the mailbox also need to reach the right colleagues. Read more about that broader problem in fragmented project communication.

What is the difference between email and a project environment?

Email organises communication around senders, recipients and email exchanges. Woub organises daily coordination around the construction project, with several chats, tasks and shared context. The project manager therefore needs to collect and forward information from separate conversations less often.

The comparison below concerns ordinary email and mailbox functions. Outlook with additional Microsoft apps or other work platforms may support more; those extensions are different from the mailbox itself.

Why is Woub better suited to quick ad-hoc communication?

A driver is outside a locked gate, an installer lacks a dimension, or the site manager wants to know whether work can start. Such questions need brief coordination with the right people. In a Woub project chat, you ask within the relevant work, respond in the same chat, and the answer remains available to other participants. You do not need to compose a new email or forward an answer again.

An emoji reaction to the message lets you briefly show you have seen it. For example, agree that 👀 means ‘seen, I will look at it’. A user's acknowledgement is different from automatically measured read status: the emoji is a deliberate response. And ‘seen’ does not yet mean ‘carried out’ or ‘change approved’. Turn a necessary follow-up action into a task so that it remains visible after the quick conversation.

That makes Woub suitable for brief questions and answers between office and site. It makes a quick response easier; how quickly someone actually responds also depends on availability and working agreements. Email can also be fast, and some email apps support reactions, but project chat keeps this brief coordination within the shared project context.

Project overview and collaboration

Microsoft describes how a shared Outlook mailbox lets people receive and answer email together. That is useful for a general contact address, for example. Woub focuses on collaboration around the project, including conversations, actions and handovers between office and site.

How do you share actions after a site meeting?

With Woub, you do not first need to turn a recorded meeting into an email and then retype all agreements in a separate action list. For supported recorded conversations, Wouby AI creates a conversation record with a summary and tasks. The right people are automatically assigned to the recognised tasks.

From meeting to actionable follow-up

De Woub documentation lists uploads up to 1 GB per file, in a February 2021 update. Email limits are service-specific: see Gmail attachments Outlook.com attachments and Yahoo Mail attachments. A cloud link is not an ordinary email attachment. Woub's upload limit also does not mean a 1 GB file can be delivered to an external mailbox through the chat-to-email route.

Illustrative example: a supplier can deliver the window frames on Friday, provided the unloading area is accessible. The site manager checks access; the construction project coordinator then asks for final confirmation. In Woub, the discussion and follow-up remain within the project. The possible delivery is not yet a definitive delivery.

Check important names, conditions, quantities and decisions in the summary. You can listen back to the audio. Wouby AI takes over recording, but an automatically created task does not prove a supplier or client has already approved a change.

Also see recording agreements from construction conversations and the explanation of calling with Woub.

Who sees outstanding tasks?

In Woub, tasks sit within the project and can be found in the overall task overview. Follow-up therefore goes beyond who received the last email. The person responsible sees what they need to pick up; the project manager can track outstanding work within the available permissions.

No deadline agreed? The task is dated today

Wouby AI automatically assigns recognised tasks to the right person. If no work date is known, Woub dates the task today. That suits quick daily coordination. The date means the task needs attention; it is not an automatically agreed delivery date or contractual deadline.

If one conversation covers different projects, there remains one conversation record. Wouby AI recognises the projects mentioned and links specific tasks to the right project. The work can therefore be found by project.

With ordinary email, the same follow-up needs extra actions: flagging, creating a task, assigning it or entering it in a shared action list. A well-configured Microsoft environment can support this. The difference is the built-in connection with daily project communication in Woub. See Woub's task functionality.

At completion, make the result clear: ‘confirmation requested’ is different from ‘delivery confirmed’. The next colleague then knows whether they can continue.

How do you separate internal and external communication?

Create separate chats within the Woub project for the groups involved. For example, internal discussion of costs and staffing, a site chat with subcontractors, and a client chat for progress and questions. Coordination stays within the same project while each chat has its own participants.

That is also the practical setup Beentjes describes in its customer story. The value lies in the right information for the right people, rather than adding everyone everywhere. Check participants before sharing internal data. New participants see the available history of chats they are added to by default.

External participants join free, including tasks and Wouby AI

Invited external participants use Woub free within the contractor's paid environment. Within their project permissions and that environment's capabilities, they can also work with project tasks and Wouby AI. They do not need to take out their own paid Woub subscription for this.

That is a different level of collaboration from simply emailing minutes to an external participant: they can take part in follow-up within the project environment. For someone who only needs to answer an individual question, there is also the email route without an account.

How does chatting through email without a Woub account work?

An external party can receive Woub chat messages by email and answer them without first creating an account. The response returns to the project chat. A supplier therefore does not need to change their own email approach immediately to communicate with the project team.

The Woub guide Chats naar mail describes this approach:

1. Add the external party's email address to the right chat.

2. The recipient receives an invitation; creating a free account is optional.

3. Chat messages are bundled and sent by email, including attachments.

4. A reply to that email appears as a message in the same project chat.

The guide of 6 January 2025 mentions bundling messages from the past fifteen minutes. Do not therefore treat this route as immediate delivery of every individual chat message. For urgent coordination, make direct contact.

Two ways to involve external participants

This does not import the entire external mailbox. Other separate email exchanges are not automatically collected through it. Nor has it been confirmed that every incoming email reply automatically becomes an AI task. You can record a necessary follow-up action from the chat message.

Use a chat with an external email recipient for communication intended for them: shared attachments may also be sent by email. Later access changes do not retrieve email already delivered.

When is email still needed?

Email remains useful for contact with parties outside the daily project team, correspondence and confirmations under the agreed procedure. Woub does not replace your business email address. It brings daily project coordination and follow-up together, making them less dependent on personal inboxes and forwarding.

Record the outcome where the site team works

An order confirmation may arrive by email and remain in the agreed administration. Make sure the site team can find the current delivery date, conditions and person responsible in Woub. Refer to the source when the exact confirmation is needed. You do not need to copy every email exchange twice for this.

Woub remains complementary to ERP, BIM, DMS, estimating and specialist scheduling. A conversation about a drawing does not automatically change the approved document version. Nor does a delivery agreement automatically update the programme or order. Specific integrations are subject to the capabilities of the integration concerned.

Start with one complete project workflow

Choose all daily coordination about delivery and site work on one project, for example. Have the office, site manager and relevant external party work together in it. Use project chat for questions and feedback, and tasks for actions. Keep formal correspondence where agreed.

Assess three things: can someone covering find the current agreement, does every action owner know what remains outstanding, and does the owner need to forward less information? These are more useful criteria than just the number of emails sent.

Try Woub free for 14 days with one project and view the subscriptions and capabilities.