Twenty-one requests addressed to an engineer of record sit drafted and unsent in the external request register. Exactly four of them depend on no other external request [TARGET]. Three of those four name the owner as the approving party rather than any engineering discipline, and the fourth is a negative entry whose status is recorded as existing evidence, unverified. The part of the engineer-of-record queue that is ready to go out is therefore, on the register's own fields, not an engineering queue.
The Dependency Field Isolates Four Unblocked EOR Requests
The register carries a dependency field for each request and a mechanical rule for filling it, and it publishes the partition that results: of the eighty earlier entries, twenty-four depend on nothing, one depends only on an internal change candidate, and fifty-five point at another request. Applied to the engineer-of-record class that leaves four [TARGET]:
- a submittal that would name a licensed party to absorb the design basis;
- a civil-side decision, countersigned by the civil discipline;
- a decision that two separate authority requests are themselves waiting on;
- the negative entry recording two feeders from one substation as not constituting utility redundancy.
The first three are also the only entries in the class whose required-by date is anchored rather than unresolved. That is a second field, filled by a different rule, pointing at the same three rows.
The closed set is ninety-three requests: eighty from the first revision plus thirteen later skeletons. Ninety of them are drafted and not sent. Three carry existing unverified evidence. Sent, response, closed and reopened each count zero.
The block that applies to all twenty-one is not technical
Every entry in the class carries a code meaning the recipient does not yet exist, because no engineer of record is appointed. That is a different condition from a missing prerequisite, and the register keeps the two in separate fields precisely so they cannot be confused. The send gate is a conjunction of six terms and the register evaluates every one of them as false today, so both the count of sendable batches and the count of sendable requests are zero [TARGET]. Appointing an engineer of record clears one term. It does not clear the other five, and on three of these four questions it does not produce an answer either, because the approver is the owner.
Naming the other five terms is worth the space, because they say what kind of work is outstanding. None of the eighteen mechanical quality gates has been evaluated by a validator; the legal entity of the receiving party is open; the enquiry baseline the supplier-class requests hang off is flagged as having failed its own red-team pass; every one of the ninety-three requests still carries a placeholder in place of a named addressee; and three of the enclosures that would travel with a request have not been written. Four of those five are administrative rather than technical, and every one of them is closable by a decision rather than by a calculation. Handwritten quality-gate passes are a forbidden action on this register.
The register states seven non-authorisations in its own opening, of which the first is that it does not authorise sending any request, any subset or any batch. Directly issuable count equals zero.
The appointment letter is itself unsent
The consequence is an ordering choice the owner can make with no new technical data at all. The scope and fee enquiry that would appoint an engineer of record is itself drafted and marked not sent, with no appointment made and none claimed anywhere in it. It is a solicitation for a proposal, not an appointment, a notice to proceed, a design acceptance, a procurement authorisation or a transfer of professional duty. Taking the three owner decisions first means the appointment arrives to a queue three dependencies shorter. Taking the appointment first means paying a licensed party to wait on decisions that were never theirs to make.
That letter would walk into a thirteen-item calculation index with author, checker, approver, inputs, software, date and fee still blank on every row, and into native models it itself describes as concept and coordination evidence, not completed engineering design.
Nowhere does the register permit the absolute historical claim, in either direction. It allows only the statement that it holds no verifiable evidence of sending, and its completeness against actual historical communication is marked unknown. A question may have been asked and answered outside the register, and its dependency and approver fields would read exactly the same.
One row will not resolve into either group. The negative entry carries no dependency, which under the register's own rule should have flagged it beside the other three, and it did not receive that flag; the difference is booked as a change candidate with no adjudicator named. It is also the only one of the four whose approver is an engineering discipline. The single question in this class that an engineer of record could answer unaided is the one the register has not decided how to rank.
Limits and open items
Confirmed: the register does not authorise sending any request; both sendable-batch and sendable-request counts are zero; no engineer of record is appointed. [FACT]
Register figures: twenty-one requests in the engineer-of-record class; exactly four with no external prerequisite; three of those four naming the owner; a six-term send gate, every term false; ninety-three requests in the closed set, ninety drafted and not sent. [TARGET]
Open: the three owner decisions; an appointment; any of the eighteen quality gates evaluated by a validator; a named addressee on any of the ninety-three rows. [HOLD]
Nothing here has been reviewed or sealed by an Engineer of Record. Nothing describes how any installed system behaved.
Name the Three Owner Decisions That Shorten the Queue
The useful test is not whether an engineer of record should be appointed. Name the three owner decisions that would shorten the queue. If those names cannot be written, the appointment arrives to the same four questions it would have found today.
© 2026 K&K Data Service Inc. All rights reserved. Reproduction or republication is permitted only with clear attribution to K&K Data Service Inc. and a working hyperlink to the canonical URL of this article. Excerpts must preserve the technical context, maturity labels, assumptions, and limitations. No excerpt may imply project approval, field validation, certification, or endorsement that the original article does not state.
Source: K&K Data Service Inc., “Four Engineer-of-Record Requests Have No Prerequisite; Three Need the Owner,” https://www.kkdatasvc.com/lab/errata-and-open-questions/four-questions-have-no-prerequisite-and-three-are-not-the-engineers/.
Discuss This Constraint. If your project record shows a different result, or the same failure domain under another name, we want to see it. Email inquiry@kkdatasvc.com or use the contact page.