ClickUp for Construction Contractors in the Gulf: Tenders, Submittals, Progress Claims and Snagging

Quick answer

ClickUp works for construction contractors in the Gulf as the coordination layer above the ERP, estimating and BIM tools — where submittals, RFIs, site progress, snags and the monthly claim are tracked. A project–package–zone Workspace, statuses from tender to defects liability, the consultant as a guest and the site team on the mobile app cover it.

At a contractor we worked with in Doha, the monthly progress report began as a voice note. The site engineer recorded it on the 24th, a planner typed it into Excel on the 25th, and the quantity surveyor turned it into the claim on the 26th, the day before it was due. Nobody disputed the percentages because nobody could check them: the photos were in WhatsApp, the consultant's comments were in a PDF, and the subcontractor's figure was in a different spreadsheet.

Main contractors, MEP specialists and fit-out firms in the UAE, Qatar and Kuwait all run the same four loops: submittals and RFIs, daily site progress, the monthly claim, and snagging through to handover. This guide is for you if you own one of them. If you sit on the developer's side of the table, read our guide for real estate developers instead.

What ClickUp is, and isn't, for a contractor

ClickUp isn't an estimating tool, a cost-control ERP, a BIM platform or the document control system that records transmittals for a dispute. Rates, BOQ quantities, certified values and the model stay where they are. What those systems handle badly is the work between people and companies: who is waiting on whose approval, what the site did today, which snag is still open on the ninth floor, whether the claim is ready.

That coordination layer is the job. We'd draw the line in week one, because the rollouts we've seen fail are the ones that tried to move the BOQ into Custom Fields. Keep the money in the ERP. Put the handoffs in ClickUp.

A Workspace map: projects, packages and zones

The structure that has held up on the sites we've worked with mirrors how a contractor is paid. One Workspace for the company. A Space per project, because each has its own consultant, approvals and guests. A Folder per work package: civil, MEP, finishes, external works. A List per zone, floor or building, so the site engineer opens one List in the morning and sees only the work in front of them.

Custom task types carry the difference between kinds of work: Activity for a programme item, Submittal for a shop drawing or material awaiting approval, RFI for a question to the consultant, Snag for a defect, Variation for an instructed change. Custom Fields by task type keep each honest: a Submittal carries the specification reference, revision and the consultant's response code; a Snag carries the zone, the subcontractor and a photo. Task-type availability varies by plan, so confirm yours first. One rule we'd never break: don't create a List per subcontractor. The subcontractor is an assignee or a guest; the List is the place.

Statuses that follow the job, from tender to DLP

A project's top-level statuses follow the contract, not the software: Tender, Awarded, Mobilised, In progress, Substantially complete, Snagging, Handed over, DLP, Closed. Activities use a shorter set, Not started, In progress, Inspected, Done, because Inspected is the status that matters on site: the consultant has seen it. Submittals and RFIs get their own flow, Submitted, Under review, Returned with comments, Resubmitted, Approved, mirroring the response codes consultants already use.

Keep the words the ones your site says on the radio; a status nobody says out loud lies in the dashboard. The useful habit, explained in our statuses guide, is to make Inspected a Done-group status for Activities, so dependencies release when the consultant signs rather than when the foreman says it's finished.

Submittals, RFIs and the approval chain

Most delay on a Gulf site is waiting, and most waiting is invisible. Model it. A shop drawing submittal blocks the material order, which blocks the activity, which blocks the inspection. Create those as dependencies, so the Gantt shows the real chain and the Reschedule Dependencies ClickApp moves everything behind a late approval instead of leaving it to the planner. Our dependencies guide covers the mechanics; the construction-specific part is who sits in the chain.

The consultant's engineer is a guest with edit access to the Submittals List and nothing else, so they set Returned with comments themselves and your engineer hears at 10 am rather than at the Thursday meeting. Authorities don't log in, but they get a task: the municipality inspection, the civil defence approval, the utility connection, each with its reference number and expected response in Custom Fields, each blocking the activity that can't start without it. Our procurement approvals guide shows the same pattern for subcontract awards. If the site is waiting on it, it has a task.

The site: diaries, progress and the mobile app

