FOR SUBCONTRACTORS

See the project, RFI, assignee, and due date before responding.

Keep each trade question tied to the selected job, responsible person, due date, original request, response, and status.

Get Started

See the RFI flow

Konstructo filled RFI form with expanded navigation categories

CLEAR RESPONSIBILITY

Give trade partners the project and RFI context needed for the next action.

Use focused project and coordination records so questions can be reviewed without rebuilding the context from messages and attachments.

Selected project context

Confirm the job, site, dates, responsible contacts, and the project record behind the question.

Assigned RFI details

Review the subject, assignee, due date, question, and current status before responding.

Recorded response

Keep the original request and final response together in the project Coordination area.

Partner and commercial context

Keep subcontractor and vendor records available to the project team for bid, purchasing, billing, and change reviews.

RFI RESPONSE FLOW

A clean path from question to recorded response.

Use the same source record from first review through response and follow-up.

Open the assignment

Confirm the selected project, RFI subject, assignee, due date, and current status.

Check the source

Review the original question and the project information needed to respond accurately.

Respond

Record the response in the RFI so the project team can review it in context.

Confirm follow-through

Confirm the final status, responsible follow-up, and the project record affected by the answer.

REQUEST · FILLED RFI FORM

REQUEST → RESPONSE

FOLLOW-UP · RESPONSE KEPT WITH THE QUESTION

Konstructo RFI detail with project, assignee, due date, response, and current status

RFI RESPONSE FLOW

A clean path from question to recorded response.

Use the same source record from first review through response and follow-up.

Open the assignment

Confirm the selected project, RFI subject, assignee, due date, and current status.

Check the source

Review the original question and the project information needed to respond accurately.

Respond

Record the response in the RFI so the project team can review it in context.

Confirm follow-through

Confirm the final status, responsible follow-up, and the project record affected by the answer.

REQUEST · FILLED RFI FORM

REQUEST → RESPONSE

FOLLOW-UP · RESPONSE KEPT WITH THE QUESTION

Konstructo RFI detail with expanded navigation categories

CURRENT VIEW • RFI DETAIL • OWNER, DUE DATE, RESPONSE

TRADE COORDINATION RECORD

Keep trade coordination focused on the question and project it affects.

Use the selected project and structured RFI record to keep the request, response, owner, due date, and status together.

●

Give trade partners the project and RFI details needed to answer the question

●

Connect RFI questions to the selected project

●

Keep billing and communication attached to the partner record

BEFORE YOU RESPOND

Four checks for a clean trade-partner RFI response.

Keep the job, question, responsibility, and response visible in one review path.

Confirm the job

Verify the selected project, site, and responsible project contacts.

Read the source question

Review the RFI subject and original question before responding.

Confirm responsibility

Check the assignee, due date, and current status.

Record the response

Keep the response with the original request and return to the record for follow-up.

BEFORE YOU RESPOND

Four checks for a clean trade-partner RFI response.

Keep the job, question, responsibility, and response visible in one review path.

Confirm the job

Verify the selected project, site, and responsible project contacts.

Read the source question

Review the RFI subject and original question before responding.

Confirm responsibility

Check the assignee, due date, and current status.

Record the response

Keep the response with the original request and return to the record for follow-up.

WHAT IMPROVES

A structured response creates a clearer project record.

The RFI remains useful after the response because its subject, project, owner, dates, question, answer, and status stay together.

Less searching

Keep current scope, files, and actions together.

Clearer ownership

Show responsibilities and required follow-up.

Better traceability

Preserve partner questions, records, and commercial context.

RFI field anatomy

See exactly what makes a question ready for response

Use the RFI form and detail view to review the question, assignee, due date, response, and status for a specific project.

CURRENT KONSTRUCTO VIEW

01 · REVIEW POINT

Project

Attach the question to the selected job context.

01 · REVIEW POINT

Project

Attach the question to the selected job context.

02 · REVIEW POINT

Subject and question

State what needs clarification in the record.

02 · REVIEW POINT

