Use cases · 13

Tawasol for Construction: Site Communication for Projects and Contractors

Contracting and ConstructionInside Tawasol13
Inside Tawasol
Inside Tawasol — Organization
ShawtsOrganizationLibraryTracking

Built around your operations

Project construction crews rotate with every new phase, and their informal messaging groups usually disappear with them. Tawasol keeps the operational record with the general contractor. Every project site operates as its own dedicated unit with sub-groups for each trade, subcontractors coordinate inside role-restricted channels, and every site instruction, clash photo, and consultant approval remains permanently archived after the crew moves on.

The Operational Breakdown

  • Project Chats Disappear: Sites coordinate through informal chat groups on personal phones, which vanish when contractors rotate off the job.
  • Building from Superseded Blueprints: Trade crews build off an outdated paper drawing that has been sitting in the site shack for weeks, causing costly rework.
  • Subcontractors See Proprietary Data: External trade partners added to general communication channels gain access to commercial terms and discussions outside their scope.
  • Verbal Site Directives Lead to Claims: Technical queries and drawing clashes are settled over quick phone calls, leaving zero written proof when delay claims surface later.

How Tawasol Solves It

Scroll the table to read all columns

Operational ProblemWhat Tawasol DoesThe Functional Result
Project Chats DisappearProject-specific units and trade-specific groups managed inside the general contractor’s private platform.All project communications remain institutional property rather than private phone histories.
Superseded BlueprintsThe latest verified drawing revisions hosted in the mobile Library, accessible via mobile devices.Site crews build exclusively from current, approved drawing sets.
Subcontractor Data ExposureDedicated subcontractor channels configured with strict role-based access rules.Trade partners coordinate their work packages without seeing project-wide communications.
Verbal Site DirectivesBlueprints, conflict photos, and engineer sign-offs logged inside tracked project threads.Technical variations remain permanently archived against the project's digital record.

Case Studies in Practice

Scenario A: New Method Statement Rollout

The Role
Project Health and Safety Officer.
The Situation
A revised method statement for heavy pre-cast concrete lifting takes effect for all crane crews starting Sunday morning.
The Action
The approved method statement uploads to the Library and deploys via a Shawt to that project site's unit with the document attached.
The Outcome
Riggers and crane operators review the safety steps on their phones before lifting begins, while site superintendents confirm receipt inside the channel.

Scenario B: On-Site Structural Drawing Clash

The Role
Site MEP Engineer.
The Situation
Installed structural beams on Level 12 physically clash with the planned routing for primary HVAC ductwork.
The Action
He photographs the physical clash and posts it to the project engineering channel along with the blueprint reference number.
The Outcome
The consulting structural engineer reviews the photo from his desk, authorizes an elbow offset in the thread, and uploads the revised sheet to the Library. The photo, timestamp, and approval remain permanently logged against the project.

Comprehensive Sector Capabilities

  • Trade-Specific Communication Channels: Keep steel fixers, MEP teams, drywallers, and painters focused on their respective scopes without cluttering general site communication.
  • Fast Site Workforce Provisioning: Onboard dozens of trade laborers in minutes via bulk Excel upload; workers sign in using their National ID or site badge number.
  • Direct Mobile Safety Reporting: Safety officers document near-misses, missing fall arrest gear, or scaffold defects with instant photos from the work face.
  • Toolbox Talks and Safety Training: Announce mandatory toolbox talks under Events; site crews register via mobile, and safety officers log verified attendance.
  • Permanent As-Built Documentation: Drawing revisions, safety sign-offs, and site variations remain archived against the project indefinitely.

Measurable Value

  • Day-to-day: Work crews arrive on site briefed on the day's tasks, while technical RFIs reach the engineering office with photographic proof attached.
  • Over time: Launching a new construction site becomes a structured, repeatable process, while project records survive long after the physical crew departs.

Frequently Asked Questions

Can construction workers use Tawasol without an enterprise email address?

Yes. Laborers and trade workers sign into the mobile app using their Employee ID or National Civil ID number.

Can subcontractors participate with limited system privileges?

Yes. Subcontractor groups are governed by role-based access, ensuring trade partners see only communications relating to their trade package.

Do project archives remain accessible after the job is finished?

Yes. All communications, photos, and drawings remain archived against the project record for future claims defense.

Can announcements target a single trade crew?

Yes. Senders direct each message to a specific project unit, a trade group, or named individuals.

How quickly can a newly mobilized site crew be onboarded?

Entire workforces can be uploaded in a single step using formatted Excel templates.