Artifacts and transmittals on the project record.
Controlled documents, drawing revisions, model federations, transmittals, RFIs, and submittals — evidence next to delivery, with lineage into FyDrive and AlphaCore when a canonical home is required.
Issued
86
In review
12
Open RFIs
5
Transmittals
31
DRW-0412 · Civil
Foundation GA · Rev C
SPEC-110 · MEP
MEP coordination set
RFI-028 · Civil
Slab penetration clash
TRM-019
Issue for construction
Files should not be a side system.
Controlled documents fail when the register, revisions, and formal issue live outside the project. Evidence belongs on the delivery record.
The shared-drive pile
Drawings and specs live in a folder tree nobody trusts. “Latest” is a filename suffix — and the wrong one still gets issued.
Transmittals as email
Formal issue happens in threads with attachments. Recipients, acknowledgements, and what was actually sent are tribal knowledge.
Handover archaeology
Audits and closeout start with a search across drives. RFIs and submittals aren’t linked to the packages they moved.
Documents and drawings with a status.
Document types, disciplines, numbering patterns, and register states — draft through issued, superseded, void, and archived. Models & drawings sit beside the document surface when enabled.
Register by status
- DRAFT18
- IN REVIEW12
- ISSUED86
- SUPERSEDED41
- ARCHIVED57
Document types
- DRW
Drawings
Discipline + drawing profile
- SPEC
Specifications
Discipline
- RPT
Reports
Optional discipline
- SUB
Submittal packages
Review workflow
Issue a controlled revision.
Share, submit, review, approve (with or without comments), issue, or void — with artifact roles for native, PDF, viewable, signed, and supporting files. Relations track supersedes, references, and responds-to.
DRW-0412 · Rev C · Artifacts
Issued · supersedes Rev B
- NATIVEfoundation-ga.dwg
- PDFfoundation-ga-revC.pdf
- VIEWABLEfoundation-ga-revC.svf
- SIGNEDfoundation-ga-revC-signed.pdf
Formal issue as a record.
Issue transmittals with recipients and delivery state — queued, sent, delivered, acknowledged, declined, failed. Provenance stays on the project, not in an inbox.
Recent transmittals
- ACKNOWLEDGED
TRM-019 · 6 recipients
Issue for construction · Civil set
- DELIVERED
TRM-018 · 4 recipients
MEP IFC package
- SENT
TRM-017 · 3 recipients
Commissioning procedures
Communication as a register.
Open and overdue RFIs, submittal rounds, and decisions sit on the project communication register — linked to the documents and packages they move.
Open RFIs
5
Overdue RFIs
1
Open submittals
8
Overdue submittals
2
RFIs
RFI-028
Slab penetration clash at grid C/4
Overdue · Schedule
RFI-027
Fire damper access clearance
Due Fri · Cost possible
Submittals
- Pending
SUB-014 · Round 2
HVAC equipment data sheets
- Approved
SUB-013 · Round 1
Structural steel mill certs
Drive and records without a fork.
Projects documents are not an island. Artifacts resolve through FyDrive; federations cover models; AlphaCore holds the canonical record when contract continuity requires it.
FyDrive lineage
Versioned files stay permissioned in FyDrive and linked from the project revision — not copied into a second dump.
Model federations
Link coordination models into federations so clash and coordination context stays with the drawing surface.
AlphaCore continuity
When a document needs a canonical contract or records home, the AlphaCore link stays intact from Projects.
Keep evidence next to delivery
Controlled register, revisions, transmittals, RFIs, and submittals — linked to FyDrive and AlphaCore when a canonical home is required.