A Drive Morning Checklist for One Clean Outcome

Set up one verdict per job before the upload, or the morning will not stay boring. On a Monday in May 2026 I watched a campus folder go up with sales profiles and testing profiles in the same batch. The marks came back looking sure of themselves. They were sure about the wrong opening, because the run had one description selected and every file was judged against it. Skip the setup and you spend the afternoon explaining numbers.

This is the checklist I want on the wall for that hour. It is not the whole product tour. It is the sequence that keeps each role’s outcome attachable to the role you think you opened.

How HireQwik should be set up for one verdict before invites go out

Set up one verdict per job by finishing five checks before any candidate is asked to book. The checks are the job, the label, the must-haves, the intake, and the sentence your team will use when a tier looks surprising.

Skip them and the failure is predictable. Coordinators send links because the placement office is waiting. By lunch you have outcomes computed on a rubric nobody in the room can describe. Then the argument is about students, when the argument should have been about setup.

A full campaign walkthrough already exists in setting up a first screening campaign. Use that when you are new to the screens. Use this page when you already know the clicks and you need the order that protects the outcome. The sibling page is how the three locks work. The page you are on is the morning sequence.

Do the checks in order. Later checks are useless if an earlier one is wrong. A perfect invite email on the wrong job description is still the wrong job.

Pick one HireQwik job description and name it so humans can tell

Start on the job, not on the folder.

Create or select one job description per requisition you will actually hire for. If sales and testing are both open, that is two jobs, even when one college sent one zip. If Pune and Bengaluru will be shortlisted by different people, consider two jobs as well. A shared job with a city column “for later” becomes a shared verdict, and later never comes.

Read the parsed title before you trust it. Two files from the same template can parse to the same role name, company and skills. HireQwik can add a suffix when titles collide: location, then upload date, then a short id. Unique titles stay clean. I still want a human label, because a suffix that is correct can still be opaque at 9 a.m. Set the label at upload or rename it when the campus changes the posting name. The inbox reads the live label, so a rename shows up on existing rows. Deleting is the wrong cleanup: a delete archives the job so interviews are not orphaned, and a guard tells you how many inbox rows and interviews point at it. Details sit in renaming a job mid-campaign and in what happens if you try to delete one.

What coordinators try, and what I stop, is “we will separate them in Excel after scoring.” You cannot separate a judgement that was never separate. The match score and the later call both assume the job you selected. Sort all you like. The assumption remains.

Write the label on a sticky note next to the person running the upload. If they cannot say the label without opening the file name, the label is not done.

Write HireQwik must-haves on that job before the first booking

Knockouts are how a must-have becomes one clear outcome instead of a polite, high-scoring conversation you then reject by hand.

Put only the conditions you would reject for early, often before the second minute ends. Work location, a required credential, a shift the person cannot do. Phrase them so a yes or no is audible. A vague knockout (“are you a culture fit?”) produces a quote nobody wants to defend. A concrete one (“this role is on site in Pune five days a week; can you do that?”) produces a reason.

HireQwik asks those disqualifiers first. A fail ends the call early and tags the verdict as a knockout, with the question id and a short extract of what the candidate said. That extract is trimmed, and it is checked against the transcript so a reject does not rest on words the person did not say. If you see a review flag instead of a clean reject, open the call before you act. Do not “fix” it by inviting them to a second job.

Teams that skip knockouts discover the requirement at debrief. The call scored Go. The person cannot relocate. Someone asks for a new link. That request is the subject of when a completed screen should not be rerun. The setup fix is dull and better: add the knockout now, for the next batch, and record a human No Go on the people already scored, with the reason in the note.

Glance at the bands before invites, too. Defaults are not a secret, but they are per scheme. On the weighted path, Strong Go starts at 8.0 out of 10, Go at 6.0, On Hold at 4.5. On the points path, the defaults sit higher: 9.0, 7.5 and 6.0 out of a 10-point total. Either set can be changed on the job. If your director thinks Go means “7 or above” and the job does not, you will spend the week translating. Say the bands in the standup once. Then stop putting stale numbers in the filter labels. We removed hardcoded ranges from our own Decision filter in July 2026 after they drifted. The filter matches the verdict word. Your slide should too.

Connect one HireQwik intake, then stop touching the source

One job accepts one resume source at a time.

If the college sent a sheet of links, connect that sheet to this job. New rows can be enriched, scored and mailed a self-schedule link without a coordinator pasting names. If the college sent files, use the shortlist upload: PDF or DOCX, against the job you already picked. Do not attach both. The product refuses the combination, and the refusal is correct. A typed cell and a parsed document are not the same object. Forcing them into one run hides which name was keyed and which name was read off a page. Run two jobs if you truly hold both piles, point them at the same role on purpose, and keep the exports labelled so a 70 from the link list is not compared blindly with a 70 from a document that failed to parse.