Subject and question

State what needs clarification in the record.

03 · REVIEW POINT

Assignee and due date

Make the responsible party and expected timing visible.

03 · REVIEW POINT

Assignee and due date

Make the responsible party and expected timing visible.

04 · REVIEW POINT

Response and status

Return the answer to the record and review its displayed state.

04 · REVIEW POINT

Response and status

Return the answer to the record and review its displayed state.

Explore the project workspace

Response context packet

Give the responder the job context before asking for an answer

Build the response brief from the project, RFI question, assignee, due date, and final response.

01 · REVIEW POINT

Job and site

Name the project context visible in the record.

02 · REVIEW POINT

Responsible contacts

Identify the assignee or project-side contact shown.

03 · REVIEW POINT

Source question

Preserve the subject and full question.

04 · REVIEW POINT

Required response

Make the expected answer and due date explicit.

05 · REVIEW POINT

Return point

Direct the responder back to the RFI detail for the recorded answer.

See project execution

Response context packet

Give the responder the job context before asking for an answer

Build the response brief from the project, RFI question, assignee, due date, and final response.

01 · REVIEW POINT

Job and site

Name the project context visible in the record.

02 · REVIEW POINT

Responsible contacts

Identify the assignee or project-side contact shown.

03 · REVIEW POINT

Source question

Preserve the subject and full question.

04 · REVIEW POINT

Required response

Make the expected answer and due date explicit.

05 · REVIEW POINT

Return point

Direct the responder back to the RFI detail for the recorded answer.

See project execution

Request and response

Keep both sides of the RFI exchange in one visible trail

Create the RFI, assign an owner, capture the response, and review its status from the selected project record.

01 · REVIEW POINT

Request created

Start from the filled RFI form in the right project.

01 · REVIEW POINT

Request created

Start from the filled RFI form in the right project.

02 · REVIEW POINT

Assignment checked

Confirm the visible assignee and due date.

02 · REVIEW POINT

Assignment checked

Confirm the visible assignee and due date.

03 · REVIEW POINT

Response recorded

Add or review the answer in the RFI detail.

03 · REVIEW POINT

Response recorded

Add or review the answer in the RFI detail.

04 · REVIEW POINT

Follow-through

Return to the affected project work and confirm the next action.

04 · REVIEW POINT

Follow-through

Return to the affected project work and confirm the next action.

See the connected platform

Return path

A response is useful when the team can carry it back to the job

Expand the story from submitting an answer to reviewing the affected work, with the final step framed as team process rather than automatic updates.

01 · STEP

Open project context

Confirm which job the RFI belongs to.

02 · STEP

Review the original form

Check the question, assignee, and due date.

03 · STEP

Read the response detail

Use the response screen as the source for the answer.

04 · STEP

Revisit affected work

Carry the decision back into the relevant project record or conversation.

Explore project teams

Return path

A response is useful when the team can carry it back to the job

Expand the story from submitting an answer to reviewing the affected work, with the final step framed as team process rather than automatic updates.

01 · STEP

Open project context

Confirm which job the RFI belongs to.

02 · STEP

Review the original form

Check the question, assignee, and due date.

03 · STEP

Read the response detail

Use the response screen as the source for the answer.

04 · STEP

Revisit affected work

Carry the decision back into the relevant project record or conversation.

Explore project teams

Commercial context nearby

Connect the trade-partner conversation to the relevant business record

Use partner and commercial modules as adjacent context, not a proven end-to-end subcontractor transaction chain.

01 · REVIEW POINT

Partner record

Use the company-level vendor or subcontractor record where available.

01 · REVIEW POINT

Partner record

Use the company-level vendor or subcontractor record where available.

02 · REVIEW POINT

Bid or proposal

Open a proposal or bid-related screen only when it matches the implemented process.

02 · REVIEW POINT

Bid or proposal

Open a proposal or bid-related screen only when it matches the implemented process.

03 · REVIEW POINT

Purchase or bill

Review the relevant commercial record and confirm any required matching step.

