Subcontractors depend on information they do not always control. A specialist team may plan labour, order materials and prepare an installation based on drawings issued by the main contractor. The work can then be affected by a revised detail, an unanswered technical question, a change in sequence or a condition discovered on site. The quality of the subcontractor’s work depends partly on how quickly that information reaches the right people and how clearly it is recorded. On many projects, the information exists. The difficulty lies in finding the current version, understanding what changed and making sure the people carrying out the work have received it. That is where alignment begins.
A revised drawing can be uploaded correctly and still fail to influence the work on site. The project manager might receive the update immediately, while the supervisor continues working from a printed copy issued earlier in the week. A fitter may have downloaded the previous revision to a mobile device. Another team member is possibly using an attachment forwarded through email. In this situation, the document has been controlled at project level, but the operational process has broken down.
Subcontractors need to agree on how drawings will move from issue to use. Someone must review each revision, identify the affected work and communicate the change to the people involved. Printed and downloaded copies also need to be considered.
The team should be able to answer three questions without delay:
A shared document environment helps, but responsibilities remain essential. Technology can make the latest information visible; the project team still needs a dependable process for reviewing and acting on it.
The handover of a revised drawing also depends on how efficiently the new package is prepared. Repetitive manual work can delay the point at which the information becomes available to supervisors and site teams, even when the revision has already been received by the project office. AI-powered drawing upload can reduce part of that administration and help the project team organise new packages more efficiently. The review and communication responsibilities remain important, particularly where a change affects work already planned or underway.
Questions arise throughout construction for many reasons: an unclear dimension, a site condition that differs from the design, a clash with another trade or a material still awaiting approval.
Many of these questions start informally, through a conversation on site, a meeting or a photograph sent to the project manager. As more people and channels become involved, the original context becomes harder to follow. The response can end up in an email thread, while a revised drawing is issued separately and the site team continues working from earlier information.
By the time the answer reaches the people carrying out the work, the original question, the decision and the latest project information are often sitting in different places.
A structured RFI process gives the question a clear owner and deadline, while keeping the supporting drawings, photographs and final response in one place. The people planning and carrying out the work can then see both the current status and the agreed answer. For subcontractors, this visibility supports better decisions. A supervisor can see whether the issue has been resolved, whether work can continue and which information has been approved. The project record remains useful long after the immediate question has been answered. It provides a traceable explanation of what was raised, how the team responded and which information guided the work.
Construction teams often need to make quick decisions on site. A main contractor asks a subcontractor to revise an installation, complete additional work or change the sequence, and the instruction is usually clear to everyone involved at the time. The difficulty comes later, when the project team needs to confirm exactly what was agreed. The commercial team needs to know who issued the instruction, the project manager needs to identify which area was affected, and the supporting photographs or marked-up drawings need to be easy to find.
A simple project record makes that follow-up much easier. It should show what was requested, who issued it, where the work was affected and which drawings, photographs or other information support the instruction. If the request could affect programme or cost, it is also useful to capture the relevant evidence while the work is still taking place. Recording this information should be part of the site workflow, rather than an administrative exercise carried out weeks later. When the project, site and commercial teams need to revisit the decision, they have a clear record of what happened and the information that supported it.
An issue record only becomes useful when another person can understand and act on it. A photograph with a short caption such as “access blocked” may make sense to the person standing in the area, but it gives much less guidance to a project manager reviewing the item later. Useful records include the location, a clear description and the person or company responsible for the next step. A due date and current status help the wider team understand whether the issue is being managed or has begun to affect progress.
Context matters particularly when several trades are involved. A subcontractor identifies an obstruction caused by preceding work, but the resolution requires input from the designer, main contractor and another specialist team. Clear ownership of the next action prevents the issue from remaining open while every party waits for someone else to respond. The record should also show how the issue was resolved. Photographs, comments and completion evidence create a clearer history and reduce repeated questions.
Site photographs are valuable because they capture conditions that may later become hidden, altered or difficult to inspect. Their usefulness depends on context.
A close-up photograph explains a specific item without showing how it relates to the surrounding work. Where access, neighbouring trades or the condition of a wider area affects the next decision, a dated 360 record can provide more useful context. Linking that visual record with the relevant drawing or issue helps the office understand where the condition belongs and compare it with a later capture. The team should still agree when this level of evidence is necessary and which workflow it is intended to support.
Snagging becomes harder to manage when several lists are circulating at the same time. The main contractor works from one tracker, the subcontractor from another, while the client or consultant keeps a separate report. Before long, the same item appears in different places with slightly different descriptions or statuses.
That creates unnecessary follow-up, especially towards the end of the project when teams are already under pressure to close work and prepare for handover.
A shared digital snag process keeps each item connected to the right location, description, owner, due date and supporting evidence. Subcontractors can see what has been assigned to them, update progress from site and add photographs or other evidence as work is completed. The main contractor gets a clearer view of the current position without chasing separate updates, while the subcontractor keeps a record of what was corrected and when.
Field processes need to work in the field. Supervisors and installers move between locations, work under time pressure and might have limited connectivity. A process that requires too many steps will quickly be replaced by a message, a paper note or a photograph stored for later. Mobile access should make routine tasks straightforward. Site users should be able to review drawings, check assigned actions, raise an issue, add evidence and update completed work without returning to the office.
Offline access also matters. Basements, plant rooms and large construction sites do not always provide a reliable connection. Teams need access to the information required for the task and a clear way to synchronise updates once connectivity returns. Adoption also depends on relevance. Site teams are more likely to use a platform when it helps them complete work, resolve questions and avoid repeated reporting.
Every main contractor has its own systems and expectations. A subcontractor probably works with one platform on one project, email-based processes on another and a combination of spreadsheets and shared folders elsewhere. Complete standardisation across all projects is unlikely, but the subcontractor can still define its own minimum working practices.
For example, the business can decide that every important instruction must be recorded, every drawing revision reviewed before distribution and every completed snag supported by evidence. Technical questions should always have an owner, while critical photographs should remain connected to a project location or record. These habits create greater control even when the external systems change. They also help new project managers and supervisors understand what the company expects. The team does not need to rebuild its working method at the start of every project.
A short discussion at project start can prevent many of the issues that later consume time. The main contractor and subcontractor should agree where current drawings will be stored, how revisions will be communicated and how technical questions should be raised. They should also clarify the process for site instructions, snags, evidence and overdue actions.
The most useful outcome is a workflow that both sides understand and can apply during normal project activity. A process that looks complete in a procedure document may still fail if site users cannot access it or if responsibility remains unclear. The project team should therefore test the workflow using realistic tasks, such as receiving a revised drawing, raising a question or closing a snag from site.
ProjectSight brings project and site information into one centralised environment, helping subcontractors keep drawings, documents, RFIs, issues, digital snag lists, checklists and site evidence connected with the work they support. AI-powered drawing upload can reduce repetitive administration when new packages and revisions arrive, while customisable dashboards help project managers focus on current responsibilities and open work.
ProjectSight 360 Capture can add a dated visual record where a single photograph does not explain the wider site condition. Mobile and offline access support normal site use, while unlimited free collaborators can participate in approved ProjectSight workflows, subject to permissions and role-based feature limits. In-app assisted onboarding helps new users become familiar with the agreed process.
Construsoft can help project teams review how information currently moves between the main contractor, subcontractors, office teams and the site, then select a practical field collaboration workflow for the first rollout stage.
Construsoft offers the Field Collaboration Checklist, which helps subcontractors assess how they manage drawings, technical questions, site instructions, issues, evidence and mobile access. Complete it using a current or recently completed project. The results can help your team identify recurring gaps and choose three practical priorities.