Your site team doesn't sit at a desk, and a tool they won't open on a phone is a tool they'll ignore. The mobile app gives a site engineer today's Activities in their zone, a checklist to tick, a camera for the progress photo and a comment thread instead of a voice note nobody transcribes. The daily site diary becomes a Form filled from the phone, weather, manpower by subcontractor, plant, delays and a photo, creating one task per day that the project manager reads the same evening.

Two things to train rather than assume. ClickUp's offline mode lets the team create tasks and view ones they've already opened without signal, but editing waits for a connection, which matters in basements and on remote sites. And progress is a number only if someone enters it: a Percent complete Custom Field on each Activity, updated by the engineer who inspected it, turns the diary into something the claim can use.

The monthly claim as a checklist

The progress claim is the one deadline every contractor respects. Give it a task: a recurring task per project, due three working days before the contractual cut-off, with a checklist that reads like the quantity surveyor's routine. Percentages confirmed by the site engineer. Subcontractor statements received. Variations listed with their status. Photos attached by zone. Claim issued. Each item has an owner, so a late subcontractor statement shows on the 22nd, not the 26th.

The money still lives in the ERP. What ClickUp gives the commercial manager is readiness: a Dashboard with the claim tasks across every project, the Activities whose Percent complete hasn't moved in two weeks, the Variations stuck in Priced, and the submittals Under review longer than the contract allows. We'd keep labour hours in payroll and use time tracking only for your own engineers on fixed-fee design.

Snagging, handover and the defects liability period

An MEP subcontractor we met in Kuwait kept three hundred snags in a PDF the consultant had marked up by hand. Three were closed twice. Eleven were never closed, and the retention was still being argued over a year after handover. Snagging is where reputation and retention money meet, and it's the loop ClickUp fixes fastest. A Snag is raised from the phone through a Form: zone, trade, description, photo, severity. It lands in the zone's List assigned to the subcontractor, who closes it with a photo; the engineer sets Inspected; the consultant, as a guest, closes it or sends it back.

Drawings get their own loop. ClickUp's Proofing lets you drop a comment on an image or PDF attachment, so the consultant's markups sit on the drawing inside the task rather than in an email thread; guests can use it, it doesn't work on attachments stored in cloud drives, and usage limits vary by plan. Across several sites, a Location Custom Field with a Map view shows every open Snag as a pin coloured by status. After handover, DLP inspections become recurring tasks at the intervals the contract names, owned by the person who will actually visit.

A 60-day rollout, timed to the programme

Start on one live project, not on the template library, and respect the regional calendar: the summer midday-break rules shorten the site day for three months, Ramadan shortens it further, and nobody adopts a new tool in the week before a claim.

• Days 1–10 — draw the line with the ERP; agree the Workspace map and the five task types; load one project's programme and open submittal register.
• Days 11–25 — build the status flows, the dependency chains, the diary and snag Forms and the first six Automations; run two weeks of site diaries from the phone.
• Days 26–45 — bring the consultant's engineer and the three largest subcontractors in as guests; run one monthly claim from the checklist; add the authority tasks.
• Days 46–60 — train by role in English and Arabic, foremen included; retire the voice note; template the Space for the next tender.

Three mistakes to avoid

We see the same three on almost every site.

• Rebuilding the BOQ in Custom Fields. The moment a value in ClickUp disagrees with the ERP, the site stops trusting both. Reference the cost code; don't copy the money.
• Leaving the consultant outside. If the engineer reviews in email and your coordinator retypes the response code, every submittal is a day older.
• Starting with a template instead of a project. A perfect template built in the office meets a site that says 'we don't work like that'. Build on the live job; template what survived.

How BuyClickUp helps

BuyClickUp is an independent ClickUp partner operated by Inspark, a Salesforce and ClickUp consultancy serving the UAE, Qatar and Kuwait from Dubai. For contractors we design the Workspace map and task types around how you're paid, build the submittal and snagging loops with your consultant in the room, connect ClickUp to the ERP or Salesforce environment your commercial team already uses, and train every role, from the commercial manager to the foreman, in English and Arabic. Tell us about your projects through our contact page, or take the free ClickUp readiness assessment.

ClickUp is a trademark of Mango Technologies, Inc. BuyClickUp is not ClickUp. This article reflects our reading of ClickUp's help documentation in October 2026. Feature availability, including custom task types, Proofing, Map view, guest seats and the scheduling ClickApps, varies by plan and changes over time; confirm current details with ClickUp before relying on them.