The Repair LibraryRead · Learn · Master

Board Documentation Techniques

With the ethics and the law of the previous section settled, this one turns to the first real technique of reverse engineering: taking an undocumented board and turning it into a documented one — a reference a technician can actually repair from. The premise is that an undocumented board is not repairable in any reliable way until it has been documented, because a repair is a series of decisions about specific parts in specific places, and without a record of what those parts are and where they sit, every decision is a guess. So the section teaches how to build that record, and it begins with a discipline that governs everything after it: document the board as found, before anything is changed. A repair alters the board — a part is removed, a jumper is moved, a socketed chip is pulled — and the original state, once altered, cannot be recovered, so the as-found condition is captured first, in full, as the baseline the whole repair will be measured against. From there the section builds the record in layers. Photography is the base: the board captured whole and in macro detail, both sides, under raking light that throws the silkscreen and the copper into relief, with the tiny markings on the ICs and the small parts caught close enough to read. On top of the photographs comes the component inventory, the systematic census in which every part is located, named, and recorded — its type, its value read from its markings or measured when the markings are gone, and every IC's part number captured — so that the board's contents become a list rather than a blur. And the photographs and the inventory assemble into the deliverable the section is really about: the board map, an annotated reference that says where each part is, what it is, and how the board is organized into its regions of power, signal, and the rest. The section closes on the point that gives all of this its purpose: the documented board is the repairable board, the record is the deliverable, and a technician who documents systematically has not merely described a board but has made it — and every future repair of it — possible.

AdvancedLow Risk23 min read

What You Will Learn

  • You will learn the discipline of as-found documentation — capturing the board's original state before a repair changes it.
  • You will learn photography as the base record — whole and macro, both sides, under raking light.
  • You will learn to build a component inventory — locating, naming, and recording every part and IC systematically.
  • You will learn to assemble a board map — an annotated reference of where each part is and how the board is organized.
  • You will learn why the documented board is the repairable board, and why the record is the deliverable.

What You Will Be Able To Do

  • You will be able to capture a board's as-found state before making any change to it.
  • You will be able to photograph a board whole and in macro detail, both sides, under raking light.
  • You will be able to build a systematic component inventory of a board's parts, values, and IC part numbers.
  • You will be able to assemble a board map that names each part's location, identity, and region.
  • You will be able to produce documentation reusable for this and future repairs of the board.

Required Tools

  • A macro-capable camera and a raking light source — the base record of a board is high-resolution photography of both sides under grazing light
  • A microscope or loupe — IC markings and small-part codes are read at magnification and captured into the inventory
  • A multimeter — component values whose markings are gone are measured rather than guessed
  • The notebook or a spreadsheet — the component inventory and the board map are built as a systematic, reusable record

When NOT to Attempt This

Do not attempt this section if any of the following apply to you:

  • You are not comfortable working with small surface-mount components.
  • You have not completed the prerequisite sections for this skill.
  • You do not have the required tools in working condition.

Section Overview

With the ethics settled, this turns to the first technique of reverse engineering: making an undocumented board into a documented, repairable one (reverse-engineering-ethics-and-legality). An undocumented board is not reliably repairable, because a repair is decisions about specific parts in specific places, and without a record each decision is a guess (finding-schematics-and-board-diagrams). One discipline governs everything. As-found documentation — capture the board before anything is changed, because a repair alters it and the original state cannot be recovered. The record is built in layers. Photography is the base — whole and in macro, both sides, under raking light that throws the silkscreen and copper into relief. On top comes the component inventory — the systematic census locating, naming, and recording every part, its value, and every IC's part number (schematic-symbols-and-conventions). And these assemble into the deliverable. The board map — an annotated reference of where each part is, what it is, and how the board is organized into its regions (reading-a-complete-schematic). The point that gives it purpose: the documented board is the repairable board, and the record is the deliverable — a technician who documents systematically makes the board, and its every future repair, possible.

Why This Matters

