Read the reel, not the facility description
A facility name, motor name, or aisle label is background, not a cable specification. For every reel, transcribe the manufacturer, part number, complete readable jacket printing, and marked voltage. Attach a data sheet only when its identity fields match the offered reel. A sheet for a similar product is not a substitute for missing printing on the item being listed.
Use one row for one construction. If the tag is faded, state that the detail is unknown and preserve a photograph of the available text. This supports the core decision: can the cable line be matched to its construction, condition history, and current length without assuming facts from its surroundings?
- Manufacturer and part number
- Complete jacket legend and marked voltage
- Reel reference connected to the supporting file
- Unknown fields retained rather than guessed
Separate construction variants before totaling
Record conductor count and size, conductor metal, jacket designation, and any documented shield or armor on separate fields. Reels that look alike can still have different counts, shields, or ratings. Do not group them merely because they were stored together or served the same equipment area.
Record each continuous piece and label the length as measured, documented, or estimated. For several matching reels, retain each length before a total is shown. The reviewer needs to see whether the quantity represents one usable run or several shorter pieces.
- Conductor count and size
- Metal and jacket designation
- Shield or armor field with unknown where needed
- Continuous footage with a stated basis
Record history and end condition as separate facts
Keep uninstalled maintenance stock distinct from cable that has been removed from prior service. For each line, describe only known history, fitted ends, visible jacket damage, and storage condition. A photo documents what is visible; it does not prove internal condition. The difference between stock states should remain visible even if both lines share an apparent product family.
Add the current storage location, access constraints, and the role that can authorize release. These operational fields belong beside the item record, not in a broad facility description. They help maintain an accurate scope for the actual cable being offered.
- Uninstalled or prior-service status
- Fitted ends and visible jacket condition
- Storage location and access limitation
- Role authorized to release the listed cable
Use local industrial context without making a demand claim
SMUD identifies large-scale manufacturers, heavy commercial and industrial development and data centers as high-demand developments driving inquiries across its service area. That statement is Sacramento-area development context, not evidence that a particular seller has industrial cable or that Industrial Wire Buyer will purchase a certain construction.
Its limited relevance here is record discipline: broad industrial labels can cover very different cable constructions. The seller packet should stay tied to the actual reel printing, item condition, and quantity instead of relying on a generalized facility description.
- Local context is not a claim about a seller lot
- Jacket marking takes priority over equipment labels
- Each photo and file uses the reel reference
- Release evidence stays item-specific
Illustrative cable record and unknown markings
Illustrative inventory example—not a purchased lot: IC-SAC-02; manufacturer part number copied from the reel tag; four conductors, 6 AWG; shield status unknown; 420 feet documented; uninstalled maintenance stock. The unknown shield field is more useful than a guess because it tells the reviewer what documentation is still needed.
The common mistake is to use the facility or equipment name as the specification and attach an unrelated data sheet. The resolution is to preserve actual reel markings, leave unsupported construction fields unknown, and split stock with prior service history from uninstalled stock. The example is a formatting model, not a reported transaction.
