ACELAB · RFI LOOP

ACELAB · RFI LOOP

From a missing product detail to an answer in the schedule.

From a missing product detail to an answer in the schedule.

I designed an end-to-end request workflow that connects architects and manufacturer reps—from selecting what’s missing to bringing the response back into the project.

I designed an end-to-end request workflow that connects architects and manufacturer reps—from selecting what’s missing to bringing the response back into the project.

Sole product designer · Stephen Sandberg, PM · Engineering team
Foundations April 2026 · Full loop shipped August 2026 · Enterprise Pro

Sole product designer · Stephen Sandberg, PM · Engineering team
Foundations April 2026 · Full loop shipped August 2026 · Enterprise Pro

My role

My role

I was the sole designer, working with product and engineering from discovery through launch.

Frame the problem

Interviewed architects and manufacturers, mapped the journey, and defined the opportunity.

Design the loop

Defined request ownership, shared statuses, and the send, response, and recovery flows.

Test and ship

Built an end-to-end prototype, aligned the team, and supported the launch.


The architect’s working table. Acelab's Schedules.

A schedule is a live table of the products selected for a building project. Rows represent products; columns hold details such as manufacturer, cost, lead time, and technical requirements.

Acelab Schedules: a live table of specified products with a comments panel and notes pointing to specifying products and managing fields

The architect’s working table. Acelab's Schedules.

A schedule is a live table of the products selected for a building project. Rows represent products; columns hold details such as manufacturer, cost, lead time, and technical requirements.

Acelab Schedules: a live table of specified products with a comments panel and notes pointing to specifying products and managing fields

PROBLEM & OPPORTUNITY

PROBLEM & OPPORTUNITY

The question left the material schedule.
The answer rarely made it back.

Pricing, lead times, and compliance details often aren’t available online.

We needed a way to request that information without breaking its connection to the product and schedule.

Examples of today’s RFI forms and tools: long PDFs and manual logging, RFIs living in a workspace, and no material specs requested
Examples of today’s RFI forms and tools: long PDFs and manual logging, RFIs living in a workspace, and no material specs requested
Too many tools

A single question meant switching between schedules, email, PDFs, and spreadsheets.

Too much follow-up

Architects chased replies, then copied the answers back into the project.

Too little context

Vague or partial replies restarted the conversation.

PRODUCT AT A GLANCE

Ask in context. Route to the right rep. Resolve in place.

Ask in context. Route to the right rep. Resolve in place.

What is an RFI?

A Request for Information (RFI) is how an architect asks a manufacturer for missing product details—such as pricing, specifications, or compliance documents. In Acelab, the request stays connected to the products in the project’s schedule.

Architect → Requests product information → Manufacturer rep responds

Architects choose products and fields in their schedule. Manufacturer reps receive a shared request and fill in a scoped version of the same table.

Their response returns to the original cells, with a receipt both sides can follow.

01 / Send a request

Prototype showing shared project context, Comments and Activity tabs
Prototype showing shared project context, Comments and Activity tabs

Select products and the fields you need. Review the recipients, add context, and send all from the schedule.

02 / Receive and respond

Reps answer in a scoped schedule view. The architect receives the response in the original project.

Reps answer in a scoped schedule view. The architect receives the response in the original project.

RFI which the MFR responds back to writes within the schedules cell
FIG. 06.3RFI which the MFR responds back to writes within the schedules cellIMAGE

Early impact

~1 day

Customer-reported turnaround, compared with the previous 11.4-day baseline.

Answers on platform

Customers received PDFs attached to the RFI, reducing phone and email follow-up.

New use cases

Architects began requesting complete hardware sets from project requirements.

“We issued RFIs to completely random vendors …

they replied within a day!”
Architect, design firm · Customer call, October 2026

Early impact

~1 day

Customer-reported turnaround, compared with the previous 11.4-day baseline.

Answers on platform

Customers received PDFs attached to the RFI, reducing phone and email follow-up.

New use cases

Architects began requesting complete hardware sets from project requirements.

“We issued RFIs to completely random vendors …

they replied within a day!”
Architect, design firm · Customer call, October 2026

HOW WAS DATA BEING REQUESTED TODAY

Two findings shaped the workflow.

Tracing the existing journey showed two recurring gaps: finding someone who could answer, and getting that answer back into the schedule.

Infographic of the old process: a schedule gap, an email to the rep, a buried inbox, follow-up calls, a PDF reply, and retyping the answer by hand

Keep the request in the workspace.

Architects preferred managing RFIs from Schedules, where the product and requested fields already lived.

Design the route back.

A reply wasn’t enough: the data needed to reach the original cells without manual re-entry.

I used an end-to-end Claude Code prototype to test routing and handoffs.

HOW WAS DATA BEING REQUESTED TODAY

Two findings shaped the workflow.