03 · REVIEW POINT

Purchase or bill

Review the relevant commercial record and confirm any required matching step.

04 · REVIEW POINT

Change review

Carry any project decision into the team’s agreed commercial follow-up.

04 · REVIEW POINT

Change review

Carry any project decision into the team’s agreed commercial follow-up.

Explore cost management

Proven and to confirm

Separate the fields on screen from the workflow details still to validate

Make clear what is visible today and which trade-portal behaviors still need confirmation.

01 · REVIEW POINT

Proven fields

Project, question, assignee, due date, response, and status are visibly supported.

02 · REVIEW POINT

Role access

Confirm the project and record access each external participant needs during setup.

03 · REVIEW POINT

Handoff channel

Name how and when the assignee should receive the RFI handoff, then confirm that requirement during setup.

04 · REVIEW POINT

Attachments and audit

Precise attachment handling, revision history, and audit behavior need validation.

05 · REVIEW POINT

Commercial follow-through

Carry the RFI outcome into the relevant purchasing, billing, or change record.

See the product tour

Proven and to confirm

Separate the fields on screen from the workflow details still to validate

Make clear what is visible today and which trade-portal behaviors still need confirmation.

01 · REVIEW POINT

Proven fields

Project, question, assignee, due date, response, and status are visibly supported.

02 · REVIEW POINT

Role access

Confirm the project and record access each external participant needs during setup.

03 · REVIEW POINT

Handoff channel

Name how and when the assignee should receive the RFI handoff, then confirm that requirement during setup.

04 · REVIEW POINT

Attachments and audit

Precise attachment handling, revision history, and audit behavior need validation.

05 · REVIEW POINT

Commercial follow-through

Carry the RFI outcome into the relevant purchasing, billing, or change record.

See the product tour

Trade-partner handoff

Use a simple checklist before an RFI leaves either side

Use this recommended practice around the visible RFI fields rather than attributing the checklist to an unseen automation.

01 · STEP

Right job

Verify the project before creating or answering the record.

01 · STEP

Right job

Verify the project before creating or answering the record.

02 · STEP

Clear question

Preserve a concise subject and complete question.

02 · STEP

Clear question

Preserve a concise subject and complete question.

03 · STEP

Named owner

Confirm the assignee and due date.

03 · STEP

Named owner

Confirm the assignee and due date.

04 · STEP

Recorded response

Put the answer in the RFI detail.

04 · STEP

Recorded response

Put the answer in the RFI detail.

05 · STEP

Completion check

Review the displayed status and the affected project work.

05 · STEP

Completion check

Review the displayed status and the affected project work.

Review the RFI tour

Bring a real question

Test the workflow with an RFI your team already needs to resolve

A representative question helps validate access, fields, response handling, and follow-through without exposing sensitive project data publicly.

01 · REVIEW POINT

Select the project

Use a job familiar to both project and trade teams.

02 · REVIEW POINT

Write the question

Choose a current issue with clear context.

03 · REVIEW POINT

Name the responder

Identify who should see and answer it.

04 · REVIEW POINT

Choose the due date

Define the expected response window.

05 · REVIEW POINT

Define resolution

State how the team will know the answer reached the affected work.

Get Started

Prefer a guided walkthrough? Book a Demo

Bring a real question

Test the workflow with an RFI your team already needs to resolve

A representative question helps validate access, fields, response handling, and follow-through without exposing sensitive project data publicly.

01 · REVIEW POINT

Select the project

Use a job familiar to both project and trade teams.

02 · REVIEW POINT

Write the question

Choose a current issue with clear context.

03 · REVIEW POINT

Name the responder

Identify who should see and answer it.

04 · REVIEW POINT

Choose the due date

Define the expected response window.

05 · REVIEW POINT

Define resolution

State how the team will know the answer reached the affected work.

Get Started

Prefer a guided walkthrough? Book a Demo

Resolve the next RFI with the project context still attached.

Connect project information, RFI records, and current financial headings.

Get Started

SUBCONTRACTOR FAQ