Two answers dominate this question and neither states the condition attached to it. Always include your references, says one. Never include them, says the other. What actually settles it is not a fact about your document, it is a fact about the employer's process: whether anyone has asked yet, and where they asked.
The request comes from a stage, not from the resume screen
Inside the software employers run a hiring process on, a reference check is a step with its own position in the pipeline. Greenhouse, to take one applicant tracking system whose documentation is public, wires reference checking in as a stage on the job's interview plan. The setup instructions for one of its reference checking integrations are to open the job's interview plan and add a reference request stage to it, and the request then becomes available on a candidate's profile once that candidate has been moved into the stage.
That ordering is the whole answer. Your resume is read at the top of the pipeline by someone deciding whether to start a conversation at all. References are gathered further down, at a named step, from a short list of people who are already in play. A reference block on the resume is answering a question that nobody in the process has reached yet, in front of a reader who has no use for three phone numbers.
The gap between those two moments is also long enough for the list to rot. A job title changes, a manager leaves, a work number stops being answered. The version of the list that matters is the one you send on the day it is requested, not the one you froze into a document in the spring.
What the block costs you on the page
Space on a resume is not neutral. Every line is competing with the lines that carry the match, and the lines a references block uses are usually prime ones near the bottom of a short document that a reader still reaches.
It is worth being concrete about what those lines earn. The scorer behind our own ATS resume checker settles each skill named in the job posting exactly once, as matched, partial or missing. A name, a job title and a phone number name no skill from the posting, so a references block cannot move that result in either direction. The same lines given over to a tool you actually use, or a responsibility the posting asks for, can. If you want to see the difference rather than take it on trust, run the file with the block and again without it, and compare the two reports.
This is the same trade as the one behind what belongs in the contact line, where a street address survives on resumes long after anything started reading it. It also pulls in the same direction as the length question: if you are already deciding how long a resume should be, a section with no reader at that stage is the easiest thing on the page to cut.
When the application does ask for them
Sometimes the field is right there in the form, and then the answer is simple: fill in the form. An application that asks for reference contacts in its own fields is collecting them in a structured place, and typing them a second time into the resume file adds nothing.
A posting that asks for references as a document wants a document, and that document is not your resume. Whitman College's career centre guidance is to put them on a separate page, with the contact information of three to five people who have agreed to recommend you. The same guidance says to use the same name and contact heading as the resume, and for each person to give their name, their title, the organisation, the address, a phone number and an email address. Adding how you know them, in a few words, saves the reader a guess.
Asking first is not a formality. The same guidance is blunt about it: ask the person's permission rather than assuming they will be willing, and give them a copy of your current resume, because many of them know you from one context only.
Pick the references the posting can use
A reference list benefits from the same treatment as the resume. Three names are not interchangeable: the useful one is the person who can speak to the work this particular posting is about. If the posting is weighted toward a system or a responsibility that one former manager saw and another never did, the first of them belongs on the list you send for this job.
Reading the posting for that is the same reading you did to decide what the resume leads with. Our resume keyword generator will pull the posting's own vocabulary out for you, and the question to carry into the list is simply which of your people have watched you do those things.
Leave the "available upon request" line off
The closing line that offers references on request is the one piece of this that is safe to delete without thinking about it. The reason is in the same guidance: because it is assumed that a candidate will provide references when they are asked, the line is unnecessary. It spends a line of a document that is short on lines in order to restate a default.
What it signals is worse than what it costs. A reader who has seen the line a thousand times reads it as filler, and filler at the bottom of a page is the last impression the document leaves.
Before you send either file
Cut the block, let the page close on your work, and check that the file still parses the way you expect. Run it through the ATS resume checker to confirm the sections you kept are being read and the terms from the posting are landing. If reclaiming those lines leaves you with room and nothing obvious to put in it, the gap the report shows is the brief: tailoring a resume to a job description covers what belongs in the space a references block was holding.