Read the result in layers
Inputs are facts supplied by the visitor. Calculated values follow the published formula contract. Assumptions such as symmetric span mode, waste and product coverage are choices that require support. Warnings mark boundaries rather than changing the answer silently.
Check units, endpoints and pitch representation first. Recalculate one representative section independently and compare the total with the original plan or takeoff.
Export and privacy
Exports include the job label, timestamp, inputs, assumptions, formulas, results and safety disclaimer. They do not require an account and should not contain personal details.
Local save remains on the device until cleared through the workbench or browser controls.
Keep a record of the original measurements, unit system, selected mode and any adjustment. Recalculate independently before ordering material or making a construction decision.
Detailed field guide
Inputs are visitor-supplied facts; calculated values follow formulas; assumptions are choices such as span mode, waste or coverage; warnings identify limits. Keeping these categories separate prevents a calculated number from making an assumption look verified.
Check units, endpoints, pitch representation and mode first. Independently reproduce one section and compare plan totals with the source drawing before relying on the combined sloping total.
JSON preserves structured metadata, method, version, timestamp and safety boundary. CSV provides an itemised table for spreadsheet review. Print produces a readable record without navigation controls.
Exports are generated in the browser and are not sent to RoofFigured. A job label or measurement can still be commercially sensitive, so store and share the downloaded record deliberately.
Checks before using the result
- Preserve the original measurement, unit, endpoints and drawing revision.
- Keep different pitches and unsupported intersections separate.
- Compare one representative result with an independent calculation.
- Do not access a roof merely to obtain calculator inputs.
Separate facts, choices and results
Source measurements are facts supplied to the tool; mode, unit and waste are user choices; derived values are results. Record all three. A precise subtotal does not validate the measurement or the selected boundary—it only shows the consequence of those inputs under the stated formula.
Perform a layered check
Check labels and units first, then input ranges, then one independent formula, then totals. In a multi-section record, reconcile plan area before sloping area. Confirm that excluded rows contribute zero and that every valid subtotal appears exactly once in the combined total.
Choose the appropriate export
JSON preserves field names, methods, raw numeric values, timestamp, calculation version and boundary text for machine checking. CSV is convenient for spreadsheet review but has a flatter structure. Print provides a readable snapshot. All three should show the same valid sections and totals.
Treat files as project records
Exports are generated locally and not uploaded by RoofFigured, but filenames, job labels and measurements may still be sensitive. Store them in the appropriate project location, retain the drawing revision they relate to, and regenerate the record after any changed input rather than editing a displayed total by hand.
Separate supplied facts, selected assumptions and derived results
A good calculation record distinguishes what was measured from what the user chose and what the software derived. Source dimensions and stated pitches are supplied facts. Input mode, unit, waste allowance and coverage are choices or assumptions. Ratios, factors, line lengths, areas and totals are derived results. Do not copy a derived display back into the facts column without identifying the change, because that breaks the chain needed to reproduce the result.
Read the formula beside the result and check that its variables correspond to the visible fields. A mathematically correct answer can still describe the wrong line or plane if the endpoints, mode or units were misunderstood. Preserve descriptive labels such as “horizontal wall-to-ridge run” rather than shortening everything to “length.” The additional words make later checking faster and reduce false confidence in an isolated number.
Check in layers before accepting the total
Start with names and units, then inspect input ranges and boundaries. Reproduce one representative row with an independent formula or known triangle. For a multi-section job, reconcile horizontal plan area before sloping area, confirm that each valid subtotal appears once and verify that invalid rows contribute zero. If the total changes after a unit conversion, compare the ratio with an exact known conversion rather than judging by the number of decimal places.
Review warnings and exclusions as part of the result. A row can be numerically valid while the roof form remains unsupported by the simple model. Compare the schedule with the source plan and identify any hip, valley, dormer, opening or intersection handled elsewhere. Record those omissions explicitly so the export cannot be mistaken for a complete professional takeoff.
Choose and retain the appropriate record format
JSON preserves field names, raw numeric values, methods, timestamp, calculation version and boundary text for machine checking. CSV provides a flatter table that is convenient for spreadsheets. Print produces a human-readable snapshot and can be saved as PDF through the browser. The same valid sections and totals should appear in all formats. A mismatch is a defect and should be resolved before the file is relied upon.
Exports are created locally and are not uploaded by RoofFigured, but job labels and measurements may still be sensitive. Store them with the appropriate project controls and retain the source drawing revision. When an input changes, regenerate the record instead of editing only the displayed total. The website provides no account, collaboration service or long-term backup, so responsibility for retention and access remains with the person creating the file.
Perform a final handover review
Before sharing a record, read it as if you had not created it. Can every section be found on the source drawing? Are wall, ridge and eaves boundaries stated? Do all dimensions use the shown unit? Are invalid rows excluded and visible? Does the plan-area sum reconcile independently? Are material coverage and waste clearly separated from geometry? A reviewer should be able to reproduce one representative subtotal without asking what a field meant.
Name the file and job clearly without adding personal or confidential information. Retain the unedited export, source revision and review date together. If a recipient changes an input, create a new version rather than overwriting the evidence used for the earlier decision. RoofFigured provides a transparent calculation record but no approval workflow, signature system or cloud archive. The project team remains responsible for deciding who reviews the output, which document governs and whether a competent professional must confirm it before consequential use.
Final verification before use
A robust handover includes the untouched export, a human-readable print, the source drawing revision, the calculation version, the review date and a short exclusions note. The recipient should know which values were measured, converted, assumed and derived. If the record cannot answer those questions without oral explanation, improve its labels and notes before it is used as evidence for another decision.
Compare file totals with the visible interface immediately after export. Open CSV in a spreadsheet without changing values and confirm headers, units, valid rows and total. Inspect JSON for the job label, timestamp, method, raw values and boundary text. Print preview should retain the calculation record while removing navigation. If any format omits information needed to reproduce the result, treat it as a failed handover rather than a cosmetic issue.
Complete the review by recording who performed the check and when, without inventing credentials or approval status. A review note means the arithmetic and stated scope were examined; it does not turn the file into structural certification, code approval, a supplier quotation or permission to undertake roof work.