01ProductIn development · Early access

What gets noticed should get finished.

Spotting the issue is rarely the gap. Getting the right person on it, and knowing what came back, is.

An open interior seen from above during construction: floor protection marked with blue layout tape, a small rolling scaffold, stacked trim and plastic over a wall opening. — Field photograph. An interior during construction, shown for context. It does not depict STRUXIS in use or a result achieved with it.

01In your words

Say it the way you’d say it on site.

Shorthand, half sentences, the name everyone uses for the electrician. STRUXIS keeps the recording, shows what it heard and proposes the work. A person decides what happens next.

01The recording, and what STRUXIS heard

“Sparky needs to drop that box six inches before the tile guys roll in tomorrow.”

Voice note · 0:06Recording kept

The text is what STRUXIS heard. Correct it in review; the recording is there to check against.

02What STRUXIS proposes

Proposed task

Lower outlet box 6 in. before tile

What: Lower the outlet box 6 inchesHeard
Who: Carlos, electricianInferred · checkfrom “Sparky”
Where: Master bathroomInferred · checkfrom where the walk was
When: Tomorrow, before tileHeard

03What a person confirms

“Sparky” means Carlos
It is the master bathroom
Due tomorrow, before tile

Nothing is assigned until a person confirms it. When the work is done, someone else verifies it.

It won’t always hear it right.: Jobsites are loud and shorthand is local, so the text is only what STRUXIS heard. The recording stays with the item to check against, and guesses are marked.
Meant to pick up your crew’s shorthand.: The intent: correct a term once, say that “Sparky” means Carlos, and STRUXIS carries it forward on that project, with the history kept. This is design direction. It is not released.

Representative demonstration of the intended workflow. Notes, names and tasks are illustrative. The text shown is what STRUXIS would have heard, not a guarantee that it hears every word correctly. Marking what was heard and what was inferred is the intended design and is not fully built.

02From note to verified

Eight visible states. Three rules that hold in all of them.

A work item can move through these states. Pick one to see who acts, what happens and what the record keeps.

CapturedCapture · 1 of 8

Who acts: Whoever noticed it
What happens: A voice note, a photo or a typed line is saved as it was given. No form, no menu.
What the record keeps: The original recording or note and the photo, who captured them and when.

The original stays.
The voice note and photo stay with the item, as captured.
A draft isn’t a decision.
STRUXIS drafts the task and marks what it inferred. Nothing is assigned until a person reviews and confirms it.
DraftReviewConfirm
Completed isn’t verified.
When work needs a check, someone other than the person who did it reviews the evidence, or returns it with a note.

The intended workflow. Questions, blockers, declined work and returns stay visible along the way. Accept, Ask and Decline are built but have not been released.

Watch one item go through it

03In the field

Capture on the walk. Sort it out after.

A job is a hundred small things seen in passing. Capture them as you go and review once, off the ladder.

Talk: Say it the way you’d say it to your PM.
Snap: Photos stay with what you said.
Type: A quick note works the same way.

The planned end-of-walk summary lets you review now or later. Nothing becomes a task until you review it.

Saving on the device first is built, but not released yet.

Looking down past an unfinished stair with rough timber treads to a protected floor, a rolling scaffold and cabinet boxes waiting to be installed. — Field photographs. Three jobsite interiors, shown for context. They do not depict STRUXIS in use or a result achieved with it.

A corridor at the drywall stage: taped and mudded joints on the walls, new floor tile, and an open doorway ahead. — Field photographs. Three jobsite interiors, shown for context. They do not depict STRUXIS in use or a result achieved with it.

04Trades and review

Two people close an item. Never the same one.

A utility room counter with oak cabinetry, a stone top, a wall outlet and a faucet below a window.

For the trade

Know exactly what done means.

The photo, the room and the deadline
Who asked
What done means
Finish it and attach evidence

A bathroom with a frameless glass shower enclosure, large floor tile and a long vanity under an arched mirror.

For the reviewer

Check the evidence, not the story.

The original note beside the evidence
Verify it, or return it with a note
The first submission stays in the history
You can’t verify your own work

Field photographs. Jobsite interiors during finish work, shown for context. They do not depict STRUXIS in use or a result achieved with it.

The trade view is designed, not released. Team verification records your own review. It is not an official inspection, engineering review or code-compliance certification.

05The record, later

A wall of three arched niches with oak shelves, blue tape around the edges and plastic sheeting over the cabinets below. — Field photograph. A jobsite interior, shown for context. It does not depict STRUXIS in use or a result achieved with it.

Months later, the answer is still there.

See the original note, the decision, the person responsible and the review that closed the work. Each piece stays tied to the project.

Field Walk: What was noticed, as it was captured.
Decision: What was agreed, and with whom.
Task: Who owned it, the evidence that came back and who verified it.
Question: Who asked, who answered and what the answer was.

06Where it stands

What’s built. What’s still ahead.

STRUXIS is in development. This is where each part of the intended workflow stands.

Read our trust principles

Saving captures on the device first: Built and reviewed. Not released.
Accept, Ask and Decline: Built. Not released.
The trade view: Designed. Not released.
Marking what was heard and what was inferred: Intended design. Not fully built.
Picking up a crew’s shorthand from corrections: Design direction. Not released.
Daily Logs, project plans and Ask STRUXIS: In development, still being refined.
Product access: Not open. Early access records interest only.

Details

What happens when there's no signal?

STRUXIS is designed to save captures on the phone first and sync when a connection returns, showing which is which. On-device saving is built and reviewed but has not been released yet. Once released, photos that exist only on the phone can be lost if the phone is lost or its storage is wiped before they sync.

Can one person use it alone?

Yes. One person can capture and follow through. Work you finish yourself is shown as completed rather than independently verified, because verification needs someone else.

Is verification an inspection?

No. Team verification records your own team's review of completed work. It is not an official inspection, engineering review or code-compliance certification.

Request early access.

STRUXIS is in development. Registering records your interest. It does not grant product access or start a trial.

Request early access

Status: In development
Early access: Interest registration only
Product access: Not granted by registering. No trial.

Field photograph. A vaulted ceiling on a jobsite, shown for context. It does not depict STRUXIS in use or a result achieved with it.