Tracing the existing journey showed two recurring gaps: finding someone who could answer, and getting that answer back into the schedule.

Infographic of the old process: a schedule gap, an email to the rep, a buried inbox, follow-up calls, a PDF reply, and retyping the answer by hand

Keep the request in the workspace.

Architects preferred managing RFIs from Schedules, where the product and requested fields already lived.

Design the route back.

A reply wasn’t enough: the data needed to reach the original cells without manual re-entry.

I used an end-to-end Claude Code prototype to test routing and handoffs.

HOW WAS DATA BEING REQUESTED TODAY

Two findings shaped the workflow.

Tracing the existing journey showed two recurring gaps: finding someone who could answer, and getting that answer back into the schedule.

Infographic of the old process: a schedule gap, an email to the rep, a buried inbox, follow-up calls, a PDF reply, and retyping the answer by hand

Keep the request in the workspace.

Architects preferred managing RFIs from Schedules, where the product and requested fields already lived.

Design the route back.

A reply wasn’t enough: the data needed to reach the original cells without manual re-entry.

I used an end-to-end Claude Code prototype to test routing and handoffs.

Three people. One connected request.

ARCHITECT

Sends the request

Chooses the products and fields. Gets answers back in the schedule.

MANUFACTURER REP

Answers the request

Fills the requested fields in a scoped schedule view.

MANUFACTURER CONNECT

The internal proxy

Routes requests with no rep on file. Can invite or close, but cannot answer.

The RFI workflow across architect, manufacturer rep, and Manufacturer Connection.
FIG. 06.3The RFI workflow across architect, manufacturer rep, and Manufacturer Connection.IMAGE

Three people. One connected request.

ARCHITECT

Sends the request

Chooses the products and fields. Gets answers back in the schedule.

MANUFACTURER REP

Answers the request

Fills the requested fields in a scoped schedule view.

MANUFACTURER CONNECT

The internal proxy

Routes requests with no rep on file. Can invite or close, but cannot answer.

The RFI workflow across architect, manufacturer rep, and Manufacturer Connection.
FIG. 06.3The RFI workflow across architect, manufacturer rep, and Manufacturer Connection.IMAGE

FLOW 01

How could sending a request take less work?

DESIGN SOLUTION

I kept product and field selection inside Schedules, with the project context and matched rep already attached.

SCREEN TO ADD

Choose the information to request

Add a close crop of Select Fields and Review: selected product, requested cost or technical fields, recipients, and Send RFI. Suggested export: 1600 × 1000.

Prototype showing shared project context, Comments and Activity tabs

The correct Rep is selected automatically based on your project.

FLOW 01

How could sending a request take less work?

DESIGN SOLUTION

I kept product and field selection inside Schedules, with the project context and matched rep already attached.

SCREEN TO ADD

Choose the information to request

Add a close crop of Select Fields and Review: selected product, requested cost or technical fields, recipients, and Send RFI. Suggested export: 1600 × 1000.

Prototype showing shared project context, Comments and Activity tabs

The correct Rep is selected automatically based on your project.

FLOW 01

How could sending a request take less work?

DESIGN SOLUTION

I kept product and field selection inside Schedules, with the project context and matched rep already attached.

SCREEN TO ADD

Choose the information to request

Add a close crop of Select Fields and Review: selected product, requested cost or technical fields, recipients, and Send RFI. Suggested export: 1600 × 1000.

Prototype showing shared project context, Comments and Activity tabs

The correct Rep is selected automatically based on your project.

FLOW 02

How could both sides stay aligned?

I reused Acelab’s conversations and added shared receipts, so both sides could follow the request and its current status in one place.

No rep on file: the request routes to an Acelab Manufacturer Connection.
FIG. 06.3No rep on file: the request routes to an Acelab Manufacturer Connection.IMAGE
Prototype showing shared project context, Comments and Activity tabs

RFI is received by Rep in a shared conversation thread

SCREEN TO ADD

The same RFI, visible to both sides

Add architect and manufacturer dashboard crops showing the same request and status. Suggested export: 1600 × 900.

FLOW 02

How could both sides stay aligned?

I reused Acelab’s conversations and added shared receipts, so both sides could follow the request and its current status in one place.

No rep on file: the request routes to an Acelab Manufacturer Connection.
FIG. 06.3No rep on file: the request routes to an Acelab Manufacturer Connection.IMAGE
Prototype showing shared project context, Comments and Activity tabs

RFI is received by Rep in a shared conversation thread

SCREEN TO ADD

The same RFI, visible to both sides

Add architect and manufacturer dashboard crops showing the same request and status. Suggested export: 1600 × 900.

FLOW 02

How could both sides stay aligned?

I reused Acelab’s conversations and added shared receipts, so both sides could follow the request and its current status in one place.

