Section 1The page
The page title is Search, Filter & Investigate Individual RFIs. The question on the header is which RFIs require review, follow-up, or document action. The first three pages count the project, the document changes, and the parties. This page is the row behind each count.
Filters sit on the left: an RFI number search, a party list, status, discipline, and document impact. Four cards sit across the top. The register table fills the rest of the page. It is sorted by RFI number. Question Summary is the start of fact_rfi.question, shortened so the row stays one line. The full question and the response stay in the fact table.
Section 2Live report
The published report is rif_vis. The bar under the frame switches pages: executive, Drawing & Specification Change Analysis, COORDINATION & RESPONSIBILITY, and RFI Register.
This chapter is dashboard 4. Use the arrows beside 4 of 4 to open the RFI Register. Page 1 is the executive dashboard. Page 2 is Drawing & Specification Change Analysis. Page 3 is COORDINATION & RESPONSIBILITY.
Section 3KPI cards
The four cards match the earlier pages, and they recount whatever the filters leave in view.
| Card | Unfiltered | Meaning |
|---|---|---|
| Total RFIs | 107 | Rows left after the current filters |
| Open RFIs | 8 | Those rows with a blank response |
| Response Rate | 92.52% | Answered rows divided by the rows in view |
| Document Update RFIs | 19 | Rows whose document-update flag is Yes |
Setting status to Open leaves eight rows. All eight are unanswered, so the response rate becomes 0%. All eight have document impact Unknown, so the document-update card becomes 0.
Section 4Filters
The RFI number box searches fact_rfi.rfi_id. Typing RFI-008 leaves that one row: Architectural, Specification Clarification, submitted by DAVID BOLAND, INC, tasked to AE, document impact Both.
Status is Answered or Open. Discipline is the ten names from dim_discipline. Document impact is five labels built from the drawing flag and the specification flag.
| Document impact | RFIs | Flags |
|---|---|---|
| Both | 16 | Drawing Yes and specification Yes |
| Drawing only | 2 | Drawing Yes and specification Unknown |
| Specification only | 1 | Specification Yes and drawing Unknown |
| No update | 51 | Both flags No |
| Unknown | 37 | Both flags Unknown |
| Total | 107 |
The party slicer is titled party_name and lists all 16 names in dim_party. The filter uses the active relationship, from_party_key, so it keeps the submitter. Six names return rows: DAVID BOLAND, INC (71), Carbon Recall Chattanooga (11), and Willdan, Dobco, Inc., and Richard Group LCC (8 each), plus Schweitzer Engineering Laboratories, Inc. (1). The other ten names are tasked parties. Selecting AE, CT, JBMDL, PM, or USACE DB leaves the register empty.
The received date is on every row, shown as year, month, and day. There is no answered date, so this page does not show days open or a response-time target.
Section 5The register
Each row is one RFI. The columns are the RFI number, the received date split into year, month, and day, status, discipline, issue type, originating party, responsible party, the question preview, and document impact. The table below is the first 10 of 107, in RFI number order.
| RFI | Received | Status | Discipline | Issue type | Submitter | Tasked | Impact |
|---|---|---|---|---|---|---|---|
| RFI-001 | 1 Sep 2026 | Answered | Electrical | Material Requirement | Schweitzer Engineering Laboratories, Inc. | JBMDL | Unknown |
| RFI-002 | 2 Sep 2026 | Answered | Electrical | Drawing Conflict | Willdan | AE | Both |
| RFI-003 | 2 Sep 2026 | Answered | Other | Compliance Requirement | Willdan | CT | Unknown |
| RFI-004 | 2 Sep 2026 | Answered | Other | Design Clarification | Willdan | CT/PM | Unknown |
| RFI-005 | 2 Sep 2026 | Answered | Controls / SCADA | Interface Coordination | Willdan | AE/JBMDL | No update |
| RFI-006 | 2 Sep 2026 | Answered | Cybersecurity | Compliance Requirement | Willdan | AE/JBMDL | No update |
| RFI-007 | 2 Sep 2026 | Answered | Other | Compliance Requirement | Willdan | CT | Unknown |
| RFI-008 | 4 Sep 2026 | Answered | Architectural | Specification Clarification | DAVID BOLAND, INC | AE | Both |
| RFI-009 | 4 Sep 2026 | Answered | Quality / Inspection | Inspection / Quality | DAVID BOLAND, INC | AE | Unknown |
| RFI-010 | 4 Sep 2026 | Answered | Structural | Specification Clarification | DAVID BOLAND, INC | AE | No update |
The question preview for RFI-001 starts with the approved electric meter models for AMRS integration. RFI-002 starts with the battery energy storage system capacity discrepancy. RFI-008 starts with the finishes schedule and the paint specification.
Section 6The eight open RFIs
Filtering status to Open leaves these eight rows. All eight are discipline Other, all eight are tasked to CT, and all eight are document impact Unknown.
| RFI | Received | Issue type | Submitter | Question preview |
|---|---|---|---|---|
| RFI-086 | 14 Sep 2026 | Compliance Requirement | Willdan | FAR liquidated damages |
| RFI-092 | 16 Sep 2026 | Missing Information | Dobco, Inc. | Award date and notice to proceed |
| RFI-093 | 16 Sep 2026 | Compliance Requirement | Dobco, Inc. | New Jersey prevailing wage |
| RFI-095 | 16 Sep 2026 | Compliance Requirement | Dobco, Inc. | Tax-exempt certificate |
| RFI-096 | 16 Sep 2026 | Scope Gap | Dobco, Inc. | Percentage of work the contractor performs |
| RFI-100 | 21 Sep 2026 | Design Clarification | Richard Group LCC | Hand delivery of the bid |
| RFI-106 | 21 Sep 2026 | Missing Information | Richard Group LCC | Target date for funding |
| RFI-107 | 21 Sep 2026 | Material Requirement | Richard Group LCC | Adjusting the bid for material prices |
Section 7How to read it
Use the earlier pages to see the pattern, then use this page to find the row. Status Open is the eight-RFI backlog, all with CT. Document impact Both is the 16 RFIs that change a drawing and a specification. An RFI number in the search box opens that one record, with its submitter, its tasked party, and the start of the question.
The party list looks like every organisation on the project. It filters the submitter. A tasked party such as AE or CT has to be read from the Responsible Party column, or from the coordination page.