An architect takes photos and dictates comments during the walkthrough. The AI-generated draft brings observations, images and follow-up actions together—instead of requiring everything to be typed again that evening.
Explanation prototype · This is a local simulation with fixed sample text. No microphone, AI service, upload, task assignment or external sending is activated.
Less retyping of notes, less sorting of photos afterwards and less separate work to get action items to the right person.
This example does not assign a person based on a photo. The project role comes from the selected project configuration; an unclear role or instruction remains a question.
Living room. Check the position of spotlight SP-LIV-02 against the approved lighting plan L-R18. Have the electrician verify the reference dimensions before drilling. Photo 1 belongs to this item. The finish by the window needs repair; photo 2 belongs to that. Please follow up by Friday. There is still an unclear point in the corridor: we will discuss that first.
Check the source first. Nothing is being recorded.
Source: confirmed sample transcript + explicitly linked photo references.
Living room · SP-LIV-02 · source plan L-R18 · photo reference 1.
Living room · window area · photo reference 2.
The comment contains no clear action, location or discipline. No assignment or deadline is invented.
Check the transcript, photo links, task content, role and deadline. After confirmation, the available task workflow can place the selected actions with the appropriate project role.
Observations, spaces, images, actions and requested time frames. Missing information remains an open question.
An approved workflow can assign confirmed tasks to the appropriate role. Extended automatic assignment is a design proposal, not a proven live feature.
A different spotlight position is a design change. Additional work, technical approval and contractual agreements are not silently made final from a single sentence.
Meet Lucas
A plan becomes a building. Its information grows with it.
Explore a practical example
Construction
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usLucas · Product specialist · 36 s
ObraPad is designed to keep Obra Core as the shared foundation while you add capabilities over time.
Building-specific activation and restricted installer access are being prepared for the pilot and verified end to end. Ask which scopes can currently be tested.
The pilot direction is to begin with one workspace and add more later.
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
The access model is being developed so an installer or partner can use only the selected building, installation or task.
In the intended scenario, the installer only accesses the heat pump, its documents and assigned maintenance tasks in one building. Other buildings, financial information and private documents remain outside the scope. View, change, duration and revocation controls must be proven server-side before availability.
The design keeps an additional workspace and partner access as separate choices, with the building passport as the shared foundation.
Help me choose