Tablero

Right now, one of your jobs is waiting on someone.

For each job: what’s holding it up, who follows up, and when to check again. Overdue comes first.

Your email goes only to Jose, the founder, who replies to each one. It isn’t kept anywhere else.

The waiting-on board: six open waits grouped Overdue, Today, This week and Later. The revised layout approval at Westside Offices has waited eight days on Dana Brooks, and Maya follows up.
  1. Overdue comes first
  2. What’s holding it up
  3. Who follows up
  4. When to check again
Two overdue rows up close. The revised layout approval at Westside Offices has waited eight days on Dana Brooks for a customer decision; Maya follows up, and it was due Oct 20. The roof-access window at Riverside Clinic has waited five days on Riverside Facilities for site access; Sam follows up, and it was due Oct 21.

Any update?

When a job stalls, you find out where it stands by asking. Knowing a job exists is different from knowing what it’s waiting on: a part, a customer’s decision, access to the site, another trade.

Nobody writes down who you’re waiting on or when to check again, so the customer gets a vague answer and you ask again tomorrow.

48% of rework came down to poor project data and miscommunication.

PlanGrid and FMI, 2018: a survey of 599 US construction leaders.

How it works

Bring in your open jobs from the spreadsheet you already keep. The file is checked before anything goes in.

Nothing changes until you accept it

An update is a report until you decide it belongs on the board, and the original note stays one tap from what came of it. When a supplier calls you with a new date, you add the update yourself and say who told you.

A wait opened from the board: the roof-access window at Riverside Clinic, overdue since Oct 21, with a photo of the rooftop unit and the technician’s note above Sam Ortiz, who follows up next by calling facilities to confirm access.

Friday’s brief writes itself

It’s built from what you accepted: each job, what it’s waiting on, and who checks when. Uncheck what shouldn’t go, then copy it or open it as an email.

The weekly brief for Northgate Mechanical, Oct 19 to 25: six open waits across six jobs, nothing resolved this week, each job with what it’s waiting on and who checks when.

A day on the board

Real screens, with sample jobs. Click what’s marked to go on.

Six open waits, two overdue. Four updates are waiting for a decision: open Review.

The waiting-on board: six open waits grouped Overdue, Today, This week and Later; Review in the sidebar carries the four updates waiting for a decision.

Alex sent a photo and a note from Northpoint Laboratory at 9:14. Review it.

The review queue: four updates need a decision and five progress notes wait to be filed. Alex’s, sent at 9:14 from the AHU motor replacement at Northpoint Laboratory, says the supplier has the bracket ready and needs a PO number, with a photo.

The note suggests the wait it belongs to. Nothing changes until you accept it.

The review panel for Alex’s update: the photo, the note, and the suggested change: update the existing wait Mounting bracket, with the title, category, who follows up and the next action filled in. Accept is the one button.

Accepted. The wait carries the photo and the note, and Maya checks today. Now open Weekly brief.Close it; Weekly brief is in the menu.

The board with the bracket’s wait open, now titled PO number for bracket release: waiting on Central Supply, the photo, Alex’s note, and Maya, who sends the PO number to the supplier today.

Friday’s brief, built from what you accepted. Copy it.

The weekly brief for Northgate Mechanical, Oct 19 to 25: six open waits across six jobs, nothing resolved this week, each job with what it is waiting on and who checks when, with Copy and Email draft above it.

Copied. You send it yourself, to whoever asked.

The brief after Copy: a message reads “Copied. Read it before you send it.”

Straight answers

Can my techs use it on their phones?

Not yet. Today it’s for you, the manager. Which phones your crew carries decides what comes next.

Does it use AI?

No. Nothing on the board changes unless you accept it.

Does it connect to the software we already use?

No. It takes your open jobs from a spreadsheet export and runs next to the tools you already pay for.

Can my customers see it?

Not on their own. You copy the brief, or one job’s update, and send it yourself.

Count first, then decide

The pilot is two weeks of counting. For the first, before you use anything, tally every “any update?” text or call you send. Then we put your open jobs on the board, and you count again for a week while you use it. If the number doesn’t go down, it isn’t worth your money, and I’d rather know that than sell it to you.

JoseFounder

Join the waitlist