QQuantumSteel Design

Your browser. Your workspace.

Project Consistency Checker

Check saved steel project records for duplicate marks, quantity differences, mixed length units, missing drawing references, and associations that need review.

Find record disagreements before the next handoff

Use this checker to identify data questions worth resolving before issuing a package. It checks the loaded records only. It cannot read design intent, verify a connection, certify a material, or determine whether a drawing has been approved.

Files and project data are processed in your browser. Nothing is uploaded. A coordination review is a snapshot: source tools are never changed, and fresh source changes require a new snapshot. Save or export work you need to retain.

Load your project records

Start in Project Workspaces to create a project. Save takeoffs, drawing registers, and RFIs to it. Operations records use the same project identifier; purchasing uses an exact project name or reference match. Unsupported or unreadable individual sources are reported below.

Opening a file replaces this tab's review after confirmation if there are unsaved edits. It never imports into the original project tools.

No project loaded

    The three coordination tools share one saved review. Save before moving between them. Export JSON before clearing browser storage. Concurrent changes in another tab block saving until you reload.

    Worked example: a beam changes after an order

    This fictional service platform has two B1 beams, each 20 feet long, in takeoff A. Takeoff B changes B1 to three beams, each 22 feet long, adds B2, and removes B3. PO-001 still shows two W12X26 pieces, and the shop batch still contains two B1 pieces.

    1. Load the fictional example. In the explorer, search B1. Its drawing and order are explicitly linked. RFI-001 only matches the drawing reference, so its effect still needs review.
    2. Open the impact report with takeoff A before takeoff B. The entered USD 875 and two-day adjustment for B1 are teaching assumptions. They stay outside confirmed totals until you choose a decision and apply the impact note.
    3. Run the consistency checker. It flags the unmatched S999 RFI reference, mixed takeoff units, the B1 quantity difference, and the distinct A1 assembly mark for review.
    4. Record the outcome, export the review, and make approved corrections in the original tools. Loading a fresh snapshot starts a new review without silently carrying decisions across changed input.

    Download the fictional review JSON. The file can be inspected in a text editor before loading it.

    Troubleshooting

    If a mark is missing, check the selected project, save the source record, and load a fresh snapshot. If a drawing reference contains several numbers, review them separately: only an exact whole reference is matched automatically. If storage is blocked or full, keep working in memory and export JSON. A corrupted stored review is preserved instead of overwritten.

    Common questions

    Are mixed units necessarily an error?

    No. A takeoff may intentionally use feet and meters. The checker flags mixed input units so you can confirm them; the revision comparison converts lengths before comparing them.

    Why are different revisions not added together?

    A previous takeoff and a current takeoff are alternative versions of a requirement. Adding them would duplicate demand. Quantity comparisons use only the takeoff selected as current.

    Does zero findings mean the project is ready for fabrication?

    No. It means none of these limited checks found a listed inconsistency in the loaded data. Source completeness, dimensions, tolerances, connection requirements, approvals, and release authorization still need their normal reviews.

    Continue your project review

    Piece mark explorer ? Revision impact report ? Project consistency checker ? Drawing register ? RFI log ? Purchasing and receiving