Kroo Data Syncers

By audience

General Contracting

• Keeps the GC's own Autodesk Forma (ACC) RFIs and submittals aligned with the architect's separate tenant, so neither side re-keys the record.
• Kroo's own general-contractor page names this workflow directly: duplicating RFI and submittal data across two project-management systems between the GC and the owner or architect.
• Bartlett Cocke, a Texas GC, reports eliminating up to 30 hours per project per month of manual RFI and submittal entry.
• Status changes propagate as records are created, reviewed and closed, so project teams stop reconciling two copies by hand.

Specialty Contracting

• Kroo's specialty-contractor page names duplicating information across two distinct project-management systems between the specialty contractor and the GC as the workflow this automates.
• A sub running its own project-management system stops re-entering the GC's RFIs and submittals to stay aligned with them.

Architecture

• Architects working with a contractor on a separate Autodesk Forma (ACC) tenant see RFIs and submittals in their own environment instead of being asked to work in the contractor's.
• Kroo's customer case study is written around keeping RFIs and submittals in sync with the GC's architects, and reports reduced administrative overhead on the architect side as well as the contractor's.
• Supporting file attachments move with the record, so the architect's copy carries the same documents.

By phase

Construction

• RFIs raised during construction reach the counterpart system as they are created, reviewed and closed, so both parties act on the same status.
• Submittals follow the same path, with attachments kept consistent between the two tenants.
• Removes the double-entry step that otherwise sits between the contractor's construction-administration workflow and the design team's.