What a report should contain
A report is intended to organise answers to agreed questions, such as availability, experience or preferred hours. The team should be able to review a short summary beside the applicant’s own words. Any example on this site uses fictional data.
The employer needs to see which details came from the applicant and which wording was summarised by software. If an answer is unclear, the right next step is to ask—not to guess.
A report, not an automated ranking
The report is meant to support a review, not produce a score or rank people. Selection should be tied to role requirements and owned by a responsible person. Vencur is not intended to trigger automatic rejections.
- Questions stay visible and tied to the role.
- Quotes make answers easier to verify.
- A person chooses whether to invite, follow up or decline.
Development and review
Reports are in pilot development. Pilot teams will help check whether the structure, language and level of detail work in practice. We will not replace their feedback with invented accuracy or success claims.
Frequently asked questions
Does the report give someone a suitability score?
No. It is intended to organise answers and make them checkable with quotes, not score or rank an applicant.
Can a report reject an applicant?
No. The hiring team reviews the information and makes the decision.
Are examples on this site real applications?
No. Product examples use fictional data and are labelled as examples.
Is the report available now?
Reports are in pilot development. Their structure and scope are being checked with pilot teams.