The problem
Electrical teams spend substantial time cleaning drawings and organizing layers before design work can begin — and then do it again every time the architect issues a revision.
This brief separates the two deliberately. Everything under "What SIFDR does today" is a capability the product has now. Everything under "Where DraftCore is heading" is intent.
Electrical teams spend substantial time cleaning drawings and organizing layers before design work can begin — and then do it again every time the architect issues a revision.
SIFDR cleans up the CAD baseplan on architect DWGs for MEP firms. It performs layer cleanup, duplicate reduction, and source quality review. It creates the reflected ceiling plan grid and cleans up existing RCPs. Reference points come back aligned, so the drawings XREF together.
SIFDR does not populate the RCP. That remains your engineer's work. Your engineer also reviews the cleaned drawing before it lands.
SIFDR is a tool that assists your engineer's work. It is not the final word, and it is not a compliance engine. Your engineer reviews the plans for accuracy, and the stamp is theirs.
SIFDR reads and writes DWG and DXF. It has its own CAD engine, so it fits the workflow you already have rather than replacing it. It also accepts PDFs exported from CAD that still carry layer information — scanned or flattened PDFs will not work, and PDF is an input only. One plan per upload: one floor, one unit type.
The architect moves a wall. On a revision you re-run SIFDR instead of cleaning the same drawing again, for the life of the project.
DraftCore is building toward the wider electrical design workflow — load calculations, circuiting, sizing, panel schedules, and riser diagrams. That is the direction of the company, not a description of what SIFDR does today. It is not built.
One free month of SIFDR, the full product. No card up front, nothing renews on its own. After the month we talk about what you saw and you decide whether to keep going. We onboard every firm ourselves — the product is in user-acceptance testing and we want your feedback.