Before the first mail leaves, look at the confirmation that shows role, count and schedule. If the role name is the other opening, stop. Stopping a live campaign revokes join links that are still only scheduled or waiting. Calls already underway or already finished stay. Unused capacity for interviews that never started is returned to the original payer. I mention that so nobody is afraid to stop a wrong send. A wrong send that you “let finish” is how you collect a pile of outcomes for a job you did not mean.

The HR dashboard is where you confirm the job filter shows one label and the rows under it belong to that label. If a second label appears and you did not create it, you have a second job. Find out why before lunch.

Let each candidate finish one HireQwik call, then read one outcome

Invites are not the outcome. The outcome is what exists after a conversation, or an explicit status that says the conversation did not complete.

Candidates pick a slot. They may move that slot a few times inside a short window after the original booking. That is the same interview changing time, not a second exam. The exact cap is on the reschedule page linked from the campaign guide, not something to improvise in chat. Instant start, if you enable it, is also per job and off unless you opt in. Turn it on for one role as a trial if you want. Do not flip every job because one campus asked.

When the call ends, scoring runs on the transcript. You will see Awaiting eval briefly. That is not a reject. When the tier lands, it carries one of the four tier names, unless the session is Incomplete. Read the tier with the note. If you only read the pill, you will bulk-move people you cannot describe, which is the failure mode in bulk actions on a filtered list.

A hiring manager who will not log in still needs the same single outcome. Send the shared scorecard for the binding call. Do not attach the resume-match export and ask them to weigh it. A walkthrough of that page is in reading a scorecard.

Record the human call beside the HireQwik outcome, on purpose

The AI tier is a recommendation. The recruiter decision is a second field: same four labels, the reviewer’s name, the time, optional scores next to the model’s, and a note. Setting it does not rewrite the tier.

Use the field. On Hold is the pile that needs a person. No Go needs the reason read before it is closed. Strong Go can move, with a spot check so speed does not become blindness. Go needs one dimension you scored yourself if the role is sensitive. I do not want a quota of disagreements. I want it to be possible to disagree, and I want a blank human column to bother the team lead.

What fails on drive day is pasting the tier into the tracker and leaving HireQwik as the archive nobody opens. Six weeks later a director asks why a student was held. “The system said so” is not an answer you should practice. The name on the human field is the answer. If the name is missing, the review did not happen.

Notes should be one sentence a stranger can use: “Generic on the customer example, hold for a human screen,” or “Knockout on night shift, quote matches, close.” A note that says “good” is how the file rots.

If On Hold is ageing, set a date. Do not clear the pile by re-inviting. Re-inviting is a second outcome, and you already decided not to run those.

A HireQwik checklist you can paste to the drive channel

Copy this into Slack or Teams the evening before. Assign a name to each line. A line without a name is a wish.

1. Job: one description for this requisition. Owner confirms the label matches the campus email.
2. Split: any other role in the same folder is a different job. Owner lists those jobs or writes “none.”
3. Must-haves: knockouts written as questions you would reject on. Owner reads them aloud once.
4. Bands: the scheme for this job (weighted or points) stated in one sentence. Owner writes the Go line you will actually use.
5. Intake: sheet or files, not both. Owner names which.
6. Stop rule: if the confirmation names the wrong role, owner stops the campaign before anyone treats the links as real.
7. Outcome rule: one completed call, one tier. A reset only if the session did not complete. Owner points people at the redo rule rather than improvising.
8. Human rule: No Go reasons get read. On Hold gets a decision date. Nobody averages the resume match into the tier.

That is the whole operating system. It fits on a phone. If step 1 is wrong, do not heroically complete steps 5 through 8.

Review one middle row in public before any bulk move. If the room cannot explain the note, you are not ready to export.

What I tell founders who want to skip HireQwik setup and send invites

The invite is the easy part to show a stakeholder. The job is the part that makes the invite mean something.

Every shortcut I have seen collapses into the same afternoon: mixed files, a rubric nobody owns, two pills for one student, and a sheet where someone typed an average because the meeting was in ten minutes. The checklist is how you stay out of that afternoon. It is also how you stay inside what the product will actually enforce. HireQwik will reject a mixed intake. It will not reject a vague knockout you wrote yourself, and it will not reject a human who forwards the wrong pill. Those last two are still your job.

If you want to run the checklist against a requisition you are opening this month, send the description plus the file or link list through the demo form. We will stop at the first check that is not singular. That is a better use of the hour than watching a perfect call on a role you will never hire.