Submittals connect a candidate and job through client review, interview, offer, and outcome stages. InferOwl limits transitions and may require a reason or completed package before accepting a status change.
Manage a submittal
- 01
Create the submittal
Choose the candidate and job, confirm the intended client workflow, and create the record with Manage submittals access.
- 02
Complete the submission package
If the job requires a submission package, resolve missing documents or fields before moving to Submitted to client.
- 03
Update status
Open the submittal drawer and choose an allowed next status. Add a reason when moving to a negative outcome; conditional offer acceptance requires a note.
- 04
Track an interview
Schedule the interview, then record pass, fail, or no-show outcomes when known.
- 05
Create and resolve the offer
Enter offer dates, rate, and gross-profit information as applicable. Record acceptance or decline and the required reason or condition note.
- 06
Review the portfolio
Use status, client, job, and submitted-after filters to review work. Counts and funnel stages follow the selected job when one is chosen. CSV export uses the active filters and should be downloaded only when authorized.
Record the actual outcome
Statuses drive shared reporting. Update them only after the real client, candidate, interview, or offer event occurs, and use the configured reason rather than a generic note when one is required.
Confirm the candidate, job, and client relationship
Open the underlying records before creating the submittal. Check that the candidate is being considered for the intended job and that the job belongs to the correct client. Similar requisitions can have different facility requirements, so use the actual job context rather than a title alone.
Confirm the candidate's relevant interest and the agency's authorization to submit. A matching recommendation is useful review input, but it does not establish candidate consent or a client decision. Resolve material uncertainty about dates, requirements, or the submission package with the responsible recruiter or manager.
Prepare the package for its destination
Review the documents and fields required for this job's submission. Use current, appropriate files and confirm that they belong to the correct candidate. A package that is complete for one client may still be incomplete for another. Read any validation message and resolve the named requirement through the appropriate document or candidate workflow.
Keep package preparation distinct from sending or recording submission. Do not move to Submitted to client merely because the internal review is finished. Record the actual event and follow the agency's approval process for anything that will be shared outside the team.
Keep client responses and recruiting outcomes precise
Record a status supported by the latest client or candidate event. A request for more information, an interview request, and an offer intention describe different stages of review. Include the relevant context when recording a response so the next recruiter can identify what still needs to happen.
For negative outcomes, select the applicable reason and add useful job-related context when required. Avoid a generic note that hides whether the issue concerned pay, credentials, timing, or another specific requirement. A conditional acceptance also needs its condition recorded accurately; do not summarize it as an unconditional acceptance.
Review interviews and offers in context
Check the time, timezone, participants, and meeting details when scheduling an interview from a submittal. Update the outcome after the real event. For an offer, verify the approved dates and financial information with the responsible owner before recording or communicating terms.
When reviewing the portfolio, check the active filters before interpreting totals or exporting a CSV. Job-specific counts and an agency-wide view cover different populations. Keep exports within the approved audience and storage process. If a status update fails, reopen the submittal and inspect the saved state before retrying; include the attempted transition and redacted error in a support request when needed.
Troubleshooting
The intended status is unavailable.
Likely cause: The current status does not allow that transition.
Choose an allowed next status and complete intervening workflow steps before trying again.
Submitted to client is blocked.
Likely cause: The job requires a complete submission package and one or more items are missing.
Open the candidate or submittal package, complete the named items, then retry the transition.
A decline, rejection, or conditional acceptance does not save.
Likely cause: The selected outcome requires a reason or condition note.
Choose the applicable reason or add the required note, then save again.