Daily Diary
- Lisa Robb
Overview
The daily diary serves as a vital documentation tool to record and track the day-to-day activities on a construction site. It provides a comprehensive overview of crucial information for effective project management, job costing communication. Some Key elements may include:
Date and Weather Conditions: Documenting the date and prevailing weather conditions to account for their impact on construction activities.
Labour Hours: Recording details about the workforce, including the number of workers, the activity they undertake, and noteworthy achievements or challenges related to labour.
Equipment (Plant) and Machinery: Noting information about the equipment and machinery used on the site.
Material Deliveries: Keeping track of material deliveries, quantities received, and any issues or delays related to the supply chain.
Progress and Milestones: Provide updates on the progress of construction tasks, completion of milestones, and any deviations from the project schedule.
Inspections and Approvals: Document details about inspections conducted, approvals obtained, and any issues identified during inspections.
Safety Updates: Advise staff of any safety or OH&S updates and record them in the diary.
Communication: Noting significant communications, decisions, or changes made on the site, including meetings, instructions, and collaboration with subcontractors.
Unforeseen Issues: Recording unexpected challenges, obstacles, or changes in site conditions that may affect the project.
Photographs and Attachments: Optionally including photographs or attachments for visual documentation of the site's condition, progress, or issues.
The daily diary in construction is an invaluable resource for project managers and stakeholders, facilitating efficient decision-making, and issue resolution, and providing a clear historical record for future reference or dispute resolution.
Upvise Daily Diary:
In Upvise, the Workbench Daily Diary comprises a series of transactions that sync seamlessly to Workbench on an hourly basis.
Subform | Purpose | Upvise Transaction | Workbench Transaction |
|---|---|---|---|
To record an employess time worked on a project or a job in upvise. | Yes Timesheet- Timelogs | Timesheet line for the employee against workbench Job or Service log | |
To record an employess administration time worked on an overheads project in Upvise. Examples include Sick leave & training hours | Yes Timesheet- Timelogs | Timesheet line for the employee against workbench Job or service log | |
To record an employess time worked on a plant item in upvise. Commonly used by mechanics servicing equipment. | Yes Timesheet- Timelogs | Timesheet line for the employee against workbench plant item | |
To record an employess time worked on a project or a job in upvise, as well as the plants time as a plant issue against the project or job in upvise. | Yes Timesheet- Timelogs | Timesheet line for the employee against workbench Job or Service log, as well as a plant issue to the workbench Job or Service log | |
to record the plants time against a project or job in Upvise. | Yes Timesheet- Timelogs | Plant issue against a workbench Job or Service log | |
to record a docket trancaction against a project or a job in upvise | No | Docket transaction to the workbench Job or Service log | |
to record an output trancaction against a project or a job in upvise | No | Output transaction to the workbench Job or Service log | |
to record a stock issue against a project or a job in upvise | No | Stock issue to the workbench Job or Service log | |
to tranfer stock between stock locations in upvise | No | Stock Transaction between two stock locations in workbench (jobtransaction between the stock jobs) | |
to adjust the volume of stock in a stock location in upvise | No | Stock Adjustment against the stock locations in workbench (jobtransaction against the stock job) | |
to issue stock to an equipment item in upvise | No | Stock issue to the plant item |
Time transactions generate “Native Transactions” in the timesheet module which is required for the data to sync to workbench
Other transactions will sync once the diary reaches its final state.
e.g. where there is no workflow this will be when the diary is submitted, where there is a workflow it will be when the last workflow step is reached.