No rep on file: the request routes to an Acelab Manufacturer Connection.
FIG. 06.3No rep on file: the request routes to an Acelab Manufacturer Connection.IMAGE
Prototype showing shared project context, Comments and Activity tabs

RFI is received by Rep in a shared conversation thread

SCREEN TO ADD

The same RFI, visible to both sides

Add architect and manufacturer dashboard crops showing the same request and status. Suggested export: 1600 × 900.

FLOW 03

How could the answer become usable project data?

I reused a scoped schedule view: reps fill only the requested fields, and submitted values return to the original cells.

Manufacturer response written back into the architect’s schedule.

The response is instantly logged right inside the architect's workspace.

FLOW 03

How could the answer become usable project data?

I reused a scoped schedule view: reps fill only the requested fields, and submitted values return to the original cells.

Manufacturer response written back into the architect’s schedule.

The response is instantly logged right inside the architect’s workspace.

FLOW 03

How could the answer become usable project data?

I reused a scoped schedule view: reps fill only the requested fields, and submitted values return to the original cells.

Manufacturer response written back into the architect’s schedule.

The response is instantly logged right inside the architect’s workspace.

EXCEPTION HANDLING

No rep on file shouldn’t mean a dead end.

Unrouted requests go to Manufacturer Connection, who can invite a rep or close the request with a clear update to the architect.

DESIGN SOLUTION

RFI, no rep on file

The architect is told right away that it’s being handled.

→

Manufacturer Connection

An Acelab proxy: can talk, invite and close. Can’t answer.

No manufacturer status until a manufacturer exists.

↗

↘

Rep invited or assigned

A new thread with the original RFI card. Standard RFI from here.

Closed, no manufacturer response

The architect is notified and keeps their receipt.

What can Manufacturer Connection do?

The internal team can follow up, invite a rep, or close an unanswered request. Only a manufacturer rep can enter and submit product answers.

What happens when plans change?

Architects can request a deadline change or cancel an RFI. The shared receipt keeps both sides informed of the current state.

How does an invited rep pick up the work?

The invitation carries the original request and its project context, so the rep can respond without rebuilding the conversation.

EXCEPTION HANDLING

No rep on file shouldn’t mean a dead end.

Unrouted requests go to Manufacturer Connection, who can invite a rep or close the request with a clear update to the architect.

DESIGN SOLUTION

RFI, no rep on file

The architect is told right away that it’s being handled.

→

Manufacturer Connection

An Acelab proxy: can talk, invite and close. Can’t answer.

No manufacturer status until a manufacturer exists.

↗

↘

Rep invited or assigned

A new thread with the original RFI card. Standard RFI from here.

Closed, no manufacturer response

The architect is notified and keeps their receipt.

What can Manufacturer Connection do?

The internal team can follow up, invite a rep, or close an unanswered request. Only a manufacturer rep can enter and submit product answers.

What happens when plans change?

Architects can request a deadline change or cancel an RFI. The shared receipt keeps both sides informed of the current state.

How does an invited rep pick up the work?

The invitation carries the original request and its project context, so the rep can respond without rebuilding the conversation.

VALIDATION AND COLLABORATION

Two changes made the loop more complete.

Testing and launch feedback exposed the gaps below.

FOUND IN TESTING

FOUND IN TESTING

Routing hit a dead end

Routing hit a dead end

Some manufacturers had no rep on file. We added Manufacturer Connection to route the request and invite someone who could answer.

AFTER LAUNCH

AFTER LAUNCH

No way to cancel or extend

No way to cancel or extend

Architects needed to withdraw requests or change deadlines. Cancellation and deadline requests shipped on October 14.

Title slide of the Acelab launch webinar, Introducing RFI: Ending the Collaboration Chaos

▶

▶

Title slide of the Acelab launch webinar, Introducing RFI: Ending the Collaboration Chaos

▶

LAUNCH WEBINAR

LAUNCH WEBINAR

Introducing RFI: Ending the Collaboration Chaos

Introducing RFI: Ending the Collaboration Chaos

43 min · posted Sep 28, 2026

43 min · posted Sep 28, 2026

Watch on YouTube →

Watch on YouTube →

What this project taught me

What this project taught me

Design the handoff, not just the form.

Design the handoff, not just the form.

A request only works if the next person has the context and permissions needed to answer.

A request only works if the next person has the context and permissions needed to answer.

Keep the answer attached to the work.

Keep the answer attached to the work.

The loop closes when the response reaches the original schedule—not when a message is sent.

The loop closes when the response reaches the original schedule—not when a message is sent.

Make exceptions part of the core flow.

Make exceptions part of the core flow.

No rep, missed deadlines, and cancellation needed clear ownership and recovery paths.

No rep, missed deadlines, and cancellation needed clear ownership and recovery paths.

← Work / RFI

← Work / RFI