Read Plans Legends and Schedules

First step

Make a fictional sheet header with sheet number, title, date and revision. Fictional givens: practice sheet E-201, title "Level 2 Lighting", date 2099-05-02; the title block shows revision R2, but the revision cloud note says R3; tag LX-4 appears on the plan, and the mock schedule has rows LX-4A and LX-4B. Before reading the model in done_right, write the header with a status for each field, plus the tag trace status.

The header makes the exact practice sheet version identifiable. Worked model from the givens: sheet number E-201 = recorded; title = recorded; date 2099-05-02 = recorded; revision = UNKNOWN (title block R2 vs cloud note R3, both locations noted, question to the designated reviewer role); tag trace LX-4 = OPEN (matches neither LX-4A nor LX-4B exactly). Changed condition: the fictional designated reviewer confirms that R3 is the controlling revision of E-201, and says nothing about LX-4. Worked retry: mark only the revision field CONFIRMED as R3 (fictional reviewer note, dated); the LX-4 tag trace stays OPEN with its schedule-row question; no drawing approval or installation instruction follows. The reviewer note is fictional; no actual reviewer replied.

Using a sheet title alone makes two revisions look like the same source. First error in this exercise: picking R2 because it is printed in the title block, or, after the reviewer note, writing "sheet confirmed, LX-4 = LX-4A." Correction: revision stays UNKNOWN until the reviewer answers, and the reviewer note closes only the revision field; the LX-4 trace stays open.