How do you keep track of several construction projects at once?

Why do you lose oversight as projects pile up?

Oversight is lost when the latest agreement is known only to the person who had the conversation. On project A, a new delivery date comes in by phone. On B, the subcontractor is waiting for a drawing. On C, someone reports by email that the client has not yet decided. In a general task list, these look like three outstanding items. For the operations manager, they are three different decisions.

Collecting more messages only helps if the consequences are clear. Do not record every conversation again in a separate management report. Make the outcome easy to find within the relevant project and state what needs to happen now. The project manager remains responsible for an up-to-date picture of the project; a colleague must be able to understand it during their absence.

Ten projects mainly require a shared meaning of status. Agree when something counts as ‘blocked’, who must confirm a decision and when information is checked again. A project with no reported problems is not automatically a project without problems. It may also mean nobody has updated the latest position.

Headcount is an indication, rather than a firm software boundary. In a business with 1–10 people, one manager may know a great deal personally, but a shared installation team already requires coordination. With 10–100 people, handovers between project managers and site operations become more important. With 100+ people, reporting by business unit may be added, for example. Choose the workflow based on simultaneous projects, shared capacity and the parties involved. See also the broader guide to project management in construction.

What information should a project manager be able to see for each project?

A useful project overview answers three questions: where are we, what is holding us back and who takes the next step? Start with a small set of information that every project team can maintain.

This is a proposed working agreement, rather than a list of guaranteed fields in a particular app. Keep a formal drawing, cost estimate or programme in its designated system. Refer from the agreement to the right source and check that the recipient has access.

The following fictional example shows why a colour alone says too little. Project names, deadlines and situations are illustrative.

Here, the refurbishment does not receive a reassuring green label based on old information. ‘Unknown’ is a separate state requiring a checking action. Keep the date and source close to the status.

How do you gain oversight without rereading every conversation?

Use a brief summary as an entry point to the underlying agreement. A good summary states what is confirmed, what remains outstanding and which follow-up action is needed. It also retains conditions: ‘installation on Monday if the drawing is approved on Friday’ is a different agreement from ‘installation on Monday’.

For supported recorded conversations, Wouby AI creates a summary and automatically turns identified agreements into tasks with people responsible. Check the important outcomes: the right project, action, owner, date and any condition. A created task does not prove that an external party has received or accepted the instruction. Read more in turning agreements into project tasks.

A practical checking pattern is to read the summary, review outstanding decisions and return to the source only if something is unclear or involves an important commitment. This avoids everyone having to review everything again. Continue checking amounts, quantities and changes affecting site operations carefully.

One phone call about three projects

Wouby AI identifies the projects mentioned and automatically links specific tasks to the right project. You can find these actions within each project and in the overall task overview. You therefore do not need to redistribute all the action items across three lists after every conversation.

There is still one call report. Easy sharing of sections of a report with other projects is still in development; do not present it as automatic splitting that is already available. For an important agreement, check the assigned project context and avoid unnecessarily sharing the full conversation with everyone.

How do you prevent external action items becoming invisible?

Distinguish between the person who needs to do something and the person waiting for the answer. For example, the supplier confirms the delivery date, while your construction project coordinator ensures the confirmation comes in. A task assigned only to the supplier does not give the coordinator an overview of their own outstanding enquiries.

Check four things for an external agreement: the right contact, the content of the question, receipt and the agreed response. Also make clear who follows up internally if no answer arrives. A sent message is not substantive approval; an internal tick is not confirmation from the construction partner.

Invited external participants use Woub tasks, their project chats and the accessible Wouby AI workflow free of charge within the contractor’s paid environment. This lets the subcontractor carrying out the work participate directly in follow-up. Project and chat permissions remain decisive: this does not grant unrestricted access to all tasks at other businesses.

When team membership changes, follow-up must transfer too. Give the replacement the outstanding question, contact, latest confirmation and next step. Transferring the entire chat history is insufficient if nobody knows what still awaits an answer.

How do you handle deadlines and project priorities?

Prioritise by consequence and the time a decision is needed. An action date and a decision date differ. If a team must start on Monday, missing approval may already be more urgent on Thursday than an administrative task due on Friday.

Use this sequence in regular project meetings as a practical aid:

1. Handle immediate safety and construction problems through the agreed people responsible and procedures; do not wait for the next overview.

2. Discuss blockers affecting a confirmed milestone. Record which decision is needed and who can make it.

3. Review conflicts between projects: the same people, plant or delivery.

4. Check actions and answers whose agreed deadlines are approaching or overdue.

5. Update missing or outdated project information and plan other actions.

