Three Gutter Quotes, Three Different Jobs: A Scope Ledger for Swiss Roofline Metalwork
A quote for a gutter, downpipe, or roof-edge repair is only comparable with another quote when both describe the same water path, the same interfaces, and the same exclusions. A lower total may simply leave a component unpriced; a higher total may include access, removal, or a transition another offer omits. Start by defining the work in rows, then ask each sheet-metal contractor to mark each row as included, excluded, provisional, or requiring an inspection.
For a local starting point, the Plateau de Diesse sheet-metal roofer guide and request page already asks owners to document the location, visible symptoms, photos, dimensions, access, and unresolved questions. The additional tool here is a scope ledger for the roofline itself: it lets you compare which parts of the rainwater route each offer actually covers, without treating a blank as a zero-cost item.
The decision in one minute
Do not rank offers by total price until each one answers the same scope questions:
- Which roof edges and lengths are included?
- Which components are being repaired or replaced: gutter, brackets, outlet, downpipe, bends, collector, flashing, or a connection to another trade?
- What has the contractor observed, and what remains unverified until safe access or opening-up?
- Which material, finish, profile, and connection assumptions are in the offer?
- Who provides access protection, removes old material, handles waste, and records the completed work?
- Which amount is fixed, which is provisional, and what event changes the price?
If one company quotes a gutter replacement and another quotes a gutter plus outlets, downpipes, and access equipment, the totals answer different questions. Do not “correct” this by guessing what the missing work would cost. Ask for a revised offer or record the gap as unknown.
This is a buyer-side comparison method, not a roof inspection guide, installation specification, price estimator, legal opinion, or substitute for a qualified tradesperson. Do not climb onto a roof, lean from a window, or remove a component to fill out the ledger. Photograph only from a safe place and let the contractor decide what needs an on-site inspection.
What the visible search results already cover
The local MeilleurArtisan guide asks for useful photos, location, access, approximate dimensions, the desired result, and open questions. It also says that some issues require an on-site visit rather than a remote promise. Those are good request basics, but they do not, by themselves, make three offers comparable line by line.
A separate Swiss roofing guide from Experts Romands already recommends distinguishing roof covering, under-cover, sheet metal, drainage, roof windows, insulation, ventilation, and access safety; it also advises asking for the same scope, materials, exclusions, and assumptions. That is the correct high-level baseline. This article makes the next step operational: it gives the owner a common row set for rainwater and metalwork at the roof edge, plus a small checker that flags rows that cannot yet be compared. Experts Romands’ guide is a commercial directory and editorial guide, not a technical standard. Use its list as a scoping prompt, not as proof that a particular detail is compliant.
The distinction matters because “roof repair” can mean several different jobs. A leak near an eave might involve the roof covering, a flashing, a gutter, the fascia, a downpipe connection, or more than one of these. A homeowner can describe the symptom and show where water appears; only an inspection may determine the cause. A quotation should preserve that uncertainty instead of converting a guess into a fixed scope.
The owner’s scope ledger
Use one row per component or boundary. If a row does not apply, ask the contractor to mark it “not applicable” and state why. If the contractor cannot decide remotely, mark it “inspection required.” A blank is not a decision.
| Scope row | What the owner records | What the contractor should clarify | Evidence to retain |
|---|---|---|---|
| Location and roof edge | Building side, approximate edge or zone, safe ground photo | Which exact edge or section is included | Annotated photo or sketch |
| Observed symptom | Overflow, visible corrosion, loose element, staining, or “unknown cause” | Observed fact versus suspected cause | Dated ground-level photos and visit note |
| Gutter or channel | Existing profile if known; approximate run only if safely measurable from records | Repair, partial replacement, or full replacement; profile and material assumption | Offer line and product description |
| Supports and brackets | Visible sagging or missing support, without touching it | Whether supports are retained, adjusted, or replaced | Before/after photos where safely taken by contractor |
| Outlets and collection points | Visible outlet count only if known; identify where water enters a pipe | Included outlet, strainer, collector, or connection work | Itemised line or explicit exclusion |
| Downpipe route | Visible route to ground or drainage connection | Bends, clips, offsets, bottom connection, and any work beyond the trade boundary | Marked route and handoff note |
| Roof-edge flashing and transitions | Nearby roof, wall, fascia, or window junction visible from the ground | Which transition is opened, retained, repaired, or excluded | Detail photo and written boundary |
| Material and finish | Existing material if documented; desired appearance if relevant | Proposed material, finish, compatibility assumptions, and alternatives | Product specification or named material |
| Access and protection | Site access, parking, garden, shared path, or other constraints | Who plans and supplies work access and fall protection | Access plan and responsible party |
| Removal and waste | Components expected to be removed, if known | Removal, sorting, transport, and disposal included or excluded | Separate line or written inclusion |
| Quantity and pricing basis | Unknown unless measured by a professional or existing drawing | Unit, measured quantity, fixed amount, allowance, or time-and-materials basis | Quantity, unit, rate or total, tax basis |
| Inspection and handover | Desired photos and records | What is checked, what is photographed, and what is handed over | Dated completion note, photos, care information |
The ledger deliberately does not tell you the correct gutter size, slope, fastener spacing, metal combination, flashing geometry, or drainage capacity. Those choices depend on the building and applicable technical requirements. Ask the contractor to state the design or product assumption and explain what they have actually checked. Do not infer technical adequacy from a neat table.
The most useful distinction is between an observed condition, a diagnosis, and a proposed intervention. “Water appeared below the left eave after rain” is an observation. “The gutter is undersized” is a diagnosis. “Replace the complete run” is a proposed intervention. Keep the three separate until a qualified person has enough evidence to connect them. If a company can only inspect after safe access is installed, the offer should say so.
Why water-path boundaries matter
A roofline is a chain, not one object. Water can move from the roof surface into a channel, through an outlet and downpipe, then into a ground-level connection. At the same time, sheet metal may meet tiles, a roof membrane, a wall, a fascia, a window, or a chimney. The quote must make it visible where one work item ends and the next begins.
A useful request follows the path from the point where water leaves the roof to the point where the contractor’s scope ends. Ask: “Which component receives water from this one? Which connection is included? Where does your work stop?” These questions expose gaps such as a new downpipe ending above an old connection, a replaced channel with old brackets left in place, or a flashing repair that excludes the adjacent roof covering. The examples are questions to ask, not claims that any of those failures occurred at your property.
Use three boundary labels in the ledger:
- Included: the offer names the component and the work.
- Excluded: the offer says the component or follow-on work is outside its scope.
- Interface to confirm: the component meets another trade or system and no one has yet accepted responsibility.
“Included” still needs enough detail to identify what is included. “Excluded” is not automatically a defect in the offer; a contractor may be correctly limiting the job. The problem is an exclusion that the owner assumes is covered. “Interface to confirm” is a decision to resolve before acceptance, not a promise that the contractor will do it for free.
If the roof covering is being replaced at the same time, ask who coordinates the order of work and who is responsible for the joint between trades. If the sheet-metal job is a small repair, the same question may be simpler: the contractor may state that no roof-covering work is required. The ledger should record the answer, not dictate a project structure.
How to compare units without inventing a price
A quantity is useful only when its unit and boundary are clear. A line item measured in metres might describe a channel run, but it does not tell you whether outlets, end caps, bends, supports, or access are included. A lump sum may be perfectly reasonable if the scope is complete and the contractor has inspected the work. The goal is not to force every offer into the same billing style; it is to understand what each amount buys.
For every priced row, record:
- the quantity and unit, if the contractor provides them;
- whether the quantity is measured, estimated, or provisional;
- whether the rate is a unit price, a fixed sum, or time-and-materials;
- which materials and small parts are included;
- whether access, protection, removal, disposal, and travel are included;
- whether tax is included and whether the offer contains a validity period;
- the condition that can change the amount.
Never convert a missing quantity into zero. Never multiply a guessed length by a public “average price” and present it as the cost of your building. Public price examples often describe different work, quantities, locations, material grades, access conditions, and tax bases. They can be useful for asking questions, but they cannot normalize two offers that cover different components.
A comparison can still be useful before all quantities are known. Mark the offers as “scope-aligned,” “scope differs,” or “not yet comparable.” If a row is provisional, ask what discovery changes it and how approval works before extra work begins. If an offer uses time-and-materials, ask what records the contractor will provide and who authorizes additional time. These are commercial clarifications, not a promise that one pricing form is inherently better.
Safety is part of scope, not a homeowner measurement task
Work at roof level creates a safety boundary. The Swiss Accident Insurance Fund’s summary of the Construction Work Ordinance explains roof-work fall-protection duties and the conditions around limited exceptions. Its guidance prioritises collective protective measures where applicable. The practical consequence for a buyer is modest but important: ask the contractor to describe how access and protection are planned and who supplies them. Do not specify a protection method yourself based on a photograph or a short video. Suva’s OTConst summary is the current source to check for the applicable rule; this article does not restate thresholds or decide which exception applies to a particular job.
The owner’s ledger should therefore contain separate rows for access and for protection, even if the contractor combines them into one price. This helps distinguish a low total that excludes access from a higher total that includes it. It also allows the contractor to explain why an inspection, scaffold, lift, or other arrangement is required. The owner does not approve a method by selecting the cheapest word in a quotation.
Do not ask a contractor to quote “from the ground” if the work cannot be assessed safely that way. A sound offer may include an inspection or a provisional stage. Record what must be confirmed before the work is fixed. If there is an urgent leak, protect people and belongings from a safe location and contact an appropriate professional; do not step onto a roof to make the request more complete.
A synthetic three-offer exercise
The table below is a hand-authored exercise, not a survey of Swiss contractors. It uses three fictional offers and ten fictional scope rows to show how a price comparison can fail. No home was inspected, no quotation was collected, and no contractor, material, cost, leakage result, or installation was measured. The scenario was designed on 18 November 2026. Its purpose is to demonstrate the comparison method, not to estimate what a real job costs.
| Row | Offer A | Offer B | Offer C | Can the owner compare yet? |
|---|---|---|---|---|
| Main channel | Included; quantity to confirm | Included; measured after visit | Included; quantity stated | Not yet; quantity basis differs |
| Supports | Existing supports retained | New supports included | Not stated | No; one unknown |
| Outlets | One included | Outlet work excluded | Included, count to confirm | No; work differs |
| Downpipe route | Existing pipe retained | New pipe included | Provisional after inspection | No; boundary differs |
| Roof-edge transition | Excluded | Included at named edge | Not stated | No; scope differs |
| Material | Named in offer | Alternative to confirm | Not stated | No; assumption differs |
| Access | Separate line | Included | Inspection required | No; commercial basis differs |
| Removal | Included | Not stated | Included | No; one unknown |
| Disposal | Included | Excluded | Not stated | No; responsibility differs |
| Handover evidence | Completion photos | Not stated | Photos and care note | No; records differ |
The exercise does not prove that Offer A, B, or C is better. It shows why a total without a scope definition is not a decision. A buyer could ask all three contractors to clarify the same rows, accept a clearly stated exclusion, or narrow the project to only the work that is actually needed. The correct next step depends on the site inspection and the owner’s priorities.
What this comparison method adds
A common search-result recommendation is to obtain multiple offers and compare the same scope. The local guide from Experts Romands says to identify the work, supplies, exclusions, access, and assumptions. A Swiss owner forum also illustrates a recurring question: when a quote’s headings are broad, what exactly was priced, and what should the owner ask the contractor? In one 2015 thread, participants discuss an offer with a few broad demolition and installation lines; that discussion is an anecdote, not a representative sample and not a legal source. It is useful here only as evidence that labels alone can leave a buyer unsure about the underlying work. The discussion is here.
The reusable contribution is the explicit row structure and a comparator that refuses to treat unknown scope as included. The table records a state for every interface; the code below flags a row when the offers disagree about status, quantity, or unit. It intentionally does not score a contractor, calculate a “fair” price, or decide which repair is technically correct.
A small, executable scope-comparison checker
This dependency-free Node.js example uses fictional offers and fictional quantities. It checks whether the offer records are complete enough for a scope discussion. It is not an engineering calculator, estimating tool, safety assessment, or substitute for a site visit.
Copy the code to compare-roofline-scope.js and run node compare-roofline-scope.js. The fixture reports row-level questions; it does not print a winning offer.
const requiredRows = [
{ id: "channel", label: "Main channel", needsQuantity: true },
{ id: "supports", label: "Supports and brackets", needsQuantity: true },
{ id: "outlets", label: "Outlets and collectors", needsQuantity: true },
{ id: "downpipe", label: "Downpipe route", needsQuantity: true },
{ id: "flashing", label: "Roof-edge transition", needsQuantity: false },
{ id: "material", label: "Material and finish", needsQuantity: false },
{ id: "access", label: "Access and protection", needsQuantity: false },
{ id: "removal", label: "Removal", needsQuantity: false },
{ id: "disposal", label: "Disposal", needsQuantity: false },
{ id: "handover", label: "Completion evidence", needsQuantity: false }
];
const offers = [
{
name: "Offer A",
rows: {
channel: { status: "included", unit: "m", quantity: "confirm" },
supports: { status: "retained" },
outlets: { status: "included", unit: "each", quantity: "confirm" },
downpipe: { status: "retained" },
flashing: { status: "excluded" },
material: { status: "named" },
access: { status: "separate-line" },
removal: { status: "included" },
disposal: { status: "included" },
handover: { status: "photos" }
}
},
{
name: "Offer B",
rows: {
channel: { status: "included", unit: "m", quantity: "measured" },
supports: { status: "included", unit: "each", quantity: "confirm" },
outlets: { status: "excluded" },
downpipe: { status: "included", unit: "m", quantity: "confirm" },
flashing: { status: "included" },
material: { status: "alternative-to-confirm" },
access: { status: "included" },
removal: { status: "not-stated" },
disposal: { status: "excluded" },
handover: { status: "not-stated" }
}
},
{
name: "Offer C",
rows: {
channel: { status: "included", unit: "m", quantity: "stated" },
supports: { status: "not-stated" },
outlets: { status: "included", unit: "each", quantity: "confirm" },
downpipe: { status: "provisional" },
flashing: { status: "not-stated" },
material: { status: "not-stated" },
access: { status: "inspection-required" },
removal: { status: "included" },
disposal: { status: "not-stated" },
handover: { status: "photos-and-care-note" }
}
}
];
function describe(row) {
const entries = offers.map(offer => ({
offer: offer.name,
item: offer.rows[row.id] || { status: "not-stated" }
}));
const statuses = new Set(entries.map(entry => entry.item.status));
const unknown = entries.filter(entry =>
["not-stated", "provisional", "inspection-required", "alternative-to-confirm"]
.includes(entry.item.status)
);
if (unknown.length) {
return { row: row.label, result: "clarify", offers: entries };
}
if (statuses.size > 1) {
return { row: row.label, result: "scope-differs", offers: entries };
}
if (row.needsQuantity) {
const units = new Set(entries.map(entry => entry.item.unit || ""));
const quantities = entries.map(entry => entry.item.quantity || "");
if (units.size > 1 || units.has("")) {
return { row: row.label, result: "normalise-unit", offers: entries };
}
if (quantities.some(value => value === "" || value === "confirm")) {
return { row: row.label, result: "quantity-to-confirm", offers: entries };
}
}
return { row: row.label, result: "aligned-for-discussion", offers: entries };
}
for (const row of requiredRows) {
const result = describe(row);
console.log(result.row + ": " + result.result);
}
The output is a prompt list, not an approval score. “Aligned for discussion” means only that the recorded status and, where relevant, unit look consistent in this fictional fixture. It does not mean that a contractor’s measurement is correct, the work is safe, the material is compatible, the drainage capacity is adequate, or the price is reasonable.
For a real project, replace the fixture with the exact rows from the site visit and the wording of each written offer. Do not paste personal addresses, access codes, private phone numbers, or confidential contractor correspondence into a public tool. Keep the working file locally, remove unnecessary personal details, and share only the fields the contractors need to clarify.
How to ask for clarification without turning the request into an argument
Send the same short questions to each contractor whose offer leaves a material row open:
- “Does this amount include the full channel run, or only the visibly damaged section?”
- “Are the brackets retained, adjusted, or replaced?”
- “Which outlets and downpipe sections are included?”
- “Where does your work stop at the connection to the existing drainage route?”
- “Which material and finish are assumed, and what would make you change that assumption?”
- “Is access and fall protection included in this amount or quoted separately?”
- “Is removal and disposal included?”
- “Which observations must be confirmed on site before the amount becomes fixed?”
- “If a hidden condition is found, will you pause and ask for written approval before proceeding?”
- “What completion photos or care information will you provide?”
The wording is intentionally neutral. It asks for scope, evidence, and decision rights; it does not accuse anyone of hiding costs. A contractor may reasonably refuse to make a fixed commitment before inspecting the building. In that case, record the inspection as the next decision point instead of forcing a false comparison.
When the companies use different but defensible solutions, do not flatten them into a single number. Ask each one to explain the difference and quote a common alternative if that is technically appropriate. The comparison may conclude that the offers are not interchangeable. That is useful information: the owner can then decide whether to commission a separate assessment, revise the brief, or select a contractor based on a clearly described approach.
From request to acceptance: a controlled sequence
- Capture the symptom safely. Record the date, weather context if known, location, and visible result from the ground. Avoid diagnosing from a stain or a single photograph.
- Define the desired outcome. For example, “repair the identified leak” or “replace the named section and restore the stated connection.” Avoid writing a technical design that you are not qualified to specify.
- Prepare one common brief. Use the ledger rows and send the same brief and available photos to each company.
- Separate observation from assumption. Ask the contractor to label what was seen, what is inferred, and what requires inspection.
- Resolve safety and access. Ask how the work will be accessed and protected. Suva’s roof-work guidance explains why this belongs in planning and execution, while the competent employer and contractor remain responsible for the work method. The owner should not select protective equipment from this article.
- Normalize scope, not the contractor. Compare each component, quantity basis, material assumption, exclusion, allowance, and handover record. Do not create a composite offer by taking the cheapest line from each company.
- Record change approval. Before work starts, identify who may approve a changed scope, how that approval is documented, and whether the contractor pauses before extra work.
- Keep the handover evidence. Save the final offer, amendments, photos supplied by the contractor, any completion note, and care information with the building record.
A renovation decision is broader than a quotation. ETH Zurich’s research-based “Renovating – yes! But how?” tool helps users compare renovation solutions by cost and environmental impact at building and building-stock levels. It does not select a sheet-metal detail for a particular property, but it reinforces a useful owner habit: compare options against the goals and constraints of the building rather than reading one headline number in isolation. ETH Zurich describes the tool and its scope here.
Deloitte’s capital-projects service description groups requirements definition, procurement support, project controls, risk mitigation, and asset operation under delivery confidence. That is a consultancy’s service framing, not evidence that a small repair needs corporate project bureaucracy. For a homeowner, the proportional version is simple: define the requirement, preserve the scope, record changes, and retain a handover note. Deloitte’s service description supports the vocabulary of controls, not a claim about the price or performance of local roof work.
What to retain after the contractor leaves
A useful file need not be elaborate. Save:
- the final, accepted offer and any written amendments;
- the annotated scope ledger, with unknown rows resolved or explicitly excluded;
- the contractor’s description of the material and finish actually installed;
- before-and-after photos taken by the contractor from safe positions;
- a note naming any item left unchanged;
- completion observations and any open item with an owner and due date;
- care or inspection information supplied for the installed system;
- the contact route for future maintenance or a follow-up visit.
Ask the contractor which current rules and product instructions apply to your building, and have a qualified professional answer technical questions.
Do not confuse a photograph with a test. A photo can document what was visible at a moment; it does not establish hidden workmanship, long-term durability, or compliance with a specification. If a particular test or inspection matters, name it in the request and ask the contractor to confirm that it is appropriate for the system and the contract.
Failure modes and what to do instead
Comparing totals before scope
Failure: The lowest total wins even though one offer excludes an outlet or access.
Better: Mark every line “included,” “excluded,” “provisional,” “inspection required,” or “not stated.” Resolve the rows that change the decision before comparing totals.
Treating blank as included
Failure: The owner assumes that a short label such as “gutter work” includes supports, downpipes, removal, and disposal.
Better: Ask the contractor to state the boundary. The written offer, not the owner’s interpretation of a category name, should identify what is covered.
Treating blank as zero
Failure: The spreadsheet turns missing work into a zero-price row and makes an incomplete offer look cheaper.
Better: Keep “unknown” separate from “excluded.” Unknown means no decision; excluded means the contractor has stated the boundary.
Diagnosing from a symptom
Failure: A wet wall is automatically attributed to the nearest gutter.
Better: Record the symptom and ask for an inspection. Water can travel, and more than one component may be involved.
Requesting unsafe measurements
Failure: A homeowner climbs onto a roof or leans over an edge to obtain a more precise length.
Better: Use plans, existing maintenance records, or a professional site measurement. Leave access planning to the contractor. Suva’s OTConst guidance makes roof-work protection a real planning matter, not a box to tick after the price is chosen.
Combining offers into a “best of all” contract
Failure: The owner picks one company’s material, another’s access, and a third’s installation line without assigning responsibility for the interfaces.
Better: Ask one selected contractor to quote the combined scope and state which interfaces they accept. If multiple trades are required, assign coordination explicitly.
Letting a provisional amount become an unapproved change
Failure: The offer says “as needed,” and the owner later discovers that the cost changed without an agreed decision point.
Better: Ask what observation triggers the change, who contacts whom, and whether written approval is required before proceeding.
Assuming the cheapest material label is equivalent
Failure: Two offers use different product descriptions or omit material entirely, but the totals are treated as identical alternatives.
Better: Ask for the product, finish, compatibility assumptions, and any alternative in writing. A generic material label is not enough to establish technical equivalence.
Treating a maintenance record as a technical specification
Failure: A homeowner reads an old maintenance checklist as a current rule for replacement or installation.
Better: Use maintenance references to prepare questions only. Ask the contractor to identify current requirements and product documentation for the actual building.
Choosing by communication alone
Failure: A polished response is treated as proof of technical competence, or a terse response is treated as proof of poor work.
Better: Evaluate evidence, scope, inspection plan, qualifications where relevant, references, and the contractor’s explanation of limits. A quotation is one input, not a complete quality test.
When this method is useful—and when it is not
Use the ledger when several written offers describe overlapping but non-identical work, when a roofline repair touches multiple components, or when the owner needs a record before approving a change. It is especially helpful when a proposal combines “repair,” “replacement,” or “make good” language with no component boundary.
It may be unnecessary for a tiny, clearly observable task that one trusted professional can describe in a brief fixed offer. A formal comparison tool should not turn a simple service call into paperwork for its own sake. Similarly, if an architect, property manager, insurer, or building expert has already defined the scope, preserve their specification and ask contractors to price against it rather than inventing a second checklist.
The ledger also cannot determine whether a repair is the right long-term investment. The owner may need a roofer, building-envelope specialist, architect, insurer, or public authority depending on the cause and scale. If there is structural damage, recurring water ingress, suspected hazardous material, protected-building status, or a dispute about responsibility, seek competent advice before authorizing work. This article does not determine liability or legal deadlines.
A quotation can be incomplete for good reasons. The contractor may not be able to see a junction without safe access, may need a measurement visit, or may be unable to identify a hidden substrate condition without opening the construction. The right response is not to punish uncertainty; it is to make the uncertainty visible, price the inspection if appropriate, and establish the next decision. ETH Zurich’s renovation decision-support material likewise frames decisions around costs and environmental effects across options, not an isolated “best” choice. The analogy is about decision structure, not about the technical design of a gutter.
A blank request you can reuse
Copy this note into your email and fill only what you know. Leave unknown technical fields blank and ask the contractor to inspect them.
Property / municipality:
Roof edge or area, described from a safe location:
Observed symptom and when it was noticed:
What outcome I am asking for:
Photos or existing plans attached:
Known access or site constraints:
Components I believe may be involved (not a diagnosis):
Please state which components your offer includes:
Please identify exclusions, provisional items, and inspection-dependent items:
Please state the material and finish assumptions:
Please show the quantity and pricing basis for each material scope row:
Please say whether access, protection, removal, and disposal are included:
Please identify the connection to adjacent roof or drainage work:
Please state what completion photos, notes, or care instructions you provide:
Please explain how changes are approved before extra work proceeds:
Send the same note to each contractor. If a company prefers a phone call, summarize the outcome in writing and ask the company to correct anything you misunderstood. Do not ask a contractor to guarantee that a problem is solved before the source has been inspected.
A compact decision table
| Evidence state | What it means | Owner’s next move |
|---|---|---|
| Same rows, same boundaries, quantity basis stated | The offers can be discussed on a similar scope | Compare the commercial terms and approach |
| Same component, different quantity or unit | Scope might match, but measurement basis does not | Ask how each quantity was obtained |
| One offer excludes a component | The offers do not cover the same result | Accept the boundary deliberately or ask for a revision |
| One offer says “provisional” | A condition remains unresolved | Ask what observation converts it to a fixed scope |
| One offer is blank | No answer is recorded | Ask; do not treat as included or zero |
| Contractor requires safe access before diagnosis | Remote evidence is insufficient | Arrange a professional inspection and record its scope |
| Offers propose different technical solutions | Price totals are not direct substitutes | Ask for rationale and a common alternative only if appropriate |
| Change is likely after opening-up | Final scope may depend on a hidden condition | Set a written pause-and-approval process |
Checklist before accepting an offer
- [ ] I can describe the visible symptom without presenting a guess as a diagnosis.
- [ ] The offer identifies the roof edge or zone and each included component.
- [ ] Supports, outlets, downpipes, bends, and transitions are either included or expressly excluded.
- [ ] Material and finish assumptions are stated or identified as pending confirmation.
- [ ] Quantities have units and a source, or are explicitly provisional.
- [ ] Access and fall protection are included, separated, or assigned to a named party.
- [ ] Removal and waste handling are clear.
- [ ] The offer states what happens when inspection reveals a hidden condition.
- [ ] I know who approves a scope change and how that approval is recorded.
- [ ] The completion record, photos, and care information are described.
- [ ] I have not treated an unknown item as free, included, or technically unnecessary.
- [ ] I have not climbed or accessed the roof to collect information for the comparison.
Limits and source note
The scope ledger and code fixture in this article were created for this guide on 18 November 2026. The worked comparison contains three fictional offers and ten fictional rows. It is a designed acceptance exercise, not a measured sample of homes, contractors, prices, materials, or work outcomes. The code checks completeness and consistency in the entered records only. It does not inspect sites, calculate quantities, evaluate technical compliance, estimate costs, or assess contractor quality.
The source review included the GSC page and query that motivated the local task, visible search results for Swiss roof and sheet-metal work, the site’s own preparation guide, official Suva safety information, ETH Zurich renovation decision-support material, a consulting service description, and homeowner discussions. Search Console query data identifies a question and a page context; it does not prove market size or predict a Dev.to ranking. The reviewed forum threads are anecdotes, not a representative survey. The official safety source is used for the general point that roof work requires proper planning; the article intentionally does not turn it into a do-it-yourself safety procedure. No price survey or technical field test was performed.
A video search did not surface an independently accessible Swiss-specific demonstration that added evidence beyond the written official and trade references reviewed here. No installation claim in this guide relies on a video. The guide also avoids quoting an old federal maintenance PDF as a current code and does not reproduce any standard’s technical dimensions. For a particular roof, ask the qualified contractor which current rules, drawings, product documentation, and site conditions govern the work.
The recommendation is therefore bounded: use the ledger to make offer boundaries visible, ask a professional to resolve technical uncertainty, and compare only those rows that describe the same work. If the offers remain different after clarification, the honest result is “not directly comparable,” followed by a deliberate choice about scope, inspection, coordination, and budget.
How the offer moves to a decision
flowchart TD
A[Describe the symptom from a safe place] --> B[Send one common brief]
B --> C[Contractor inspects and separates facts from assumptions]
C --> D[Mark each ledger row: included, excluded, provisional, unknown]
D --> E{Same boundary, unit and quantity basis?}
E -- No --> F[Ask for clarification or revised scope]
F --> D
E -- Yes --> G[Compare commercial terms and stated method]
G --> H[Record change approval and access plan]
H --> I[Complete work and retain handover evidence]
Top comments (0)