How we work From your inbox to your factory floor.
Exactly how a package moves through the studio, start to finish – so a first-time account can picture week one before it happens, not after.
How a package moves through the studio
The same six steps, every package, whether it’s your first or your fiftieth.
- 1. IntakeYour drawings, specifications and any standards you already have on file, logged against the account and scoped against what’s actually in the package.
- 2. Engineering reviewThe scope is read for constructability and completeness before a single line is drawn, so queries surface early rather than mid-set.
- 3. DetailingThe set is drawn to the applicable standard, in your title block, against your Standards Record where one exists.
- 4. Two-stage checkingA studio check, then an independent review by a named senior reviewer – the same process described in full on Quality & Standards.
- 5. SubmittalThe checked set ships under your title block and review stamp, ready for your own submittal process.
- 6. RevisionsMarkups come back, get incorporated, and get checked again – tracked against the version of the Standards Record they were reviewed against, so nothing quietly drifts between rounds.
For projects under formal certification
The certification workflow, layered on top
Where a project runs under a formal quality certification, the standard six-step process doesn’t change – it gets additional sign-off points and document-control references built in at the stages your certification requires.
Tell us what your certification requires at scoping, and the workflow is built around it rather than adapted afterward.
Communication, stated plainly
One named contact runs your account throughout – not a rotating queue, not a different person on every email. Queries go to that person and come back from that person, in your working hours.
Where a Studio or Engineering Studio account is in place, that contact is the same person job after job, which is most of what makes the Standards Record useful in practice.
See how it runs on your own package
Start with one package on Overflow terms – no commitment required to see the process work.
Start with one packageStart with one package
See the process on a real drawing set
Send the basics. The right next step can follow.
Read by someone who runs accounts, not a sales desk.
See how an account’s model played out
Real project outcomes from BluEnt’s broader portfolio.
Where to go next
Related pages
Engagement
Before engaging
A process only earns trust once you can see week one before it happens.
FAQ
Frequently Asked Questions
What happens in week one?
Your first package moves through the same six steps as every package after it: intake, engineering review, detailing, two-stage checking, submittal, and revisions. Nothing special happens for a first package except that we are paying closer attention to what your standards actually are.
Who do we talk to day-to-day?
One named contact for your account, not a rotating queue. Queries go to that person and come back from that person.
What if our project runs under a formal quality certification?
That workflow layers on top of the standard one, additional sign-off points and document-control references built in where your project requires them. Tell us what your certification requires and we will build the workflow around it.
Start with one package
Send your first package. Watch the six steps run on real work.
Scope, queries and an honest read on the schedule, before any commitment.
- The same six-step process on every package, first or fiftieth
- One named contact runs your account throughout
- Certification workflows built in at scoping, not adapted afterward
- No commitment required to see it work
Project enquiry
Scope and questions come back, not a template.
