OrielRequest a pilot

Get it in writing. Every time.

Every question lives pinned to the exact spot on the drawing. The person who owes you the answer gets one link, no account, and their response files itself. When someone asks who approved this, you have the record.

  • Pin the question where the problem is
  • Answers come back through a link, not a login
  • Photos, revisions, and history stay attached
  • Nothing overwritten, everything exportable
Request a pilotSee the workflow ↓
9.7 days

Median time to get an RFI answered.

22%

Never get an official answer at all.

$1,080

The cost to process a single one.

Navigant Construction Forum, a 2013 study of 1.1 million RFIs across 1,362 projects.

How an RFI dies today

You already know how this goes.

A foreman hits a conflict and texts a photo to the super. The super calls the PM. The PM retypes it into an email, attaches a marked-up PDF, and sends it to the architect. The architect replies to an older thread, and the answer lands buried under a signature block. Nobody forwards it to the sub. The wall gets built to the old detail. Eight months later, someone asks who approved this, and nobody has the record. Now it's a change order fight, and the side with the worst paperwork loses.

The question was never the problem. The paper trail was.

The Oriel workflow

Three steps. No training.

1

Pin it

Click the spot on the sheet, type the question, attach the photo. Oriel numbers it and starts the clock.

2

Send one link

The architect, engineer, or sub opens it in a browser. They see the pin, the sheet, the question, and the photos. They answer right there. No account, no download, no software to learn.

Design Partners
review.oriel.build/r/7K9D2…
May 24, 2026 · revocable
Send link
3

It files itself

The response lands on the pin, word for word. The log updates, the crew gets notified, and the clock stops. Every step timestamped. Nothing editable after the fact.

RFI-0234
Response received

“Provide a 1-hour rated wall at this location, per Specs 07 21 13 and Detail 2/A6.201.”

Maria Chen · Design Partners
May 13, 2026 · 2:47 PM · on the record

A record that holds up

Built for the day someone questions it.

Every RFI in Oriel is append-only. Questions, answers, photos, and markups are timestamped and never overwritten.

Revisions keep their history

Supersede a drawing and the old pin stays put, tied to the revision it was asked against, so the history reads exactly as it happened.

Export any day

The entire log, in one click, in a format a mediator can actually read.

Still yours when the job closes

Not locked in someone else's account. Yours.

External review

Your architect is never going to log into your software.

Neither is the structural engineer, or the sub's PM. That's why answers die in email today.

Oriel sends a link instead. One click, full context, a reply box. Their answer files itself into your record exactly as they wrote it. You get the response. They never create an account. Nobody buys a seat.

The clock runs itself

Stop being the person who chases.

Every RFI carries a due date. Whoever holds it gets reminded before it's late, not after. The log shows whose court every open item sits in and how long it's been sitting there, so the Monday call changes from “where are we on these” to “here's what's overdue and who owes it.”

Security and control

Private, attributable, and portable.

Files
Private file storage

Nothing lives on a public URL. Every file is served through a signed, expiring link, issued only after authorization.

Tenancy
Organization isolation

Every organization's data is isolated at the database and storage layer, deny-by-default, with strict access boundaries.

Review links
Scoped, expiring, revocable

External links are scoped to one record, expire on their own, and can be revoked instantly, at any time.

History
Immutable by design

All material actions are timestamped and preserved. Edit nothing. Hide nothing. Export everything.

Who it's for

Built for the GC doing $10M to $150M.

The big platforms price by your annual volume, take a quarter to implement, and still can't get your architect to log in. Oriel does one thing: it gets your job questions asked, answered, and on the record, on your drawings, without asking a single outsider to make an account. If you're running a full enterprise platform and it's working, keep it. If your RFIs live in Outlook, this is for you.

Straight answers

The questions a skeptic asks first.

Will my architect actually use it?

They click a link and type an answer. If they can reply to an email, they can answer an Oriel RFI. The difference is the answer lands in your record instead of a thread.

Do subs, architects, or consultants need accounts or licenses?

No. Nobody outside your team ever creates an account.

Where do our files live?

In private storage. Nothing is ever on a public URL. Every file is served through a signed, expiring, server-authorized link.

What happens to our data if we leave?

Export everything, any time: the log, every response, every attachment, every timestamp. The record is yours, full stop.

How long does setup take?

Upload a drawing set and send your first RFI the same afternoon. There is no implementation project.

What happens when drawings get revised?

Pins carry their revision. Upload the new set and old pins stay tied to the sheets they were asked against, while the current set shows what's still open.

Is this a Procore replacement?

It replaces the email chain where your RFIs currently go to die. It doesn't try to be your accounting, bidding, and scheduling platform.

Is there AI writing on my record?

No. Nothing writes on your record except the people on your project. Where Oriel assists, you review and sign; the record only ever carries what people wrote.

Roadmap

Things you stopped expecting software to do.

Pinned RFIs and the record are the spine. This is what gets built on it.

Field
Text it in

Your super's camera roll is full of questions that never became RFIs. A text and a photo to the project number will be enough: Oriel drafts the RFI, you drop the pin, and the field never opens an app.

Cost
The money flag

Some answers add work, and today you find out at the pay app. Oriel will read every response as it lands, flag cost and schedule impact on the spot, and hold a scope-changing answer at the gate until a change order is started or someone signs off on why not.

Claims
The notice clock

Your contract gives you 21 days to put a claim in writing, and most GCs start counting after the window shut. Oriel will run the clocks straight from your contract, warn you while there's still time, and draft the notice for you to review and send.

Answers
Ask the drawings first

Roughly one in eight RFIs is already answered in the documents, and the standard AIA contract now lets the owner charge you for asking. Oriel will search your specs, your sheets, and every question your company has answered before, then hand back the answer with the citation. Some questions never leave the trailer.

Pilot partners get each of these first, and shape what ships. Request a pilot →

Private pilot

We're onboarding a small number of pilot GCs.

You get Oriel shaped around your live jobs and a direct line to the people building it. We get the truth about what survives contact with the field. Pilots run on real projects, and your data stays yours from day one.

By requesting a pilot you agree to our Terms and Privacy Policy.