Issue Investigation for General Contracting

Access the complaint entry in your tracking system and open any linked warranty cases, RFIs, or emails. Confirm you are viewing the latest version of each record.

Slowly read the complaint details and write a short summary in plain language that captures what the client is upset about, the impact on them, and what they want to see happen.

From your summary, list the main questions you need to answer (for example, “Was the delay caused by our team or by a change order?”, “Did we miss a scheduled inspection?”, “Was the work performed per spec?”).

Decide which topics belong in this investigation and which do not. For example, if the client is unhappy with both schedule and unrelated design choices, you may focus investigation only on schedule while logging design dissatisfaction separately.

Look for any internal or external deadlines linked to this complaint, such as upcoming inspections, legal response deadlines, or client-stated dates. Note these clearly so you can prioritize work.

Enter a short “Investigation Scope” note in the complaint record listing what you are investigating and the key questions. This will guide your work and help others understand your focus.

Based on the complaint scope, list out which documents matter: contract and amendments, drawings/specs, approved change orders, schedules, daily reports, emails, text logs (if captured), and meeting minutes.

Retrieve these documents from your project management, document management, or email systems. Save copies into a dedicated investigation folder with a clear naming convention (for example, using project and complaint ID).

Within email threads and daily logs, narrow your focus to the dates before and around the issue (for example, the week a deadline was missed or the time the defective work was performed). This keeps the volume manageable.

As you skim documents, mark key items such as schedule commitments, client approvals, delays notices, or quality concerns. Use highlights or separate notes to capture these references.

Notice if any expected documents are missing (for example, a promised follow-up email that was never sent, or an unsigned change order). Add these gaps to your list of questions.

Make a short list of the documents you collected, including file names and what they show. Store this index in the investigation folder and link it in the complaint record.

From project documents and your own knowledge, list the people who played a role in the issue—such as the project manager, superintendent, estimator, scheduler, or customer service rep.

Reach out to each person and set up short calls or in-person chats. Explain that you are gathering facts for an investigation and want them to walk through what they saw and did.

Use a consistent set of questions for each person, such as “What do you remember about this situation?”, “What did you expect to happen next?”, and “What did you communicate to the client or trades, and when?”

During each conversation, write down specific facts: dates, actions, conversations, and handoffs. Avoid recording emotional comments or blame; if someone shares an opinion, label it as such in your notes.

Compare what people say to the documents you collected. Note where they align and where there are differences or gaps that may need more clarification.

Write a short summary of internal perspectives in the complaint notes, highlighting consistent facts and noting any areas where memory or interpretation differs.

Look over your notes and highlight any unclear or conflicting points about dates, conversations, or site conditions that only the client can clarify.

Write down 3–7 focused questions, such as “On which date did you first raise this concern?”, “Who from our team was present at that meeting?”, or “Do you recall what was said about the delay at the walkthrough?”

Contact the client, explain that you are following up as part of your investigation, and ask if they are available for a brief call. If they prefer email, send your questions in a clear, numbered list.

If you speak by phone, let the client answer fully without interrupting. Do not argue or try to resolve the issue during this call; your goal is to gather facts and understand their perspective.

At the end of the conversation or email exchange, restate the key points you heard to ensure you captured them correctly. Adjust your notes based on their corrections.

Enter the new information into the complaint notes, marking what came directly from the client during clarification, and date-stamp this update.

Based on the nature of the complaint (for example, quality, safety, water intrusion), decide if a physical site visit is needed or if existing photos and reports are enough. When in doubt, lean toward verifying on site.

If a site visit is needed, coordinate with the client and field staff to set a time. If not, consider asking the client for current photos or video clips showing the condition today, especially if time has passed since the last visit.

When on site, follow a basic checklist guided by the complaint type (for example, for a water leak, look above, below, and around the area; for a finish issue, check overall consistency and adjacent areas).

Take clear photos and write down specific observations like sizes of cracks, locations of stains, or visible defects. Note anything that differs from what was previously reported.

Try to assess whether the condition is stable, improving, or worsening. Ask the client on site if they have noticed changes since the issue was first reported.

Add your site visit notes and photos to the complaint case, clearly dated and labeled so they can be referenced later in your analysis.

