Skills dossiers from BoondManager: producing the client dossier without retyping

In short

The client dossier is built from the Boond record, then filed back into it. Retyping the same data in Word pulls the dossier away from the record, takes time, and sends a text nobody has reread.

• Three copy-paste sources keep coming back: an outdated Word CV, LinkedIn, and the last dossier you sent and then duplicated. None of them is maintained the way the Boond record is.
• Six steps are enough: an up-to-date record, the opportunity, a dossier base, adaptation, the consultant's review, and a return to Boond.
• Time is saved on the record. A dossier generated from a thin record stays a thin dossier.
• The salesperson keeps three decisions: which assignments to show, how to word the scope, and the consultant's review.
• Boond stays the source. The dossier is a view of that record, for one need and one date.

---

Why retyping sets in

Nobody chooses to retype. The client dossier format is not the record format, and the client wants the PDF the same day. Word gets opened.

Three copy-paste sources

1. The consultant's Word CV. It is often several months old, it misses the latest assignments, and it is longer than the client will read.
2. LinkedIn. People open it because the page looks more recent. They copy a job title, reword it, and nobody checks that it matches what Boond shows.
3. The last dossier sent. It gets duplicated, the name is swapped, two assignments change. The previous dossier's mistakes leave with the new one.

What retyping costs

The lost time is visible. The other costs show up when the client compares two documents.

A salesperson who prepares 6 dossiers a week and spends 45 minutes on each one retyping data already in Boond spends 4 hours 30 minutes a week on it. Over 46 weeks, that is about 200 hours a year, five full-time weeks for a single role. The figure comes from those assumptions, not from a market average.

---

What Boond already holds

An up-to-date resource record holds most of what a dossier needs. The exact fields depend on your instance. The use of them does not.

The dossier does not create new data. It selects, orders and rewords what is already on the record.

---

From the Boond record to the client dossier

Step 1. Clean the source record, once

This is where the time is saved. An up-to-date record turns the next dossier into an adaptation. A thin record turns it into a rewrite.

Start with the profiles you propose most often, and with those who will be available in the next two months. There is no point cleaning the whole database at once.

Step 2. Start from the opportunity

Open the Boond opportunity before you touch the dossier. Three questions are enough: who the client is, which skills are actually required, and what made the last profile fail on this kind of assignment.

Those three answers decide the order of the assignments. A dossier that starts from the consultant lists everything they can do. The client is looking for an answer to their need.

Step 3. Generate the dossier base from the record

The base takes the CV and the data already in Boond: profile, skills, experience, certifications, languages. No intermediate export, no Word file to reopen.

At this point the dossier is complete and still generic. It goes out after the adaptation, not before.

Step 4. Adapt it to the need

This part stays manual. It comes down to four moves:

• Put first the assignment closest to the client's need
• Reorder skills to match the request, keeping 6 to 8 lines
• Reword the scope of two or three key assignments
• Move the rare item (certification, clearance, language) to the top of the page

The same consultant, at two levels of detail:

On the Boond record: "Java developer, bank, 2021 to 2023. Java, Spring Boot, Kafka."

In the client dossier: "Rebuild of a bank's settlement engine. Led the Kafka migration with no service interruption, and settled the architecture with the compliance team. Stack: Java 17, Spring Boot 3, Kafka, PostgreSQL."

The record is one line of technologies. The dossier adds the scope and the result. That rewording is done once, then it stays on the record for the next sends.

Step 5. Have the consultant review it

The consultant rereads their own presentation before it goes out: assignments, figures, availability. It takes five minutes and avoids the mistake that costs an interview. If they complete their own record, you also get what only they know.

Step 6. Export, send, file back into Boond

The dossier goes to the client as a PDF, then comes back into Boond, attached to the record, with its version number. The next person who opens the record sees what was sent, to whom, and when.

Without that return, the dossier stays a file in a mailbox. On the next request, someone retypes.

---

What stays with the salesperson

