After the Site Map: A Service-Information Checklist for Outdoor Furniture Projects

A handover is not a promise. It is a clear record of what the next person needs to know.

An outdoor furniture project does not end when a chair, table or bench reaches the site. It changes hands. Design intent becomes an operating question. A site team may need to know where an item sits, what information came with it, who can answer a question, and what must be checked again if the installation changes.

That record is useful even when it is short. It helps a hospitality operator avoid guessing. It helps a project manager see what is missing. It helps a designer keep a material question connected to the right drawing, sample or supplier document.

This is not a maintenance schedule. It does not say that a product is suitable for a coastal, poolside or Australian setting. It does not replace a contract, a manufacturer care guide, product-specific test evidence, professional advice or any approval process. It is a simple way to keep service information honest after a site map has identified the questions.

Begin with the site map, not a generic label

Before handover, return to the site exposure map. That earlier record should identify the actual location, orientation, water sources, shade, cleaning context, interfaces and access questions. It is more useful than a broad label such as “outdoor,” “coastal” or “poolside.”

The Bureau of Meteorology explains that UV at ground level varies with time, date, latitude, altitude and ozone concentration. It also states clearly that UV is not the same as temperature. Bureau of Meteorology — About the UV Index This is not a furniture-material result. It is a reminder to keep separate conditions as separate records.

At handover, do not turn those conditions into a conclusion that a material will perform in a particular way. Record the conditions, then identify which supplier document, test report, drawing, care note or project decision responds to each one. If no document responds, keep the gap visible.

What the record should carry

A useful handover file is not a folder of unnamed PDFs. Each item needs a purpose. The Australian Building Codes Board notes that documentary evidence should be appropriate to the use it relates to and that a submitted copy should be complete. ABCB — Part A5, Documentation of Design and Construction This article uses that as a documentation discipline, not as a claim that the NCC applies to Sumparwood or to all movable outdoor furniture.

For each furniture type or representative junction, the handover can carry:

• the approved location and current drawing reference;
• the exact model, configuration, finish, hardware or upholstery reference, if these have been approved for the project;
• the sample, technical statement, drawing, report or care document supplied for that exact item;
• what the document covers, including its specimen, condition, date or revision when stated;
• what the document does not cover;
• the person or team who owns the next question; and
• the event that requires the record to be reviewed again.

The point is traceability, not volume. A short, precise record is better than a large file that lets a later reader assume more than the source says.

Use the Service Information Relay

The six fields below form a practical relay. They can be used on a single sheet, in a project tracker, or beside a delivery record.

Keep evidence and operating decisions apart

The difference matters. A test report may describe one specimen under named conditions. A care guide may describe a proposed routine for a particular approved configuration. A site record may describe how a project expects the item to be used. None of these documents should silently become the other two.

CSIRO describes weathering and durability work as testing and assessment services for coatings and materials. CSIRO — Coatings, Durability and Weathering That is useful context for a project team: a relevant technical question needs a relevant specimen, condition, method and conclusion. It is not evidence that any Sumparwood material or finished furniture item has been assessed in a particular way.

If a team receives a report, record the exact item tested, the conditions stated, the result stated and the limit stated. If the project changes the material, finish, hardware, geometry, cleaning regime or location, ask whether the existing record still applies. Do not guess.

For example, ISO 9227 describes salt spray test methods. A reference to that method alone supplies no service-life result for the furniture in the handover file.

A small example: one terrace, two records

Imagine a hospitality project with the same chair design in two places: a sheltered dining terrace and an open courtyard. This is a hypothetical example, not a Sumparwood installation.

The furniture schedule may give both chairs the same model name. The handover should still identify their locations separately. The team can link the common drawing once, then attach the relevant site notes to each location. If the operator later moves chairs between the two areas, the location record gives the team a clear starting point for review.

Now imagine that a replacement cushion is proposed. The useful question is not simply whether it looks similar. Ask which approved reference it replaces, what information accompanies it, and who will confirm the change. Keep the old reference in the revision history. Mark the new proposal as open until the responsible team has made its decision.

This approach does not prescribe a replacement product or a cleaning routine. It makes a change visible before an assumption becomes part of daily use. The same logic works for a table fitting, a finish reference or an updated supplier care note.

Give the operator a usable starting point

The best handover record is readable by the person who sees the furniture in normal use. It should not ask an operator to interpret a laboratory report. It should tell them where the approved information lives, what configuration it belongs to, who to contact if a question appears, and which changes should be reported.

Useful triggers may include a revised cleaning product, a different installation location, changed hardware, a new finish, repeated water retention, a damaged component, a request to move or stack the furniture, or a new service instruction. These are triggers for review, not proof that a problem has occurred.

For a hospitality team, this can be a small information card linked to the full project record. For a design or delivery team, it can sit beside a schedule or close-out list. The format can change. The discipline stays the same: name the source, its scope, its limit and the next owner.

When should the relay restart?

Restart the relay when the real project moves away from its recorded assumptions. This could happen before delivery, during installation or later in operation. The important point is not to create a universal inspection interval. It is to record the event and reopen the right question.

For example, a site may add a new cleaning product. The operating team should record the product, intended dilution, contact scenario and the approved item affected, then ask the relevant technical owner for an evidence-based response. A moved chair may now sit under a roof edge or beside a pool. The team should update the site input rather than assume the former record still answers the new question.

This approach is deliberately modest. It makes no claim of approval, compliance or long-term outcome. It simply makes change visible before it becomes a vague operating story.

From a site question to a better conversation

Outdoor furniture projects become easier to manage when information does not disappear between selection, installation and operation. The Service Information Relay helps a team keep the site input, supplied record, document limits, owner and revision trigger in one place.

Start with the site exposure map, then compare the current public scope on Material. If a design question is still open, bring the relevant drawing, sample and location record into a Workshop conversation. A Sample Box can support a physical material review; it is not a compliance document or a substitute for project-specific evidence.

---