The Architect of the Capitol's Office of Inspector General has substantiated a complaint that a senior AOC manager used government contract personnel to write the application for a promotion, according to an investigation summary the watchdog issued Monday, July 13, 2026.
The case, numbered 2026-0001-INVI-P, carries no recommendations and no questioned costs. It is a short document with an outsized message for anyone holding a services contract on Capitol Hill: the OIG treated the misuse of contractor labor as an ethics violation and a contract violation at the same time, and it reconstructed the whole episode from e-mail, Teams chats, and shared Word documents.
Background
According to the summary, a complainant reported to the OIG that a GS-15 senior manager at the AOC had used AOC contract personnel to draft responses to the Executive Core Qualifications associated with a vacancy for a Senior Rated position at the agency. ECQs are the narrative essays that federal candidates write to demonstrate leadership competencies for senior roles. They are supposed to be the applicant's own account of the applicant's own record.
The complainant did not stop at the ethics angle. The same report alleged contract violations: improper taskings that fell outside the contract's Statement of Work, exclusion of the Contracting Officer's Representative from the tasking chain, and retaliation for reporting concerns to the OIG and to AOC leadership.
That bundle of allegations describes a pattern familiar to almost any contractor supporting a federal agency. A government official with authority in the room, but without contractual authority over the work, starts handing tasks directly to contract staff. The COR — the one official who is actually empowered to task under the contract — is not in the loop. The work drifts past the SOW. Nobody wants to say no to a GS-15.
Key Details
The OIG's investigation identified both testimonial and documentary evidence. The documentary side is the part contractors should read twice: e-mails, Microsoft Teams chats, and shared Microsoft Word documents. Collaboration platforms leave a record of who opened a file, who edited it, and who asked for it. A promotion essay drafted in a shared document by people paid under a federal contract is not a deniable event. It is a version history.
Investigators also ran a check that settled the contract-authority question cleanly. Investigative research confirmed the senior manager had never served as the contract's COR, and had not completed the requisite training courses required to be a COR at the AOC. The manager was not authorized to task the contract at all, let alone task it for personal work.
The OIG found, by a preponderance of the evidence, that the senior manager improperly used government contractor services for personal, non-government purposes and violated the AOC Standards of Conduct and Government Ethics policies as well as the AOC Contract Manual. Two separate rule sets, one act.
Not every allegation survived. The investigation did not identify evidence of retaliation by the senior manager. That matters for how the report should be read: the OIG was willing to substantiate some claims and decline others from the same complaint, which is a sign the evidentiary threshold was applied rather than assumed.
The final management action was to submit the Report of Investigation to AOC management for any action deemed appropriate. The case is closed pending that management action. The summary does not name the manager, does not name the contractor, and does not identify a dollar value for the contract personnel hours consumed. Questioned costs are listed as zero — this was an accountability finding, not a recovery.
What It Means for Contractors
The manager is the subject here, and the contractor is not accused of anything. But the contractor's employees were the instrument, and the report is a map of the exposure that creates.
Start with tasking authority. The single fact that anchors the OIG's finding is that the senior manager was never the COR and had never taken the training to become one. That is a verifiable fact, and contractors can verify it in advance. Every services contractor should be able to name, in writing, the current COR and the Contracting Officer for each task order, and every employee touching the work should know that anyone else's request is not a task order — it is a suggestion. If a company's ramp-up briefing does not cover who may lawfully direct the work, the company is relying on individual employees to guess. The AOC case shows what happens when they guess wrong.
Next, SOW discipline. The complainant alleged improper taskings outside the Statement of Work, and the OIG found a Contract Manual violation. A request that lands outside the SOW is not a favor a program manager can grant to keep a client happy; it is unpriced, unauthorized work performed on the government's dime. The right move is boring and unpopular: route it to the COR, put the scope question in writing, and let the contracting shop answer it. The written record that protects the government in this case would equally protect a contractor who pushed back and documented it.
Then the documentary trail. Investigators reconstructed the conduct from Teams chats and shared documents. Contractor personnel working in a government tenant should assume every artifact is discoverable and every collaboration session is logged. That cuts in the contractor's favor when the contractor behaves correctly, and against it when someone quietly goes along.
Finally, the retaliation piece. The OIG found no evidence of retaliation by the senior manager, but the allegation was made because someone reported concerns to both the OIG and agency leadership. Employees who report suspected misuse of contract resources are working within a protected channel, and companies that discourage those reports are on the wrong side of both the statute and the optics. A contractor whose staff feels safe saying "that request has to go through the COR" avoids the entire scenario.
The practical read: this is a small report with no money attached and no recommendations, but it is a clean statement of how a watchdog thinks about the boundary between a federal official's authority and a contractor's labor. The government has one person who can task the work. Everyone else, no matter the grade, is asking for a favor — and favors performed on a federal contract have a way of turning into findings.
