The ledger desk of BGW Capital, LLC
Position slips, mandate notes and review letters are kept at the St George desk of BGW Capital, LLC, at 1944 Centennial Dr, St George - 84770-4791, United States (US). Six service lines make up the desk. Each one has its own tray, its own fixed hour and its own signature line.
How the desk is organised
A ledger desk works because it has edges. A tray holds a stack, a stack holds a finite number of slips, and a slip that is older than the agreed review date is visible at a glance because it sits on top rather than buried. The desk at 1944 Centennial Dr, St George - 84770-4791, United States (US) is arranged on exactly that principle. Three trays run in parallel: the position tray, the mandate tray and the letter tray. A fourth tray, opened only in December, holds the bound volume of the year. Every document that leaves this office begins in one of the first three and ends in the fourth.
Clients sometimes ask why computer systems design should be organised with paper logic when everything the firm builds is digital. The answer is that the paper logic is not about paper. It is about a fixed number of open items, a named owner for each item and a date on which the item will be read again. Software has no trouble holding thousands of open threads. People do, and a system designed by people who are holding thousands of open threads will eventually reflect that confusion in its own structure. The desk keeps the human side small so the digital side can stay legible.
Position Slip Bays
A position slip is the first document in any engagement. It states three things in one page: what we believe about the system today, what we have assumed in order to hold that belief, and what evidence would force us to reverse it. The slip is filed in a numbered bay and stays there until the assumption is tested. Bays are not a filing convenience. They are a commitment. A slip in bay fourteen tells every person at the desk that question fourteen is still open, and that nobody is allowed to describe it in a proposal as though it were settled.
Position slips are also how we begin integration work. When two vendor systems must exchange data, the question of who owns the translation layer is usually answered by silence. The slip names an owner before any code is written, records the format assumptions on both sides and lists the failure modes we expect to see first. Six months later, when the export arrives with a field in the wrong encoding, the slip is the document that ends the argument without a meeting.
Mandate Note Runs
A mandate note is the scope document for a commission. It records what the client asked for, what we agreed to deliver, and, just as importantly, what we declined. Declining in writing is a habit we borrowed from survey practice. A surveyor who leaves out a boundary line will be asked about that line in court. A systems firm that quietly excludes a migration will be asked about it during an outage. The note makes the exclusion visible on day one so it can be argued then rather than at the worst possible moment.
Mandate notes are revised in runs. Each Monday at ten in the morning the desk reads every open note against the work that actually happened in the previous week. A note that has drifted from the build is corrected on the spot, and the correction is dated. Clients receive the revised note the same day. Nobody at this firm is permitted to say that the scope changed when what actually happened was that the scope was never written down.
Review Letter Desks
Every quarter the client receives a review letter. It is not a status report generated from a tracker. It is a letter, written by the partner who owns the mandate, and it follows a fixed shape. It opens with what changed in the system since the last letter. It continues with the decisions the client made and the ones the desk made under delegated authority. It closes with the items still open at the desk and the date each will next be read. The letter is signed, scanned and placed in the letter tray in case a client ever needs to prove what was known on a given day.
The letter desk also holds correspondence that is not a regular quarterly review. When a client asks a direct question about a security posture, a licensing obligation or the behaviour of a vendor under load, the answer is written as a letter even when it takes two paragraphs. Answers given in chat windows are convenient and unaccountable. Answers given in letters can be relied upon years later, which is exactly what a firm in the professional and technical services sector owes its clients.
Distribution Watch Windows
A watch window is the period between sending a release and closing the tray on it. For a small change the window may be a single afternoon. For an integration that touches a payment rail, a warehouse ledger and a customer portal, the window stays open for a full working week, and during that week the person who shipped the change is the person who watches the logs. This is a deliberate departure from the usual arrangement in which engineering hands work to operations and forgets it. The context of a change is warmest in the head of the person who made it, and using that warmth to catch the first fault is the cheapest reliability measure available.
Watch windows are logged with an open time and a close time. A window that is still open when the next release is due blocks that release until the desk makes a written decision. We have delayed shipments for this reason and will do so again. A schedule that bends to a watch window is a schedule that survives a year. A schedule that pushes past its own watch windows is a schedule that will eventually ship a fault into a live ledger.
Custody Review Rounds
Custody rounds are a physical walk across every key, credential, certificate and build artifact in the mandate. The custodian holds the page and the second reviewer countersigns each line. Anything that cannot be produced at the moment of the round stops the round and is written into the review letter as an open item. The round is not an audit performed by a stranger once a year. It is a habit performed by the people who use the keys, every month, at a fixed hour, so that a lost credential is discovered in days rather than in the aftermath of an incident.
The rounds also cover build artifacts. A binary that cannot be traced to a source revision at the time of the round is treated as unaccounted. This standard is strict, and clients occasionally push back on it, but it is the reason BGW Capital, LLC has never had to reconstruct what was deployed on a given date from a fragmentary chat log. The answer is on the page, with two signatures beneath it.
Year-End Sittings
The year closes with a sitting rather than a summary. On the first Monday of December the desk sits with the client for a full day at 1944 Centennial Dr, St George - 84770-4791, United States (US), or on a conference line for clients who cannot travel. The year is read back from the first position slip to the last review letter. Every open item is either closed, carried forward on a dated page or retired in writing. The client leaves with the bound volume and a fresh page for the coming year.
A sitting is deliberately slow. There is no agenda slide and no dashboard. The purpose is to let a client hear the whole record in one sitting, in order, and to notice the places where the story does not hang together. Those places are almost always the most valuable discovery of the day. We have found duplicate vendor contracts, forgotten test accounts and mispriced integrations during sittings, not because we were looking for them but because the record was read aloud without interruption. That is a service no tracker can provide.
The process from first slip to bound volume
A mandate moves through five stages, and each stage has a document that proves it happened. Stage one is the position slip, written after a short reading of the existing system and an interview with the two people who run it. Stage two is the mandate note, agreed and signed before any work begins. Stage three is the build and integration period, during which watch windows are kept and custody rounds are walked every month. Stage four is the quarterly review letter, which folds the first three stages back into a single readable page. Stage five is the year-end sitting, where the whole record is bound into a volume the client keeps.
There is no stage at which a client is asked to trust a verbal assurance. If a thing is true about the system, it appears on a page with a date and a signature. If it does not appear, it is not true for the purposes of the record, and the desk treats it as unknown. This discipline is the single reason our clients can hand a mandate to a successor, an auditor or a regulator without reconstructing three years of history from memory.