Employee Portal — what was builtDelivery inventory · in scope vs beyond the agreement · as of

Everything built for the TJFACT Employee Portal — in scope, and beyond it.

Every capability on the live portal, classified against Section 1 of the Master Agreement & Statement of Work (v1.0, August 2026) and the specification it cites — TJFACT Intranet Department Wireframes, Operational Workflow with Home Page (12 Aug 2026). In scope means named in that Section or that specification. Beyond scope means asked for afterwards (the department requirement documents of 28 Aug–5 Sep, the Monday.com boards, the TAG/MPP workbook, the 18 Sep, 28 Sep and 1 Oct feedback rounds) or added on Paint Your Heaven's initiative. Status is the honest state today, including what waits on TJFACT.

By department

Count of delivered capabilities, in scope (agreement / specification) and beyond scope. Click a bar to open that department in the inventory — where the larger items carry an itemised “What that involved” breakdown of what was actually built, part by part.
In scopeBeyond scope

Where the depth is

The largest deliverables, with the count of parts broken out under each. Open one to read what it actually involved, or click through to the item.

How to read the statuses

Every item carries one of these; none of them means "almost".
Live — working on the live portal today, verified by the automated suites.
Live · needs TJFACT input — working; a Checklist value, file or mailbox from TJFACT completes it.
Built · blocked on TJFACT — built end to end; cannot run until TJFACT (or its vendor) provides access.
Partial — part delivered; the remainder is named.
Answered — a question answered in words; no build was the right answer.

Where the build deviates from the agreement's wording — stated plainly

Same outcomes, different mechanics; TJFACT saw and used each of these as they were built.
Substrate. The agreement describes SharePoint pages, Microsoft Lists, Power Automate flows and Power BI embeds inside the Microsoft 365 tenant. The portal is a dedicated application with Microsoft 365 as its identity (Entra sign-in, enforced), document (SharePoint/OneDrive), calendar and mail backbone; trackers, automations and dashboards are native to the portal, exportable and role-gated. Documents never leave SharePoint/OneDrive.
Costpoint. The read-only bridge is complete and runs on its report route today (Finance’s Costpoint exports on OneDrive, every figure dated); the GET-only REST route is built and tested against a stand-in Costpoint and switches on when Deltek issues the read-only service account (Client dependency in §1). Nothing in the portal can write to Costpoint.
GovWin. Built both ways, so the decision is TJFACT’s to make on price rather than on capability. Replacing it is done: the BD Suite runs the same market research in house on live public data — SAM.gov, USASpending and FPDS — with no seat licences. Using it is done too: every tracked opportunity has a full, editable record on the BD page, filled by importing a GovWin export, with no outward links. Refreshing those records automatically needs Deltek’s Web Services API, a separate paid add-on that is not switched on; the client for it is built and tested.
Power BI. The five dashboards are native views computed live; no Power BI workspace was provided or needed.
Controlled information. By TJFACT's 18 Sep instruction, CUI/CMMC material never enters the portal; a gate enforces it on every read and Dash flags it. Two Deployment Operations boards stay held for that reason.

Prepared by Paint Your Heaven LLC for TJFACT LLC · live portal at tjfact.paintyourheaven.com/prototype · agreement at /agreement. Counts on this page are computed from the inventory below; portal figures (pages, modules, lists, routes, forms, AI tools) are read from the deployed build. Nothing here carries credentials, personal data or controlled information.