This is the technique that turns the legitimate purpose of the last section into an actual, repairable result (reverse-engineering-ethics-and-legality). This matters because an undocumented board fights every repair: without a record of what each part is and where it sits, a technician guesses at values, loses track of orientation, and cannot reason about the board as a system — so documenting it first is not preparation for the repair but the thing that makes the repair possible (finding-schematics-and-board-diagrams). This matters because the as-found state is unrecoverable once lost: the moment a part is removed or a jumper moved, the original configuration is gone, and any detail not captured first — a link setting, a socketed part, a subtle prior modification — is gone with it, so capturing as-found is a one-time chance that governs everything after (schematic-symbols-and-conventions). It matters because a systematic record is worth more than a thorough memory: a board documented ad hoc leaves gaps that surface at the worst moment, while a board inventoried and mapped in a consistent order is complete and reusable — by the same technician months later, or by another entirely (reading-a-complete-schematic). And it matters because the documentation is the real deliverable: the repair is one use of the record, but the record itself outlasts the job — it makes this board, and every future instance of it, repairable — so the effort spent documenting is not overhead but the most durable value the work produces. Document the board as found, inventory it systematically, and map it into a reusable reference — and an undocumented board becomes one a technician can actually fix.

Required Prerequisites

Before starting this section, you should have completed:

  • Low-tack labels and fine markers — components and regions are labeled consistently as they are inventoried, because a systematic naming scheme is what makes a record complete rather than a pile of notes.
  • Isopropyl alcohol and swabs — a board is cleaned before it is photographed and read, because flux residue and grime hide the very markings and silkscreen the documentation depends on.
  • Archival storage for the record — the photographs, inventory, and map are saved in a durable, organized form, because a record that cannot be found again is not a deliverable.
  • An undocumented donor board with legible parts — a real board to document end to end, ideally one whose markings are still readable, so the full process can be practiced.
  • A board with some unreadable component markings — so measuring a value whose markings are gone becomes part of the inventory practice, not an afterthought.
  • A macro camera and a raking light — the base tools of the photographic record, so the technique of throwing silkscreen and copper into relief is learned on real hardware.

Real-World Applications

This is the work a technician does before repairing anything without a schematic. A repairer facing an undocumented board photographs it as found, both sides, before touching it, because the moment a part comes off the original state is gone (schematic-symbols-and-conventions). A technician inventorying a dense board works in a consistent grid, recording every part's location, value, and part number, so nothing is skipped and the census is complete (finding-schematics-and-board-diagrams). A bench documenting a board for a repair it will repeat builds a reusable board map rather than scattered notes, because the same board will come back and the map is what makes the second repair fast (reading-a-complete-schematic). And a tech who owns and lawfully documents a board does so within the legitimate purpose the last section established, producing a record for repair rather than for copying (reverse-engineering-ethics-and-legality). The confusions this prevents: an as-found detail lost to an early rework, a part skipped in an ad hoc pass, a record too scattered to reuse, and documentation undertaken without the legitimate footing the ethics section set.

Common Challenges

  • The as-found chance comes once. The original state is captured before any change or it is lost — a jumper setting or a socketed part not photographed first cannot be recovered after the rework (schematic-symbols-and-conventions).
  • Markings hide and vanish. IC part numbers and small-part codes are tiny, and some are worn away entirely — they must be read at magnification, and measured when reading fails (finding-schematics-and-board-diagrams).
  • Ad hoc documentation leaves gaps. A board documented without a system misses parts that surface at the worst moment — only a consistent order over the whole board yields a complete record (reading-a-complete-schematic).
  • A record that cannot be reused is half-wasted. Notes scattered across scraps document the board only for the moment — the value is a reusable map, not a transient description (reverse-engineering-ethics-and-legality).

Safety Notes

Risk Level: Low. This section photographs, reads, and records a board — it reworks nothing — and the standing bench law and the ethics of the last section frame it.

  • ESD discipline throughout — a documented board is often working or repairable, so it is handled by its edges, on a grounded mat, with static control.
  • Legitimacy governs the work — documentation is for repair, interoperability, and understanding, on a board one is entitled to document, per the previous section.
  • Gentle cleaning only — solvents and soft technique to reveal markings, never force that damages silkscreen, pads, or small parts.

