BuildFlow Help Guides for the BuildFlow app

The board & tasks

The board is where the work lives. Rows are your stages (Foundation, Structure, Finishing…), columns show how far along each task is, and each card is a task.

Setting up the board

Working with a task

Click a card to open it. There you can:

Tasks show a small reference like luga-07 (from your project code) — handy in meetings and messages.

Site-visit & meeting tasks

When creating a task, you can make it a Site visit or a Meeting instead of a plain task — built for dropping everything from that visit in one go.

Everything about the visit lives in this one block on the card — the pile of files, the invitees, the notes and minutes, and the billing — so there is one place to look and one set of minutes to confirm.

Confirmed minutes are also something FlowBot can be asked about later — like "what did we decide at the last site visit?"

Taking minutes during a meeting

Every meeting and site-visit task has a Minutes pad — a fast place to jot rough notes while the meeting is happening. Don't worry about tidy sentences or sorting anything: type fragments as they come ("client wants teak louvres", "nimal to recheck the beam sizes") and press Enter or tap Add note. Filed a typo? Point at the line to fix or remove it — the time and name stay as they were. Each line files itself with the time and your name, and the ⤢ button gives you a clean full-screen pad for the meeting hour. Colleagues on the task can add their own lines too — nothing gets overwritten.

When the meeting ends, tap Wrap up. BuildFlow reads your notes and lays out who attended, what was decided, and what needs doing. Check it over — everything is editable — then tick the follow-ups you want as real tasks and confirm. The minutes stay on the task for everyone to read, each follow-up becomes a task on the board with the right person on it, and Generate document turns it all into a formatted minutes document whenever you need the formal version.

If you've uploaded notes to the task, Read the uploaded documents adds what they say to the same minutes — useful when a paper arrives after the meeting, or was filed under the wrong heading when you uploaded it. Anything you wrote yourself is kept as you wrote it; only what's new is added.

If something comes up after you've confirmed, Reopen notes lets you add more and wrap up again. And a line you typed but hadn't filed yet survives a lost connection — it's still in the box when you come back.

Recording a meeting

Recording is an early feature, so it's switched off until you ask for it — an admin turns it on under Settings → Experimental features. Taking notes works either way.

Rather than typing everything, you can have BuildFlow record the meeting. Press Record in the Minutes pad and hold your meeting as normal — keep jotting notes if you like, both work together. Press Stop when you're done.

Please tell everyone in the room that you're recording — BuildFlow reminds you the first time, and shows a clear red indicator the whole time it's recording, but telling people is on you.

The recording is filed in the project's Storage tab, where it can be played back, restricted to certain people, or deleted like any other file. In the background BuildFlow writes out what was said; usually within a few minutes — longer for a long meeting — a Transcript section appears under your notes. From then on, Wrap up reads the transcript and your typed notes together — so the things nobody had time to write down still make it into the minutes.

Meetings in Sinhala or Tamil — or the usual mix with English — work the same way. BuildFlow writes the minutes in English, and the transcript keeps both versions: an English tab and an As spoken tab with the original words, so nothing said is lost in translation. (A meeting held in English simply shows the one transcript.)

If the write-up ever fails, nothing is lost: your typed notes are untouched and Wrap up still works from them alone.

Watchers

Watching a task means you get notified about it — a new comment, someone mentioning you, activity moving it forward. It's not the same as being the task's assignee: a watcher isn't responsible for the task and can't approve anything, they're just kept in the loop.

Watching, being assigned, and holding a role in a payment's approval chain are three different things — see assignee vs role vs watcher.

Filtering the board

The board opens on All — every task on this project you're allowed to see. Two controls in the header narrow it down:

Filters only hide cards — nothing is changed or deleted. A filtered column header shows "shown/total" (e.g. 3/7) instead of a plain count.

My Tasks

My Tasks in the sidebar collects everything assigned to you across all projects, grouped by project and stage. Update status right from the list. Only tasks explicitly assigned to you appear here — an unassigned task won't, even on a project you own.

Everything on the board saves as you go — the small "Syncing…" dot in the header shows when BuildFlow is saving. If something can't be saved you'll see a short message and the change is undone. See Instant edits.