Plutio is not connected yet Everything below is sample data shaped exactly like a real Plutio pull. PLUTIO_API_KEY is not set on the organisation, so there is nothing to sync from. The panel at the bottom of this page is the wiring, and it is short.
18
Open tasks
Across six people. Done and archived tasks are never fetched.
2
Overdue
Both sit on the Snapshot pipeline, and both have a named owner.
6
Due this week
Counted in Asia/Manila, which is the only clock that matters here.
3
Blocked on a person
Not one of them is blocked on engineering.

The board

Sorted by priority, then by what is closest to slipping.

One list, one order, no personal interpretation of what matters this week. Priority comes from Plutio, so the ranking is argued once on the board rather than five times in five heads.

Open tasks

Last sync: never · key not set
TaskProjectOwnerPriorityStatusDue
Capture the three screenshots for PetcuraChrome Incognito, from Davao Visibility Snapshots Chiarah Gulle P1 Urgent In progress 1 day late
Rewrite the two headlines that failed the vocabulary scanKanto Kape Roasters deck Visibility Snapshots Lois Alberio P1 Urgent Blocked 1 day late
Sign the SSS, PhilHealth and Pag-IBIG rate tablesReleases the payroll gate Payroll Angela Sabejon P1 Urgent Awaiting signature Due today
Set the Anthropic key and the monthly spend capReleases the Snapshot gate Portal build Patrick Panuncillon P1 Urgent Not started Due today
Send the Sunrise Dental deck for internal reviewTagum City query set needs a second read Visibility Snapshots Lois Alberio P2 High In progress Wed 12 Aug
Confirm the SMS rate line before the MACE kick-offPinned at ₱2.00 per segment Proposals Patmae Cubos P2 High In review Thu 13 Aug
GHL specialist, second interviewBuilder, CSM and sales in one seat Recruitment Angela Sabejon P2 High Scheduled Fri 14 Aug
Restore the brand typeface on the live sitepublic/fonts is empty, so the site falls back to Arial Website Patrick Panuncillon P2 High Not started Fri 14 Aug
Reconcile one parallel payroll period to the pesoSpreadsheet against portal, before anyone is paid from it Payroll Patmae Cubos P3 Normal Not started Fri 21 Aug
Refresh the Sales Exec Study Deck for the current catalogSlide 14 pricing must match the service catalog Enablement Richie Cubos P3 Normal Not started Sat 22 Aug

The portal reads. Plutio owns the task · Priority is set once, on the board, not per person · Overdue is computed in Asia/Manila

Blocked

Three things are waiting, and each one is waiting on a person.

A block with no name attached is not a block, it is a wish. Every row here resolves when one named person does one thing.

  • Kanto Kape deck, rules scan failed twice Two headlines carry banned vocabulary. The scan is doing its job, the deck cannot ship until the copy changes. Waiting on Lois.
  • Payroll run 2026-08-A cannot lock The statutory rate tables are empty on purpose and the run refuses to lock without them. Waiting on Angela to sign, and Patrick to countersign.
  • Petcura captures Google will not serve a Davao local pack to a datacenter. Somebody in the city has to open Incognito and take three screenshots. Waiting on Chiarah.

Load by person

PersonOpenLate
Lois Alberio51
Patrick Panuncillon40
Angela Sabejon30
Patmae Cubos30
Chiarah Gulle21
Richie Cubos10

A Plutio assignee with no matching roster row shows as unassigned rather than being guessed at by name.

Integration

How Plutio gets here, and what it is not allowed to do.

Two systems holding the same task is how a team ends up arguing about which screen is right. Plutio owns the task. This portal owns nothing about it and only ever shows a cached copy.

The pull

  1. A read-scoped key, held as a secretThe Plutio API key lives as a Wrangler secret. It is never in the repository, never in a config file, and never sent to the browser.
  2. A scheduled Worker polls, not the portalCloudflare Pages cannot run cron, so the same standalone Worker that handles period rollovers pulls the board every ten minutes and writes rows to D1.
  3. The portal only reads its own cacheWhich means Plutio having a slow morning never becomes the dashboard having a slow morning, and a failed sync shows as a stale timestamp rather than an empty screen.
  4. Nothing is written backNo status change, no comment, no reassignment. If somebody wants to move a task, they move it in Plutio. One source of truth, held deliberately.
  5. Failure is visible, not silentIf the key is missing or the pull errors, the header says so in plain words. A board that is quietly four days old is worse than a board that admits it.

Field mapping

Title
Task, rendered as written. No truncation, no cleverness.
Project
Project column, and the client tag where one exists.
Assignee
Owner, matched to the roster by email address only.
Priority
Urgent and high map to P1 and P2. Everything else is P3.
Due date
Due, rendered in Asia/Manila regardless of who is looking.
Status
Status. Completed and archived tasks are not fetched at all.
Retention
Open tasks only, refreshed on every pull. The portal is a mirror, not an archive.

If the key cannot be scoped read only

Then the fallback is a Make or n8n bridge posting task changes to a signed portal endpoint. Same cache, same table, different courier. The rule that the portal never writes back does not change either way.

Why priority lives in Plutio and not here The team already works a board. Putting a second priority field in the portal would create a daily question about which one is real, and that question has no good answer. This screen exists so nobody has to open Plutio to know what is on fire, not so anybody can re-rank the week from a second place.
Fourth Ground Consulting · Internal Operations Portal · Presentation-only demo, August 2026
Staging Environment Fourth Ground Consulting