Non-software engineering: design, drafting and field engineering delivered to a client or project owner.
A record here is built from things like a deliverable accepted by the client, confirmed by somebody other than the person who did it.
Both directions. A record that only carries the good weeks is not a record, and the person it is about is told about every entry and can contest any of them.
The engineering deliverable (drawings, design, report) was delivered and accepted by the client or project owner.
A project milestone was paid by the client.
The delivered work passed an independent inspection or review.
The client or reviewer required the work to be reworked to meet the agreed spec.
Due and done are the pair that decide whether something counts as delivered on time rather than merely delivered. Send one without the other and the outcome can only ever read as finished.
3 kinds of third party confirm work in this trade. None of them outranks another. The formula does not read this at all. What varies is how hard each one is for either side to lean on, which is a fact worth knowing and not a weighting.
A client who did not attend, work the business itself pulled or rescheduled, conditions nobody controls, time off taken with notice, and an opinion about the person. None of it belongs on the record of whoever showed up to do the work.
The full list is on the index, and it is the same list for every trade.
A confirmed outcome becomes evidence in a published formula, version 5.6, with five weights and six bands running from Distinguished down to At Risk. An outcome nobody else confirmed is still recorded, and it shows on the record as a claim rather than as evidence. No plan and no payment moves a score.
The record belongs to the person, not to the business that recorded the work. They take it with them. The model is published in full, and what an employer records covers the recording side.
