Seven stops between coffee and the drive home, on the Riverside Medical Center sample job. The point isn't the tools. It's that the RFI, the meeting, the task and the change event are the same linked records all day.
Times are illustrative. The arcs are links the app stores between records, so a task knows the RFI or meeting topic it came from, and the change event knows its RFI.
7:00 · Project desktop
Desktop in the dock is the project home, a board of widgets that sum up the job: revised contract, committed cost, billed to date, margin, My open items with how many are late, open field items by tool, today's daily log and the activity feed. The bell holds assignments, mentions and status changes. Each widget only shows numbers from tools you're allowed to see.
On Riverside this morning: 23 open RFIs, 4 of them overdue (sample data).
7:45 · RFIs
The architect's official response is on the RFI: dampers are required. The response sits with the question, ball in court and due date, so nobody has to dig through email for it. Two things start here. Create task opens a follow-up already linked to the RFI. And a change event can name the RFI as its origin, which is where the money side begins.
Watch the walkthrough · 1:57
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.
Video page with chaptersStep-by-step guideMore in RFIs & submittals
9:30 · Submittals
Storefront glazing product data is due from the glazing sub. The submittal is created against its spec section, with a type, a responsible contractor and a submittal manager. The submittal log shows each one's status, ball in court and due date, so what's late is visible before it holds up the work.
11:00 · Daily log
The super's daily log is one page per day: weather, manpower by company with cost code and location, notes, deliveries, delays and the rest. Because manpower and quantities carry the job's own cost codes, the field record and the budget speak the same language. Once the day is complete, its entries are locked until someone reopens it.
Watch the walkthrough · 2:18
Start with the project and date. We are in the local sample project's Daily Log, which opens on today. A useful field note tells the next reader what happened, where, and what needs attention next.
Scroll to Notes. This section has its own entry form. Keep an observation specific enough that another team member can understand the location, the time, and the next check without asking you to reconstruct the day.
Our invented example records an access check at the east corridor, the time, and a follow-up before the delivery. The unique demo reference distinguishes this sample note from other recordings. Replace the example with facts you actually observed on your project.
Select Create in the Notes form. Wait for the new row to appear, then read the saved comment. Checking the row confirms the submitted text reached the day's log instead of remaining only in the form.
Use Previous Day to leave this day's view. Each day has its own log. The Today link lets us return to the day where we created the note and check that the saved entry is still there.
Select Today to return to the day where we created the note. Check the displayed date, then return to Notes to find the saved observation.
Here is the same note in the Notes table after returning to the day. Read the time, location, observation, and next check. We have saved a specific field note and confirmed that another reader can find its context again.
Video page with chaptersStep-by-step guideMore in Field: daily logs & tasks
14:00 · Meetings
The weekly OAC meeting is part of a recurring series. Agenda topics have a category, a priority, a due date and an assignee, and open topics carry forward to next week. On a topic, Create task turns a decision into a follow-up that remembers which meeting and topic it came from.
15:30 · Tasks
The tasks from the morning's RFI and the afternoon's meeting land on one list with an owner, a due date and a status, on a list or a board. A comment says what happened and what's next; assignees and the creator are notified.
Watch the walkthrough · 2:33
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.
Video page with chaptersStep-by-step guideMore in Field: daily logs & tasks
16:30 · Change events
Before leaving, the PM opens a change event with RFI-212 as its origin and a rough line by cost code, so the exposure is on the record the day it's known. The RFI lists the change event; the change event shows its whole chain to PCOs, change orders and the budget.
Company Accounting covers the ledger, AP, AR and payroll. AI agents that prepare this kind of work remain planned. See how agents will work.
Keep exploring
Sample project included
Every trial workspace includes a sample project with sample data, so you can follow these steps in the app before touching a live job.
RFIs, submittals, daily logs, meetings, tasks and change events are live. Company Accounting covers the books; AI agents remain planned.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →
All figures are illustrative sample data, not a real project. Contract terms and state law decide how retainage, stored materials and change orders work on your job. Check both.
