“Unitized panel rev. C did not match opening dimensions on grid B-12.”
Filed by the field super after a layout check. The earliest curtain wall record, tagged as blocking closeout.
- RFI #142
- Tower B
- 2024-08-12
- Open · 27 days
Search & DiscoveryOne box. Every project.
Anything you ever filed.
Ask the way you would ask a colleague. Storia reads every document in every system you already run, and every answer arrives with its source attached.
Storia · Ask & search--:--
- Every hit cites its source
- Every source opens in one click
- Your data stays where it lives
One question
Ask it the way you would say it.
Why did the curtain wall delay start?↵ Search
“Rain delay AM. Glazing crew released; opening B-12 to be re-measured Monday.”
Same area, three days earlier. The crew noted a measurement before any RFI existed.
- Daily log
- 2024-08-09
- Tower B · Lvl 14
- Weather 0.6″
“Re: B-12 mullion. Architect is reviewing. Please hold release of unitized lot 4.”
A PM to architect thread that predates the formal change order by two weeks, carrying a revised shop drawing.
- 2024-08-14
- 4 participants
- 3 attachments
The shift
Whoever knows the job should be the one searching.
6systemsUnified
answered one question at once, out of the fourteen Storia reads from.
Sample query · Meridian Heights
11secondsAnswered
from question to cited answer in a working session, across three taps and zero menus.
Measured session · B-12 mullion
Two moves
Ask in plain words. Get the whole story back.
01 / 02 · Ask
If you can type a question, you can use it.
Describing what you want is the whole interface. Onboarding runs about as long as a toolbox talk.
- No filters menu, no query syntax
- No training beyond arrive, type, find
- No IT setup, just existing logins
What did the architect say about B-12?
Email · Aug 14“Hold release of unitized lot 4 pending review.”
Show me everything else on B-12
14 hitsRFI, daily logs, schedule update, change order.
3 taps · 11 seconds0 menus
02 / 02 · Stitch
One question. Every system that answers it.
Hits arrive assembled in the order events happened, so the true origin of a delay shows itself instead of being argued about.
- Stitched from logs, RFIs, email and schedule
- Chronological, not relevance-ranked mush
- Every row opens its source in one click
Glazing crew released for rainEarliest field mention. The opening was already wrong, but unrecorded.
Daily logRFI #142 raised on the B-12 openingFiled three days after the log, marked as blocking closeout.
RFIHold placed on unitized lot 4PM to architect, glazing sub copied. A revised drawing lands in the thread.
EmailSchedule v06 slips glazing 11 daysThe delay's first appearance on the master schedule, tied back to RFI #142.
Slip 11dCOR-019 re-fabricate mullion runEnds the chain, citing the RFI and the revised drawing as the basis.
$48,200Every hit cites its source
Three answers, three receipts.
Result 01RFI #142
Result 02Daily log
Result 03Email thread
The formal record, and the day it was raised.
The RFI is where most searches would stop. It names the defect and it is dated, but on its own it does not tell you the crew already knew.
Open 27 days · tagged blocks closeout
“Unitized panel rev. C did not match opening dimensions on grid B-12.”
Filed by the field super after a layout check. Architect notified the same day; the item is flagged as blocking closeout on Tower B.
SourceRFI #142
Filed2024-08-12 · 10:42
LocationTower B · grid B-12
StatusOpen · 27 days
Three systems. One question.
Turn this into a claim narrativeWhat it searches
Every document. Every system. One box.
Systems it reads from
PMISProcore
PMISAutodesk Construction Cloud
PMISOracle Aconex
PMISOracle Unifier
DrawingsBluebeam
SchedulesPrimavera P6
SchedulesMS Project
EmailOutlook
EmailGmail
FilesSharePoint
FilesOneDrive
FilesDropbox
FilesBox
FilesGoogle DriveAnd the restWhatever else your team already runsRequest a source →
14 systems10 document typesread into one source-linked record
Document types it returns
RFIsSubmittalsDaily logsChange ordersMeeting minutesSchedulesDrawingsPhotosEmailsSpecs
Simple enough for anyone on the crew
The person who understands the job should not need a file clerk.
01
No filters menu
A single box takes a plain-English question and returns cited hits. There is no advanced mode to learn and nothing to configure first.
02
No training
Onboarding runs about as long as one toolbox talk. Arrive, type, find. Crews who have never opened a PMIS report use it on day one.
03
No IT setup
Connect the logins your team already has. Indexing happens in the background, and your data stays where it lives.
What’s next
Found it. Now put it in writing.
Claims & Dispute Resolution
A page-cited claim narrative.
Cover, contents, narrative and exhibits, generated from the records this search just surfaced.
See the deliverableSchedule Intelligence
The delay, with its cause attached.
The same event chain measured against the schedule: what slipped, why, and what it broke downstream.
See delay analysis- Separate products
- Identical data
- One record
Search & Discovery
Stop hunting through folders. Start asking questions.
Bring one project. We will connect the systems you already run and let you ask it anything, then hand you a sample report from your own record.
- 20 minutes
- One project
- Walk out with a report