Skip to content
Back to skills

Quantity Surveying Troubleshooting Guide

ASecurity

Diagnose and resolve common problems a quantity surveyor meets in construction projects and offices. TRIGGERS - Use when a quantity surveyor needs a troubleshooting & problem solving for developers, contractors and public clients in construction projects and offices.

  • 38 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 12, 2026
developmentgorailsdatabasedocumentation

Works with

  • cli

Security analysis

A100/100

Scanned November 12, 2026

npx -y skills add lionelsimai/claude-skills-collection --skill quantity-surveying-troubleshooting-guide --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quantity Surveying Troubleshooting Guide?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Quantity Surveying Troubleshooting Guide
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lionelsimai-quantity-surveying-troubleshooting-guide/badge)](https://www.skillsdirectory.com/skills/lionelsimai-quantity-surveying-troubleshooting-guide)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: quantity-surveying-troubleshooting-guide
description: |
  Diagnose and resolve common problems a quantity surveyor meets in construction projects and offices.
  TRIGGERS - Use when a quantity surveyor needs a troubleshooting & problem solving for developers, contractors and public clients in construction projects and offices.
category: Quantity Surveying
license: MIT
version: 1.0
---
# Troubleshooting & Problem Solving — Quantity Surveying

Diagnose and resolve common problems a quantity surveyor meets in construction projects and offices. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.
This skill is written for a quantity surveyor working with developers, contractors and public clients in construction projects and offices.

## When to use
- You are a quantity surveyor preparing, delivering or reviewing this part of your work in construction projects and offices.
- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Bill of quantities | an itemised list of materials and work for pricing |
| Valuation | an assessment of work completed for interim payment |
| Final account | the agreed total cost at a project's end |

## Workflow
1. **Step 1** - Describe the problem precisely from the record in bills of quantities — when it started, what changed, who it affects
2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to cost overruns unreported early
3. **Step 3** - Run checks in a logical order using measurement software, changing one variable at a time so the cause can be isolated
4. **Step 4** - Apply the fix, then verify against valuation timeliness that the problem is actually resolved, not just quieter
5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work

## Profession-Specific Components
| Component | Details for Quantity Surveying |
|-----------|-------------------------------|
| Core documentation | bills of quantities; valuations; cost reports; final accounts |
| Core tools & equipment | measurement software; cost databases; BIM models; spreadsheet models |
| People involved | developers, contractors and public clients; the quantity surveyor; colleagues and other services in construction projects and offices |
| Primary record | bills of quantities — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in construction projects and offices] | **Objective:** [What this must achieve] | **Audience:** [developers, contractors and public clients and other stakeholders]

The finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in bills of quantities.
2. **Short-term:** Complete the workflow steps and record outcomes against valuation timeliness.
3. **Medium-term:** Review results, close actions, and update local procedures in construction projects and offices.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| valuation timeliness | Agree a local target and track the trend | Measured from bills of quantities and reviewed on a set cycle |
| cost forecast accuracy | Agree a local target and track the trend | Measured from bills of quantities and reviewed on a set cycle |
| final account agreement times | Agree a local target and track the trend | Measured from bills of quantities and reviewed on a set cycle |
| dispute rates | Agree a local target and track the trend | Measured from bills of quantities and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: cost overruns unreported.
- Never let this happen: measurement errors.
- Never let this happen: contractual deadlines missed.
- Work only within the competence and authority of a quantity surveyor; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to construction projects and offices's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A quantity surveyor in construction projects and offices applies this workflow for developers, contractors and public clients: they open
bills of quantities, work through the five steps using measurement software, and close by recording
the outcome against valuation timeliness and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.