Layer Background

Layer in Action

Learn how easy it is to save time using Layer with these action packed demo videos!

Layer Background

Layer in Action

Learn how easy it is to save time using Layer with these action packed demo videos!

All
Architect
Engineer
Interior Designer
Owner
Facility Manager
Contractor

How to write an RFI

RFIs—short for Requests for Information—are a critical yet often time-consuming part of any construction project. A good RFI ensures that your team gathers the right information at the right time, reducing costly delays and miscommunications on-site.

In this short video, Giorgios from Layer’s Customer Success team walks you through how to write an RFI using Layer’s construction management platform. Whether you're on desktop, mobile, tablet, or in Revit, Layer makes it simple to create, manage, and track RFIs—all in one place.

What is an RFI?

A Request for Information (RFI) is a formal process used in construction to clarify project details, resolve design issues, or verify discrepancies between documents. Effective RFIs are clear, concise, and contain the right type of information to ensure fast and accurate responses.

RFIs are often confused with other requests like Request for Proposal (RFP) or Request for Quotation (RFQ)—but they serve a distinct purpose. While RFPs and RFQs involve pricing and vendor selection, RFIs help gather additional information and clarify uncertainties before construction progresses.

Why Use Layer for the RFI Process?

Layer streamlines the RFI process from start to finish, enabling you to:

  • Create an RFI directly from your project drawings

  • Tag and assign team members for quicker response times

  • Upload relevant attachments like site photos or specs

  • Track status and due dates to avoid missed deadlines

  • Export RFI documents as polished PDF reports

  • Automate notifications and workflows

The result? A more transparent and efficient way to manage RFIs—no more chasing down email threads or managing disjointed spreadsheets.

Video Walkthrough: Creating an RFI in Layer

In the video, Giorgios shows how to:

  1. Open your project from the Layer dashboard.

  2. Use a built-in RFI template to get started quickly.

  3. Navigate to the RFI category, where each RFI includes key fields like:

    • Title

    • Status

    • Due Date

    • Assigned Team Member

    • Question + Answer

    • Attachments

    • Drawing References

  4. Mark up drawings with annotations to pinpoint exactly where the issue exists.

  5. Assign the RFI to a teammate or collaborator directly within the platform.

  6. Add supporting documents or photos as needed.

  7. Receive responses, and see everything tracked in one place.

Layer automatically generates an RFI report as you work. You can export individual RFIs or a full report with multiple entries—perfect for sharing with stakeholders or including in your project documentation.

What Makes a Good RFI?

A good RFI does more than ask a question. It helps the recipient understand the context, urgency, and potential impact. In Layer, you can create an RFI that includes:

  • Clear background information

  • Relevant drawing or spec references

  • Well-defined questions with space for detailed answers

  • Evaluation criteria, if applicable

  • A due date to encourage timely responses

Layer’s intuitive fields guide you through the process of writing and sending an RFI that gets results—fast.

Automate RFI Tracking

One of the standout features in Layer is RFI automation. In the video, you’ll learn how to:

  • Trigger an email when an RFI’s status is updated (e.g. from “Open” to “Closed”)

  • Customize the message using fields from the RFI itself

  • Stay informed in real-time without constantly checking for updates

Automation is especially useful when managing RFIs across multiple vendors, trades, or project phases.

Layer Supports Every Step of the RFI Process

From drafting to resolution, Layer helps streamline your RFI process with tools that support collaboration, transparency, and speed. Here’s how Layer fits into your larger construction communication workflow:

  • Create an RFI directly from a drawing or floor plan

  • Send an RFI with background information and attachments

  • Receive an RFI response from the assigned team member

  • Generate an RFI report as part of your documentation

  • Use evaluation criteria to ensure consistency across multiple RFIs

  • Transition to an RFP or RFQ if the next step involves pricing or bids

Designed for Collaboration

Layer allows you to tag anyone on your team—whether it’s an architect, engineer, consultant, or contractor. Everyone has access to the same data and can contribute to the request for information process without switching tools.

You can even associate your RFI with other project details like FF&E items, field observations, or design specs to create a single source of truth for your team.

Conditional Formatting for Layer Document View

In this video, Zach from the Layer team walks you through our latest and most powerful feature yet — Conditional Formatting in Document Views! 🎉 Now you can easily track revisions, highlight changes, and streamline your workflows with customizable formatting rules. Whether you're working with project updates or data submissions, this tool will save you time and effort.

🎯 What you'll see in this video

  • How to set up conditional formatting rules for document views.

  • Step-by-step guide to highlighting changes since specific submission dates (e.g., 9/27 or 9/20).

  • How to create multiple rules, customize text colors, and export reports with ease.

  • Best practices for automating document updates and improving revision tracking.

👉 Who is this feature for?

This feature is perfect for Layer users looking to highlight key data changes without the hassle of manual tracking.

A Tour of Layer's Construction Administration Template

See how Layer's Construction Administration template can help you keep track of it all. Product Manager Georgios Papadogeorgakis will walk you through this template and show you how you can get started customizing everything to your own organization's workflows.

This template includes tools for tracking RFIs, submittals, punch lists, meeting minute notes, and more. Learn how to capture and organize all meeting minute notes, RFIs, site observations, punch lists items and more in a single platform connected directly to Revit.

Connect with Vendors, GCs, and other project stakeholders in a single source of truth so that everyone is on the ball and no time is lost during the most crucial stages of construction.

Customize and export custom reports so that your team is not wasting time formatting docs, and instead concentrating on what matters: delivering beautiful spaces your clients will love.

Work Order Forms linked to Revit

Many of the architects and engineers that use Layer may be surprised to find out that a large portion of our user base leverages Layer to run and organize their building operations.

A side effect of this is that they've created a data flywheel between their ops teams and the AEC teams their organization works with. Looking at this data in the context of an upgrade allows the architect or engineer to better understand the spatial performance of a room. This creates a valuable feedback loop for the architect and owner to work through proposed changes to a space.

This week on Layer Quick Bytes I'll be covering a workflow that's native to the operations space: Work Orders. In less time than it takes to have lunch, I'll show you how you can setup a CMMS from scratch in Layer, upload historic work orders, then associate them with a model so that they can be viewed within the context of a space.

Sync to Spreadsheets with the Layer API

The word "spreadsheet" elicits a mixed reaction from many people in the AEC space. Spreadsheets are the root of alot of pain. They can also be an invaluable tool when passing information between organizations or internal teams where our software tools can't talk to eachother.

The problem is, spreadsheets tend to contain dead data. They were created at a set moment in time from an export function or copy & pasting data. As data in your source of truth changes, the spreadsheet does not.

That means that person you are collaborating with is working on outdated information. It may even be outdated by the time that you've emailed it to the them.

Live data is always better. While Layer offers direct Shared Views, sometimes you still need the spreadsheet. If you're already asking how, I invite you to join me for Layer Quick Bytes this week! I'll show you how to create a living spreadsheet that is updated by the Layer API.