The record can supply the list of assignments and skills. It does not choose what answers the need.

A dossier generated with no review carries the same risk as one retyped in a hurry. The review takes five minutes. Retyping takes forty-five.

---

Traps, from Boond to the dossier

Fixing the dossier and not the record

You spot a mistake, you fix it in the dossier, you send. The Boond record keeps the mistake. The next dossier picks it up. Every fix is made on the record.

Filling gaps from LinkedIn on every dossier

LinkedIn can fill a hole, once. If you go back on every send, the record was not enriched. Complete the record, then start from Boond for that consultant.

Forgetting anonymisation

A client dossier may have to hide end-client names or contact details. The rule is set once. You check that it applies before export.

Overwriting data you already cleaned

When two systems exchange data, one can overwrite the other. Decide in advance which data (skills, technical data) stays as it is in Boond.

---

Internal objections

"Our Boond records are too thin"

The problem sits upstream of the dossier, and it is fixed once. Take the ten profiles you propose most often, enrich their records, then measure the time of the next dossier. The rest of the database can wait.

"Every client wants their own format"

The format changes from one client to the next. The consultant's data stays the same. One template per client and one record per consultant removes the retyping.

"Consultants never update their CV"

They do when the update has a visible effect. When the consultant rereads their dossier before it goes out, they correct it at the moment the document leaves for the client.

"We have always done it in Word"

Time three dossiers, from the first click to send. In most teams, layout takes longer than choosing the content.

---

Checklist before sending a dossier that came from Boond

On the source record

1. Experience states the context, the scope and the result, not only the stack
2. Skills are up to date and limited to the most relevant ones
3. Certifications and languages are filled in
4. Availability is checked on the day you send

On the dossier

1. The dossier starts from the opportunity, not from a duplicated previous dossier
2. The assignment closest to the need comes first
3. The consultant has reread the final text
4. The PDF you sent is attached to the Boond record, with its version number

---

Frequently asked questions

Can you create a skills dossier from BoondManager without retyping?

Yes, if the resource record is filled in. The dossier reuses the profile, skills, experience, certifications and languages already in Boond. You still adapt the content to the client's need, have the consultant reread it, and file the result back into Boond.

Do you still need LinkedIn or the Word CV?

Only to fill a gap, once. If you go back on every dossier, the Boond record is not rich enough. Enrich it, then start from Boond for that consultant.

What do you do when the Boond record is incomplete?

Start from the attached CV to complete experience and skills, then have the consultant confirm the additions. Handle first the profiles you propose most often. Cleaning the whole database at once costs time for a small gain.

Where do you keep the final dossier?

In Boond, attached to the resource record, with a version number. The team sees what was sent, to which client, and on which date. The file does not live only in a mailbox.

How do you keep the dossier and the record from diverging?

Every fix is made on the Boond record, then the dossier is regenerated or adapted. A fix made only in the PDF comes back on the next dossier.

---

Where Boond stops and the dossier tool starts

BoondManager holds candidates, resources and opportunities. The client document, laid out and adapted to one request, is produced in a dossier tool connected to it.

Betterfolio is an official BoondManager partner. It creates the dossier from Boond data, then files the finished dossier back on the record, without going through Word. If BoondManager is down for maintenance, Betterfolio says so and lets you keep working.

Guarani describes the time saved between HR and sales. Clevermind describes adoption by the sales team, with the dossier staying in Boond. For the next step, how a shortlist is built is in Shortlist of 3 ESN profiles.

---

What to keep

The dossier sent to the client reuses the Boond record, adapted to one need. Retyping that record in Word creates a gap between the two documents.

Three habits:

• Enrich the record once, starting with the profiles you propose most often.
• Start from the opportunity, not from an old duplicated dossier.
• Fix the record, and attach every sent dossier back to Boond.

The time you save goes into choosing which assignments to put first.

If you already work in BoondManager, you can see how Betterfolio connects to it.