Consultant onboarding: add structure without losing the human touch

Three areas to address together

1. Professional knowledge

In­tern­al meth­od­o­lo­gies, sample de­liv­er­ables and cla­ri­fic­a­tion ques­tions can be doc­u­mented in re­sources suited to the role. Video or a con­ver­sa­tion­al as­sist­ant are op­tions to eval­u­ate ac­cord­ing to the con­tent, con­fid­en­ti­al­ity and sup­port needs.

2. The firm’s culture

Values, un­writ­ten prac­tices and col­lab­or­a­tion habits can be ex­plained in re­sources, but also through con­ver­sa­tions with a mentor and the team. Plan op­por­tun­it­ies to ask ques­tions and meet key con­tacts; di­git­al ma­ter­i­als do not re­place that re­la­tion­ship.

3. Internal tools and processes

In­tern­al tools and pro­ced­ures can be doc­u­mented in up-to-date guides. An as­sist­ant may help people find in­form­a­tion, but its an­swers must be checked and sens­it­ive pro­ced­ures must remain avail­able through ap­pro­pri­ate chan­nels.

What conversational AI changes in practice

The volume and nature of a new starter’s ques­tions depend on the role, or­gan­isa­tion and on­board­ing jour­ney. Before de­ploy­ing an as­sist­ant, record the ques­tions ac­tu­ally re­ceived and use a su­per­vised trial to check wheth­er an­swers are ac­cur­ate, up to date and ap­pro­pri­ately refer people to a human con­tact. See the solu­tion for businesses.

With clear con­fid­en­ti­al­ity and re­ten­tion rules, re­cur­ring ques­tions can help identi­fy gaps in doc­u­ment­a­tion. Teams must in­ter­pret and val­id­ate them, then use them to update re­sources. See also evaluating internal training.

Define expected autonomy through concrete outputs

On­board­ing is not just about know­ing the firm’s meth­ods. Spe­cify what new starters can pre­pare in­de­pend­ently, what re­quires review and what re­mains re­served for a re­spons­ible man­ager. Ex­pect­a­tions differ ac­cord­ing to ex­per­i­ence, as­sign­ment and client-re­la­tion­ship rules. An identic­al learn­ing path for every­one will not ne­ces­sar­ily reveal these dif­fer­ences.

Build an autonomy map by task: pre­par­ing a brief­ing note, struc­tur­ing an ana­lys­is, taking part in an in­ter­view or shar­ing a doc­u­ment. For each task, name an ob­serv­able output and the ex­pec­ted level of su­per­vi­sion. Avoid con­fus­ing con­fid­ence in speak­ing, know­ledge of in­tern­al ter­min­o­logy and the abil­ity to pro­duce a re­li­able de­liv­er­able. As­sess­ment must focus on the work and its cri­ter­ia, not a gen­er­al im­pres­sion of how well someone has settled in.

The de­liv­er­able is a pro­gres­sion agree­ment dis­cussed between the con­sult­ant and their des­ig­nated con­tact. It spe­cifies the ini­tial situ­ations they can take on, review cri­ter­ia and the de­cision-maker who au­thor­ises great­er autonomy. This doc­u­ment re­mains open to re­vi­sion if the as­sign­ment changes. It is neither a prom­ise of a uni­ver­sal time­frame nor an auto­mated de­cision about the person’s per­form­ance.

Prepare usable cases without exposing client files

As­sign­ment ex­amples help make meth­ods con­crete, but their use re­quires prior review. Re­mov­ing a client’s name is not always enough to pre­vent iden­ti­fic­a­tion: a highly spe­cif­ic sector, a known event or a com­bin­a­tion of fig­ures may still reveal their iden­tity. For ini­tial prac­tice, an en­tirely con­struc­ted case often pre­serves the reas­on­ing without re­using a real file.

If per­son­al data is being con­sidered, France’s data pro­tec­tion au­thor­ity, CNIL, states that col­lec­tion must be lim­ited to the data needed for a defined pur­pose. At the same time, have the firm’s con­fid­en­ti­al­ity ob­lig­a­tions and rel­ev­ant con­trac­tu­al terms re­viewed. The tech­nic­al abil­ity to upload a doc­u­ment to a tool does not au­thor­ise shar­ing it or re­using it in train­ing.

Build an ex­er­cise pack con­tain­ing a fic­tion­al con­text, the ne­ces­sary doc­u­ments, de­lib­er­ately miss­ing in­form­a­tion and mark­ing cri­ter­ia. Identi­fy what may be used with an as­sist­ant and what must remain out­side that use. Have this scope ap­proved before dis­tri­bu­tion. This pre­par­a­tion avoids asking a junior con­sult­ant to decide alone which client in­form­a­tion may enter their learn­ing tools.

Organise mentoring around evidence of work

A mentor who is avail­able in prin­ciple may not be ac­cess­ible when a dif­fi­culty arises. Spe­cify the chan­nel for re­quest­ing help, how to flag a block­age and the al­tern­at­ive when the mentor is absent. New starters must know how to dis­tin­guish a ques­tion that can wait from a situ­ation re­quir­ing ap­prov­al before con­tinu­ing, par­tic­u­larly before send­ing any­thing ex­tern­ally.

Base follow-up meet­ings on some­thing the con­sult­ant has pre­pared: an ana­lys­is out­line, a scop­ing note or a list of as­sump­tions. The mentor ex­am­ines the reas­on­ing, iden­ti­fies pri­or­ity cor­rec­tions and ex­plains their own de­cisions. This ap­proach makes im­pli­cit ex­pect­a­tions vis­ible without turn­ing the meet­ing into a re­cit­a­tion of the in­tern­al guide. It also helps identi­fy a meth­od­o­lo­gic­al dif­fi­culty sep­ar­ately from a prob­lem ac­cess­ing re­sources.

Keep a pro­por­tion­ate record of de­cisions: the task re­viewed, feed­back given and the next prac­tice situ­ation. There is no need to archive every hes­it­a­tion or turn ques­tions asked of an as­sist­ant into in­di­vidu­al rank­ings. The fre­quency of re­quests for help de­pends on the con­text; on its own, it is not an in­dic­at­or of low com­pet­ence. Mon­it­or­ing should sup­port pro­gres­sion and make sup­port needs ex­pli­cit.

Application: preparing a diagnostic note before an assignment

The de­liv­er­ables are the ini­tial note, the review rubric and the an­not­ated ver­sion after dis­cus­sion. Pro­gres­sion to a more autonom­ous task de­pends on the abil­ity to jus­ti­fy con­clu­sions and flag un­cer­tainty, not simply on com­plet­ing the learn­ing path. If an urgent as­sign­ment arises, the re­spons­ible man­ager ad­justs su­per­vi­sion rather than de­clar­ing on­board­ing com­plete. This case de­scribes no real client and prom­ises no re­duc­tion in time to become es­tab­lished in the role.

Key takeaway

Struc­tur­ing on­board­ing does not mean auto­mat­ing the entire in­teg­ra­tion pro­cess. Di­git­al re­sources can sup­port the trans­fer of in­form­a­tion, while ment­or­ing, team con­ver­sa­tions and human follow-up still need to be ex­pli­citly or­gan­ised.