7.2 Project Documentation and Reporting

Why documentation is a project management skill

A BICSI Technician is the bridge between the crew and the project's engineer of record, general contractor, and owner. The paperwork that flows across that bridge — RFIs, submittals, daily reports, test reports, certification records, and the final handover package — is what allows the project to be built, certified, warranted, and turned over. The written exam treats these as distinct artifacts with specific purposes; confusing them is a common wrong-answer pattern.

Requests for Information (RFIs)

An RFI is a formal written question submitted by the contractor to the designer or owner when the contract documents are unclear, ambiguous, conflicting, or incomplete. The Technician writes or reviews RFIs for the cabling scope. Typical ICT RFIs ask:

• Which standard applies when two are cited (e.g., TIA-568 vs an earlier edition referenced in the spec)?
• Where is the demarcation between the owner's cabling and the carrier's entrance facility?
• What is the required firestop design for a sleeved penetration that does not match any listed system?
• Which outlet type is intended in a location shown but not scheduled?

A well-written RFI states the question, cites the drawing or spec that triggered it, offers a proposed interpretation, and requests a written response by a date. RFIs are tracked in a log; the response becomes part of the contract record and may authorize a change order. A Technician should never proceed with an assumption based on an oral answer — get it in writing.

Submittals

Submittals are contractor-prepared documents and samples submitted to the designer for approval before fabrication or installation. For ICT cabling, common submittals include:

• Product data sheets for cable, connectors, patch panels, firestop systems, and bonding components.
• Shop drawings for fabricated pathway elements (custom racks, ladder rack assemblies, cabinet layouts).
• Samples (rare in cabling, but a label sample or faceplate sample may be requested).
• System design/installation qualifications for specialized work such as fusion splicing or MPO arrays.

The submittal review confirms that what the contractor intends to furnish matches the specified performance. A Technician should verify that submitted cable categories match the spec (e.g., Cat 6A, not Cat 6) and that the firestop system submitted has a listed design number that matches the wall or floor assembly on the project. Proceeding with non-approved materials is a warranty risk.

Daily reports

A daily report is the project's contemporaneous record. The Technician or crew leader produces one each day work is performed. It contains:

• Date, project, and report number.
• Weather conditions (relevant for outdoor pathway work).
• Crew members and hours, by area.
• Work performed — pathways installed, cable pulled, terminations made, tests run.
• Materials received and inspected.
• Delays and their cause (waiting on other trades, missing information, owner directive).
• Safety observations and any incidents, no matter how minor.
• RFIs submitted, submittals returned, and change orders received.
• Photographs.

Daily reports are the primary evidence in a dispute. If the owner later claims the cabling was installed late, the daily report showing the crew was on site but blocked by the GC's drywall schedule is the contractor's defense. Conversely, a gap in the daily record invites the question: was work actually performed that day?

Test reports and certification records

Test reports are the machine-generated outputs of the field testers. For copper, each permanent link and channel is tested to TIA-568 limits (NEXT, return loss, length, propagation delay, delay skew, and PS measurements) using a certifier such as a Fluke Versiv or WireXpert. For fiber, each link is tested with a light source and power meter (OSL) for insertion loss, and longer runs may also be tested with an OTDR.

The Technician's responsibility is to ensure:

• Every required link is tested — none skipped.
• The test equipment is calibrated and the correct adapter and limit set is loaded.
• Each test result is identified by cable ID that matches the as-built schedule.
• Failures are corrected and retested, with the original and retest results both retained.
• Reports are exported in PDF and machine-readable (e.g., .flkproj) formats.

Certification records are the curated subset of test results that demonstrate compliance with the specified standard. They are part of the warranty package and may be required by the manufacturer for the warranty to be valid.

The handover package

At project closeout the Technician assembles the handover (closeout) package delivered to the owner. A complete ICT handover package typically includes:

1. As-built drawings (covered in 7.1).
2. Cable and outlet schedules with unique identifiers.
3. Link maps tying work-area outlets to patch-panel and switch ports.
4. Certification test results — copper and fiber, in PDF and machine-readable formats.
5. OTDR traces for backbone and long horizontal runs, where specified.
6. Bonding and grounding records with measured resistance values.
7. Firestop documentation — listed design numbers, installed locations, and installer qualifications.
8. Warranty certificates from the cable and connector manufacturers, often requiring registration.
9. Operation and maintenance data for any active equipment in scope (rare for cabling-only work, but included when the project includes switches or wireless APs).
10. RFI and change-order log showing the final agreed scope.
11. Spare parts and leftover materials inventory.

A handover package that omits the certification records or the link map is not complete; the owner cannot operate or maintain the system without them. Many manufacturers' warranties are void if the certification records are not delivered to the owner within a defined window after project completion.

Reporting during the project vs at closeout

A common exam trap is to confuse ongoing reporting (daily reports, RFIs, submittals) with closeout deliverables (as-builts, certification records, handover package). The distinction: ongoing documents drive project decisions in real time; closeout deliverables transfer the system to the owner. Asking "when is this artifact used?" is the fastest way to tell them apart on the exam.