The project manager’s week, on one record.

Here we are in the actual os.construction app, using a local sample project. On the New RFI page, we can prepare a question and save it as a draft before opening it.

Use a subject that tells the reviewer what needs clarification. In this example, we are asking about the corridor fire damper detail. The demo adds a unique reference so each recording creates a separate sample record.

State the decision the team needs. Our question asks the reviewer to confirm the required fire damper detail before installation and identify which detail the field team should follow.

Select Create as Draft. The app saves the RFI and opens its detail page. We will check that the Open RFI action is available before moving forward.

The saved record now has its own detail page. Review the subject and question here. A draft gives the team a chance to check the request before opening it.

Select Open RFI. Wait for the Open RFI action to disappear after the update. Close RFI remains available. We have written a request, saved it as a draft, reviewed it, and moved it into the open workflow.

Open Create Task in the sample project. A useful task names a specific follow-up and gives the next reader enough context to understand what needs to happen. We will save this example, change its status, and add an update.

Give the task an action-oriented title. Confirm delivery window tells the reader what needs attention. The unique demo reference distinguishes this sample record from other recordings.

Use Description to explain the expected result. Our invented example asks for the delivery window, the agreed time, and access instructions. Review the task's other fields before saving. This recording leaves assignees and distribution empty.

Select Create and wait for the task detail page. Confirm the title and description. The saved record now has a task number and a current status that the project team can use to track the follow-up.

For this sample, select In Progress. Check the current status in the task header after the update. A status change records the stage of the task; the delivery window itself still needs confirmation.

Add a comment that explains the next check. Our sample update says that the delivery window needs confirmation and identifies who to check with. This gives the reader more context than the status alone.

Select Add Comment. Wait for the text to appear in the saved comment list. Read the saved update so you can confirm the task contains the information you intended to leave.

Here is the saved update on the task. We have created a specific follow-up, moved its status into progress, and recorded the next check. Keep updating the record as the work changes so another reader can understand what remains.