// HOW IT WORKS

A Tuesday With DPM.

Follow a real PM through their day. This is what Documint PM looks like when drift hits, documents need answers, and margin is on the line.

Based on a real POC project, $70M MEP build, 14 active trades

Scroll to start the day
6:15 AM
Kitchen Table
Your phone buzzes. DPM caught something overnight.

You haven't left the house yet. Coffee's still brewing. DPM scanned 14,847 data points across your project while you slept. At 3:42 AM, it found a problem nobody on the team has seen yet.

SCHEDULE DRIFT DETECTED
Level 3 mechanical rough-in is 4 days behind. Root cause: Submittal SB-112 response was delayed 6 business days by the engineer. Downstream impact: Insulation crew start date shifts from March 14 to March 18. Cost exposure if unaddressed: $12,400 in idle labor and remobilization.
DPM, DRIFT SIGNALS, LIVE
DPM Drift Signals Dashboard showing active drift alerts and signal status
You know about the problem before your GC, your super, or your crew. That is the difference.
7:30 AM
30 Min to the Job
Thirty minutes of windshield. Your to-do list, cleared.

Used to be radio and coffee. The thirty-minute drive to the job was windshield time, non-productive by default. Now you turn off your street and open a voice chat with DPM. TIA walks you through every active scope and the latest projections. She emails the most recent three-week lookahead to your phone. She reminds you of the deliverable you owe today's BIM coordination meeting at 11, and the three deliverables for the foreman's meeting at 2, the one you have to cover because Carl is on another site. You ask her to summarize yesterday's coordination meeting and last week's pull plan. She offers to draft a memo with the action items and email it to the team, holding for your sign-off before anything sends. All chats are logged.

TIA is the intelligence inside DPM. She is what you interact with. PhD-level command of your project. Access to every data point you shared with the project file, every email, every message, every field reality. She is your cognitive assistant. She drafts the documents. She tracks every deliverable. You ask. She answers. No digging through folders. No calling the office.

DPM, PROJECT DETAILS + MESSAGING
DPM project details showing schedule tracking and messaging integration
DPM, VOICE CHAT WITH TIA, 30 MIN TO THE JOB
Brief me. Owners is at 9.
All three active scopes reconciled this morning. Two are on plan. L2 mechanical is behind, recovery plan ready to walk through. Three-week lookahead emailed to your phone. Owners asked about closeout last month, projection still holds.
What do I owe BIM at 11?
Revised coordination drawing for the L3 mechanical room. Already drafted from your markups last week. Awaiting your sign-off. Sending to your phone.
Carl's out. I'm covering his 2 PM foreman's meeting.
Three deliverables on you for that meeting: Monday's manpower plan for L2 recovery, two-week material call on the prefab racks, and sign-off on the L1 inspection schedule. Notes from Carl's last two foreman meetings attached for context.
Summarize yesterday's coordination meeting and last week's pull plan.
Coordination, yesterday: 7 action items, 3 assigned to you. Pull plan, last week: L2 HVAC moved up 2 days to recover slip, L3 inspection sequence reordered, 4-day buffer added to closeout. Want me to draft a memo of the action items and email it to the team? I'll hold it for your review before sending.
Yes, draft it. I'll review when I park.
Drafted. Waiting on your sign-off. All chats logged to today's project record.

Thirty minutes ago, this was radio and coffee. Now your to-do list is clear, the memo is drafted and awaiting your sign-off, the three-week lookahead is in your inbox, and you know exactly what you owe three different meetings before the day is over. The non-productive hour just became the most productive hour of your week.

You park at the job with the most current information, the day's deliverables locked in, and nothing left on the windshield. A chill chat just cleared your to-do list.
const drift = dpm.reconcile(contract, fieldReality, pmDecisions) if (drift.detected) alert.immediate(drift, site.pm) // ▸ never wait for Monday
Mon 6:30 AM
Weekend Analytics
DPM ran the numbers over the weekend. Eight percent on the table.

Over the weekend, DPM ran cross-scope analytics on every crew on every active job. Monday morning, you open it. Three junior crews are outperforming the senior crew on the L2 mechanical scope. Under the original projection, the senior crew was on the critical path. They had to be there. After the updated reconciliation, DPM's revised projection says they don't, not for the next three days. The junior crews are holding the pace on their own.

DPM surfaces the move. Pull the senior crew off L2 for three days. Send them to CH-08, where the upcoming route picking and layout work matches their experience exactly. Splitting the crews for three days saves 8 percent across both scopes. To cover the senior crew's seat on L2, DPM recommends pulling Darrell out of the shop to supervise the junior crews. He matches the scope, and he's available starting tomorrow.

DPM, DEEP ANALYTICS + RECONCILIATION
DPM analytics dashboard reconciling crew performance and projected outcomes
DPM, MONDAY MORNING, CROSS-SCOPE OPTIMIZATION
Weekend analytics turned something up. Three junior crews on L2 mechanical are running ahead of plan. The senior crew is at plan, not ahead. Want to walk through it?
Yes. What's the move?
Pull the senior crew off L2 for three days. Send them to CH-08, route picking and layout start there next week and that crew is the best fit. Original projection had them on the L2 critical path. The updated projection says they don't need to be there for the next three days. Net save: about 8 percent across both scopes.
Who covers their seat on L2?
Pull Darrell out of the shop. He matches the scope and the junior crews need supervision, not direction. He's the right level. Available tomorrow.
Approve. Draft the move plan and notify the team.
Drafted. Reassignment plan, three-day schedule rewrite for L2 and CH-08, notifications to the senior lead, Darrell, and the GC. Holding for your sign-off before anything sends.

