Findings Die Without a Route. One-Click RFI Fixes That.
Finding the issue is only half the job.
A door tag with no schedule row, a schedule line with no tag on the plan, a callout that points nowhere: MarkedUp flags those. If nobody routes them to drafting, engineering, or the design partner who owns the sheet, the finding sits. Then it walks into the field as an RFI you write under pressure, or as the wrong hardware, or as a claim about a design error you saw and did not raise.
One-Click RFI is the handoff. It turns selected audit findings into an RFI you review and send, with sheet references and boxed evidence already filled in. MarkedUp routes the problem. Your existing RFI home stays where the RFI lives.
This post is the training companion to a short walkthrough. Watch it, then run the same steps on a live set.
~2 minute walkthrough: One Click RFI Resolution in MarkedUp
The problem the Loom opens with
In the recording, the set already has core audit results: a door schedule and a batch of missing tags. Those are the boring misses that still burn time. They are also easy to leave in a findings list while the week moves on.
One-Click RFI sits next to those results. The point is not another log to babysit. The point is to get the question in front of the people who can change the drawings.
Step 1: Pick the findings
Start from the audit results on the project. In the Loom example, the open items are door schedule and tag misses. Select the ones that belong in an RFI now.
MarkedUp is not a chatbot and does not use general AI models. It runs the same integrity checks on every sheet, then lets you turn the ones that matter into a dated, documented request. A person still decides what goes out.
Step 2: Bundle or keep them separate
You get two clean choices:
- Separate RFIs when each miss needs its own assignee, due date, or answer.
- One bundled RFI when related misses share one question. The designer gets a single request with an itemized list instead of a pile of near-duplicates.
For door tags that all fail the same way against the schedule, bundling is usually the clearer read. Split when the answers will diverge.
Step 3: Review, then send one RFI with history
Nothing leaves until someone on your team clicks Send. Before that, you set assignee, due date, and any proposed solution. Sheet references and boxed evidence travel with the finding so the recipient is not hunting the set for context.
In the walkthrough, a single bundled RFI goes out by email. After send, MarkedUp keeps the history of what you created. For live pushes, RFI numbers and Open or Answered status show across the integrations you use. That is status for the handoff, not a replacement RFI system.
Where it can go today:
- Email from your own inbox, with the RFI PDF and an xlsx issue list attached
- Autodesk RFI push
- Trimble RFI push
- Procore RFI push: coming soon (not live yet)
Say that last line out loud when you train a team, so nobody assumes Procore RFI push is already shipping.
Step 4: Read the results, then leave RFIs where they already live
Results can land in email or as a downloadable XLS. The spreadsheet carries a project summary, the combined RFI details (location and suggested resolution), and a log of where the issues sit on the set.
That is the product boundary. MarkedUp helps you route problems to internal drafting and engineering, or from preconstruction and operations out to design partners. It is not becoming the RFI tracking system or the log of record. Email, Autodesk, and Trimble (and Procore when that push lands) remain where RFIs live and get answered.
One-Click RFI is a MarkedUp add-on. If your office already runs the integrity checks and needs the handoff next, ask for it on a live set rather than inventing a second place to track RFIs.
Watch it once, then run it on your set
The Loom is short on purpose. Watch the ~2 minute walkthrough, pick a door schedule or tag miss on a real package, decide bundle vs separate, review, and send.
Watch: One Click RFI Resolution in MarkedUp (~2 minutes)
Book a meeting and we will walk the same flow on one of your packages.