Construction Project Cost & Contract Management System For Mersa
1. Application Overview The Submission Completion Automation application is designed to provide teams with a structured digital process for completing and recording submission checks before a submission is finalized. The application allows users to select the relevant Microsoft Team and one or more Channels, complete a detailed Submission Completion Form, verify required CostX and document-related checks, and submit the completed information for centralized storage. The solution uses Microsoft Power Apps for the user interface and Power Automate for submission processing and notifications, with the application intended to operate within the Microsoft Teams environment. 2. Team and Channel Selection Users can select the relevant Microsoft Team and associated Channel(s) when completing a submission. The application includes: Team selection Channel selection with multi-select support Automatic population of selected Team and Channel information into the submission The Team and Channel selections are designed to be dynamically retrieved so that users can associate each submission with the appropriate Microsoft Teams location. 3. Submission Completion Form The application provides a structured Submission Completion Form containing the information and checks required before completing a submission. Each submission records core information including: Submission ID Team Name Channel Name Submitted By Submission Date Status The Submission ID is automatically generated, while user and submission information can be prefilled or automatically captured where applicable. Submission status can be maintained as: Draft Submitted Approved This provides a structured record of each submission and its current stage. 4. CostX Completion Checks The application includes a dedicated CostX checklist to ensure that key CostX-related requirements have been reviewed before submission. The checks cover areas such as: Object visibility and duplicate checking Model and design consistency Revit scale issues Workbook recalculation Reference verification Drawing scale verification Bulk checks Master set completion Users complete these checks through checkbox-based fields within the Submission Completion Form. 5. Document Completion Checks A comprehensive Document Checks section allows users to verify that the required document quality and submission requirements have been completed. These checks include areas such as: Correct document template File naming standards Correct project and company information Correct tabs and dates Assumptions and clarifications Client review areas Efficiency calculations Drawing register and revisions Formula validation Baseline budget alignment Page and take-off totals Separable portions Design variance calculations Footer information Borders and formatting Take-off headings Document cleansing Spell checking Print area setup Color coding Font verification Mersa theme Heading hierarchy Privacy review PDF generation Director review Infrastructure Team Bcc These checks provide users with a structured checklist to verify the completeness and quality of submission documentation before final submission. 6. Structured Form Interface The Submission Completion Form is organized into grouped sections, including CostX Checks and Document Checks , making the required verification activities easier to complete and review. The interface uses appropriate controls such as: Checkboxes Dropdowns Read-only information fields Team and Channel selectors The application is designed to provide a responsive and user-friendly experience while handling the complete submission checklist. 7. Automated Submission Processing When the Submission Completion Form is submitted, automated workflows process the submission information. The automation is designed to: Trigger a notification when a form is submitted. Save submission metadata in the configured storage system. Maintain the relevant Microsoft Teams/Channel context associated with the submission. This reduces manual processing and ensures that submission information is captured consistently. 8. Centralized Submission Records Each completed form is maintained as a structured submission record containing the user, Team, Channel, date, status, and results of the individual completion checks. This provides a centralized record of completed submission checks and allows the submission information to be stored and retrieved through the configured SharePoint or Dataverse storage environment. 9. Microsoft Teams Integration The application is designed to operate within the Microsoft Teams environment and associate submissions with the appropriate Teams and Channels. The planned rollout includes embedding the application across 20 channels , allowing users to access the submission process from the relevant working environment. 10. Testing and Validation The complete solution is tested to ensure that the application, submission data, dynamic Team/Channel selections, and automated workflows operate correctly together. Testing includes: End-to-end user flow validation Verification of submitted data Dynamic Team and Channel selection testing Form field validation Functional testing User feedback and refinements This helps ensure that the application and automation operate correctly before the final rollout. Overall Application Workflow The process begins when a user accesses the Submission Completion application and selects the relevant Microsoft Team and Channel or Channels. The selected Team and Channel information is automatically associated with the submission. The user then completes the Submission Completion Form by reviewing the required CostX and Document Checks. Each requirement is verified through the appropriate checkbox or form control, while submission information such as the user and submission date is captured as part of the record. Once the required checks have been completed, the user submits the form. The automated workflow processes the submission, stores the relevant metadata in the configured storage system, and triggers the required submission notification. The completed record provides a centralized history of the submission, its status, associated Team/Channels, and the checks performed before completion. Select Team & Channel(s) → Open Submission Completion Form → Complete CostX Checks → Complete Document Checks → Review Submission → Submit Form → Store Submission Record → Trigger Notification → Track Submission Status
Project Summary
1. Application Overview The Submission Completion Automation application is designed to provide teams with a structured digital process for completing and recording submission checks before a submission is finalized. The application allows users to select the relevant Microsoft Team and one or more Channels, complete a detailed Submission Completion Form, verify required CostX and document-related checks, and submit the completed information for centralized storage. The solution uses Microsoft Power Apps for the user interface and Power Automate for submission processing and notifications, with the application intended to operate within the Microsoft Teams environment. 2. Team and Channel Selection Users can select the relevant Microsoft Team and associated Channel(s) when completing a submission. The application includes: Team selection Channel selection with multi-select support Automatic population of selected Team and Channel information into the submission The Team and Channel selections are designed to be dynamically retrieved so that users can associate each submission with the appropriate Microsoft Teams location. 3. Submission Completion Form The application provides a structured Submission Completion Form containing the information and checks required before completing a submission. Each submission records core information including: Submission ID Team Name Channel Name Submitted By Submission Date Status The Submission ID is automatically generated, while user and submission information can be prefilled or automatically captured where applicable. Submission status can be maintained as: Draft Submitted Approved This provides a structured record of each submission and its current stage. 4. CostX Completion Checks The application includes a dedicated CostX checklist to ensure that key CostX-related requirements have been reviewed before submission. The checks cover areas such as: Object visibility and duplicate checking Model and design consistency Revit scale issues Workbook recalculation Reference verification Drawing scale verification Bulk checks Master set completion Users complete these checks through checkbox-based fields within the Submission Completion Form. 5. Document Completion Checks A comprehensive Document Checks section allows users to verify that the required document quality and submission requirements have been completed. These checks include areas such as: Correct document template File naming standards Correct project and company information Correct tabs and dates Assumptions and clarifications Client review areas Efficiency calculations Drawing register and revisions Formula validation Baseline budget alignment Page and take-off totals Separable portions Design variance calculations Footer information Borders and formatting Take-off headings Document cleansing Spell checking Print area setup Color coding Font verification Mersa theme Heading hierarchy Privacy review PDF generation Director review Infrastructure Team Bcc These checks provide users with a structured checklist to verify the completeness and quality of submission documentation before final submission. 6. Structured Form Interface The Submission Completion Form is organized into grouped sections, including CostX Checks and Document Checks , making the required verification activities easier to complete and review. The interface uses appropriate controls such as: Checkboxes Dropdowns Read-only information fields Team and Channel selectors The application is designed to provide a responsive and user-friendly experience while handling the complete submission checklist. 7. Automated Submission Processing When the Submission Completion Form is submitted, automated workflows process the submission information. The automation is designed to: Trigger a notification when a form is submitted. Save submission metadata in the configured storage system. Maintain the relevant Microsoft Teams/Channel context associated with the submission. This reduces manual processing and ensures that submission information is captured consistently. 8. Centralized Submission Records Each completed form is maintained as a structured submission record containing the user, Team, Channel, date, status, and results of the individual completion checks. This provides a centralized record of completed submission checks and allows the submission information to be stored and retrieved through the configured SharePoint or Dataverse storage environment. 9. Microsoft Teams Integration The application is designed to operate within the Microsoft Teams environment and associate submissions with the appropriate Teams and Channels. The planned rollout includes embedding the application across 20 channels , allowing users to access the submission process from the relevant working environment. 10. Testing and Validation The complete solution is tested to ensure that the application, submission data, dynamic Team/Channel selections, and automated workflows operate correctly together. Testing includes: End-to-end user flow validation Verification of submitted data Dynamic Team and Channel selection testing Form field validation Functional testing User feedback and refinements This helps ensure that the application and automation operate correctly before the final rollout. Overall Application Workflow The process begins when a user accesses the Submission Completion application and selects the relevant Microsoft Team and Channel or Channels. The selected Team and Channel information is automatically associated with the submission. The user then completes the Submission Completion Form by reviewing the required CostX and Document Checks. Each requirement is verified through the appropriate checkbox or form control, while submission information such as the user and submission date is captured as part of the record. Once the required checks have been completed, the user submits the form. The automated workflow processes the submission, stores the relevant metadata in the configured storage system, and triggers the required submission notification. The completed record provides a centralized history of the submission, its status, associated Team/Channels, and the checks performed before completion. Select Team & Channel(s) → Open Submission Completion Form → Complete CostX Checks → Complete Document Checks → Review Submission → Submit Form → Store Submission Record → Trigger Notification → Track Submission Status
Location: Brisbane, Queensland
Industry: Construction / Infrastructure / Quantity Surveying / Cost & Contract Management Consulting
Challenge and Requirements
1.
Solution Delivered
CodeScale delivered a powerapps solution using PowerApps, PowerAutomate, SharePoint for Construction / Infrastructure / Quantity Surveying / Cost & Contract Management Consulting.
Technology Used
- PowerApps
- PowerAutomate
- SharePoint
Business Outcome and Impact
CostX Completion Checks The application includes a dedicated CostX checklist to ensure that key CostX-related requirements have been reviewed before submission. The checks cover areas such as: Object visibility and duplicate checking Model and design consistency Revit scale issues Workbook recalculation Reference verification Drawing scale verification Bulk checks Master set completion Users complete these checks through checkbox-based fields within the Submission Completion Form. 5.
Project Screenshots
