| RFI and submittal management is the process of logging, routing, answering and approving requests for information and technical submittals during construction. Delays start when items are copied by hand between systems. Newforma Konekt logs RFIs and submittals directly from email, and its Procore connector moves them between Procore and Konekt without typing them twice. |
This guide follows an RFI or a submittal from the moment it is raised to the moment it is closed. It explains why this stage of construction administration slows projects down, what a reliable log needs, how Newforma Konekt handles both items, how the Procore connector works, and which practical rules make responses faster.
Why RFI and submittal management slows projects down
RFI and submittal management sits at the busiest point of construction administration. A request for information (RFI) asks the design team to clarify something on the documents. A submittal sends technical documentation, such as product data or shop drawings, for approval. Both have deadlines, and both pass between organizations that use different tools.
On international projects in Latin America, the design team may work in one system and the contractor in another. Items are re-typed, attachments are downloaded and uploaded again, and the status in one log drifts away from the other.
The cost is not only time. When an RFI waits too long, the site either stops or proceeds on an assumption, and both outcomes create risk for the contractor, the designer and the owner.
• Double entry between the contractor’s and the designer’s systems.
• Answers sent by email that never reach the official log.
• Unclear ball-in-court, so nobody knows who owes the next step.
• Revisions of the same submittal mixed in several folders.
The two items are often discussed together but behave differently. The table summarizes the differences that matter for tracking:
| Aspect | RFI | Submittal |
|---|---|---|
| What it is | A question to the design team about the contract documents. | Technical documentation sent for approval. |
| Who raises it | Usually the contractor or a subcontractor. | The contractor, on behalf of a supplier or trade. |
| Who answers | The design team, by discipline. | The design team, reviewing against the specification. |
| Typical attachments | Sketches, photos, marked-up drawings. | Product data, shop drawings, samples, calculations. |
| Where delays start | The question is unclear, or the answer is sent outside the log. | Several revisions circulate and the reviewer cannot tell which is current. |
“Ball in court” deserves a note. It names who owes the next action on an item at any moment. When it is unclear, items sit unattended because each party assumes the other is responsible. A log that always shows the ball-in-court person removes that ambiguity.
What a good RFI and submittal log needs
A reliable log records each item once and keeps its full history: who asked, who answered, which documents were attached and when each step happened. It should link the item to the drawings, models and emails it refers to, so a reviewer does not have to search for context.
A good log also makes reporting easy. Project managers should be able to see overdue items by discipline in seconds, and owners should be able to check status without asking for a spreadsheet.
• One record per item, with status and due date.
• Attachments and revisions kept with the item.
• The email trail linked, not lost in inboxes.
• Search across all items and related correspondence.
An RFI follows a simple lifecycle, and a good log makes each step visible:
• 1. Raised. The item is created with a clear question and a reference to the drawing or specification.
• 2. Routed. It goes to the right discipline reviewer, with a due date.
• 3. Reviewed. The reviewer consults the documents and, if needed, other disciplines.
• 4. Answered. The response is issued through the log, with any attachments.
• 5. Closed. The requester confirms and, if the answer changes the contract, a change is initiated.
How Newforma Konekt handles RFIs and submittals
Contract administration in Newforma Konekt covers RFIs and submittals, and both can be logged directly from email. That matters because most requests and answers still arrive in Outlook. Konekt also includes document control and contract change management, so a response that leads to a change stays connected to it. The manufacturer reports 6 million submittals managed on its platform.
Contractors have a second option. Newforma Constructex is a cloud product built for construction companies, with RFI and submittal management, document control, field management and file sharing.
For design teams, this means the person who receives a question by email can turn it into a tracked item without leaving the conversation. The Konekt Outlook add-in lets users forward and respond to RFIs and submittals from the mailbox, so the answer goes through the log instead of around it.

The Procore connector: one item, two systems
Many contractors run Procore while design teams work in Konekt. The published Procore connector transfers RFIs and submittals between Procore and Konekt, so nobody types the same item twice. Newforma says it saves up to 12 minutes per item.
Shive-Hattery, a design firm that integrated Konekt with Procore, reported cutting the response time for RFIs and submittals by about 50% and saving between USD 1,000 and 3,000 per project. SFCS Architects reported reducing the time spent on construction administration by about 75%. These are the results of those customers, not a guarantee, but they show where the hours go.
The connector, which Newforma released in February 2024, works in a defined sequence according to Newforma’s documentation:
| Step | Who does it | What happens |
|---|---|---|
| 1. Install the app | A Procore administrator. | The Newforma Konekt app is installed in the company’s Procore account from the Procore Marketplace, and project webhooks are configured. |
| 2. Connect the project | A Konekt project administrator. | The Konekt project is linked to the Procore project from the RFIs or Submittals page. |
| 3. Receive items | The design team. | RFIs and submittals assigned to a ball-in-court user in Procore arrive in Konekt as pending incoming items. |
| 4. Review and answer | The design team. | The review is completed in Konekt, and the answer or reviewed submittal is sent back to Procore. |
Two details help set expectations. Existing open items are transferred in batches every ten minutes, and real-time syncing can be enabled for faster updates. And only items that arrive through Procore can be returned to Procore: emails filed as RFIs or submittals through the Outlook add-in stay in Konekt.
Practical rules for faster responses
Software removes double entry, but response times also depend on habits. Teams that answer quickly tend to agree on a few rules at kickoff and review them at each progress meeting.
• One question per RFI, with a clear reference to the drawing or specification.
• A named reviewer for each discipline and a backup when that person is away.
• Response times agreed in writing and visible in the log.
• Submittals reviewed in the order the construction schedule needs them.
• Every answer issued through the log, even when it was discussed by phone.
Four measures show whether the rules are working. Average response time per discipline reveals where answers are slow. The number of overdue items shows the backlog. The share of RFIs that need a clarifying follow-up points to unclear questions. And the number of answers issued outside the log shows whether the habit has taken hold.
A few pitfalls appear often when a team introduces a shared workflow. Reviewers are not told that an item is waiting for them, so notifications and reminders matter. Items are raised with several questions at once, which makes them slow to answer and hard to close. And the connector is configured but nobody agrees who owns each type of item, so the ball stays in the air.
Setting up RFI and submittal workflows with Aufiero
Before configuring any tool, agree on numbering, response times and who reviews each discipline. Then connect the contractor’s platform. Aufiero Informática, the official Newforma distributor and a regional wholesale software distributor for Latin America with more than 90 brands, supports implementation and training in Spanish and Portuguese, which helps design teams and local contractors follow the same workflow.
Review the log together after the first month. Most delays show patterns, such as one discipline or one type of submittal, that are easy to fix once they are visible. You can see the options at Newforma at Aufiero.
Moving RFIs and submittals between your design team and a Procore contractor? Talk to Aufiero about connecting the workflow with Newforma.
Frequently asked questions
What is the difference between an RFI and a submittal?
An RFI asks the design team to clarify something in the contract documents. A submittal sends technical documentation, such as product data or shop drawings, for approval. Both are part of construction administration.
Can Newforma log RFIs directly from email?
Yes. In Newforma Konekt, RFIs and submittals can be logged directly from email. The email trail stays linked to the item.
Does Newforma integrate with Procore?
Yes. The Procore connector transfers RFIs and submittals between Procore and Newforma Konekt without double entry. Newforma says it saves up to 12 minutes per item.
What results have firms reported with Newforma and Procore?
Shive-Hattery reported cutting RFI and submittal response time by about 50% and saving USD 1,000 to 3,000 per project after integrating Konekt with Procore. These are that customer’s results, not a promise.

