Onboarding What the first two weeks actually involve.

Most onboarding pages describe a supplier's process. This one describes what your team has to do, because that is the part that actually costs you something.

What we need from you, and when

Four things. None of them requires a workshop.

  • Your title block and template files. Native format, not a PDF. This is the single item that most often delays a first package.
  • A sample of your standards. Two or three recent sets that represent how you want work drawn. Marked up is better than clean, because the corrections tell us more than the drawings do.
  • The specification and finish schedule for the first package.
  • One named contact on your side who can answer a convention question without escalating it.

That is the handover. If your conventions are undocumented, which is common, we record what your sets actually show and confirm it with you rather than asking you to write a standards manual first.

What happens on our side

The Standards Record is opened for your account and populated from what you sent. Layer conventions, dimensioning practice, tagging scheme, hardware preferences, construction defaults and the details you reuse.

That record is versioned. When you correct something on a package, the correction goes into the record rather than into one detailer's memory, which is why the second project starts closer to finished than the first.

A named contact is assigned on our side too. You are not routing questions into a general queue.

The first package is deliberately small

Not a pilot in the marketing sense. A real package, small enough that a misunderstanding costs a conversation rather than a schedule.

It runs through the full process, including two-stage checking, so what you see is what the arrangement actually produces rather than a first impression. The comments that come back on it are the most useful part of onboarding, and they usually reshape the Standards Record more than the initial handover did.

What week one costs your team

Honestly: a few hours, concentrated at the start.

Assembling the template files and sample sets is the bulk of it. After that it is answering convention questions as they arise, and reviewing the first package when it returns.

The load falls sharply after the first package. That is the point of the Standards Record, and it is the difference between onboarding a supplier and permanently supervising one.

What does not happen

  • No software for you to install. We work in your platform, on your conventions.
  • No process change on your side. The submittal goes out under your title block, through your contractual route, as your submittal.
  • No lengthy discovery phase. The first package is the discovery.

Who owns what

You
Us
Standards and conventions
Own them
Record and apply them
Title block and templates
Provide
Work inside
Specification interpretation
Final say
Raise queries before drawing
Submittal issue
Issue under your name
Prepare and check
Design-team relationship
Yours throughout
Never contacted directly

Start with one package

Start with one package

Onboarding is mostly what happens around it

Send the basics. The right next step can follow.

Read by someone who runs onboarding, not a sales desk.

This field is for validation purposes and should be left unchanged.

See how an account's model played out

Real project outcomes from BluEnt's broader portfolio.

See our case studies

The studio adapts to your standards. Someone still has to hand them over.

Answers

Common questions

How long does onboarding take?
The handover itself is short. The first package runs on a committed calendar date agreed at quoting, like any other package. Most of what onboarding achieves happens through that first package rather than before it.
What if we do not have documented standards?
That is normal. We record what your recent sets actually show and confirm it with you. You do not need to write a standards manual before starting.
Do we need to change how we work?
No. Work happens in your platform, to your conventions, under your title block. If the arrangement requires you to change your process, it has been set up wrong.
Who do we talk to once we start?
One named contact on our side, with a senior reviewer accountable for what ships. Not a general queue.
What if the first package goes badly?
Then it goes badly on a small package rather than a large one, which is why it is deliberately small. The comments feed the Standards Record and the second package is measurably better. If it does not improve, that is useful information for both of us.

Start with one package

Onboarding is mostly what happens around one real package.

  • Four things needed to start, none of them a workshop
  • A deliberately small first package, run through the full process
  • One named contact on each side, not a general queue
  • No software to install, no process change on your side

Read how we work  ·  See Studio Models

Project enquiry

Scope and questions come back, not a template.

  • This field is for validation purposes and should be left unchanged.
  • Accepted file types: pdf, dwg, Max. file size: 100 MB.

Reserve Your
Meeting Slot Today!

Contact Now

Connect with us!

Let's Talk Fixed form

Let's Talk

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Services We Offer*
Subscribe to Newsletter
Go up