Skip to main content

Truth Engine: keep your project records in sync

Keep the task tool your team already uses, and see when its status no longer matches the plan Pocket PMO is computing.

Topics this page coversproject data reconciliationJira Asana sync driftTruth Engine project managementproject status reportingsingle source of truth project managementstatus drift

The Monday status deck problem

Every PM running several projects knows the ritual. Status is due, so the deck gets rebuilt: colors are reconsidered, summaries are rewritten from memory, and the task tool everyone actually worked in all week gets consulted second, if at all. The result is status theater, a color-coded opinion that looks like reporting and costs a morning per project per week.

The failure is structural. The task tool holds the facts, the deck holds the story, and nothing compares the two. Pocket PMO's Truth Engine exists to make that comparison automatic, so status becomes something you read off a sync instead of something you compile before every meeting.

What the Truth Engine compares

Each item from a connected source is compared against the local override, the position of record Pocket PMO holds for that item. The comparison runs on the fields where a discrepancy actually matters: status, due date, and assignee. Items where you have set no position are not compared, because an override that does not speak about a field cannot drift on it.

The output is the drift audit: one row per item showing the tool's value beside yours, so the question "is the board telling the same story as the plan" gets answered by reading. A drifted-item count sits above the list, alignment is a computed percentage, and when every tracked item matches, the screen says so with a badge instead of a vibe.

Pocket PMO Truth Engine drift audit comparing external task tool status and due dates against the recorded plan position.
The drift audit: each row shows the external tool value beside the recorded plan position.

Connect the tools without moving anyone

The team keeps its task manager. You paste a link to the board, sheet, or project (Jira, Asana, Monday.com, and Smartsheet are supported), add an API token, and the sync pulls items through the official API. Projects can also arrive as a CSV: download the template, fill in ProjectName, StartDate, and DueDate, and upload. A demo mode loads sample remote state, so you can watch the drift mechanics work before pointing the engine at anything real.

The pre-meeting sweep

Four stat cards answer the questions a status meeting usually settles by argument: how many sources are connected, how many items are tracked, how many have drifted, and what percentage of the picture is aligned. Under them, each item renders as a comparison row, tool value against plan value, with the drift fields called out.

Sync problems surface in the same place. A failed source shows its error on the integration card with a retry, the header shows whether you are working online or offline, and a refresh pulls every connected source on demand. Before the meeting, this sweep is the whole preparation: read the drift count, work the drifted rows, done.

Changes that need your attention

Raw drift is noise until someone ranks it, and the Assurance Inbox is where that happens. Each sync is observed for substantive changes: a status regression out of Done and a move into Blocked are flagged as high severity findings. A bulk signature, the same field changing identically across many items at once, is called out as a possible bulk edit or mapping change and summarized as one investigation instead of forty separate alarms.

The second rule is staleness. An active item with no substantive update and no owner review for long enough becomes a finding, and the threshold tightens when the due date is within a week. Findings can be suppressed with a reason and a review-by date, or escalated into a Resolution Room case with an owner and a response deadline, so "we noticed" turns into "we assigned it".

Pocket PMO Assurance Inbox flagging a high-severity status regression and a bulk edit pattern across multiple external items.
The Assurance Inbox ranking a status regression and a suspected bulk edit as findings.

Evidence quality, stated plainly

Comparisons are only as good as their inputs, so each connection carries an explicit evidence state: current (with coverage unverified), stale once an observation ages past a day, partial when a sync was truncated by pagination, failed when the fetch errored, and unknown before the first observation. Findings and reports inherit those states rather than laundering them into confidence. The whole engine runs in shadow mode: it observes, compares, and reports, and it says so. When schedule impact cannot be assessed because a linked work package has no duration or dependency data in the model, the finding states the gap instead of inventing an impact. An assurance tool that is vague about its own certainty is in the wrong business.

Pocket PMO Truth Engine connection cards showing evidence quality states: current, stale, and failed with a retry action.
Connection cards carrying their evidence states: current, stale, and failed with a retry.

From drift to schedule impact

