41.2% gross margin for the year. 33.5% for the quarter. Delivery personnel having that information at their fingertips is what leads to bottoms-up program financial management.

Am I making money on this contract. Are there ways to improve the margin. When do we run out of funding. When are my upcoming recompetes. A P&L answers the first one late and at the wrong grain, and the other three not at all.

So program managers build their own spreadsheets—which is not a failure of discipline but a rational response to a reporting system organized around accounting periods when the work is organized around contracts. The report a PM needs is a different cut of the same data, not a different set of numbers.

What this page counts is what the person running the program knows, and how current it is. It starts at a number that arrives after the close if somebody builds it, and ends at four rolling windows, two years of trend, the cost detail underneath and the same view across every contract—on that person’s own programs, as of any date they pick.

Every question at stop 01 has an implicit when, and the answer changes with it. A program report is therefore computed for a contract set and an as-of date rather than published on the accounting calendar—a portfolio, a division, one contract, a saved group you defined for a customer who spans three of them.

And the date is a control on the screen, not a filter you re-run. A period scrubber moves the as-of backward without leaving the view, so how did this look in March is a drag rather than a request. Every figure at stops 03 to 05 recomputes against the date you land on.

Saved groups belong to the person who made them. A PM’s grouping of contracts is a working artifact, and one person’s view of the portfolio is not another’s to edit. That is enforced rather than conventional.

Month to date, trailing three months, trailing six, trailing twelve—revenue, gross profit and gross margin on each, from posted cost and actual billing rather than from an estimate of how the job is going. 41.2% across the year and 33.5% across the quarter is a contract whose economics moved. One number cannot tell you whether 41.2% is where this contract lives or where it is passing through.

The four windows tell you it moved. Two years of monthly revenue and margin tell you when, and roughly what did it. A labor mix that shifted toward higher-cost categories, a subcontractor added mid-period, an option year that repriced—each has a shape, and each shows up as a month where the revenue bars hold steady and the margin line steps down.

Which is the difference between a report and an instrument. A report tells you the contract ran at 41.2% last year. An instrument tells you it has been running at 33.5% since March—and that is a conversation with a customer, a staffing decision or a repricing request, all three of which are available in March and gone by December.

Underneath the trend sits the JSR—twenty-three cost lines, each against the same four windows, with budget and variance stacked beside the actual wherever budgets exist. The lines that move a gross margin are the direct ones—direct labor, subcontracts, travel and other direct costs. Fringe, overhead and G&A are on the same report and move a different number, which is why the two are never read as one.

So the step in the margin line is attributable rather than mysterious. The same contract that shows 33.5% for the quarter shows which of twenty-three lines moved to produce it, over the same windows, without exporting anything or asking anyone.

Everything to this point is one program. The adjacent tab runs the same figures across all of them—monthly revenue, cost, gross profit and gross margin, contract by contract, against the same as-of date. Trends and outliers are visible in one pass rather than assembled by opening twelve programs in turn.

Which is the view a division lead actually works from. Run over a division, a customer or a saved group from stop 02, the strip is produced for the group and then broken out per contract underneath it—so the division’s gross margin and the question of which contract is carrying it are answered in the same place, at the same grain, from the same ledger.

How long until we would be working at risk. The government has obligated $1,188,150.00 against this contract and $1,045,572.00 has been billed. At $47,526.00 a month that is exactly three months of funded work—against a period of performance with nine months left.

Six months of scheduled work has no money behind it—$285,156.00 of it. On a time-and-materials contract the right to stop attaches to the ceiling, not to what has been obligated, so performance is still owed while the funding catches up. That figure appears on no financial statement: it is not a receivable, because the work is not performed, and not a liability, because the cost is not incurred. It exists entirely in the relationship between two dates.

The gap at stop 06 is not a shortfall in the ordinary sense. The ceiling is $2,400,000.00 and $1,188,150.00 has been obligated against it, leaving $1,211,850.00 unobligated—more than four times the gap. So the conversation is administrative rather than commercial: somebody raises a modification, and modifications take an amount of time that has nothing to do with how obviously correct they are.

When are my recompetes. Nine months is the funding horizon at stop 06 and it is also the recompete horizon—a contract ending in nine months is one whose successor solicitation is likely already being written. Plotting contracts by months of runway against their average monthly revenue over the trailing year is how a portfolio’s real exposure becomes visible: a fifth of next year’s revenue expiring in one quarter is a different business from the same revenue expiring across four. The forecast counts that as its recompete segment; here it is a date on a specific contract with a specific PM’s name against it.

And the options all get worse with time. Chase the modification, slow the burn, or stop at the funded limit and explain why. All three are available at six months’ notice and only the last one is available at three weeks’, which is what makes the date this is discovered matter more than the amount.

Everything from stop 02 onward is scoped, and the ordering is the whole of it. A chief executive sees every program; a division lead or a program manager sees their own. That session is pinned to their division before the query runs—not queried broadly and filtered on the way out.

Those two designs look identical until one of them has a bug. Filtering after the fact means the data was fetched, and every subsequent code path is one mistake away from showing it. Pinning before the read means the rows were never selected, so there is nothing to leak—the same reasoning that makes scope a property of the reader everywhere else in Arcvue.

Which is what makes stops 03 to 05 safe to hand out. Giving twelve program managers their own margin only works if the narrowing is structural, and that is the whole of this stop.

Am I making money and are there ways to improve the margin are answered at stops 03 to 05—at four grains, two years deep, against the JSR lines that produced it, and across every contract at once. When do we run out of funding and when are my recompetes are answered at 06 and 07, off the same as-of date, in the same place. None of the four required anybody to build anything.

Which reverses the usual order. The funding gap was the thing worth opening a report for—quarterly, when somebody remembered—and gross margin was the thing you got at year end. Here margin is what the program manager is already looking at, and the funding answer is sitting in the same view when it matters.

And it ran because the close ran. Revenue and cost come off the ledger, funding off the contract, burn off the timecards—sources a PM would otherwise reconcile by hand, monthly, in a spreadsheet nobody else can open. Arcvue produced it from the close event, and nobody had to remember.