OneBloc Tasks — the work your team owes each other

A task is one job, one person, one date.

That sounds obvious and it is the whole product. Most task tools let you create work nobody owns and nothing is due — which is how a list becomes a graveyard people stop opening. Tasks won't let you.

One accountable owner

Other people can be on a task and get told about it, but it counts against exactly one person's name. A task owned by four people is a task nobody chases.

Always a deadline

Required, not optional. Undated work is invisible work — it never appears in a “what's late” list because it can never be late.

Tied to the property

A task can name the unit or the whole building. That's what makes “what's outstanding at Setia Sky?” a question with an answer.

How it works, end to end.

Raise it where you noticed it

A tick icon in the PMS opens a two-field form in a new tab, with the unit already attached and your place in the PMS untouched behind it.

It lands on a board

Columns you name yourself. Drag a card to the finish line and it's done — the finish line is a flag you set, not a column called “Done”, so renaming things never breaks the counts.

The owner is told

Email and WhatsApp, once, when it's assigned to them. Not a notification per keystroke.

One message each morning

What of yours is late and what's due tomorrow — a single summary per person. Eleven separate alerts is how somebody mutes the channel, and then the messages that matter stop landing too.

Managers see where it stands

A team dashboard ordered by what's late, and reports over time. Staff see their own work and nothing else.

This is the actual product.

Not mockups — these are screens from a running instance, seeded with the kind of work a property team actually logs.

A OneBloc Tasks board with four columns and task cards — **The board.** Columns you name yourself, with a finish line you set. Each card carries its deadline, the unit it's about, and one owner's face. Drag a card onto a colleague in the hand-over strip and it's theirs — one gesture instead of opening the card and hunting for a field.

Team dashboard showing who is behind and what needs attention — **The team dashboard.** Overdue first, always. Who's behind is sorted by how late they are, and *Needs attention* is the half people actually use — a morning check takes seconds instead of a scroll.

My tasks laid out as personal board columns — **My tasks.** Your own work, in the same columns as the team board — so “where is this up to” reads the same wherever you look.

The recurring tasks page showing a weekly schedule — **Recurring.** The rule in plain English, when it next runs, and how many it has created. SILENT means this one won't message anybody.

Tasks arrive from wherever the work is.

The reason a tracker dies is that logging something is more effort than remembering it. So the job of this half of the product is to make raising a task cost almost nothing.

✓From the PMS. On a unit page, the unit comes with it. It also shows what's already open on that unit, so two people on the same screen don't log it twice.

✓From the ERP. Raise a chase from an invoice and the task carries the document reference, clickable straight back to the ledger.

✓On a rhythm. Every day, every Monday, the 1st of the month — a schedule creates a new task each cycle, so every occurrence keeps its own owner, notes and completion date.

✓By hand, from any board, in about fifteen seconds.

A repeating card that just moves its own due date forward looks tidier and destroys the record. You could never answer “did we actually do the fire-alarm check in March?” — so schedules spawn real tasks instead.

And then it chases itself.

Email and WhatsApp

Staff live on WhatsApp, so that's where an assignment lands. Both channels, one message, and nothing at all until the owner has actually been given something.

Ask what happened last time

Ask an assistant “how did we handle this before?” and it answers from completed tasks at that building — the steps ticked and the notes staff wrote, each linked to a card you can open and check.

Built for a phone

Add it to the home screen and it opens like an app. You stay signed in for 30 days, and you can issue yourself a link for a new phone without asking anyone.

What it looks like on a normal week.

Four situations every property operation has. None of them is a new problem — the difference is only whether the follow-up survives the day it was mentioned.

Guest complaint A guest messages at 9pm: the aircon in Trion 25–08 is dripping. Whoever reads it is not the person who will fix it, and by morning it is one of forty messages.

Raised from the unit's own page in the PMS, so the unit is already attached. Ken gets it on WhatsApp with a deadline. Before he goes, he asks what happened last time — and gets the three previous aircon jobs at that block, with the notes the technician wrote.

Compliance The fire alarm has to be tested every Monday. It gets done for a month, then somebody is on leave, and nobody notices until an inspection asks for the records.

A schedule creates it every Monday with its own owner and its own completion date. Miss three and the schedule stops and reports itself as falling behind, rather than silently stacking copies nobody reads. The record is the answer to the inspection.

Month end Owner statements, the payout run, the SST return — the same list every month, held in one person's head, and everything waits on them.

Each one is a monthly schedule with a real owner. The dashboard shows what is late while there is still time to act, and the month-end list stops being one person's memory.

Money An invoice is past due. Finance knows; operations doesn't. The chase happens if somebody remembers to mention it.

Raised straight from the invoice, carrying its reference — the card shows ERP · INV-2026-0142, clickable back to the ledger. Whoever picks it up can see the document without asking finance for it.

Straight answers.

Do staff need another password?

No. They sign in from the PMS tile they already use, or through OneBloc Connect. Tasks mirrors the staff list — nobody registers themselves, and there is no separate directory to keep in step.

Can everyone see everything?

No. Staff see their own tasks and their team's boards. Managers see their account's dashboard. Someone with all-accounts access sees every operator account. A personal board is reachable only by the person who owns it — not by their manager, not by anyone.

What happens when a recurring task isn't getting done?

It keeps creating them, up to a limit you set, then stops and reports itself as falling behind. Silently stacking thirty copies would just be noise nobody reads; stopping is something a person notices.

Does it need its own server?

It's a normal OneBloc web app against your existing database, deployed like the rest of the suite. Notifications reuse your own mail account and the OneBloc Dispatch WhatsApp sender.

What if we already track this in a spreadsheet?

Then you already know the problem — the sheet is accurate on the day it's written. The difference here is that the task chases the person, rather than a person having to open the sheet to find out.

The work your team owes each other, written down.