The Dig Daily Dose

The Dig Daily Dose

By The Dig TeamNewsDaily News
Download on the App Store

The Dig Daily Dose episodes

  • Keep the Next Warranty Action Visible After the Visit

    Source edition: Keep the Next Warranty Action Visible After the Visit — 2026-11-08.

    After the next service visit

    Use this editorial coordination check with the responsible project participants:

    1. Record the visit and the attending party's observation.

    2. Name the owner of each unresolved next action.

    3. Set the next review through the existing service process.

    For the wider field-risk review, use our existing free Construction Risk Radar alongside the project record.

    Open the free Construction Risk Radar (https://www.thedigdailydose.com/products/construction-risk-radar)

    ---------- ## Keep the Next Warranty Action Visible After the Visit

    A service visit has happened. The person who opened the report hears that someone attended. The contractor's coordinator is waiting for another document. The facilities team still has an unanswered question. If the shared record says only visited, the next shift cannot tell what remains open or who is carrying it.

    The leadership decision comes after the appointment: connect the observation, the unresolved action and its next review in one traceable record. Attendance and resolution are different events. Keep that distinction visible rather than asking colleagues to reconstruct it from several conversations.

    The August 2026 UFGS 01 78 00, Closeout Submittals, section 1.9.6, describes warranty reviews supported by service records and issue logs. Its tracking provisions connect identified issues with responsibility, corrective action, status and resolution dates. This federal guide requires project-specific tailoring; the actual contract and authorized reviewers determine your project's requirements.

    Describe what happened without closing the question

    Our editorial recommendation is to record a visit as a dated event against the existing service reference. Identify the report or observation supplied by the attending party. Keep the original description intact, and distinguish what someone observed from what an authorized reviewer has accepted.

    For an illustrative case, a facilities coordinator receives a note that a contractor attended an interior finish concern. The note requests a document before the proposed next step can be reviewed. Recording the attendance is useful. Marking the issue resolved at that point would erase the open dependency.

    This example illustrates communication only. It does not determine warranty coverage, diagnose a defect, authorize work or establish a contractual response deadline. Responsible specialists retain those decisions, using the governing documents and established reporting channels.

    Make the next action readable by someone else

    Ask the coordinator to name the unresolved action in ordinary language. Which document is missing? Who will supply it? Who needs to review it? Where will the response be recorded? A status label becomes useful when a colleague can connect it to a specific next step.

    Record a review point through the project's normal process. Keep an internal reminder distinguishable from a contractual deadline or service promise. If the responsible participant has not accepted the assignment, show that the ownership remains unconfirmed. Copying someone on an email does not prove that person has taken responsibility.

    Keep the reference in the system the team already uses. A separate spreadsheet may help coordinate work, but it should link to the authoritative record rather than become a competing account. Restrict personal details and sensitive operational information to approved channels.

    Carry the unresolved item across the handoff

    When the coordinator changes, review open items together. Have the receiving person explain the last recorded event, the outstanding action and the location of its supporting evidence. A difference between the two accounts identifies a communication gap to resolve before the outgoing person leaves.

    Keep the final disposition connected to the same reference. A completed visit, a submitted recommendation and an accepted resolution should remain distinguishable. Ask the authorized participants what evidence supports closure; do not turn an unanswered message into acceptance or silently overwrite an earlier status.

    Review a small cohort before claiming improvement

    At the next service coordination review, select a defined group of open reports. Count how many have a traceable latest event, an identified next-action owner and a recorded review point, against every report selected. Show unresolved ownership separately. This measures record clarity, not coverage, service quality, prevented callbacks or financial return.

    Choose one report that another coordinator will inherit this week. Make its next action understandable without the original participants in the room. That is a practical result the team can check before it claims a broader benefit.

    Share this decision: Forward this briefing to the coordinator inheriting your next open service report. New readers can subscribe to The Dig Daily Dose.

    Source note: UFGS 01 78 00, August 2026, section 1.9.6, reviewed October 30. The scenario, handoff questions and internal measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Connect Each Waste Ticket to Its Material Record

    Source edition: Connect Each Waste Ticket to Its Material Record — November 7, 2026.

    Connect Each Waste Ticket to Its Material Record

    The container has left the site. An invoice has arrived. The project report needs an updated total. Before those three events become one confident statement about the material, the team needs to know which supporting document belongs to which record.

    Consider an illustrative project with several non-hazardous material collections during the same week. One ticket describes a specific material; another uses a general description. A colleague preparing the report can find both files, but cannot immediately explain which collection each represents. The gap is not the amount of paperwork. It is the connection between the evidence and the entry people intend to use.

    Start with the document, then review the entry

    The federal UFGS 01 74 19, Construction Waste Management and Disposal, February 2019 with Change 3 dated November 2021, addresses records in sections 1.8.1 and 1.8.2. It calls for documentation of material types and quantities, retention of supporting records such as weight tickets and receipts, and a running project record. This is a guide specification for project-specific editing and non-hazardous waste. The applicable contract and responsible project specialists determine the actual reporting and handling requirements.

    Our editorial recommendation is to select one recent collection and follow its evidence into the report. Ask the record owner to identify the material description, the supporting document and the entry that relies on it. Make any missing connection explicit before carrying the quantity into a summary.

    Keep three questions beside the record

    1. What does the document identify? Locate the project or collection reference, the material description and the quantity information actually supplied. Mark an unclear description as a question for the responsible reviewer rather than silently improving it.

    2. Which report entry uses it? Link the original document to the corresponding entry in the team’s existing record system. A reviewer should be able to move from the reported figure back to its source without searching a colleague’s inbox.

    3. What remains unresolved? Give a discrepancy or missing record a named owner and a follow-up date. Keep that question visible until the responsible person records its disposition.

    These questions are a proposed document-review aid. They do not establish that a receiving facility accepted a particular material, that a load was recycled, or that any reporting standard has been satisfied. Those conclusions need their own applicable evidence and review.

    Separate a missing link from a completed outcome

    In the illustrative example, a person reviewing the general-description ticket asks the responsible participant to clarify its connection to the collection record. The original file stays intact. The question and any later clarification remain linked to it. The team can then see what was known at the time of the report and what was resolved afterward.

    A convenient filename can help someone find a document, but it should not carry the whole explanation. Use the project’s established references and retain the underlying record. If a corrected document arrives, make its relationship to the earlier version visible rather than leaving two apparently independent entries in circulation.

    Keep technical questions with the appropriate specialist. A document-review exercise should not become an improvised rule for classifying, transporting or handling materials. The leadership task is to make the evidence gap and accountable next action clear.

    Try one traceability review before the next report

    Select a small, defined group of recent records. Count how many have a retrievable supporting document and an explicit disposition for every open question, against all records selected. Record the review date and any exclusions. Treat the result as a proposed internal traceability measure; it does not prove waste diversion, cost savings, compliance or improved project performance.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    5 min
  • Make the Next-Trade Handoff Specific

    Source edition: Make the Next-Trade Handoff Specific — November 6, 2026.

    Make the Next-Trade Handoff Specific

    The next crew is on the schedule. That does not tell its supervisor what changed in the work area yesterday, which question remains unresolved or who can answer it. A handoff becomes useful when the incoming team can connect the planned task to the conditions it will actually encounter.

    Consider an illustrative coordination problem: one trade has finished its assigned work, but materials have moved and another activity is still planned nearby. The outgoing supervisor reports completion. The incoming supervisor hears that the area is available. Those statements can describe different things. Leadership needs to bring the two accounts into the same conversation before the next crew relies on an assumption.

    Start with the current conditions

    A construction case study by Babak Memarian, Sara B. Brooks and Jean Christophe Le examined 30 job hazard analysis documents and interviewed 23 professionals representing 17 companies. It identified coordination and communication gaps among the challenges and discussed keeping hazard information aligned with changing work conditions. The paper appeared in the International Journal of Construction Education and Research, volume 19, issue 2, in 2023, following online publication in 2022.

    Our practical recommendation is to use the next-trade handoff as a short conversation about the actual work area. The three questions below are The Dig Daily Dose’s editorial checklist, informed by that case study. They support coordination; they are not a study-tested inspection form or a complete job hazard analysis.

    Before the next trade starts: a three-point handoff

    1. Work area: What is complete, what remains open, and is the area ready for the next crew?

    2. Hazards and controls: What changed during the previous work, what hazards remain, and what controls are in place? Share this information with the incoming crew before work begins.

    3. Point of contact: Who can answer questions or resolve a conflict before work proceeds? Confirm the receiving crew knows whom to contact.

    If one answer is unclear, resolve it with the responsible parties. Use this checklist to support the handoff; responsible project personnel determine the required checks, controls and authorization for the actual work.

    Give the unanswered question a visible owner

    In the illustrative example, the useful next step is to identify the unresolved interface rather than repeat that the earlier task is complete. The receiving supervisor might need a decision about the material location or the timing of the adjacent activity. Record the question in the team’s existing coordination system, name the responsible decision owner and identify when the answer is needed.

    Keep an observation separate from an approval. A note saying that a package was moved describes an event. It does not establish that the new arrangement meets every project requirement. Route the technical decision to the responsible person and keep the outcome connected to the original question.

    At the next coordination meeting, select one upcoming handoff. Ask the receiving supervisor to describe the planned work area and identify any unanswered question. Compare that account with the outgoing team’s account. The point is to expose a difference while the people who can resolve it are available.

    A useful internal check: Of the handoffs selected for review, how many have an identified receiving contact and a traceable disposition for each open coordination question? Record unresolved questions separately. This is a proposed management measure, not evidence of improved safety, productivity or profit.

    For a companion discussion on keeping materials and access organized, listen to Give Every Delivery a Clear Staging Plan. Use episode 342 to prompt the next conversation about the receiving footprint and ownership of material moves.

    Source: Obstacles and Solutions to Implementing Job Hazard Analysis in Construction: A Case Study, archived in CDC Stacks. The checklist and coordination example above are our editorial application; the paper does not establish their effectiveness.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Give Stored Finish Materials a Protection Owner

    Source edition: Give Stored Finish Materials a Protection Owner — 2026-11-05.

    Before the next material move

    Use this editorial coordination check with the responsible project participants:

    1. Connect the package to its current storage instructions.

    2. Name the coordinator and designated location.

    3. Record the move and route unresolved suitability questions.

    For the wider field-risk review, use our existing free Construction Risk Radar alongside the project record.

    Open the free Construction Risk Radar (https://www.thedigdailydose.com/products/construction-risk-radar)

    ---------- ## Give Stored Finish Materials a Protection Owner

    The flooring delivery is accounted for, but the room holding it has become a temporary workshop. A second crew moves the packages to make space. The people preparing installation know where the material went; they cannot yet explain whether its new location meets the storage instructions. A logistics decision has quietly created a quality question.

    Leadership can make that question visible before installation depends on an assumption. Treat storage as a continuing assignment with an owner, a defined location and a record of changes. Receipt confirms that a delivery arrived. It does not establish that every later condition was suitable.

    The federal UFGS 09 65 00, Resilient Flooring, November 2024, section 1.4, addresses identified original packaging, clean and secure storage, environmental conditions and manufacturer-recommended stacking. It also identifies contamination considerations. This is a guide specification requiring project-specific editing. Your applicable contract, product instructions and responsible project authorities determine the requirements for the actual materials.

    Connect each location to the applicable instructions

    Our editorial recommendation is to choose one incoming finish package and put its storage information beside the location assignment. Identify the product, the current instructions, the designated area and the person responsible for coordination. Ask that person to identify any unresolved requirement before the team relies on the space.

    A generic label such as indoor storage leaves useful questions unanswered. Which room is assigned? What other activities are planned there? Who knows when the area will change? The coordinator should route technical questions to the responsible specialist rather than inventing a universal temperature, ventilation or conditioning rule for different products.

    Keep material identification connected to the package when it moves. Where a label or record is missing, make that uncertainty explicit. A colleague should be able to connect the stored item to the information used to plan its care without depending on one person's recollection.

    Make a move a recorded handoff

    Consider an illustrative project where a finish delivery must leave its assigned room because another trade needs access. Before the move, the coordinator asks the responsible participants to confirm an appropriate destination and identify any conditions that require attention. The move record names the material, old and new locations, the time and the receiving owner.

    This is a coordination example, not a technical acceptance procedure. The project team determines the necessary checks and authority. The useful leadership habit is to keep a change visible while there is still someone accountable for resolving its implications.

    If damage, exposure or an uncertain condition is reported, connect that report to the affected material identification and the established quality process. Preserve the observation and the required decision. An undocumented reassurance should not become the only evidence available to the installation team.

    Review the gap before the work depends on it

    At the next look-ahead meeting, select the finish package closest to installation. Ask who owns its current storage arrangement, which instructions support that arrangement and whether any relocation or concern remains unresolved. Give each unanswered question a named decision owner and a follow-up date.

    Use an existing project record where possible. Another disconnected spreadsheet can make the answer harder to find. A short, accessible reference linking the item, its location and the open decision is more useful than a lengthy account nobody updates after the next move.

    A useful internal check: Count the selected packages with an identified storage owner, a current location and a traceable instruction reference against all packages selected for review. Record unresolved conditions separately. This measures coordination readiness; it does not prove product compliance, prevented damage or financial return.

    Source note: UFGS 09 65 00, November 2024, section 1.4, reviewed October 28, 2026. The ownership workflow, scenario, meeting questions and internal measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Keep the Approved Sample Available for Comparison

    Source edition: Keep the Approved Sample Available for Comparison — 2026-11-04.

    Before the next delivery review

    Use this editorial coordination check with the responsible project participants:

    1. Locate the retained sample and its custodian.

    2. Link the exact approval and its conditions.

    3. Route a missing or unclear reference to the responsible reviewer.

    For the wider field-risk review, use our existing free Construction Risk Radar alongside the project record.

    Open the free Construction Risk Radar (https://www.thedigdailydose.com/products/construction-risk-radar)

    ---------- ## Keep the Approved Sample Available for Comparison

    A finish delivery reaches the project, and someone asks which sample the team approved. One person remembers the meeting. Another has a photograph. The physical reference is in a box that moved when the site office changed. The delivery now has an identity question before anyone can make a useful comparison.

    Leadership can prevent that search by treating the approved sample as a controlled project reference. Give it a known location, a responsible custodian and a clear connection to the approval record. A remembered choice becomes much easier to use when the next person can find the evidence without finding the original participants.

    The August 2026 UFGS 01 33 00, Submittal Procedures, section 1.15, limits sample approval to the characteristics or use identified in that approval and calls for incorporated materials and equipment to match approved samples. This is a federal guide specification requiring project-specific editing. The applicable contract and responsible project authorities determine the requirements for your job.

    Identify what the reference actually represents

    Our editorial recommendation is to connect each retained sample to the exact submission and disposition that give it meaning. Record the material identification, the reviewed version and the characteristics the approval addresses. Where the record contains conditions, keep those conditions beside the reference rather than reducing the decision to a broad approved label.

    That distinction matters when people use the same object for different questions. A reference reviewed for appearance may not answer a separate performance question. Ask the responsible reviewer to clarify the scope when the record is unclear. A coordinator can make the uncertainty visible without expanding an approval or deciding technical suitability.

    Make custody practical for the people doing the comparison

    Choose a storage arrangement appropriate to the item and the project's requirements. Record who can retrieve it, where it belongs and how a temporary move will be communicated. Keep its identification readable. When custody changes, make the handoff visible to the people expecting to use the reference.

    A dated photograph can help someone locate the right object and understand its label. It should be identified as a photograph, with a link to the underlying record. Do not quietly substitute an image for a physical reference where the project's comparison process requires the actual sample. Let the responsible participants determine the appropriate evidence.

    Consider an illustrative finish package with a retained panel and an approval covering specified appearance characteristics. Before the next delivery review, the coordinator confirms the panel's location and sends the current disposition to the designated reviewer. If the reference cannot be found, the coordinator records that gap and seeks the authorized next step. Nobody has to resolve the question from memory.

    Keep an unresolved reference visible

    When an item is missing, damaged or inconsistent with its label, record the condition and identify who must decide what happens next. Use the project's established quality and authorization process. Do not relabel a replacement as the original approved sample or let an undocumented conversation close the issue.

    At the next coordination meeting, select one material package approaching a comparison decision. Ask three questions: Can a colleague find the reference? Can that colleague locate the exact approval? Can the responsible reviewer explain what that approval covers? Name an owner and a resolution date for each unanswered question.

    A useful internal check: Count the selected packages with a traceable approval, a known reference location and a named custodian against all packages selected for this review. Record the review date and unresolved items. This measures reference readiness; it does not establish material compliance, avoided rework or financial return.

    Source note: UFGS 01 33 00, August 2026, section 1.15, reviewed October 27, 2026. The custody workflow, scenario, questions and internal measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Make the Substitution Differences Visible

    Source edition: Make the Substitution Differences Visible — November 3, 2026.

    Make the Substitution Differences Visible

    A supplier offers an available product while the specified one has a long lead time. The offer may deserve serious review. The leadership problem begins when the conversation carries only the attractive difference and leaves everyone else to discover the consequences later.

    Start with a comparison that makes the proposed change understandable to the people responsible for deciding it. Availability belongs in that comparison. So do the unresolved questions about fit, coordination, documentation and the work already planned around the original selection.

    The federal GSAM Submittals clause, 552.236-72 provides one specific reference point. It says general submittal review does not permit departures from contract requirements, and requires written identification of deviations or changes in resubmissions. Those provisions belong to their applicable contract context; they are not universal instructions for every project. Have the responsible project participants determine the requirements governing yours.

    Describe the change before selling its benefit

    Our editorial recommendation is a short difference record beside the formal submission. Identify the originally selected item, the proposed alternative and the exact versions of the documents being compared. Explain what prompted the request. Separate a supplier's stated availability from a confirmed commitment, and attach the dated evidence each statement depends on.

    A useful opening question is: What would a reviewer need to notice if the attractive lead time were removed from this proposal? This helps expose the assumptions hidden by urgency. It also gives the proposer a fair opportunity to explain the alternative clearly rather than relying on a product name or a broad claim of equivalence.

    Put the affected interfaces in view

    Ask the responsible technical participants which adjoining work, approvals or operating needs require review. Keep their questions in the record with a named responder. A project coordinator can assemble those questions and track responses without deciding technical suitability or treating an unanswered issue as acceptance.

    Consider an illustrative equipment proposal that arrives sooner but uses a different connection arrangement. The procurement discussion records the quoted availability, while the responsible reviewers examine whether the interfaces affect other work. The proposal stays visibly unresolved until the authorized decision is recorded. This scenario illustrates coordination only; it gives no installation or design instruction.

    Where a change affects several trades, make the dependencies explicit. Record who needs the decision, what information remains missing and which planned commitment depends on the answer. An email copied to a long distribution list is weaker coordination evidence than a specific question accepted by a named responder.

    Carry the decision into the next commitment

    Use the project's established submission and authorization process. Link the actual disposition to the exact proposed version, including its stated conditions. Ask the responsible decision maker to clarify any ambiguity before the team describes the alternative as approved. A meeting recollection should not silently become the basis for an order.

    After a decision, check that the people preparing the next authorized commitment can find the same record. If the supplier later changes the proposed model or its stated terms, preserve that difference and route it for review. Do not assume a decision about one proposal answers a later, changed proposal.

    Measure record quality separately from savings

    For an internal check, count reviewed substitution requests with a versioned comparison, named decision owner and linked disposition, divided by all substitution requests reviewed. Track unresolved requests separately. This measure describes documentation completeness; it does not establish compliance, technical acceptance or project savings.

    Choose one live request before the next procurement meeting. Ask a colleague who missed the original conversation to explain what changes and who decides. If that is difficult, improve the record before the team relies on its shorthand. Any eventual schedule or cost benefit needs its own evidence.

    Source note: GSAM 552.236-72, March 2019 clause text on Acquisition.gov, reviewed October 26, 2026. The comparison record, scenario, questions and internal measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Keep the Envelope Test Boundary Traceable

    Source edition: Keep the Envelope Test Boundary Traceable — November 2, 2026.

    Keep the Envelope Test Boundary Traceable

    A strong test result can lose its meaning when it leaves the report. One person remembers an improvement percentage; another assumes it applies to every area in the building. Before that number becomes a closeout statement or a planning assumption, connect it to the boundary and conditions actually tested.

    The General Services Administration's automated building envelope sealing evaluation describes Oak Ridge National Laboratory research during an office renovation at the Denver Federal Center. GSA reports improved airtightness at that site and identifies air leakage as a concern for energy use, comfort, indoor air quality and ventilation operation. Its page links to both a brief and the full research report.

    A project-specific finding is a reason to examine evidence, not a transferable promise for another building. Our leadership recommendation is to make the test boundary an explicit part of the decision record. The point is to help authorized project participants understand what the result supports before it is repeated in a meeting, a proposal or an owner update.

    Start with the decision the evidence must support

    Ask the responsible project lead what is being decided. Is the team reviewing a defined work area, comparing recorded conditions, or checking a contractual deliverable? Put that question beside the report reference. A headline about improved performance cannot answer every one of those questions.

    Keep technical interpretation with the qualified people responsible for testing and design. Their explanation should identify the applicable method, units, boundary and limitations. This coordination record does not establish an acceptance threshold or replace project requirements. Where the evidence does not address the decision, record the missing information and the person who will resolve it.

    Keep the boundary visible when the result travels

    Request a clear reference to the tested area and the drawing or description that defines it. Link the report version and test date so a later reader can find the same evidence. Have the responsible specialist explain any exclusions and relevant differences between comparison conditions. Do not let a simplified slide silently expand the scope of a measured result.

    Consider an illustrative renovation where one floor has completed a test while another remains under construction. An owner update that says the building is complete could erase that distinction. The coordinator instead identifies the tested floor, links the report and leaves the second floor's evidence open. This example concerns reporting discipline; it prescribes no testing or sealing procedure.

    Give unresolved interpretation a named owner

    Three useful review questions are: What exact area does this result describe? Which decision does the responsible specialist say it supports? What remains outside that conclusion? Assign any unanswered question to one decision owner with a review date. Keep a visible hold on broader claims until the appropriate reviewer resolves the gap.

    If an area changes after testing, flag that change through the project's established process. The responsible technical participants determine whether the existing evidence remains applicable and whether further work is required. A coordinator should preserve the issue and route it, rather than infer that a previous result automatically covers changed conditions.

    Measure traceability before claiming a benefit

    For a small internal check, count reviewed test records that have a defined boundary, report reference and decision owner, divided by all test records reviewed. That measures documentation completeness. Track accepted deliverables, actual building performance and documented costs separately. A complete register does not prove energy savings, contractual acceptance or financial return.

    Choose one result that will appear in the next project update. Ask someone outside the original conversation to find its boundary and report. If that path is unclear, fix the reference before the headline spreads. The useful outcome is a statement the next decision maker can trace back to the evidence.

    Source note: GSA evaluation page, updated September 14, 2026; reviewed October 25, 2026. The coordination record, scenario, review questions and internal measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Give Salvaged Materials a Destination Before Removal

    Source edition: Give Salvaged Materials a Destination Before Removal — November 1, 2026.

    Give Salvaged Materials a Destination Before Removal

    A renovation team can agree that something is worth saving without deciding where it will go. The item comes out, occupies a temporary corner and eventually becomes someone else's disposal problem. Before removal begins, connect each selected reuse candidate to a decision owner and a credible destination.

    The Environmental Protection Agency's best practices for construction and demolition materials, updated May 4, 2026, describe salvage and reuse as ways to divert materials from disposal. EPA explains that deconstruction can range from retaining whole structures to carefully removing selected items. It also describes different outlets for recovered materials, including reuse centers and materials exchanges.

    That guidance does not mean every existing component belongs in the next project. The leadership task is to get a qualified decision made early enough to influence the work plan. Our recommended starting point is a short candidate list with the proposed use or receiving organization, the unresolved question and the person responsible for the next decision.

    Separate a candidate from an accepted item

    Ask the project team to identify a small, manageable group of potential salvage items during its normal planning review. Record where each item is, what information is available and why reuse is being considered. Keep that candidate status visible until the appropriate project participants have assessed the proposal. An attractive appearance or an available storage area does not establish suitability.

    EPA notes that some construction and demolition materials contain potentially harmful constituents and points readers to applicable federal, state and local requirements. Keep environmental and safety assessment with the qualified people responsible for that work. The candidate list is a coordination record; it cannot authorize disturbance, removal, reuse or a substitution.

    Confirm who will receive it

    For each candidate that moves forward, ask the coordinator to verify the proposed destination through the project's established process. If an outside organization is involved, confirm what it will accept and any relevant condition, quantity or timing requirements before treating that route as available. A directory listing is a starting point for a conversation, not evidence that a particular batch has been accepted.

    For a proposed on-project reuse, obtain the required project review rather than assuming that ownership of the item establishes permission to reinstall it. Record the decision and its conditions in the normal project system. Where approval or acceptance is still pending, show that state clearly so procurement and field teams do not plan around different versions of the decision.

    Connect the destination to the work sequence

    Consider an illustrative renovation team assessing interior cabinets for donation. A coordinator has identified a possible recipient, but the recipient has not confirmed its collection window. Before the team changes its plan, the coordinator resolves that question with the authorized project lead and records the agreed next step. The example describes an information handoff, not a removal method or a claim that those cabinets are suitable.

    For accepted candidates, connect the receiving arrangement to the approved work sequence and identify who owns coordination if dates change. Let the responsible site personnel determine handling, protection and storage arrangements. If the destination becomes unavailable, return the decision to its owner rather than allowing an undocumented pile of material to become the default plan.

    Close the loop with evidence of receipt

    Keep the eventual outcome with the candidate record. Distinguish an approved proposal, an item prepared for transfer and a transfer actually acknowledged by its recipient. Those are different stages. A useful review asks which items remain open, whose decision is needed and what evidence would close each record.

    If a simple coordination measure helps, count selected candidates with a recorded owner, destination decision and next review date, divided by all selected candidates reviewed. Measure actual transfers and documented costs separately. Neither a completed list nor a donation proposal proves savings or avoided disposal. The immediate result is a decision that the field team can follow without inventing the missing destination.

    Source note: EPA best-practices guidance, updated May 4, 2026; reviewed October 23, 2026. The candidate record, scenario and coordination measure above are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Check the Backlog Collision Before Accepting the Work

    Source edition: Check the Backlog Collision Before Accepting the Work — October 31, 2026.

    Check the Backlog Collision Before Accepting the Work

    A new award can look attractive in isolation while competing with work the company has already promised to deliver. Before accepting the next project, put its busiest weeks beside the existing commitment calendar. The decision deserves evidence about the overlap, a named owner and a clear point for review.

    Associated Builders and Contractors reported on October 13 that its September Construction Backlog Indicator reached 8.7 months, up 0.2 months from August. Its member survey ran September 21 through October 5. Staffing confidence rose, while sales and profit-margin confidence declined. Read the ABC release published by its Massachusetts chapter for the survey context.

    Those are aggregate signals from surveyed contractors. They do not establish a particular firm's available crews, achievable margin or ability to start another job. Our editorial recommendation is to use the release as a reason to review project commitments before making another scope, duration or price promise.

    Which commitments occupy the same weeks?

    Ask the estimating lead and operations lead to put the proposed start, major work periods and handoffs beside the corresponding periods for awarded work. Separate confirmed commitments from proposals and tentative dates. A list of project values cannot show whether three demanding phases land in the same month.

    Keep the first review narrow: identify the overlap most likely to change the acceptance decision. It might involve a superintendent, a specialist crew or shared equipment. Record the underlying date assumption and the person who can confirm it. If the proposed project depends on another job finishing first, make that dependency visible rather than treating the release date as settled capacity.

    Who has confirmed the constrained resource?

    For the overlap, ask who has actually confirmed availability and what that confirmation covers. An estimate that assumes a trade partner will be available differs from a current, project-specific response. Record the scope, timing and unresolved qualifications with the bid review so operations can understand what was known when the decision was made.

    Do not resolve a capacity conflict by silently moving the same people between two plans. Have the responsible operations leader review the competing commitments and identify an acceptable arrangement. If additional resources are proposed, check their availability and the relevant cost assumptions through the company's normal approval process. A national backlog reading cannot supply that project evidence.

    What would change the bid decision?

    Ask the accountable commercial decision owner to name the unresolved assumption that could change acceptance, scope, duration or price. Connect it to a next action and a review time. For example, an illustrative bid review might remain open until operations confirms a supervision plan for two overlapping starts. The example is a management practice, not a survey finding or a universal contract requirement.

    Write down which assumption remains provisional and who may approve a commitment. Use the firm's established commercial and contract review process to determine any qualifications or changes. Where the missing evidence affects the promise, return the decision for review before representing the assumption as confirmed. Do not treat an internal checklist as permission to alter an agreement.

    Make the decision record useful to the next team

    Close the review with a short record: the proposed commitment, the competing work, the resource evidence, the named decision owner and the condition requiring another review. Give the delivery team access through the normal project handoff. Track reviewed bids with those fields complete divided by all bids in the chosen review cohort if a simple process measure helps.

    Measure actual delivery and financial results separately. A completed review does not prove that a project will finish on time or earn its expected margin. Its immediate value is a traceable decision that the next person can understand before another commitment consumes the same capacity.

    Source note: ABC September Construction Backlog Indicator release, October 13, 2026; reviewed October 23. The three review questions, scenario and process measure are The Dig Daily Dose's editorial recommendations.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    6 min
  • Confirm the Delivery Route Before the Truck Leaves

    Source edition: Confirm the Delivery Route Before the Truck Leaves — October 30, 2026.

    Confirm the Delivery Route Before the Truck Leaves

    A delivery appointment can be on the calendar while the driver still has an outdated entrance, an incomplete receiving instruction or a contact who is no longer covering the site. Before the next supplier dispatch, connect that booking to the current access plan and a named receiving contact. The coordination should happen while the truck is still at its origin.

    The August 2026 federal guide specification UFGS 01 50 00, Temporary Construction Facilities and Controls, includes access and haul routes, entrances and storage areas in its construction site-plan requirements in paragraph 1.3. Its traffic provisions also address coordinating oversized and slow-moving vehicle movements with highway-authority requirements. This is a guide specification tailored to a project; the adopted contract and approved plans establish the actual requirements.

    Connect the booking to the current plan

    The following is our proposed management practice. Give the person coordinating deliveries one place to check the booking reference, intended entrance, receiving area, current plan reference and responsible site contact. Record when those details were last confirmed. The purpose is to make the dispatch instruction traceable rather than relying on an address copied from an old email.

    Ask the receiving lead to compare tomorrow's deliveries with the work planned around the entrance and receiving area. A booking made last week may have been reasonable when it was accepted. The useful question now is whether its assumptions still match the site. Where a question remains, record who will resolve it and when the supplier should expect a response.

    Confirm who receives the truck

    An instruction that says only to call the site can leave a driver working through several numbers. Identify the receiving contact and the agreed backup route for communication. Check that the supplier has the current contact details and understands the project's arrival instructions. Keep any site access or security information within the project's established sharing process.

    Do not confuse a confirmed contact with confirmed physical readiness. Have the appropriate site team check the relevant conditions under its approved plan. The delivery coordinator can assemble and communicate that decision, but should not invent an alternate route, loading arrangement or traffic-control instruction to keep an appointment on the calendar. Changes belong with the people authorized to review them.

    Resolve the exception before departure

    Consider an illustrative case: a supplier has tomorrow's delivery booked, but the receiving lead learns that the planned entrance will be unavailable. Record the conflict against the booking and contact the plan owner and supplier before dispatch. If the project approves revised arrangements, communicate the agreed instruction and confirm that the supplier received it. If the issue is unresolved, make that state explicit rather than leaving the old instruction to circulate.

    Keep the confirmation with the booking so the next shift can see the decision. Separate the arrival time from the receiving-readiness decision; one does not establish the other. Where dispatch details change, identify the current version and retire superseded instructions through the normal project process. A short, maintained record is more useful than several competing screenshots.

    Review one day's deliveries

    For tomorrow's list, ask the coordinator to identify every booking with a current plan reference, confirmed receiving contact and recorded response to any open exception. Review the missing items with their accountable owners. If useful, track complete coordination records divided by all bookings reviewed, while measuring actual arrivals and unresolved conflicts separately. The record is a coordination measure, not proof that every field condition is acceptable.

    The leadership habit is simple: finish the information handoff before distance makes a correction harder. At the end of the review, the supplier and receiving team should know which instruction is current, who owns an exception and where the next decision will be recorded.

    Source note: UFGS 01 50 00, August 2026, paragraphs 1.3 and 3.4.1; reviewed October 21, 2026. The booking record, review measure and scenario above are editorial recommendations and an illustrative example, not added specification requirements.

    Hosted on beehiiv. Read the full Privacy Policy at beehiiv.com/privacy.

    8 min

About The Dig Daily Dose

From the publisher's feed

The Dig Daily Dose reinforces leadership habits that drive profits for your team.