Professional Tips Before Starting

  • Capture as-found first. Photograph both sides before a single change — the original state is a one-time chance, and everything after depends on it (schematic-symbols-and-conventions).
  • Light it to read it. Raking light throws silkscreen and copper into relief — and macro captures the markings a normal photo blurs (finding-schematics-and-board-diagrams).
  • Inventory in a consistent order. Work a grid or region by region — a system is what makes the census complete rather than gapped (reading-a-complete-schematic).
  • Measure what you cannot read. A worn marking is not a dead end — the value is measured and recorded rather than guessed or skipped.
  • Build for reuse. Assemble a real board map, not scattered notes — the same board returns, and the record is the deliverable that outlasts the job (reverse-engineering-ethics-and-legality).

Documenting an Undocumented Board

Capture As-Found — The One-Time Baseline

Every board documentation begins with a discipline that cannot be repeated later: capturing the board exactly as it arrived, before anything is changed (schematic-symbols-and-conventions). The reason is simple and unforgiving. A repair alters the board — a component is desoldered, a jumper is repositioned, a socketed chip is removed, a connector is unplugged — and the original configuration, once altered, is gone, recoverable only from a record made before the change. As-found documentation is that record: a full capture of the board's original state — its parts in place, its links and switches as set, its socketed and modular pieces where they sit, and any damage or prior modification visible on arrival — made as the very first action, before a tool touches it. What it protects is everything a repair might disturb. A jumper setting that configured the board, a part that was socketed rather than soldered, a subtle earlier repair, a connector's keyed orientation — each is obvious on the intact board and invisible once the board is changed, and each can be the difference between a correct reassembly and a broken one. This makes the as-found capture a one-time chance, not a routine step. There is no going back to photograph the original jumper positions after the board has been reworked, so the discipline is to document first and completely, treating the untouched board as a source that will never exist again in exactly this form (finding-schematics-and-board-diagrams). Capture it whole, capture it before, capture it once — the as-found baseline that every later step of the repair is measured against, and the foundation the rest of the documentation is built on.

Photograph and Inventory — The Base and the Census

On the as-found baseline the record is built in two layers: the photographs that capture the board as an image, and the inventory that captures it as a list (finding-schematics-and-board-diagrams). Photography is the base record. The board is captured whole, both sides, and then in macro detail — high resolution, under raking light that skims across the surface and throws the silkscreen text and the copper topology into readable relief, with the tiny markings on the ICs and the small passives caught close enough to read, so that the photographs are not just a picture of the board but a legible document of it. On the photographs is built the component inventory. This is the systematic census of what is on the board: every component located and given a reference — its own designator if the board has none printed — and recorded with its type, its value read from its markings, and, for every integrated circuit, its full part number captured from the top of the package — together with the polarity or pin-1 orientation of every polarized part, the electrolytics, tantalums, diodes, and ICs, because orientation is exactly the as-found detail a reassembly depends on (schematic-symbols-and-conventions). When a marking will not read, it is measured, not guessed. A resistor whose code has worn away is measured with the meter — isolating the part with a lifted leg where an in-circuit reading is corrupted by the parallel paths around it, done after the as-found capture and never before it — and its value recorded; a capacitor whose marking is gone is identified as far as measurement allows — because a census with holes in it is a census that will fail at the moment the missing part matters. And the census is systematic, not opportunistic. The board is worked in a consistent order — a grid, or region by region — so that every part is reached exactly once and none is skipped, which is what separates a complete inventory from a scatter of the parts that happened to catch the eye. Photograph the board legible, inventory it complete, and measure what will not read — the base and the census that turn a board into a documented set of parts.

Assemble the Board Map — The Reusable Deliverable

