Material Intelligence / Evidence Handover
From Material Note to Handover File: A Documentation Workflow for Outdoor Furniture Projects
A material note is useful. A handover file makes it usable.
Before design approval, link each material claim to its source, sample and drawing revision. Record the unresolved question and the person authorised to decide it. This is the design-evidence file, not the operator's care manual.

Preparing information for the receiving or operating team instead? Read the service-information handover checklist.
In plain English
Three things to know.
Say which item, drawing or decision is under review before adding documents to a folder.
A sample, drawing, statement and report do different jobs. None should quietly become a broader promise.
Name what is still open, who must answer it and which change should reopen the record.
Start with the project question
Begin with the decision, not the first PDF that arrives.
A material record often begins in fragments. A sample is passed around. A drawing changes. A note explains one aspect of a proposal. Months later, another person needs to know which configuration was discussed and what the team actually approved. That is where a small question at the top of the file earns its place.
Write one sentence: what is being decided, for which item, and why now? Add a drawing reference, project zone or revision when it matters. This stops a broad material description being used as an answer to a narrow project question.
RIBA describes its Plan of Work as a framework for stages, outcomes and information exchange. We use only that bounded lesson: information needs a clear purpose before it moves to the next decision. This does not say a Sumparwood project follows RIBA or that RIBA is a furniture requirement.

Name the source, version and scope
A joint record needs labels, not a pile of files.
The source can be a controlled sample record, an approved drawing, a supplier statement, a care note, a laboratory report or a project instruction. These sources are useful in different ways. A drawing can identify a configuration. A sample can support a physical review. A report can state a result for a named specimen under named conditions.
Record the document title, source organisation or owner, date, revision, exact item and the conditions named by the source. This makes it possible for a later reader to see whether a file supports a visual sample review, an exact detail, a method-limited report or a general proposal.
The RIBA Plan of Work template distinguishes types of information as a project develops. It is used here only as a prompt to label the record. It is not a legal responsibility map, a Sumparwood requirement or evidence of RIBA compliance.

State what the source does not establish
A clear limit is a useful part of the handover.
If a document does not state a service life, do not add one. If it covers a particular specimen, do not extend it to every configuration. If it contains a laboratory result, do not turn it into a result for a completed installation. A visible limit does not weaken the record; it tells the next person what still needs to be checked.
The Australian Building Codes Board says documentary evidence should be appropriate for its purpose and complete in the form submitted in NCC Part A5. We use this only as a general discipline for matching a record to its purpose. It does not make the NCC applicable to Sumparwood or movable outdoor furniture in Europe.
Use a short sentence for the boundary: “This note describes the material proposal; it does not confirm performance at this site.” Then add the next evidence that may be needed instead of letting a silent assumption fill the gap.

Let the record evolve
Handover is a controlled continuation, not a final freeze.
Use the Evidence Handover Card beside a furniture schedule, in a digital tracker or inside a handover file. Its five fields are simple: project question, source or document, exact scope and conditions, decision owner, and unresolved item or next evidence. The compact format can be read by more than the person who created it.
A changed finish, revised hardware detail, new cleaning instruction, substituted component or different site condition should reopen the card. Keep the earlier record. Write the updated question and ask the named owner for the next source or decision. A revision is not a fault. It is an explanation of why the record changed.
RIBA's Plan for Use guide encourages project-specific outcomes, review and learning as understanding develops. It is a process reference only, not a contract instruction or maintenance outcome for a furniture project.

Take it to the prototype
The five-field Evidence Handover Card
Use one card for each material question, then revise the card when the configuration, source or project condition changes.
| Field | Record | Use it to ask |
|---|---|---|
| Project question | Decision, uncertainty, item and drawing reference | What exactly must this record answer? |
| Source or document | Named sample, drawing, statement, report or instruction | What did the team actually receive? |
| Exact scope and conditions | Specimen, configuration, method, location and stated limit | Does this source match the current decision? |
| Decision owner | Role that must accept, clarify or obtain the next record | Who carries the open question? |
| Unresolved item / next evidence | What is still needed and the trigger to review again | When should this card reopen? |
Evidence boundary
What this workflow does not prove
This workflow does not certify Sumparwood, confirm a standard, predict service life, prescribe maintenance or establish suitability for a particular location or installation.
It gives a project team a clearer way to keep a named source, its stated scope, the open question and the next owner together. Any product conclusion still needs evidence matched to the real item and decision.
Primary references