Skip to content

Keep project questions with the revisions and decisions

Keep the request, revised drawing, quoted cost and approval message together. Give the reviewer the versions behind the proposed change and record the decision beside them.

Project question

Riverside · RFI-027

Could you confirm the revised loading-bay layout? The proposed increase is £4,800.

Project
Riverside
Reference
RFI-027

Proposed change review

Proposed cost
£4,800
Review state
Awaiting review
Review owner
Mira

Keep the proposed cost and RFI beside the assigned review.

Keep a proposed project change linked to its RFI.

The proposal and the decision

Follow the question as it becomes a proposed change

Use the project and request references your team recognizes to find a request for information, revised drawing, quoted cost and approval email across inboxes and folders. Save useful groups of emails or documents in Collections.

Keep the email explaining a revision beside its attachment. Use the available document history to check which version was discussed.

See the proposed cost and schedule effect beside the decision

Extract the request reference, quoted cost, stated schedule effect and date into fields you can compare. Keep the proposal and the later acceptance or rejection clearly identified, with their supporting emails and files.

Use the latest checked details to compare updates, while your responsible reviewer approves the change and records the decision.

Reviewer questions and project updates

Give the review the evidence it needs

Assign a question, clarification or change review to the right person, with an optional due date. Include the relevant request, proposed change and revised files they can read.

When the action is completed, record the outcome and supporting evidence. Another project lead should be able to identify what was checked and which version the decision concerned.

Prepare an update for each project audience

Give the project lead open questions and quoted impacts, and give an outside contractor the relevant request, drawings and response. Create a separate shared view for each audience.

Use reviewed dates for scheduled alerts when a review deadline needs attention. Keep notices and agreement cycles in the contract workflow, and operational delivery changes in supplier coordination.

Common questions

How can a reviewer find the request behind a change order?

Use the request reference to find related messages and documents, and save useful groups in separate Collections. Check their references and available document history during the review.

How do we record the decision on a proposed change?

Assign the review to an owner and record their outcome beside the quoted cost, schedule effect and supporting documents. Your project approval process makes the decision.

Follow a project question from request to decision

See the quoted impact, revised documents and message recording the decision together, ready for the next project review.