This sequence is our process advice, rather than a general contractual rule. A task labelled urgent does not automatically take priority over every other project. The planner needs to know what flexibility the programme allows; the project manager knows the consequences for their project. Decide together and inform the teams involved of the changed agreement.

When postponing something, record what changes, who confirms it and when it will be reviewed. Simply moving the date hides the cause. Closing a task because someone has sent a message can give an equally misleading picture if no answer has arrived.

A task date is not yet an agreed action date

If no action date is known for a task created by Wouby AI, Woub sets it to today. That brings the action to people’s attention. It does not mean every task can be carried out today or that a supplier must deliver today. When prioritising, check whether the date is agreed, an internal decision date or this default date.

Learning weekly from recurring blockers

With Wouby AI Pro, you receive a weekly management report on costs arising from errors and rework and on waste, with advice to improve processes and the use of Woub. Discuss, for example, why materials are repeatedly arranged too late. Turn the improvement into a task and include the check in the project template. This uses learning across projects to reduce repetition, alongside formal cost recording in ERP. Read more in systematically reducing costs arising from errors and rework.

What is the difference between project oversight and the overall programme?

Project oversight shows which projects need attention and which agreements or decisions remain outstanding. The overall programme allocates activities, people and plant over time. Financial project information also comes from the agreed accounting system. None of these overviews is automatically made complete by the other two.

Woub’s current knowledge base describes, under Project overview, both a Kanban board and a list view, with filters and saved views. The knowledge base states that this add-on is free to install. A phase column you configure yourself still depends on correct input. It does not prove automatically calculated progress or visibility of every task at external businesses.

Woub also documents a general scheduling add-on for employees and resources. It would therefore be incorrect to say Woub has no scheduling at all. Woub remains complementary to specialist construction scheduling, ERP, BIM, estimating and DMS. The right setup depends on the functions required and the existing workflow.

A specific specialist example: the documentation for Asta Powerproject describes handling over-allocation across a programme of projects. The time intervals chosen matter: enough hours across a whole week does not mean one team is available in two places on Monday. An extra task label alone will not resolve that conflict.

For an integration, establish which data travels in which direction, who may make changes and how errors are detected. Being able to transfer a project number does not mean capacity, costs and all tasks are also updated in both directions. Read the further considerations in Woub alongside construction scheduling.

Informing several projects at once without losing context

If different teams need the same announcement, Woub lets you send one message to selected project chats through a bulk action. The knowledge base describes choosing the relevant chat for each project. The announcement therefore arrives within each separate project context. Check the selection: not every project needs the same internal information.

You can also add a replacement to several existing chats through a bulk action. They see the available history there by default. Then discuss specifically which outstanding decisions and tasks they are taking over. Making history available and handing over responsibility are two different steps.

Why do minutes and separate email tasks not yet provide an up-to-date project overview?

A full record of a construction meeting describes what was discussed at that time. Current follow-up may subsequently change. A supplier replies later, a decision is revised or someone else takes over the action. If those outcomes remain in separate emails, the project manager must repeatedly reconstruct the current position.

Link a meeting item to a clearly identified action within the project. Keep the minutes as context, but update follow-up in the agreed place. Record the response, remaining decision and who takes the next step. This avoids the next meeting having to establish again which agreement from the previous minutes remains outstanding.

An illustrative example: the minutes state that the construction project coordinator will request a delivery date. The supplier replies by email that delivery is possible provided the order is confirmed before Thursday. Simply ticking off ‘request delivery date’ hides the new condition. Also record who confirms the order and when that is needed.

For the overall picture, make these exceptions particularly visible: answer received but decision still outstanding, deadline changed, responsibility handed over or site operations still blocked. The minutes do not need to become a second programme or accounting system for this. The value lies in connecting what was discussed with what still needs to happen now.

How do you set up a pilot across several projects?

Start with two or three live projects at different phases or with different team compositions. For example, choose one project involving extensive external coordination and one with shared capacity. Use the same core information, but do not force an identical checklist where the work differs substantially.

Document beforehand what you want to assess. Ask a colleague who was not in the latest conversation to look up the current agreement, find the source and explain the next action. Have an external participant receive and answer a question. Also test a changed agreement, an unclear owner and handover during absences.

Measure what actually happens: which information is missing, how many extra actions are needed and where do participants revert to other channels? Record the starting position and what you find during the trial. Establish any time savings through measurement; do not infer a fixed saving from a successful demonstration.

Agree who checks the project picture, when, and which information the planner or administration team needs. A simple setup that employees maintain is more useful than an extensive overview whose status nobody owns. Expand after the agreed trial shows that handover, access and currency of information work.

Want to assess this with your own projects? Explore Woub for the project manager or try Woub free for 14 days. For the chosen setup, check the current availability and conditions of the add-ons and AI functions required.