// For executives, chiefs of staff and programme directors
Your pack will not tell you that. ExCom Office is the preparation method that does: one page, written in the hour before the meeting, saying what changed, what still needs a decision and what to challenge, with a source reference on every line.
One time. No subscription, no refresh commitment. The method runs on paper, so it works whether or not your tenant lets you automate it. The optional Cowork skill needs approved desktop access.
A committee approves a supplier at a cap and a date. Two meetings later the packet arrives with a higher number, a better delivery date than last time but still past the approved one, and a recovery that has quietly been withdrawn. Four actions show complete, with evidence. Three stored statuses are stale.
Everything looks like progress. Nothing has been approved. The brief that says so fits on one page.
This is the worked example that ships with the package, reduced to its spine. It is an authored illustration written by hand to teach the method. It is not a customer case, not a screenshot, and not an observed Copilot result.
FICTIONAL WORKED EXAMPLE. Authored illustration, not an observed Copilot result. Project North · ExCom 5 October 2026 · evidence through 2 October, 18:00 THE DECISION Compressor award remains on HOLD. approved authority this packet reads as price EUR 4.20m cap EUR 4.38m EUR 180k over cap [1,2] delivery by 15 December 10 January 26 days past [1,2] (10 days better than the previous offer) funding EUR 400k recovery withdrawn support removed [2] THE ACTIONS All four carry completion evidence. 4 of 4 done Three stored OPEN values are stale. 3 stale [2,3] Completing them does not lift the award hold. IN THE ROOM Procurement can B's binding terms be established before A's stated 7 October expiry? Director what supported mitigation changes the 5 February commissioning scenario? Chair if we choose A, precisely which cap, delivery and hold conditions are we changing? [1] Approved minutes, 7 and 28 September. [2] Meeting pack, 2 October. [3] Approved action list, 28 September, compared with that pack. Amounts EUR excluding tax. Later 5 October minutes are excluded.
Every consequential amount, date and condition carries a source locator. That is the discipline the package teaches, and it is what makes a one-page brief safe to hand to a chair.
Sixteen documents, each in Word and PDF, plus the installation package and an offline guide. Thirty-five files in total.
The meeting pack, the previous approved minutes, the existing action list, the one-page brief that reconciles them, the minutes that followed, and the after-the-meeting review. You can read the brief against its own sources and check every line. It walks the whole reasoning: how a EUR 4.38m request reads against a EUR 4.20m approved cap, why ten days better on delivery is still 26 days too late, and why four completed actions change none of it.
A meeting brief layout and a decisions and follow-up layout. Your existing format works just as well; these are a starting point, not a house style.
Separate what the documents establish from what you are inferring from what nobody knows. Put a source locator on every consequential amount, date and condition. Never let a completed task imply a lifted condition. Never let a recommendation read as an approval.
An installation package for Microsoft Copilot Cowork, with an executive guide, an assistant guide, a self-use guide and a one-page brief for your IT team. Requirements below. The worked case, the two templates and the written method use no Cowork at all. You can run the entire method on paper, and most of the package is built that way on purpose.
The person who prepares the pack, and carries it when the committee asks where a number came from.
It does not connect to your calendar, your mail, or your document system. You give it the documents.
It does not approve anything, record anything, or send anything. It drafts, you decide. Every output is labelled as a draft for review.
It is not a subscription. There is no promise of future releases or platform maintenance.
The worked example is an authored illustration. It is not a customer case and not an observed AI result.
Personal setup, coaching, and the preparation or review of your own briefs are not included.
The included Copilot Cowork skill depends on the access and features available in your tenant: approved desktop Cowork access and custom-skill availability, both decided by your organisation and by Microsoft, not by me. Custom skills are not supported on mobile. Microsoft licensing, usage charges and feature availability are separate and not included, and they change. Check the current requirements with your administrator before you buy if the skill is the reason you are buying.
If your tenant cannot run the skill, that is a limit of the tenant and not a fault in the files, so it is not a repair or refund case under Article 9. The method, the worked case and the templates need no Cowork and are the larger part of what you are paying for. Your mandatory consumer rights are unaffected either way.
One payment. No subscription. All 35 files, for one named committee within one legal entity.
ExCom Office may not be resold, redistributed or sublicensed, and the attribution stays on the material. It is not a trainer or reseller licence and it does not become one.
Within that limit, it is licensed for internal use by one named committee within one legal entity, including its executives, preparation staff, and the internal IT staff who help them. You keep using the release you bought, internally, for as long as you like.
Governed by the Kesslernity License and Terms, KESS-LIC-2026-001 v1.1, Article 3.2. Current published reference: kesslernity.com/license. The version in force on your purchase date applies.
No. The worked case, the two templates and the written method use no Cowork at all, and they are the larger part of the package. The skill is included and optional. If your tenant can run it, it runs the same method; if it cannot, you still have everything you need to run the method by hand.
No, and it says so on its own face. Project North is an authored illustration, written to teach the reconciliation. It is not a customer case, not a screenshot of software, and not an observed Copilot result. Its fictional sources ship with it so you can check the brief against them line by line.
Internal use by one named committee within one legal entity, including that committee's executives, preparation staff and the internal IT staff who assist them. It is not a reseller or trainer licence: the package may not be resold, redistributed or sublicensed, and the attribution stays on the material.
Write to mathieu@kesslernity.com and it gets repaired or refunded under Article 9. Gumroad handles payment and first-line refund support. Your mandatory consumer rights are unaffected.
Article 8 of the licence governs updates. This is a one-time purchase of Release 1.0, with no subscription and no promise of future releases or platform maintenance. Buy it for what is in it today.
You already do, and that is the point. What the package adds is the part that is hard to invent under time pressure: a complete worked case you can read both ways, and a written rule set for the four places a pack quietly misleads a committee. A completed action implying a lifted condition. A recommendation reading as an approval. An inference sitting next to an established fact with nothing to tell them apart. A number with no source locator.
Built by an independent practitioner who prepares and reads these packs. No testimonials yet: this release has no buyers, so judge it on what you can inspect before you pay, which is everything above plus the licence.
store.kesslernity.com · kesslernity.com · 2026