Understand the requirement
Start by asking what the site team needs to do and what a reviewer will need to see.
← Selected workProject notes / 03
Venture · Compliance systems
GreenStruct.
I started GreenStruct to explore one practical question: can a site team connect each environmental requirement to an owner, an action, and proof that the work was completed?
Illustrative workflow · Evidence must be reviewed against the requirement.
01 / The question
From a requirement to work on site.
Construction teams can miss environmental requirements because rules, site actions, and evidence are managed in different places.
I started with the handoff between understanding a requirement and getting it done on site. GreenStruct brings those steps into one record: what is required, who owns the action, what evidence is needed, and who reviews it.
My part. I worked on the compliance process, mapped the steps towards certification, and discussed the idea with people in the industry.
Progress so far. GreenStruct reached discussions about a pilot and was selected for Microsoft for Startups Founders Hub.
- Requirement
- Link the source and the obligation being assessed.
- Action + owner
- Specify the site task, responsible person, and due date.
- Evidence
- Attach the relevant photo, log, or supporting record.
- Review
- Record who checked it and whether anything is still missing.
A file attached ≠ a requirement satisfied.
Illustrative record structure. The reviewer still needs to judge whether the evidence addresses the requirement. This is not legal guidance.
02 / The work
Keeping the task and the proof together.
Write down what needs doing
Turn each issue found during an assessment into a task that someone can take responsibility for.
Keep the proof with the task
Keep the photos and records with the task so the reviewer can check what was done.
03 / The choices
What a site team needs to see.
Show the unfinished work
I chose to show the tasks and their evidence. A single score would make it harder to see what still needs attention.
Make the status easy to check
Someone reviewing a status should be able to open the requirement and see the evidence behind it.
Try it on site
The industry conversations helped me develop the idea. They do not yet show how well it works on a site.
04 / What’s next
What still needs testing.
GreenStruct reached discussions about a pilot and was selected for Microsoft for Startups Founders Hub. I now need to test the process on a site, from assigning a task to reviewing the evidence. I don’t yet have results showing how much it helps the team.
What I learned
- 01Each requirement needs a clear task attached to it.
- 02The reviewer needs to be able to find and check the supporting records.
- 03The next thing I need is feedback from people using it on site.