Go through contracts, schedules, emails, daily logs, and your notes to pull out important dates: start dates, promised dates, actual completion dates, change order approvals, missed appointments, and complaint receipt.

Include events that came from interviews and client conversations, such as “client reports first leak on this date” or “superintendent recalls rescheduling on that date.” Mark these as reported if there is no written record.

Place all events onto a simple list or visual timeline in date order. Include enough detail to understand what happened without reading all the source documents again.

Look for missing periods where you have little information and for events that conflict (for example, client saying a visit did not happen when a log shows it did). Mark these as areas needing careful interpretation.

From the timeline, identify when responses took longer than your usual standards, when commitments were not kept, or when information should have been handed from one person to another but was not.

Store this timeline where others can access it and note in the complaint record that a timeline has been prepared, including where it can be found.

Write a simple, factual problem statement (for example, “Client move-in was delayed by two weeks,” or “Client found water staining on ceiling in living room”). Make sure it is specific and neutral.

Ask “why did this happen?” and write down the answer. Then ask “why” again about that answer. Repeat this at least three to five times until you reach a process or system-level reason rather than a single person’s action.

Note supporting factors that made the problem more likely or worse (for example, unclear scope, lack of documented schedule updates, poorly defined handoff between estimating and operations).

Distinguish between things your company could reasonably control (internal communication, planning, supervision) and external factors (weather, client changes, regulatory delays). Both matter, but you will address them differently.

Ensure that your root cause statements are supported by the documents, interviews, and site observations you collected. Avoid guessing or stretching beyond what evidence can support.

Document your root cause and contributing factors in a short paragraph in the complaint record so they are clear for anyone reading later and for those planning corrective actions.

Look at the prime contract and key subcontracts to understand who was responsible for design, construction, and inspection of the affected work. Note any clauses related to delays, defects, or coordination.

Break the problem into parts (for example, original workmanship, later damage, communication about delays) and assign likely responsibility for each part: your company, specific trade, supplier, client, or shared.

Beyond contractual responsibility, assess how each potential decision (for example, strict contract enforcement vs. goodwill repair) might affect client relationship, reputation, and future work.

Note if the issue involves safety hazards, code violations, or substantial financial exposure. Flag these clearly so leadership can weigh them properly in the resolution stage.

Base your responsibility assessment on facts and contracts, not on who is most upset or whose personality is strongest. If there is genuine uncertainty, mark it as shared or unclear and explain why.

Write a concise note describing who you believe is responsible for each key part of the issue and where judgment calls may be needed.

Open your company’s investigation summary template, or create a simple structure with sections for Background, Facts, Timeline Overview, Findings, Root Causes, and Responsibility.

In a short paragraph, describe the project, client, and nature of the complaint in neutral terms. Include dates and the general context without going into full detail.

Create a bullet list of the most important confirmed facts (for example, “Original substantial completion date was X,” “Client was notified of delay on Y,” “Leak was first reported on Z”). Stick to points that are documented or clearly corroborated.

Write a few sentences explaining what you concluded about root causes and who is responsible for what parts of the issue, referencing specific evidence where helpful.

If there are areas you could not fully confirm, list them in a separate sub-section along with why they remain uncertain. This transparency helps decision-makers understand the limits of the investigation.

At the end of the summary, list the key documents, photos, and timelines you prepared, and link or reference where they are stored for anyone who wants deeper detail.

Determine who needs to review the investigation summary to decide on resolution—this might include the project manager, operations manager, customer service lead, and possibly ownership for higher-risk issues.

Send the investigation summary and links to key supporting documents to the decision-makers with a short cover note highlighting main findings and any urgent considerations.

For complex or high-risk issues, schedule a short meeting or call to walk through the summary, answer questions, and ensure everyone has a common understanding before deciding next steps.

In your cover note or meeting, outline a few practical resolution paths (for example, “goodwill repair,” “shared-cost solution,” or “policy explanation without work”), making it clear these are suggestions, not commitments.

Change the status in the complaint system to something like “Investigation Complete – Pending Resolution” so it is clear that the fact-finding stage is finished and the case is waiting for resolution decisions.

Ensure there is a named person responsible for leading the resolution stage. Record their name and role in the complaint record so everyone knows who is driving the next steps.