Priority Booking for Repeat Clients
Builds guide sites for a livingPublished July 22, 2026Last updated July 26, 202632 min read
- 15 CFR 700.13(d)(1) requires a rated order to be accepted or rejected in writing within fifteen working days, or ten at the higher priority level, with reasons for any rejection.
- 15 CFR 700.13(a) requires acceptance regardless of orders already accepted and forbids charging higher prices or imposing different terms for such orders.
- 15 CFR 700.13(b)(1) says a scheduling conflict with a previously accepted lower or unrated order is not a sufficient reason to reject.
- A priority offer needs three elements: named weeks, a closing date, and a stated consequence when the date passes.
- Priority should cost the client nothing and gain them nothing but the date, because a discount attached to it becomes the expectation.
- Hold two or three weeks rather than six, and apply one rule to a defined group all at once.
There is one place in federal law where a customer is entitled to jump another customer's place in a supplier's queue, and it works by forcing a written accept-or-reject inside a fixed number of days. Fifteen working days at the ordinary level, ten at the higher one.
None of that reaches a fishing guide, and the mechanism it uses is exactly what a priority booking offer needs and almost never has. A priority window that never closes is not a priority; it is an open-ended promise that eventually conflicts with a paying enquiry. The regulation solves that by requiring the supplier to answer in writing, in a stated period, with reasons if the answer is no. Below the rated order provisions are read from the regulation, then the priority offer itself. The regime described governs defence-related supply and has no application to a guided trip. Nothing here is legal advice. The pieces around it are gathered at the running the business hub.
| Offer | What happens |
|---|---|
| You get first refusal, let me know | Nothing, and the date goes stale |
| Your week is held until 15 January | An answer by a date |
| Held indefinitely as a favour | A conflict with a paying enquiry |
What does the regulation require?
An answer in writing, inside a stated number of working days.
Section 700.13(d)(1) of Title 15 provides that a person must accept or reject a rated order in writing, in hard copy or electronic format, within fifteen working days after receipt of an order at the ordinary priority level and within ten working days at the higher one.
It adds that if the order is rejected, the person must give reasons in writing or electronically for the rejection.
Paragraph (d)(2) shortens those periods dramatically for emergency preparedness orders carrying a stated statement, with minimums of six hours after receipt where the order responds to a hazard that has occurred, and twelve hours in the other case described.
So the whole regime turns on somebody being obliged to answer rather than on anybody's goodwill.
Part 700 is carried on the eCFR.
How the offer should reach the client is covered in the season announcement piece.
How does the priority itself work?
By requiring the queue to be reordered, not by asking nicely.
Section 700.13(a)(1) requires a person to accept every rated order received and to fill it regardless of any other rated or unrated orders already accepted, subject to the section's exceptions.
Paragraph (a)(2) forbids discriminating against such orders in any manner, including by charging higher prices or imposing different terms and conditions than for comparable unrated orders.
Section 700.14(b) then makes the scheduling consequence explicit: orders at the ordinary priority level must be given production preference over unrated orders where necessary to meet delivery dates, even if that requires diverting items being processed or ready for delivery against unrated orders.
Which is a genuinely radical instrument, and the feature worth borrowing is the pairing: a real priority, and a hard obligation to answer.
An offer with the first and not the second is what most guides run.
Why the rate should not move with it is covered in the discount scripts piece.
An open hold costs more than it looks. Hold six prime weeks for returning clients with no closing date and, if three of them drift into February before answering, you have carried three peak dates through the entire winter selling period. At $650 those are $1,950 of inventory withheld from every enquiry that arrived in December and January. Close the window on 15 January instead and you either have three bookings or three dates back with a full month of selling left. The offer costs nothing either way; the open-endedness costs the season.
What does mandatory rejection add?
A duty to say the earliest date you can actually do.
Section 700.13(b)(1) provides that a person shall not accept a rated order for delivery on a specific date if unable to fill it by that date, and must instead inform the customer of the earliest date on which delivery can be made and offer to accept the order on that basis.
It then closes off the obvious excuse: scheduling conflicts with previously accepted lower rated or unrated orders are not sufficient reason for rejection.
Paragraphs (b)(2) and (b)(3) apply the same structure between priority levels, in each case requiring the person to offer the earliest delivery date otherwise possible.
Translated to a guiding calendar, the discipline is that a no should always carry an alternative, and that a genuine no is about capacity rather than about inconvenience.
Which is a considerably higher standard than the usual reply that a week is unfortunately unavailable.
What the reply should look like is covered in the response time piece.
None of this governs a guiding business. The provisions described are part of a defence priorities and allocations regime and impose nothing on a fishing guide. They are quoted as the one worked example in federal law of a functioning priority queue with a deadline attached. Your own terms decide your position. Not legal advice.
What happens when two priorities collide?
There is a tie-break, and it is worth having one.
Section 700.14(c) addresses conflicting rated orders, providing for what happens where performance against accepted orders of equal priority status conflicts.
Section 700.13(b)(4) handles the same problem at acceptance, dealing with a person unable to fill all the orders of equal priority received on the same day.
The guiding analogue is two returning clients wanting the same week, which happens every year and is almost never planned for.
Which means deciding the tie-break in advance and stating it: longest-standing client, first to reply, or alternating years.
Any stated rule is better than the improvised one, because an improvised decision looks like favouritism to whoever loses.
Recording enough to apply it consistently is the client database piece.
What should the offer actually say?
Named weeks, a closing date, and what happens after it.
The three elements are the whole offer, and omitting any one of them produces the version that fails.
Script: Before I open the calendar I am holding the week of 20 June and the first week of July for people who fished with me this year. They are yours if you want them, and I will release anything unclaimed on 15 January.
Named weeks rather than a general first refusal, because a client cannot accept an abstraction.
A closing date rather than an open promise, because that is the whole mechanism the federal version relies on.
And a stated consequence, so releasing the date is something you said you would do rather than something you did to them.
What the wider announcement should carry is covered in the season announcement piece.
How long should the window be?
Long enough to be real, short enough to be a window.
Ten to fifteen working days is the range the federal version uses for an ordinary order, and it is a defensible model for a client deciding on a fishing trip.
Two weeks over Christmas is not the same as two weeks in October, so the calendar date matters more than the number of days.
Mid-January is a sensible closing date for a summer season, because it is after the holidays and before the general announcement.
What does not work is a window that ends when you happen to need the date, since a client who learns that will not treat the next one as real.
Holding to the stated date once, visibly, is what makes every subsequent offer work.
Why the announcement should follow it is covered in the winter email piece.
Should priority cost anything?
No, and the regulation is explicit about the parallel.
Paragraph (a)(2) forbids discriminating against a rated order by charging higher prices or imposing different terms and conditions than for comparable unrated orders.
Which is the mirror of the mistake a guide makes in the other direction: attaching a premium to a held date, or a discount to it, and thereby turning a relationship benefit into a price.
Priority should cost the client nothing and gain them nothing but the date, because that is what makes it a benefit you can offer indefinitely.
A discount attached to it becomes the expectation, and a premium attached to it becomes a reason to shop.
The date is the whole of the value, and it is enough.
Why non-price benefits outperform discounts is covered in the discount scripts piece.
Who should get it?
A defined group, stated, rather than whoever you remember.
Everybody who fished in the last season is the simplest rule and the easiest to apply consistently.
Everybody who has fished twice is a stronger rule commercially, because it rewards the behaviour you want rather than the most recent transaction.
What matters far more than which rule you pick is that it is a rule, since a priority offer extended by memory will miss somebody who notices.
It also has to be applied to the whole group at once, because a staggered offer means the person contacted last gets the leftovers and knows it.
One list, one message, one closing date.
How that list should be maintained is covered in the client database piece.
Does the offer need a written reply?
Yes, and requiring one is the point.
The federal version insists the answer be in writing, in hard copy or electronic format, and that a rejection carry reasons.
Which sounds bureaucratic and is doing real work: it converts an intention into a record, and it stops a soft yes being remembered differently by each side.
Applied to a priority week, the equivalent is asking for a reply rather than treating silence as interest, and confirming any acceptance in writing the same day.
A client who replied yes in a text and received a confirmation has a date; one who nodded at a takeout in September has an impression.
Neither of you benefits from the second version.
What that confirmation should contain is covered in the confirmation workflow piece.
What if a paying enquiry wants the held week?
Hold it, and tell them when it frees up.
This is the moment the whole programme is tested, and it is the moment most operations quietly fail it.
Which is why the closing date exists: a new enquiry can be told the week is held until the fifteenth and offered the date immediately after, or an alternative week now.
That is a true, specific and helpful answer, and it costs a booking only where the enquirer cannot wait ten days.
Releasing the week to them instead saves one booking and destroys the credibility of every priority offer you make afterwards.
The federal analogue is blunt on this: a scheduling conflict with a lower-priority order is expressly not a sufficient reason to reject the higher one.
How to answer that enquiry well is covered in the response time piece.
What if nobody takes them?
Release them on the date and say so.
Unclaimed weeks going back into general availability is the expected outcome for most of them, and it is not a failure.
Announcing the release is worth doing, because it tells the group the window was real and makes next year's offer credible.
It also creates a small useful urgency at the moment the general calendar opens, without any manufactured scarcity.
Message: The priority window closed yesterday and the week of 20 June is now open to everybody.
That is a true statement, it costs nothing, and it converts.
Why manufactured scarcity is the thing to avoid is covered in the packages piece.
What should be held back?
Fewer weeks than feels generous.
Holding your six best dates for a group of forty produces a queue and a lot of disappointment, and holding two produces a clean offer.
Which means the number should be set by how many are likely to be taken rather than by how many you would like to give away.
Two or three peak weeks, offered to a defined group with a closing date, is a manageable and credible programme.
Anything more and the tie-break problem dominates, and the offer starts costing you the general selling season.
Small and real beats large and vague in every version of this.
What the calendar arithmetic looks like is covered in the margin piece.
What breaks a priority offer?
The missing closing date, above all.
An open-ended hold, which is not a priority and which quietly withdraws inventory from the selling season.
A general first refusal rather than named weeks, which a client cannot accept because there is nothing to accept.
Extending it by memory rather than to a defined group, so somebody who should have been offered it finds out.
Attaching a discount or a premium, which converts a relationship benefit into a price and resets what everybody expects.
And breaking the stated closing date when a paying enquiry arrives, which destroys every future offer you make.
What the tradition version of this looks like is covered in the tradition piece.
Setting it up at the trailer is the end-of-trip ask piece.
Does it work on a thin calendar?
Better than it does on a full one, which is counterintuitive.
An operation turning work away in July gains little from holding weeks, because those weeks would have sold anyway and the offer costs real rate.
An operation with a half-full calendar gains a great deal, because the offer is the reason a client commits in January rather than deciding in April.
Which reverses the usual assumption that priority booking is something you earn the right to run once you are busy.
The scarcity does not have to be real for the offer to work, only the deadline, and a genuine deadline is available to anybody.
What it must not do is claim availability is limited when it is not, which is a claim rather than a mechanism.
Why an unsupportable scarcity claim is a problem is covered in the packages piece.
What should happen the following year?
Run it again, on the same dates, without being asked.
A priority offer made once is a gesture and made three years running is a tradition, and the second is worth several times the first.
Which means the closing date should be the same calendar date each year, so clients learn when to expect it and start watching for it.
Clients who took the offer last year should be told first and told that they are being told first, because the recognition is most of the value.
And somebody who declined last year should still receive it, since a decline is not a withdrawal from the group.
Consistency is what converts a marketing act into a relationship one.
How that becomes an annual habit is covered in the tradition piece.
What is the working offer?
Two or three named weeks, one list, one closing date, held.
Pick two or three peak weeks and a defined group, usually everybody who fished last season.
Send one message to the whole group at once, naming the weeks, saying they are held, and stating the date on which anything unclaimed is released.
Answer every reply in writing and quickly, and where a week is gone, name the nearest alternative rather than simply declining.
Decide the tie-break before you need it and state it if two people want the same week.
Release the rest on the stated date, say publicly that you have, and charge everybody the same rate throughout.
The regime described rests on authority at 50 U.S.C. 4511, with a parallel text on govinfo.
How the winter sequence should run around it is covered in the winter email piece.
How this was checked. The requirement that, subject to the section's exceptions, a person accept every rated order received and fill it regardless of any other rated or unrated orders already accepted comes from 15 CFR 700.13(a)(1), and the prohibition on discriminating against rated orders in any manner, such as by charging higher prices or imposing different terms and conditions than for comparable unrated orders, comes from paragraph (a)(2). The mandatory rejection provisions, under which a person shall not accept a rated order for delivery on a specific date if unable to fill it by that date but must inform the customer of the earliest date on which delivery can be made and offer to accept on that basis, together with the statement that scheduling conflicts with previously accepted lower rated or unrated orders are not sufficient reason for rejection, and the parallel provisions between priority levels each requiring an offer based on the earliest delivery date otherwise possible, come from paragraph (b). The treatment of a person unable to fill all rated orders of equal priority status received on the same day also appears in that paragraph. The customer notification requirements, under which a person must accept or reject a rated order in writing in hard copy or electronic format within fifteen working days after receipt of an order at the ordinary priority level and within ten working days at the higher level, and must give reasons in writing or electronically for any rejection, come from paragraph (d)(1); the shortened periods for emergency preparedness orders carrying the specified statement, with minimums of six hours after receipt where the order responds to a hazard that has occurred and twelve hours in the other case described, come from paragraph (d)(2). The preferential scheduling obligations, including that operations be scheduled in a timely manner to satisfy the delivery requirements of each rated order, that orders at the ordinary priority level be given production preference over unrated orders where necessary even if that requires diverting items being processed or ready for delivery, and the treatment of conflicting rated orders, come from 15 CFR 700.14. Part 700 was read on the Electronic Code of Federal Regulations on 26 July 2026. The regime forms part of a defence priorities and allocations system and imposes no obligation on a fishing guide; it is quoted as the one worked example in federal law of a functioning priority queue with a deadline attached. The statutory authority is cited without further reliance on its text, and all arithmetic uses stated illustrative figures.
If your booking calendar has more open weeks than you’d like, I’ll build you a free preview of your booking site before you pay a cent.
Get a free website previewHow a real priority queue is built, why the closing date is the mechanism, and what the offer should say
How does the federal priority queue work?
By obligation rather than goodwill. 15 CFR 700.13(a)(1) requires a person to accept every rated order received and fill it regardless of other orders already accepted, subject to exceptions, and paragraph (a)(2) forbids discriminating against such orders by charging higher prices or imposing different terms. 15 CFR 700.14(b) then requires production preference over unrated orders where necessary, even if that means diverting items already being processed.
What is the deadline?
15 CFR 700.13(d)(1) requires acceptance or rejection in writing, in hard copy or electronic format, within fifteen working days at the ordinary priority level and ten at the higher one, with reasons given in writing for any rejection. Paragraph (d)(2) shortens that dramatically for emergency preparedness orders carrying a specified statement, to minimums of six or twelve hours.
Does any of it apply to a guide?
No. The provisions form part of a defence priorities and allocations regime and impose nothing on a fishing guide. They are quoted as the one worked example in federal law of a functioning priority queue with a deadline attached, which is precisely the mechanism a priority booking offer needs and almost never has.
What should the offer say?
Named weeks, a closing date, and what happens after it. For example, that before opening the calendar you are holding two specific weeks for people who fished with you this year, that they are theirs if they want them, and that anything unclaimed is released on a stated date. A general first refusal fails because there is nothing to accept.
What if a paying enquiry wants a held week?
Hold it, and tell them when it frees up. Offer the date immediately after the closing date, or an alternative week now. That costs a booking only where the enquirer cannot wait. Releasing it instead saves one booking and destroys the credibility of every future offer. The federal analogue is blunt: a conflict with a lower-priority order is expressly not a sufficient reason to reject the higher one.
Should priority cost anything?
No. 15 CFR 700.13(a)(2) forbids charging higher prices or imposing different terms for a rated order, which is the mirror of the guide's mistake in the other direction. A discount attached to a held week becomes the expectation and a premium becomes a reason to shop. The date is the whole of the value and it is enough.
How many weeks should be held?
Two or three, not six. The number should be set by how many are likely to be taken rather than by how generous you want to appear. Holding six of your best dates for a group of forty produces a queue, a tie-break problem and a lot of disappointment, and it withdraws real inventory from the winter selling season.
Sources & methods
- 15 CFR part 700 on the Electronic Code of Federal Regulations, read for section 700.13 on acceptance and rejection of rated orders, covering mandatory acceptance regardless of other orders already accepted, the prohibition on discriminating by price or terms, the mandatory rejection provisions requiring a person unable to meet a specific date to inform the customer of the earliest date achievable and offer to accept on that basis, the statement that scheduling conflicts with previously accepted lower rated or unrated orders are not sufficient reason for rejection, the parallel provisions between priority levels, the treatment of equal-priority orders received on the same day, and the customer notification requirements imposing written acceptance or rejection within fifteen or ten working days with reasons for any rejection and the shortened emergency preparedness periods; and for section 700.14 on preferential scheduling, covering the obligation to schedule operations in a timely manner to satisfy each rated order, the requirement to give production preference over unrated orders even where that requires diverting items being processed or ready for delivery, and the treatment of conflicting rated orders. The regime forms part of a defence priorities and allocations system and imposes no obligation on a fishing guide.
- 50 U.S.C. 4511 at the Office of the Law Revision Counsel, cited as the statutory authority underlying the priorities and allocations regime described, without further reliance on its text.
- The Title 50 volume published on govinfo, used as an independent copy of the authorising provision cited above.
Every figure here is traced to a named public source and checked against it. Licensing, tax, and fee rules change. Verify your state’s current rules with the agency directly before you count on any number here.
Evan Knox
I build booking websites and run the ads and search for owner-run fishing guides, one operation per stretch of water. My first guide client, Bowman Fly Fishing, grew its revenue 4x in a year from that work. Field Notes is where I put the straight numbers on the business of guiding.
More field notes
Priority weeks work on a calendar worth holding.
I'm Evan. The offer converts when the dates are genuinely good. I build guides the booking site and run the ads behind it. Free preview before you pay a cent.