The photographs and the inventory are the materials; the deliverable they assemble into is the record a repair actually works from (reading-a-complete-schematic). That deliverable is the board map. It is an annotated reference that brings the photographs and the inventory together into one usable whole: each component's location marked on the board image, its identity and value from the inventory attached, and the board's organization made visible — its regions of power, of signal, of the connectors and interfaces at its edges — so that a technician can find any part, know what it is, and understand where it sits in the board's structure. The map is what makes the documentation navigable. A pile of photographs and a spreadsheet of parts are raw materials; the board map is the thing that lets a technician point at a spot and know immediately what is there and what role it plays, which is exactly what a repair needs at the moment of a decision. And the map is built for reuse. It is made as a durable, organized artifact — not scattered notes for the moment — because the same board will return, to the same technician or another, and the map is what makes the second repair fast and the tenth routine (reverse-engineering-ethics-and-legality). This is where the section's purpose lands. The documented board is the repairable board, and the board map is the documentation in the form a repair uses — so a technician who has built a good map has not merely recorded a board but has produced the deliverable that makes it, and every future repair of it, possible. Assemble the map, make it navigable, build it to last — the reusable reference that is the real product of documenting a board.

Common Mistakes

  • Changing the board before documenting it. A part is pulled and then the technician thinks to photograph — the as-found state is already gone, and with it any detail not captured first (schematic-symbols-and-conventions).
  • Photographing without the light or the magnification. A flat, distant photo is called documentation — silkscreen and markings need raking light and macro, or the record is unreadable where it matters (finding-schematics-and-board-diagrams).
  • Inventorying opportunistically. The obvious parts are recorded and the rest assumed — only a consistent order over the whole board yields a census without gaps (reading-a-complete-schematic).
  • Guessing a worn value instead of measuring it. An unreadable marking is estimated or skipped — the value is measured with the meter, because the missing part is the one that will matter (schematic-symbols-and-conventions).
  • Leaving the record as scattered notes. Loose photos and jottings document the board for the moment only — the deliverable is a reusable map, and without it the work must be redone next time.

Troubleshooting Guidance

  • About to start a repair on an undocumented board — document as-found first: photograph both sides and record the links, sockets, and any prior modification before any change, because the original state is a one-time capture that the repair will destroy (schematic-symbols-and-conventions).
  • A component's markings will not read — magnify, then measure: read it under the microscope first, and if the marking is worn away measure the value with the meter and record it, rather than guessing or leaving a gap in the census (finding-schematics-and-board-diagrams).
  • The documentation feels incomplete but you cannot say where — check the order: an ad hoc pass leaves gaps, so redo the inventory in a consistent grid or region order, which surfaces the parts a scattered pass missed (reading-a-complete-schematic).
  • The record is hard to use during the repair — assemble a board map: raw photos and a parts list are materials, not a deliverable, so combine them into an annotated map that locates and identifies each part where the repair can use it (reverse-engineering-ethics-and-legality).

Verification & Testing Methods

Confirm your documentation skill before moving on:

  • [ ] I can capture a board's as-found documentation — its original state, links, sockets, and any prior modification — before making a single change.
  • [ ] I can photograph a board whole and in macro detail, both sides, under raking light that renders silkscreen and markings legible.
  • [ ] I can build a systematic component inventory of a board's parts, values, and IC part numbers, measuring what will not read.
  • [ ] I can assemble a board map that locates and identifies each part and shows the board's regions.
  • [ ] I can produce documentation reusable for this repair and for future repairs of the same board.

Then try the practice exercises below — documentation and record-building only; scenarios differ from the quiz.

Practice Exercises

  1. Capture as-found (5 minutes, donor board, before any change). Photograph a donor board whole on both sides and record its links, switch settings, socketed parts, and any visible prior modification — all before touching it — so the one-time baseline is secured (schematic-symbols-and-conventions).
  2. Photograph to read (5 minutes, same board). Capture the board in macro under raking light so the silkscreen and the IC and small-part markings are legible in the images, building the base record the inventory reads from (finding-schematics-and-board-diagrams).
  3. Inventory systematically (5 minutes, same board). Working a consistent grid or region order, record each part's location, type, value, and part number, measuring any value whose marking will not read, so the census is complete and gap-free (reading-a-complete-schematic).
  4. Assemble the reference (5 minutes, from the photos and inventory). Combine the photographs and the inventory into an annotated map that locates and identifies each part and marks the board's regions, producing the reusable deliverable a repair works from (reverse-engineering-ethics-and-legality).

