Microsoft Project

Reads a Microsoft Project file (saved as XML) and produces a single self-contained HTML report. Stakeholders can read it in any browser — no Project license required. Baseline variance is surfaced front and center, with the worst-drift tasks named at the top, the critical path highlighted, and a predicted-finish vs baseline-finish slip badge.

Runs the DCMA 14-Point Schedule Assessment against a Microsoft Project XML and produces a one-page HTML report — pass/fail per metric, the offending tasks listed inline, plus a consolidated fix list. Built for defense, aerospace, and federal-contract PMs whose customers reject schedules that don't pass the audit; no $thousands-per-seat tool, no cloud upload, no Project license needed on the auditing machine.

Reads every populated baseline (Baseline 0 through Baseline 10) from a Microsoft Project XML and produces a one-page HTML report ranking tasks by cumulative drift across re-baselines. Project's Multiple Baselines Gantt view shows only 3 of 11 by default; this shows all of them, with a worst-offenders callout and a stable-tasks list as the credibility signal. Built for PMs who re-baseline after change orders and need a single-page artifact a steering committee can read.

Reads Microsoft Project assignments and produces a one-page HTML heatmap showing per-resource per-week allocation, with overallocated cells called out in amber and red and underutilized cells in green. The summary table names every overallocated resource, peak %, peak week, and weeks over capacity. Built for staffing leads and program managers who need to know "who is overallocated, by how much, when" without scrolling through Project's Resource Usage grid.

Reads a Microsoft Project XML and produces a single self-contained HTML status report grouped by milestone status (Late, At risk, In progress, Complete, Upcoming), with baseline variance, percent complete, and predecessor count per milestone. Late and at-risk surface first so the broken items lead. A "what slipped this cycle" callout names the worst movers; a stable-milestones section names what's still on the date originally committed. Built for PMs who hand-rebuild this artifact every reporting cycle.

Reads a Microsoft Project XML, resolves your custom-field aliases (Text1 = Vendor, Flag1 = Needs Approval, Number1 = Contract Value), and produces a single self-contained HTML report with an inventory of populated fields, a per-task table using aliased column headers, and cross-tab counts for every Text and Flag field. Project's Report ribbon has no canned "tasks by Vendor" pivot; this one runs it from the XML in seconds.

A local tool that reconciles an MS Project schedule against a Trello board, showing where the official plan and the execution-team board have drifted apart. Three matching strategies (custom-field trelloCardId, exact normalized name, fuzzy Levenshtein) catch the renamed-card-since-MSP-export problem; drift signals span schedule (MSP Finish vs Trello due), status (MSP %Complete vs Trello list tier), and resources. Bundled fixture (27 MSP tasks vs 22 Trello cards) engineers a critical-path task with no Trello card to trigger the RED verdict — the exact case where the execution team forgot to make a card for a load-bearing task.

A local tool that operationalises the MSP↔Trello bridge around a PM's status meeting cycle. Push mode (pre-meeting): take the latest MSP XML and bring Trello cards up to date — create cards for new tasks, update due dates and list positions where MSP has newer values, skip fields the team has touched since the last sync. Pull mode (post-meeting): take the current Trello board and produce a changeset of the MSP updates the PM needs to apply manually — list moves, due-date negotiations, new scope, archived work, plus any BOTH-CHANGED conflicts flagged for deliberate resolution. v1 is demo-only against a bundled before/after fixture pair; v2 will execute live Trello writes for the push direction. The tool NEVER writes to the MSP file — the PM owns the schedule of record.