Connect and Keep: You Love Forma. Your GC Loves Procore. Nobody Has to Give Anything Up.
If you’re a design firm, you already know why Forma has become such a big part of how you work. The model collaboration, clash detection, issue tracking, RFI and submittal management. It’s not just software you tolerate. It’s the software you chose. Your team is fast in it. Your workflows are built around it.
You also already know that when a project kicks off, the GC is going to be running things in Procore, Forma, or something else. Every project comes with a different construction management platform on the other end of the table, and the industry has just kind of accepted that as the cost of doing business.
The question has never been whether your tool and theirs are different. It’s what everyone is supposed to do about it. Historically, they log into their system and re-enter everything, email files back and forth, and quietly turn a team member into a full-time translator. Each path comes with a real cost that nobody puts on the invoice.
There’s a better way. And it starts with a simple idea: nobody has to give anything up.
Connect and Keep
That’s the whole thesis. Your team keeps working in Forma. The GC keeps working in Procore, Forma, Newforma, etc. Nobody switches platforms. Nobody imports and exports. Nobody types anything twice. The connections in the background make sure everyone sees what they need to see, in the tool they already live in.
Your models. Your design work. Your submittal responses. Your RFI answers. All stay in the environment your team already knows. Their RFIs, submittals, and issues stay in theirs. The data flows between the two automatically, and everybody keeps everything.
No Duplicate Entry, No Duplicate Mistakes
Duplicate entries aren’t just annoying, it’s risky. Every time someone on your team types the same submittal response into two different systems, it’s not just wasted time but an opportunity for mistakes. A number that gets transcribed slightly wrong. A revision that gets logged in one place but not the other. A comment that made it into the GC’s platform but never made it back into your own record. And the day that mismatch comes up in a dispute, you’re the one explaining why the two versions don’t match.
When you enter something once, in the tool you actually work in, that entire category of error disappears. Not “reduced”, it disappears. Your record and the GC’s record are the same record, because they’re connected instead of copied.
Nobody Has to Learn a Tool They Don't Use
Here’s the other quiet ROI that never shows up in a project presentation: your team doesn’t have to keep re-learning Procore.
You know how this goes. Someone on your team gets an RFI and has to log into the GC’s platform to respond. It’s been three weeks since they were last there. The menu’s moved. The workflow’s slightly different from the last project because it’s a different GC’s instance. They spend ten minutes just finding the right button, and another five second-guessing whether they clicked the right thing. Multiply that across every RFI, every submittal, every issue, every project, every team member.
Your designers were hired to design. Not to maintain working knowledge of five different construction management platforms depending on which GC they’re partnered with this month. Connect and Keep means they don’t have to. They work in Forma. That’s it.
Yes, But What About the GC?
Fair question. If you’re the GC, you’re probably wondering how any of this works for you. RFIs, submittals, and issues are your lifeblood. You need to know when a response comes back. You need it in your system, in your log, on your dashboard and not living in someone else’s account.
That’s exactly where the connection earns its keep. When the design team responds to an RFI in Forma, that response flows into Procore automatically. When they update a submittal, the update lands where you need it. Issues close on their side and close on yours. Nothing gets stuck between systems. Nobody has to remember to send anything.
You don’t lose visibility, you gain it. Instead of chasing the design team for status, you’re watching updates arrive on their own, in the platform you already live in.
So Here's the Question
For years, cross-firm collaboration has been treated as a battle over which platform everyone should standardize on. What would your projects look like if you never had to give up the tool you love — and neither did anyone else on the team?
Enter: ATG Connect. With ATG Connect, a new tool to sync your project data and metadata across Forma, Procore, SharePoint, and Egnyte (more coming soon), you can eliminate data silos, streamline cross-platform collaboration, and gain unprecedented control over your project data, enabling full transparency and visibility into all active connections and data syncs.
