For programme and functional offices in defense
Start with what is out of scope and stays out: no operation, no targeting, no weapon system, no classified environment, no personnel action, and no authorization we do not hold. What remains is the unclassified administrative traffic that consumes a staff — and that band is large enough to matter on its own.
A tasker arrives with a suspense. It is assigned, coordinated across three offices that each hold a piece, staffed upward, revised, re-coordinated, and returned — and the elapsed time is dominated by waiting for a coordination that nobody is tracking because tracking it is another tasker.
The suspense is real and external. Somebody upstairs is answerable on a date, so the pressure lands downward as a shorter internal suspense, which lands as a weekend. The staff absorb it because absorbing it is the culture, and nobody measures what the absorption costs because the absorbed work looks like it was done on time.
Rotation empties the memory on a schedule. The officer who knew why a package is structured the way it is leaves in the summer, the relief arrives, and the first three months are spent rebuilding context that was never written down because writing it down was never a tasker.
The record lives in file shares organised by whoever built them, in mailboxes, in a tracker somebody maintains in a spreadsheet, and in a system of record that everyone agrees is authoritative and nobody updates until an inspection is announced. Reconstructing what happened on a package is archaeology.
And the classification boundary makes everything harder in ways an outsider underestimates. A perfectly ordinary administrative question can become unanswerable because the answer sits on the other side of a boundary, so people work around it with partial information and the workaround becomes the process.
An office can say when a package is due and when it went out, and cannot say where the elapsed time actually went — so every attempt to go faster becomes pressure on the people rather than a change to the process.
That is why the response to a late package is almost always a shorter internal suspense. It is the only lever an office has when the process is invisible, and it works by consuming the staff rather than by removing the delay.
So the first act is to make the elapsed time legible, and this needs no authority at all. Decompose a package’s life into working time, coordination wait, review wait, revision, and external dependency. In most offices coordination wait is the largest single component by a distance and has never once been quantified.
From there, the administrative band can be operated: assembling a package to the office’s own format, chasing a coordination that has not returned, reconciling two of the office’s own numbers and reporting the difference, maintaining the record so it does not need reconstructing. Document work with written rules.
What never moves is anything mission, anything classified, anything personnel, and anything that exercises military or command judgement. Those are not efficiency opportunities. An arrangement that quietly took one of them would be a serious problem regardless of how well it performed.
Where the suspense clock is actually spent — measured by elapsed time per package decomposed into work, coordination wait, review wait and revision, against your own baseline.
Coordination that has gone quiet — measured by count and age of outstanding coordinations, which is generally unmeasured and is often the largest delay.
Revision cycles per package — measured by count of substantive revisions before release, sampled the same way before and after.
Continuity across a rotation — measured by whether an incoming officer can reconstruct a package’s history from its record without asking the outgoing one.
Staff hours spent formatting rather than deciding — measured by time-on-task sampling for assembly and formatting work, before and after.
Agreement between the tracker and the system of record — measured by a count of packages where the two disagree, taken without warning rather than before an inspection.
Weekend absorption — measured by work performed outside duty hours to meet an internal suspense, which is the real cost a shorter suspense actually buys.
anything operational, anything classified, any targeting, any weapon or fires system, any personnel action, any command decision, and any authorization. Nothing here operates in a classified environment or claims an accreditation to do so. This is unclassified administrative traffic and the boundary is contractual, written, and checked before anything runs.
Deployment is inside an environment your organisation has already authorized, under your identity provider, your logging and your continuous monitoring. We hold neither a FedRAMP authorization nor a FedRAMP certification and claim no equivalency, so any position requiring one is a position we cannot occupy and we will say so before an acquisition is shaped rather than during evaluation.
It reads the systems the work already lives in — tasker and correspondence tracking, records, sustainment and property data — through documented interfaces. Nothing becomes a second authoritative record, and a second record of a package is how two offices end up briefing different numbers.
The classification boundary is a hard stop rather than a filter. Where an answer would require material on the other side of it, the work stops and says so. It is not approximated from what is available on this side, because an approximation that looks like an answer is worse than no answer in this setting.
Where an interface does not exist, that is reported as a limitation. It is not covered by driving a screen, which produces a fragile process and a record nobody can verify against the system of record.
We hold neither a FedRAMP authorization nor a FedRAMP certification at any impact level, and we claim no equivalency. That closes positions, and closing them early is more useful to a programme office than a hedged answer during source selection.
CMMC is an obligation on contractors handling federal contract information or controlled unclassified information — it is not something an organisation self-certifies, and Level 1 and Level 2 are different requirements for different data. We do not assert a level here. Where a specific engagement would place information in scope, the requirement is established in writing during scoping and the honest answer may be that we do not qualify for that scope.
Federal contract information and controlled unclassified information are also not interchangeable words, and a vendor who uses them as synonyms has told you something about how carefully they will handle either. Which category a given engagement touches is determined before the engagement rather than assumed.
Authority is enumerated in writing before it is exercised, revocable immediately by the official who granted it without a contract action, and every consequential action leaves a record naming actor, authority, time and result. Operational access is not permission to train.
The authorizing official’s question is the boundary, and the answer is that it is theirs: an unclassified environment the organisation already authorized, under its own controls and monitoring. What may happen inside it is a written grant rather than a capability description.
Security will want the data categories in scope stated precisely, and should refuse a scope that cannot state them. If an engagement cannot say whether it touches controlled unclassified information, the scope is not ready to be assessed.
The contracting officer needs the constraint plainly: no authorization held, which closes certain positions completely. That belongs in a market-research conversation, not in a proposal evaluation.
Counsel’s question is what is delegated, and the answer is a short enumerated document with everything mission, classified, personnel and command explicitly outside it.
One recurring unclassified administrative flow — a tasker line, a data call, or a sustainment record reconciliation — observed for one full cycle with no authority to act on anything.
The observation phase produces the decomposition: working time, coordination wait, review wait, revision, external dependency. It grants nothing and touches nothing. In most offices the coordination component is the largest and has never been quantified, which is a finding the office can act on with no vendor at all.
Stopping there is a legitimate outcome and sometimes the right one. A measured coordination wait is an internal fact that belongs to the organisation, and it is frequently more actionable than any capability that could be acquired.
If it continues, the first grant covers one administrative act on one flow, with the mission, classified, personnel and command boundaries written into the scope document before anything runs.
We hold neither a FedRAMP authorization nor a FedRAMP certification at any impact level, and we claim no equivalency. The route that remains is deployment inside an unclassified boundary your organisation has already authorized, where the assurance question in play is yours rather than ours. If your requirement attaches to an external service in the position being proposed, we are not a candidate and you should have that answer before a requirement is written.
Then that has to be established before an engagement rather than discovered inside one, and the honest answer may be that a given scope is not one we should take. What we will not do is treat federal contract information and controlled unclassified information as the same category, or assert a CMMC level in order to keep a conversation alive. Determine the category first; if it closes the scope, it closes the scope.
Nor should they, and nothing here asks them to. The work is read from and written back into the systems of record you already keep, and the observation phase adds no surface at all. If a proposal requires your action officers to maintain a fifth tracker, it has added a tasker rather than removed one, and that is worth refusing.
That is a fair prediction and it should shape the design rather than stop it. The measurement is the durable part: an elapsed-time decomposition and a record that reconstructs a package without asking the officer who built it are exactly what survives a rotation. Everything produced is in your systems and exportable by you, so the relief inherits the record whatever happens to the arrangement that produced it.
It is the right thing to watch, and drift is the reason the boundary is enumerated rather than described. Anything not on the written list is out of scope by default and routes to your staff, including anything that cannot be classified. The grant is revocable immediately by the official who signed it, without a contract action, and the record lets your own inspectors test the boundary directly rather than accept an assurance about it.