Blog
Building AVCTC's operating layer: a ChiefDesk engagement
AVCTC engaged ChiefDesk to build the operating layer between their executive and the day-to-day work — the brief, the dashboard, the decision log, the weekly cadence — so the team can run from a single picture instead of a stack of drafts. Here is the first-pass scope, the four artifacts we are producing, and a short comment from the founder on what we are trying to build together.
Context — who AVCTC is and why ChiefDesk engaged
AVCTC engaged ChiefDesk to fill a particular gap: the distance between the executive's intent and the day-to-day running of the organization. The team was already operating — programs shipping, partners in motion, fundraising holding — but no part of the week had a single picture of the whole. The brief lived in someone's inbox. The dashboard lived in someone's head. Decisions got made in leadership meetings, then partially chased, then re-litigated at the next one.
The gap was not effort; it was surface. Even a strong team, in a small organization, generates more signal than the executive can turn into picture in a single morning. ChiefDesk's fit with AVCTC was to build that picture with them — to ship the brief, the dashboard, the decision log, and the weekly cadence rather than to hand the executive a system and walk away. The engagement is six weeks of build, then a recurring operating handoff on the cadence piece.
AVCTC's stage matters. The organization is small enough that there is no chief operating officer, no chief of staff, no dedicated operations lead — and large enough that the executive is now handling more integration than is sustainable across a single week. The first-pass engagement is to give the executive a surface to operate against, then hand off to AVCTC's own team once the surface runs.
Scope of work
The scope is four artifacts, in order, against a signed brief. The brief is the contract: it defines what is in, what is out, and what success looks like for the engagement. The dashboard ships next. The decision log ships third. The weekly cadence goes live fourth. Every artifact sets the stage for the next, and shipping them out of order makes the handoff harder.
Inside the scope: the engagement brief itself, including the in-scope list and the out-of-scope list. The operating dashboard — open decisions, blocked items, deadlines this week, executive queue older than forty-eight hours. The decision log, formatted for cross-meeting continuity. The weekly briefing cadence, including the Monday template, the status-against-last-week summary, and the next-step ask format. A recurring check-in rhythm for the six-week build, and an operating handoff to AVCTC's team once the cadence is running.
Outside the scope: a full-time embedded chief of staff. ChiefDesk ships the artifacts and the cadence; AVCTC's team operates them. Vendor procurement beyond ChiefDesk's own toolset. Anything that requires the executive to act as the trust-holder for a funder, partner, or board member — that stays with the executive. Final decisions, final hires, final sign-offs, and the relationships whose continuity depends on the executive's name. ChiefDesk does not represent AVCTC to the outside world; ChiefDesk builds the surface the executive operates against.
The success criterion for the engagement is whether AVCTC's team runs the cadence without us by week eight. If yes, the engagement closes. If no, we extend the operating handoff for another cycle.
The four expected artifacts
We produce four artifacts over the first six weeks. Each is a concrete surface, not a deliverable in the abstract — the order of ship and the shape of each artifact is below.
Artifact 1
Engagement brief
Signed in week one — the contract the rest of the engagement is measured against.
The brief sets the in-scope list, the out-of-scope list, the success criterion, and the recurring check-in rhythm for the six-week build. It is the document both sides reference when scope is contested.
Artifact 2
Operating dashboard
The executive's daily view — opens every morning, never older than one standup.
The dashboard lists open decisions, blocked items, deadlines this week, and anything waiting on the executive for more than forty-eight hours. It is the single picture the executive reads against before walking into any meeting.
Artifact 3
Decision log
Survives between leadership meetings — what was decided, who owns it, when it lands.
The decision log is the cross-meeting continuity artifact: every decision made in a leadership meeting gets a row, an owner, a due date, and a status. The CoS chases blocked rows until they ship or get escalated back.
Artifact 4
Weekly briefing cadence
Live in week four — the recurring rhythm the team runs after handoff.
The cadence is the Monday template, the status-against-last-week summary, and the next-step ask format. After six weeks of build the team runs it; ChiefDesk stays in a recurring operating check-in for as long as the cadence is alive.
Every artifact in the grid is what the engagement is producing. The brief is what we are measured against. The dashboard is what the executive opens each morning. The decision log is what survives between leadership meetings. The weekly cadence is the recurring rhythm the team runs. They land in the order shown: brief first, dashboard and decision log in the middle weeks, cadence live in week four.
Founder voice — comment block
AVCTC's team was already running. They just did not have a single picture of the running. Our job is to build that picture with them — not to hand them a system that runs their operation for them. The four artifacts are the visible version of that deal: a brief we both signed, a dashboard the executive opens every morning, a decision log nobody has to chase, and a weekly cadence that turns everything into a next step. If we ship those well, the rest of the engagement is obvious.
Frequently Asked Questions
Frequently asked questions
Why did ChiefDesk take on AVCTC as a partner?
AVCTC's leadership team was already running the day-to-day of the organization. What they did not have was a single picture of the running — no brief the executive signed against, no dashboard that opened every morning, no decision log that survived between meetings, no weekly cadence that turned everything into a next step. ChiefDesk's fit was that gap: build the operating layer with them rather than handing them a system that runs their operation for them.
What is actually inside the scope of work?
Four things, in order. First, an engagement brief the leadership team signs in week one, which is what the rest of the engagement is measured against. Second, an operating dashboard that becomes the executive's daily view. Third, a decision log that runs across leadership meetings. Fourth, a weekly briefing cadence that goes live in week four. Out of scope: a full-time embedded chief of staff, vendor procurement outside ChiefDesk's toolset, and any decision the executive is the trust-holder for.
Why placeholder boxes instead of screenshots of the artifacts?
The artifacts are real but the partner has not signed off on the public exports yet. We are shipping the layout, the caption, and the intent paragraph so the post reads as a complete engagement rather than an announcement, and we are leaving the screenshot blank pending partner review. As soon as the partner approves the exports we swap the placeholder for the live image in place.
How is AVCTC's engagement different from a fractional chief-of-staff engagement?
A fractional chief of staff ships hours. ChiefDesk's AVCTC engagement ships artifacts. The brief, the dashboard, the decision log, and the weekly cadence are the deliverable, not the time on the calendar. After they ship, AVCTC's team owns them and runs them — ChiefDesk hands off, then stays in a recurring operating rhythm on the cadence piece as a check-in, not as the embedded operator.
When will the artifacts move from placeholder to live?
On partner approval. The brief and the dashboard ship first; the decision log and the weekly cadence template go live as they are produced. We update the post in place when the screenshots land, and the slug stays the same so any future link to the post is still valid.
How can a similar organization engage ChiefDesk the same way?
The intake starts with a twenty-minute discovery call, the first one of which is free. We use the call to map the week, the team shape, and the gap that the four artifacts would close. If the fit is real we scope the four artifacts to your organization in a follow-up brief, sign the brief, and ship. The discovery-call and pricing pages describe the engagement shape in more detail.
Ready to operationalize this?
Book a 20-minute discovery call.
We will look at your week, your team shape, and how a chief-of-staff role — human or AI — fits your operating reality.