These core steps — the as-found capture, the legible photography, the systematic inventory, and the assembled map — are tested in the Chapter Quiz at the end of this chapter, where a score of 80% is required to continue.

Key Takeaways

  • As-found documentation captures the board's original state before any change, because a repair alters the board and the original — its links, sockets, and prior modifications — cannot be recovered once altered, making it a one-time baseline (schematic-symbols-and-conventions).
  • Photography is the base record — the board whole and in macro, both sides, under raking light that renders silkscreen and markings legible — a photograph that documents rather than merely pictures the board (finding-schematics-and-board-diagrams).
  • The component inventory is the systematic census — every part located, named, and recorded with its type, value, and IC part number, in a consistent order so none is skipped, and measured when a marking will not read (schematic-symbols-and-conventions).
  • The board map assembles the photographs and inventory into an annotated, navigable reference — each part's location and identity and the board's regions — built for reuse, because the same board returns (reading-a-complete-schematic).
  • The documented board is the repairable board, and the record is the deliverable — a technician who documents systematically makes the board, and its every future repair, possible, which is the durable value the work produces (reverse-engineering-ethics-and-legality).

Skills Learned

After completing this section, you can:

  • Capture a board's as-found state before making any change to it.
  • Photograph a board whole and in macro detail, both sides, under raking light.
  • Build a systematic component inventory of a board's parts, values, and IC part numbers.
  • Assemble a board map that names each part's location, identity, and region.
  • Produce documentation reusable for this and future repairs of the board.

Glossary Additions

New terms introduced in this section:

  • as-found documentation — the capture of a board's original, unaltered state, made as the very first action of a repair or reverse-engineering task, before any component is removed, any jumper moved, or any socketed part pulled. It records what a repair will inevitably disturb and cannot restore: the positions of parts, the settings of links and switches, which pieces are socketed or modular, the keyed orientation of connectors, and any damage or prior modification visible on arrival. Its importance is that it is a one-time chance — the moment the board is changed, its original configuration is gone and recoverable only from a record made beforehand — so as-found documentation is the baseline the entire repair is measured against and reassembled to, and skipping it forfeits information no later step can reconstruct.
  • component inventory — the systematic census of every component on a board, in which each part is located and given a reference designator — its own if the board prints one, an assigned one if not — and recorded with its type, its value read from its markings, and, for every integrated circuit, its full part number captured from the package. The inventory is built in a consistent order — a grid, or region by region — so that every part is reached exactly once and none is skipped, and when a marking is worn away the value is measured with a meter rather than guessed or omitted. It turns a board from an undifferentiated mass of parts into a complete, referenced list of what is present, which is the raw material from which a board map and, later, a recovered schematic are built.
  • board map — the assembled deliverable of board documentation: an annotated reference that combines the photographs and the component inventory into one navigable whole, marking each component's location on the board image, attaching its identity and value, and showing the board's organization into regions of power, signal, connectors, and interfaces. It is what makes the documentation usable at the moment of a repair decision, letting a technician point to any spot and know immediately what part is there and what role it plays, where a pile of raw photographs and a parts spreadsheet cannot. Built as a durable, organized artifact rather than scattered notes, the board map is the reusable product that makes a board — and every future repair of it — practical, the form in which the documented board is actually worked from.

Suggested Next Sections

Must read next:

  • Netlist Recovery from Physical Boards — Section 4.3 takes documentation to Professional depth on connections: reconstructing which pad connects to which — the netlist — from a physical board without its schematic, the layer of understanding the board map sets up but does not yet contain.

Recommended:

  • Reading a Complete Schematic — the finished schematic that documentation and netlist recovery ultimately reconstruct, read here as the destination the board map moves toward.
  • Schematic Symbols and Conventions — the notation a documented board is eventually expressed in, the language the inventory's parts are named and drawn with.