A slipped due date on an isolated to-do is trivia. The same slip on a linked work package is schedule information. The Inbox proposes links between external records and WBS work packages by name similarity, and nothing connects until a person confirms the match with their name on it. Once linked, a date movement on the external record is assessed against the schedule model, and an over-capacity assignee raises a resource warning.

This is where the Truth Engine stops being a comparison table and starts feeding the plan: external evidence, human-confirmed mappings, computed consequences.

One comparison, everywhere it is read

The same drift comparison implementation serves the Truth Engine screen, the integration service, and the weekly status report, so the screen and the report cannot disagree about the same evidence. The weekly report pulls drift counts and blocked items straight from the engine, which is what replaces the Monday rebuild: the narrative is drafted from recorded positions and computed comparisons instead of reconstructed from memory.

Every override is a record too. The status you set as the position of record lives in the project, and the weekly report reads those same positions. Status reporting becomes an audit of differences instead of a composition exercise.

Computed, not compiled

Progress you can audit, not a color-coded opinion: that is the whole pitch. The plan Pocket PMO computes (estimates, durations, forecasts) stays in one record, the task tool stays the execution surface it already is, and the Truth Engine stands between them reporting the differences. Nobody re-types the board, and the deck stops being the product. It is an alpha preview and behaves like one: shadow mode, nothing sends automatically, and evidence states that admit what they do not know. Those are the right defaults for a tool whose entire value is being believed.

A connected workflow, not another isolated file

Pocket PMO keeps project management techniques close to the rest of the project record so decisions can be based on consistent data.

  • Connect Jira, Asana, Monday.com, Smartsheet, or a CSV export
  • Compare remote item status with the Pocket PMO project record
  • See which items have drifted before the status meeting

How teams use it

  1. Step 1

    Open a project and connect a board, sheet, or CSV export.

  2. Step 2

    Sync the remote items into the Truth Engine.

  3. Step 3

    Review drift and alignment before you report status.

Frequently asked questions

What is the Truth Engine?

The Truth Engine connects an external task source (Jira, Asana, Monday.com, Smartsheet, or CSV) to a Pocket PMO project and shows where that source no longer matches the local project record. It is a comparison and assurance layer: it reads, computes drift, and reports differences, and it does not rewrite your task tool.

Does the Truth Engine replace Jira or Asana, or write back to them?

Neither. Your task tool stays the execution surface and Pocket PMO stays a planning and forecasting layer. The engine reads items through each tool's official API and compares them with the plan of record; where the two disagree, resolution happens in your process, either by fixing the board or by recording an explicit local override in Pocket PMO.

Where are my API tokens stored?

In your browser, encrypted, and never displayed in plain text after you close the connection dialog. You can update or remove a token later from Settings, and removing an integration stops the sync for that source. Pocket PMO is a single-tenant application: Jira and Smartsheet requests pass through Pocket PMO's server-side integration proxy (your token still lives only in your browser and is forwarded per request), while Asana and Monday.com connect directly from your browser — so there is no shared server copy of your task data.

What happens when a source goes stale or a sync fails?

The connection card shows the error with a retry button, and the source's evidence state changes: stale after a day without a fresh observation, failed on an error, partial when results were truncated by pagination. Findings and weekly reports carry those states, so stale evidence reads as stale instead of masquerading as current.

Can I try the Truth Engine without connecting anything?

Yes. Demo mode loads a sample remote state with seeded drift so you can see the comparison rows, findings, and alignment stats immediately. For a lightweight real-world start, import projects from a CSV (ProjectName, StartDate, and DueDate are the required fields) and grow into live integrations when you are ready.

What is the difference between drift and a material change?

Drift is the standing difference between a tool item and your recorded position right now. A material change is an event: something substantive (status, dates, assignee, progress, blockers) moved between one sync and the next, which is what the Assurance Inbox flags. Drift tells you the two stories disagree; a material change tells you where to look at what just happened.

See it in Pocket PMO

Pocket PMO keeps project management techniques close to the rest of the project record so decisions can be based on consistent data.