From a residential design brief to coordinated schedules

Start with a need, not a row of products

The Window Room brief calls for reading, conversation, and storage while retaining the floor and openings. These requirements do not prescribe an exact sofa, joinery construction, or wall coating. They explain why information will be needed and what a later choice should serve.

Use the questionnaire to collect perspectives and the brief to record agreed intent. A drawing locates relationships. A specification records an item’s sourced attributes. Schedules organize placement, quantities, or surface assignments. These are the library’s conventions; agree the roles with your actual project team.

Trace three different kinds of information

Keep identifiers stable enough that another person can follow the chain. The table follows the original illustrative fixture; it adds no real client decision, measured quantity, or supplier evidence. Notice that some cells should remain unresolved.

Decide where each fact belongs

Avoid copying the supplier model into five editable files unless you also have a clear update procedure. Keep its authoritative record identifiable and use references elsewhere. If a display copy is necessary, identify the source revision so it can be checked during an issue review.

Do not force every kind of quantity into one register. One sofa is an item count. The sample’s 20 m² is a nominal floor footprint. Neither gives the wall-finish purchase quantity. The finish register can therefore contain a valid surface assignment with an unresolved area.

• Use one room reference throughout the package.
• Connect each significant plan item to a specification or an explicit open information request.
• Check quantities against the correct unit and application.
• Keep the source, review state, and revision with the information it describes.

• Record product attributes
• Register room quantities
• Assign finishes to surfaces

Test the chain with one proposed change

Imagine the proposed F-01 sofa changes. Begin in the product record, then review the plan, quantity register, budget, and timing. The brief may stay the same: the room still needs conversation seating. A product change and a brief change are different events even when both require review.

Document which records changed and which were checked but remained unchanged. Preserve the previous issue and identify the current coordinated set. This is a manual teaching workflow, not a claim that OpenLintel already synchronizes those records automatically.

• Work through the specification-change exercise

Before you move on

• Does each requirement connect to a relevant record without prematurely specifying a product?
• Is the authoritative source for each fact identifiable?
• Could a colleague trace a change through the affected records and find the unresolved work?