A decision like this used to take a senior ops review, a stack of timesheets, and three weeks of data the field never had time to compile. DPM ran it overnight. Eight percent on both scopes, recovered before Monday morning coffee.

DPM doesn't just find spec conflicts. It finds the moves no one on the team has the bandwidth to see.
11:00 AM
Office
$47,000 sitting in your documents. DPM found it.

You sit down at your desk to check the margin dashboard. DPM has been scanning every document on the job, meeting minutes, change orders, daily logs, purchase orders, looking for money you're owed but haven't billed.

⚠ MARGIN ALERT, SCOPE GAP DETECTED
Owner-directed scope change found in meeting minutes from February 12 (item 4.c, additional penetration firestopping, Building C). No corresponding change order on file. Estimated value: $47,200. Change order documentation auto-generated with full backup.
DPM, PROJECT ANALYSIS (data redacted)
DPM project analysis view, data redacted for client confidentiality
DPM, MARGIN RECOVERY, Q1 2026
◎ MARGIN RECOVERY DASHBOARD
$47,200, Bldg C firestopping scope gap (no CO filed)
$18,600, Level 2 T&M labor unbilled (3 crew-days)
$11,400, Material escalation clause triggered (copper +6%)
Source documents: Meeting minutes, daily logs, POs, contracts
▸ 3 change orders auto-drafted, pending PM review
▸ Total recovered this quarter: $183,400
▸ Current booked margin: 14.2% (up from 11.8%)

That $47K was hiding in a meeting minute from three weeks ago. Nobody had time to cross-reference it against the change order log. DPM does. Every day. On every job.

$183K recovered in Q1 across 14 active jobs. Margin went from 11.8% to 14.2%.
const gaps = dpm.scanForMarginBleed(meetingMinutes, changeOrders, billingLog) if (gaps.found) dpm.draftChangeOrder(gaps, fullBackup) // ▸ money you earned, now you can bill it
2:00 PM
Site Office
New super starts Monday. Add them in 10 seconds.

You just hired a superintendent for the Level 4 build-out. They need access to field data, daily logs, and crew schedules, but not contracts, billing, or margin reports. You open DPM's team panel and send an invite.

DPM, PROJECT ACCESS CONTROLS
DPM Project Access panel showing workspace member controls and permission levels

No IT tickets. No software installs. No six-week onboarding. You send a link. They click it. They see exactly what their role needs, nothing more. You control access with one screen.

New super has field access before they park their truck on Monday morning.
4:45 PM
Field Ping
Three field pings. One photo. Bad mobilization, averted.

End of the day. Rick messages DPM from the field, looking for the floor drains for the commissary. He's the third team member to ask about those drains today. DPM and TIA flag the pattern as a possible drift event and alert the leadership team. Carl follows up with a photo from the dock: four pallets stamped FD with carriers. As TIA scans the image, she sees what nobody else has yet. The drains have trap primer connections.

DPM checks the specs. There's an approved RFI on this scope. The project is not installing trap primers. It's using trap guards. The pallets on the dock are the wrong drains. TIA drafts two emails on the spot, one to the shop procurement team, one to Win Supply, and holds them for your sign-off. Nick at Win Supply responds within the hour. They have the right drains in stock, and the wrong ones can go back for credit.

DPM, DATA CONNECTIONS + DOCUMENT INDEX
DPM Data Sources panel showing document index and database connections
DPM, FIELD PING, COMMISSARY FLOOR DRAINS
Rick (field): Where are the floor drains for the commissary? Crew is staging.
Third question about the commissary drains today. Flagging it. Leadership in the loop.
Carl (dock): Photo, 4 pallets here, FD with carriers.
Looking at the photo. The drains have trap primer connections.
There's an approved RFI on this. We changed from trap primers to trap guards. The pallets on the dock are the wrong drains.
Drafting two emails. One to the shop, halt the mobilization. One to Win Supply, asking for the right drains and a return on the wrong ones. Holding for your sign-off.
Send them.
Sent. Nick at Win Supply replied. He's got the right drains in stock and we get a credit on the return. Bad mobilization avoided.

Without DPM, those four pallets get rolled onto the lift tomorrow morning. The crew installs. A junior PM from the GC walks by on inspection, catches the mismatch, and calls it out. Now you have two bad options: rip the drains out and rework, or install the trap primers the original drawings called for, more material and more labor than the trap guards you planned on. The credit on the return isn't the save. The rework you didn't have to do is.

Three field pings became one captured drift event. The wrong drains go back. The right ones arrive Tuesday. Your team didn't lose a day.
Your Tuesday

Stop the drift. Reclaim the margin.
Go home on time.

One conversation with our team. We'll show you how DPM handles your actual project documents, not a demo dataset.

Apply for Beta Access