01
Context
Record the application, stakeholders, location and project stage.
Projects and referencesReview project decisions in the order they become useful.
Projects / methodology
Review project decisions in the order they become useful.
A project reference is more valuable when it explains the question, constraint, evidence and next action instead of showing a product without context.
Procurement question
Start with the project question.
Use the methodology to frame what the team is trying to decide, what evidence is available and which detail still needs confirmation.
01Review project decisions in the order they become useful.Projects / methodology
Decision evidence
A simple project review sequence.
The sequence supports product, application, technical and commercial conversations without presenting unsupported project outcomes.
02
Constraint
Identify the site, mounting, document, market or procurement constraint shaping the decision.
03
Evidence
Link the relevant product, application, testing image or requested file to the question it answers.
Keep these facts connected
Distinguish a public reference from a customer result.
The public site can explain the review method. Customer names, measured outcomes and project documents require explicit permission and verified source material.
- 01
What is public
Use verified product, process and application information that can be reviewed openly.
- 02
What needs permission
Treat customer identity, project photography and project results as separate approval items.
- 03
What happens next
Give the project team a clear route to a product, document or enquiry review.
Questions to carry forward
Keep the next questions visible.
Use the answers as a starting point. Model, market and project-specific details still need written confirmation.
Does the methodology page describe a completed customer project?
No. It explains how to organize a review and keeps customer evidence separate from general company or product information.
How can I request a project reference?
Include the application, market and the type of reference or document needed so the team can confirm what can be shared.
Your next step
Use the method on your own project brief.
Share the application, product context, target market and documents you need reviewed. The final configuration remains subject to the selected model and project brief.