STrOp · Learn
Practical knowledge for specialty contractors
Compliance, change management, project controls, and the data discipline that compounds across bids. Written for California specialty subs — owners, PMs, estimators, and the field.
15 of 47 articles for Admin. Clear
All 91 topics
A new shop in STrOp — sign up and set up in one sitting
Create your organization in the two-step wizard, take the thirty-second tour, and let the getting-started checklist tick itself off as your real data lands.
Award a job — what flips when you win
The Award Job button is the moment a pursuit becomes a job — what the three-field form records, what changes underneath, and the setup work that's deliberately still yours to do.
Build your crew roster
Add your workers once — name, classification, agreement, rate — and every timecard, schedule slot, and certified-payroll line downstream fills itself from the roster instead of being retyped.
Certified payroll — one run a week, eCPR out the door
Build the week's certified payroll run from approved timecards, generate the eCPR XML DIR takes, print the A-1-131 for the GC's portal, and read the Compliance tab before you leave.
Companies and contacts — who you bid, who pays
Set up the GCs, owners, and people you work with once — typed correctly — and every pursuit, proposal, and invoice downstream links to the right party automatically.
Dispatch board basics
The day's service calls, who's on each, and what's still unscheduled — run the board in the morning and every tech knows where they're going without a phone tree.
Log an opportunity and work the pipeline
From "heard about a job" to a pursuit moving through Qualify, Budget, Bidding, and Bid Submitted — where work enters STrOp and how the board tracks it to award.
Migrate your data into STrOp
How a company moves onto STrOp from whatever it runs today — master data first, in-flight jobs at their current state, and the old system's paper trail as a searchable archive. Nothing re-entered, nothing silently dropped.
Send your first proposal
The proposal builds itself from your estimate — address it, shape what the GC sees, print the PDF, and mark it Submitted so your pipeline knows the bid is out.
Service agreements — cadence, visits, invoicing
Turn recurring maintenance into an agreement STrOp works from — the visit cadence generates the calls, the billing cadence drives the invoices, and neither depends on anyone remembering.
Set up a service agreement — cadence, visits, dispatch, invoice
Turn a "walk it every three months" customer into an agreement that knows its next visit, puts it on the dispatch board with a tech, and bills it on its own terms when the visit is done.
Set up the subcontract — parse the PDF into the fields the job runs on
Register the executed subcontract once, let Parse Contract read value, dates, retainage, and terms out of the PDF, review each field against its page, and flag what the contract makes due.
The STrOp glossary — what we call things, and why
Construction has never agreed on its words — the same term means three different things depending on who's talking. Here's the one name STrOp uses for each thing, and the words we deliberately split.
Who sees what — invite your team and set roles
Invite people by email with a role, read the capability matrix as the rule of your org, and see what a foreman's phone and a finance seat actually show.
Why the record is a database, not a folder of spreadsheets
Spreadsheets are where a sharp operator thinks. They're a bad place to keep the shop's record. What a relational database does that a folder of .xlsx files can't — one fact in one place, links that can't be mistyped, locks that hold for everyone, a history of who changed what — and why every list in STrOp still exports to CSV.
See STrOp in action
Single-pipeline operations for California specialty contractors — bid through warranty.
Request beta access →