Your weekly OAC meeting, start to finish

Here's the Create Meeting page in our local sample project. A good meeting record tells everyone what we're meeting about, where, and what we want to decide. Let's set one up together.

We start with a title people will recognize in a list. Ours is the weekly owner, architect and contractor coordination meeting. The demo adds a unique reference so each recording creates a separate sample record.

Next, let's check the date and time. The form suggests a date, a time zone, and a start and end time. We keep the suggested values in this sample; set them to match your real meeting.

Now we add where the meeting happens. For this sample it's the site trailer conference room.

In Overview, we write the agenda and the decision we need. Our sample covers open RFIs, the two-week look-ahead, pending submittals, and one decision on the level 2 ceiling sequence.

Then we select Create. The app saves the meeting and opens its record, with the meeting number and our title in the header.

Here's our saved meeting. Let's check that the location and agenda came through. We've created a meeting with a clear title, a place, and an overview the team can prepare for.

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.