|
◆ THE COMPLETE GUIDE TO YOUR IRN ◆ Everything you ever wanted to know about the Identity Reference Number — and rather more besides |
This document is the single most complete explanation of how the Identifly identity-review process works and how you, personally, can obtain your very own Identity Reference Number (IRN). It has been prepared by the Office of Applicant Guidance so that no applicant need ever again ask a clerk “but what do I actually do?” — a question our clerks are, by long-standing internal policy, not permitted to answer directly.
Read it from beginning to end. Read it twice. Then take a queue ticket.
| 1. Introduction: how to read this guide |
If you have arrived here, it is almost certainly because you need an Identity Reference Number and have discovered — perhaps to your considerable surprise — that obtaining one is not a single button-press but a journey. That is by design. Identifly has issued Identity Reference Numbers since 1998, and in that time we have refined our process into a multi-department review of remarkable thoroughness. This guide exists to make that thoroughness navigable.
The guide is long. We make no apology for that. An IRN is a serious instrument, and the process that produces it touches several departments, each with its own forms, its own reference numbers, and its own idea of what constitutes a properly completed request. Rather than leave you to discover these things one rejection at a time, we have gathered them here in a single place. Where a section is relevant only to certain applicants, we say so; you may skim those parts. Where a section applies to everyone — particularly the chapter on consistency — we urge you to read every word.
A note on tone. You may find the Identifly process exacting. Many applicants do. The correct response to an exacting process is not frustration but preparation, and preparation is precisely what this guide offers. An applicant who has read this document in full will move through the departments with a calm that less-prepared applicants rarely achieve.
Throughout, we use the word “form” to mean one of the numbered documents you complete on this site (F01 through F34 and their siblings), and the word “department” to mean one of the seven functional areas through which your application passes. Reference numbers — the short codes that prove a step is complete — are explained at length in Chapter 5, and you should not worry if the term is unfamiliar for now.
One further word before we begin, on the spirit in which this guide is offered. Bureaucracy has a reputation, not always undeserved, for treating the citizen as an obstacle to the smooth running of the office. We have tried, in these pages, to do the opposite: to treat you as a collaborator who, given a clear map, is perfectly capable of finding the exit. Nothing in the Identifly process is arbitrary, even where it may at first appear so; every check has a reason, and this guide explains those reasons as it goes, on the theory that an applicant who understands why a rule exists is far more likely to satisfy it on the first attempt.
Finally, keep this guide open in a second window as you work. It is written to be consulted, not merely read once and forgotten. When a form surprises you, the relevant chapter here will very often explain the surprise before you have finished being surprised by it.
| 2. What an IRN actually is |
2.1 A definition
An Identity Reference Number, or IRN, is Identifly's official confirmation that a natural person has completed our departmental identity review and that the facts recorded about that person are internally consistent. In practical terms it is a short reference number of the form IRN-7K3P9Q2M4A-8F4A2C1D9E7B that you can present to any service willing to accept it as evidence that a real, reachable human being stands behind an application. It is compact enough to type, yet it is cryptographically verifiable: the party you present it to can confirm it is genuine without contacting Identifly at all.
The IRN does not describe you. It does not contain your name, your address, or your date of birth. It is a reference — a pointer to the fact that a review took place and concluded successfully. This is deliberate. It allows you to prove that you completed the review without disclosing, to every service that asks, the underlying details you provided to us.
2.2 What an IRN is not
It is equally important to understand what an IRN is not. An IRN is not a government-issued identity document. Identifly is a private company, not a registry, ministry, bureau or authority of any kind, and nothing we issue carries legal, evidentiary or official weight. An IRN is not a password, and it is not secret in the way a password is secret; it is a reference you are expected to share with services that ask for it. An IRN is not permanent proof of anything about the world; it merely records that, at the time of issuance, a review was completed.
2.3 Where IRNs are accepted
Within the small constellation of services that recognise our work, an IRN opens doors. GetVerified, an independent email-verification service, requires an IRN before it will issue its Verified-Email Token (VET). SealBox, a timestamping service, in turn requires a VET before it will create an account. In this way your IRN is frequently the very first link in a chain of trust that runs from Identifly, through GetVerified, and on to SealBox. We describe this chain, and the occasional knot in it, in Chapter 11.
| 3. Before you begin: what to prepare |
A successful application rests on three foundations. Assemble them before you take a queue ticket and the rest of the process will feel almost pleasant.
3.1 A single, consistent version of your identity
Decide, before you begin, exactly how you will write your name and your date of birth — and then write them that way every single time. This sounds trivial. It is the single most common reason applications stall. Our departments cross-check the answers you give on later forms against the answers you gave on earlier ones, and any discrepancy — a missing middle initial, a switched day and month, a nickname on one form and a legal name on another — will halt your progress until it is reconciled. Choose one canonical spelling and one date format now. Write them on a slip of paper if it helps. Consistency is the golden rule, and Chapter 6 is devoted entirely to it.
3.2 An email address you can actually read
Every form on this site asks for an email address, and every completed step sends a confirmation to it. Those confirmations contain your reference numbers. If you cannot read the mailbox, you cannot retrieve a reference you have mislaid, and you will find later forms harder than they need to be. Use an address you check. Do not use a disposable address that expires before you finish.
3.3 Patience, and a queue ticket
Finally, bring patience. The process is not designed to be fast; it is designed to be thorough, which is a different virtue. Take your queue ticket at Reception & Triage, keep the reference it gives you, and proceed one department at a time. Resist the urge to skip ahead. A form completed out of order is a form that will ask you for a reference you do not yet have.
A brief checklist may help. Before you take your ticket, confirm that: you have written down the exact spelling of your name; you have chosen a single format for your date of birth and written that down too; you have a mailbox open that you can read; and you have set aside enough uninterrupted time to reach at least the end of a department before you stop. None of these takes more than a minute to arrange, and together they eliminate the great majority of the difficulties that befall unprepared applicants. Preparation, here as elsewhere, is simply frustration paid in advance at a heavy discount.
| 4. The departmental model, department by department |
Your application is handled by seven departments. They operate in sequence, and each produces something the next one needs. Below we describe each in turn. You need not memorise this — the forms will guide you — but an applicant who understands the shape of the journey is far less likely to get lost within it.
4.0 Reception & Triage (Department 0)
Every application begins here. Reception registers your visit, records your consent to be processed, and captures your correspondence preferences — chiefly, the email address to which your confirmations will be sent. Reception also issues the first reference in your file, which subsequent departments use to recognise you. Do not underestimate Reception because it comes first; an error introduced here propagates through everything that follows.
4.1 Identity Pre-Verification (Department 1)
Pre-Verification establishes the provisional facts of your identity and confirms, at the appropriate level, that you exist. It is here that you first record your name and date of birth. Because these particulars will be cross-checked later, take special care to enter them in the canonical form you settled on in Chapter 3. Pre-Verification is forgiving of many things, but it is the origin of the record against which later consistency checks are made.
4.2 Cross-References (Department 2)
Cross-References verifies that the records held about you are internally consistent by cross-referencing them against one another. This is the department that catches the mismatched middle initial and the transposed date. It does not gather new facts so much as confirm that the facts already gathered agree with themselves. Applicants who prepared well breeze through Cross-References; applicants who did not learn, here, exactly why consistency matters.
4.3 Fees & Stamps (Department 3)
Fees & Stamps assesses processing fees and administers waivers, proofs and refunds. We state plainly, as we do everywhere: no payment is ever collected and no payment details are ever requested. The “fees” this department administers are administrative constructs — bookkeeping entries that must nonetheless be marked as settled (typically by claiming the standard waiver) before your file may proceed. You will leave this department owing nothing and having paid nothing.
4.4 Notarization (Department 4)
Notarization authorises and timestamps the notarization of your file, producing the certified seals required for final assembly. In effect, this department attaches a dated, signed marker to your application confirming that it reached this stage in good order. The seals it produces are among the references later forms will ask you to enter by hand.
4.5 Compliance & Disclaimers (Department 5)
Compliance & Disclaimers ensures you have read and acknowledged the various notices that govern the issuance of an IRN. Much of this department consists of confirming that you understand what an IRN is and is not — the very distinctions drawn in Chapter 2. Read the disclaimers rather than clicking past them; a later form may ask you to confirm a specific point they contain.
4.6 Final Assembly (Department 6)
Final Assembly gathers every reference your application has accumulated, confirms that nothing is missing, and issues your Identity Reference Number. The decisive form here is F34. When F34 accepts your file, your IRN is minted and emailed to you. Final Assembly is also where an alternative path opens for certain applicants, which we describe in Chapter 10.
| 5. Reference numbers, explained in full |
5.1 The anatomy of a reference number
A reference number looks like IRN-7K3P9Q2M4A-8F4A2C1D9E7B and has three parts separated by hyphens. The first part is a short prefix that tells you what kind of reference it is. The second is a random handle that acts as a lookup key. The third is a signature fragment — a slice of a genuine cryptographic signature that makes the whole reference tamper-evident. Because the signature travels inside the reference, the reference can be verified by the party you present it to without any need to contact us. This is why our references are short enough to type yet still trustworthy.
5.2 The prefix table
| Prefix | Issued by | Meaning |
| IRN | Identifly | Identity Reference Number — your final result. |
| VET | GetVerified | Verified-Email Token. |
| CSA | SealBox | SealBox customer-account reference. |
Within Identifly, most intermediate steps also issue references of their own, which later forms build upon. You will need to keep each of these and enter it by hand when a subsequent form asks for it, for the reason given in the next section.
5.3 You enter every reference by hand
Here is a fact that shapes how you should work through the departments: there is no wallet and no automatic carry-over. Every reference a form requires — whether it was issued moments ago by an earlier Identifly step or last week by another service — must be entered by you, by hand, into the field that asks for it. The system does not quietly remember references on your behalf and slot them into later forms. This is deliberate: it keeps you in possession of your own paperwork and leaves no doubt about which reference was used where. The practical consequence is simple — keep every reference you are issued, because you will be asked to type it in again later.
5.4 How a form asks for a reference
Whenever a form needs a reference, it presents a clearly labelled field asking for exactly that reference — for instance, “Verified-Email Token (VET)” or the reference produced by an earlier step — together, where relevant, with a link to the service or form that issues it. Enter the reference in that field precisely as it was given to you, including its prefix and both hyphens. A form will not process until every reference it names has been supplied, and it will tell you, in plain language, which one is missing if you try to submit without it.
5.5 Retrieving a reference you have mislaid
Every step that issues a reference also emails it to you. If you lose a reference, the fastest way to recover it is to look in your inbox for the confirmation message from the step that produced it. This is precisely why Chapter 3 insists on an email address you can actually read. Keep those confirmations until your IRN is safely in hand.
| 6. The golden rule of consistency |
If you remember only one chapter of this guide, remember this one. More applications stall on consistency than on any other cause combined.
6.1 Which fields are cross-checked
Certain particulars — most importantly your full name and your date of birth — are requested on more than one form. Our departments compare each new answer against the first answer you gave, and they expect the two to be identical. The comparison is not fooled by trivial-looking differences: “Alex Moreno” and “Alex J. Moreno” are, to Cross-References, two different people, and an application that claims to be both will be held until the contradiction is resolved.
6.2 Common consistency mistakes
The classic errors are these: adding or dropping a middle name or initial between forms; switching the order of day and month in a date; using a nickname on one form and a legal name on another; introducing or removing accents, hyphens or spaces in a surname; and correcting a typo on a later form without realising it now disagrees with an earlier one. Each of these is easy to make and easy to avoid. The remedy is the discipline recommended in Chapter 3: settle on one canonical form of each particular before you begin, and never deviate.
6.3 How to correct a genuine mismatch
If you are stopped for an inconsistency, the form will tell you exactly which particular disagrees and what it disagrees with — for example, that the name you just entered does not match the name recorded earlier. Read the message, decide which version is correct, and re-enter the answer so that it matches your original. Because a form now preserves everything you typed when it reports an error, you will not have to re-enter the rest of the form from scratch; simply fix the one field the message identifies and submit again.
A subtle point deserves emphasis here, because it catches even careful applicants. The record is set by your first answer, not your best answer. If you mistype your name on an early form and only notice later, the consistency check will treat the mistyped version as canonical and flag your correct later entry as the discrepancy. When this happens, the message will make the situation clear by quoting both values; you then have a choice, namely to make your later forms agree with the original entry, or to correct the record at its source if the form that set it is still available to you. Either way, the guiding principle is the same: all forms must ultimately tell one consistent story about who you are. The process does not object to that story being simple or humble; it objects only to it being contradictory.
| 7. A step-by-step walk-through of the full review |
This chapter narrates the ordinary path from an empty file to a freshly issued IRN. Your exact sequence of forms may vary, but the shape is always the same.
- Take a ticket at Reception & Triage. Open the Departments page, enter Reception, and complete the intake form. Provide the email address you will use throughout. You will receive your first reference by email; keep it.
- Establish your identity in Pre-Verification. Record your name and date of birth in the canonical form you chose. This is the origin of your record.
- Pass Cross-References. Answer the repeated questions exactly as you did before. If everything agrees, you proceed without incident.
- Settle your fees. In Fees & Stamps, claim the standard waiver. No money changes hands. Your file is marked as settled.
- Have your file notarized. Notarization attaches the dated seals that Final Assembly will look for.
- Acknowledge the disclaimers. In Compliance, confirm that you have read and understood the notices governing your IRN.
- Submit F34 in Final Assembly. With every prerequisite reference entered, F34 accepts your application and issues your IRN. It arrives by email. You are done.
At each step, keep the reference the form issues you and enter it by hand on the next form that asks for it. Every reference field a form shows you must be filled in; nothing is carried over on your behalf.
7.1 What a well-prepared sitting looks like
It is worth painting a picture of the ideal case, because it is more achievable than nervous applicants tend to believe. A well-prepared applicant sits down with three things: the canonical spelling of their name written out in front of them, their date of birth in a single agreed format, and their mailbox open in a second tab. They begin at Reception and do not skip. When a confirmation email arrives, they glance at it to confirm the step succeeded and carry on. They enter their name identically each time it is asked, because they are reading it off the same slip of paper rather than retyping it from memory. When they reach Final Assembly, every prerequisite is on file, F34 accepts the application without complaint, and the IRN arrives moments later. The whole affair takes a single unhurried sitting. This is not a fantasy; it is simply what preparation produces.
7.2 Where applicants most often stumble
The contrasting picture is equally instructive. The unprepared applicant retypes their name from memory on each form and, on the fourth form, adds a middle initial they omitted on the first. They mislay the reference an earlier step issued them and cannot supply it when the next form asks. They skip ahead to a later, more interesting-looking form and are told it needs a reference they have not yet earned. None of these are catastrophes — each has a remedy described elsewhere in this guide — but together they turn a single sitting into a week of small frustrations. Every one of them is avoided by the preparation described in Chapter 3. We repeat the point because it is the most valuable point in the guide.
7.3 A word on doing things in order
The departments are arranged in sequence for a reason: each produces something the next one needs. Completing them in order means that, by the time a form asks for a reference an earlier step produces, you already hold it and can enter it. Completing them out of order means the opposite, and the resulting “missing reference” messages, while perfectly accurate, are dispiriting. If you take one procedural lesson from this guide, let it be this: start at Reception, and move forward one department at a time.
| 8. Verification checks and anti-abuse measures |
To protect the queue from automated abuse, most forms end with a short verification check: a four-digit code you must retype. The submit button remains disabled until you have entered the code, which is our gentle way of confirming that a human is at the keyboard. The code is not a reference number and has no meaning beyond the form you are on; a fresh code is issued each time a form is displayed. If your submission is rejected for any other reason and the form reloads, simply read the new code and enter it again.
These measures are not obstacles placed in your way for their own sake. They exist so that the applicants ahead of you in the queue — and you, when you are ahead of someone else — are not delayed by machines submitting thousands of applications a second. A moment spent on a verification code is a moment invested in everyone's fair turn.
| 9. Email confirmations and record-keeping |
Every meaningful step in your application produces an email. That email confirms the step is complete and, crucially, contains the reference number the step issued. Treat these messages as your file. If a later form asks you for a reference — which, on this site, happens only for references issued by another service — the confirmation email is where you will find the value to paste.
We recommend creating a folder in your mailbox for your Identifly correspondence and moving each confirmation into it as it arrives. When your IRN is finally issued, its confirmation email is the one to guard most carefully: it is the message you will forward, or from which you will copy your IRN, whenever another service asks you to prove that your identity review is complete.
| 10. The three paths to a completed application |
There is more than one way to arrive at a completed application. Most applicants take the first; some are eligible for the second; the third applies once you already hold an IRN.
10.1 The full review
The path described throughout this guide: begin at Reception, proceed through every department in order, and let Final Assembly issue your IRN once every prerequisite reference has been entered. It is the longest path and the one available to everyone. If in doubt, take it.
10.2 The recognised SealBox account
At Final Assembly, form F34 will accept a valid SealBox CS-ACCOUNT reference in lieu of certain in-house steps. This is a formal courtesy extended between our services: an applicant who has already demonstrated, to SealBox, that they hold a genuine account has thereby demonstrated something Identifly is willing to recognise. If you hold such a reference, F34 will present a field in which to enter it, together with a link to SealBox should you need to obtain one.
10.3 Using an IRN you already hold
Once your IRN has been issued, you rarely need to repeat the review. Your IRN is itself the proof, and you present it directly to whichever service asks for it — most commonly GetVerified, when you seek a Verified-Email Token. Keep your IRN and you keep the benefit of the entire process without repeating it.
| 11. Working with GetVerified and SealBox |
11.1 The chain of trust — and its occasional knot
The three services fit together in a chain. Identifly issues an IRN. GetVerified, on seeing a valid IRN, issues a Verified-Email Token. SealBox, on seeing a valid VET, creates an account and issues its own reference. Followed in this order, the chain is straightforward. The knot appears only if you attempt the services out of order — for instance, seeking a SealBox account before you hold a VET, or a VET before you hold an IRN. The remedy is simply to begin at the beginning: obtain your IRN here, first.
11.2 Courtesy tokens and breaking a deadlock
Occasionally an applicant finds themselves genuinely unable to obtain a prerequisite because of a circular dependency between services. Each service anticipates this. Where you can show that a genuine attempt is on file, a support desk may issue a one-time courtesy token that breaks the loop — GetVerified, for example, can issue a courtesy VET to an applicant who is otherwise stuck. These courtesies are the pressure-release valves of the system, and they exist precisely so that no well-intentioned applicant is trapped forever between two doors that each demand the key held by the other.
11.3 Why the services trust one another
It is reasonable to ask why GetVerified should trust an Identifly IRN at all, or why Identifly should, in turn, recognise a SealBox account. The answer lies in the reference numbers themselves. Because each reference carries a genuine cryptographic signature, a service that receives one can confirm it was really issued by the service that claims to have issued it, without any need for the two to be connected or to consult one another in real time. Trust, in this arrangement, is not a matter of one company vouching for another over the telephone; it is a property of the references, checkable by anyone who holds them. This is what allows three independent services to co-operate without merging, and it is what makes your IRN useful beyond the walls of Identifly.
11.4 Presenting your IRN to another service
When the time comes to present your IRN — most commonly to GetVerified — you will find a clearly labelled field asking for exactly that reference. Copy your IRN from the confirmation email precisely as it appears, including its prefix and both hyphens, and paste it into the field. Do not add spaces, do not omit characters, and do not attempt to “tidy” it; the reference is verified exactly as issued, and even a single altered character will cause it to be rejected as invalid. Presented correctly, it is accepted at once.
| 12. Troubleshooting and frequently asked questions |
Q. A form says a reference is missing, but I completed the earlier step. What
went wrong?
Most often, the earlier step was completed under a different session — for
example, in a different browser, or after cookies were cleared. References earned on this site are
tied to your session. Complete the steps in one continuous session where possible, and keep the
confirmation emails so you can re-supply a reference if needed.
Q. The form rejected my name as inconsistent, but it looks the same to
me.
Look closely for a middle initial, an accent, a hyphen, or a difference in spacing. The
comparison is exact. The rejection message quotes both the value you entered and the value on file;
compare them character by character.
Q. I lost a reference number. Where do I find it?
In the confirmation
email sent by the step that issued it. Search your mailbox for messages from the relevant
service.
Q. Do I have to pay anything?
No. No payment is ever collected and no
payment details are ever requested. Any “fee” is an administrative construct settled by
claiming a waiver.
Q. Will I lose my progress if a form is rejected?
No. When a form reports
an error it preserves everything you entered, so you need only correct the specific problem it
identifies and submit again.
Q. How long does the whole process take?
That depends on you. An
applicant who has read this guide and prepared a consistent identity can move through the departments
in a single sitting. An applicant who improvises will take longer, chiefly because of consistency
rejections.
Q. Is my IRN secret?
No. It is a reference you are expected to share with
services that ask for it. It reveals none of your underlying details, so sharing it is safe.
Q. Can I have more than one IRN?
You have no need of more than one. A
single IRN serves for every service that accepts one.
Q. Which references do I need to keep?
All of them. Because nothing is
carried over automatically, every reference you are issued — whether from an Identifly step, your
VET from GetVerified, or a SealBox reference — is one you may be asked to type into a later form
by hand. Keep each confirmation email until your IRN is safely in hand.
Q. A form is showing me a field for a reference I have never heard of. What do I
do?
Read the small print beneath the field. Every reference field on this site names the kind
of reference it wants, explains where that reference comes from, and links to the service that issues
it. Follow the link, obtain the reference, and return to enter it. The form has told you everything
you need; it simply asks that you read it.
Q. I completed everything but no IRN arrived by email. Why?
Check that
the email address you entered is correct and that the message has not been filtered into a spam or
promotions folder. The IRN is issued the moment Final Assembly's F34 accepts your file; if F34
accepted it, the email was sent. If the address was mistyped, complete F34 again with the correct
address.
Q. Is the Identifly process really this thorough, or is the thoroughness the
point?
A fair question, and one we answer honestly in Chapter 14. For now: the checks are
real, the references are genuine cryptographic artefacts, and the consistency rules do exactly what
they claim. Whether a process needs to be quite this thorough to confirm that a person exists is a
philosophical matter on which reasonable people, and unreasonable bureaucracies, may differ.
Q. Can I pause and come back later?
You can. Nothing depends on staying in
the same browser, because no references are stored for you between forms. Simply keep your
confirmation emails, which contain every reference you have been issued, and enter them by hand when
you return and a form asks for them.
Q. I received a rejection I do not understand. What should I do?
Read the
message slowly; our rejection messages are written to be specific rather than cryptic. They name the
field at fault and, where relevant, quote both the value you supplied and the value on file. Nine
rejections in ten are resolved simply by reading the message and correcting the one thing it
mentions.
| 13. Glossary of terms |
| Term | Meaning |
| IRN | Identity Reference Number — Identifly's confirmation that your identity review is complete. |
| VET | Verified-Email Token — GetVerified's confirmation that an email address has been checked against an IRN. |
| CS-ACCOUNT / CSA | A SealBox customer-account reference. |
| Reference number | A short, verifiable code (prefix-handle-signature) proving that a step is complete. |
| Department | One of the seven functional areas your application passes through. |
| Form | A numbered document you complete on this site. |
| Consistency check | A comparison of a repeated answer against the first answer you gave. |
| Waiver | The mechanism by which a notional fee is settled without payment. |
| Courtesy token | A one-time reference issued by a support desk to break a circular dependency. |
| 14. A closing note on the nature of this service |
We end where honesty requires us to. Identifly, together with its sibling services GetVerified and SealBox, forms a single interactive experience — a work of parody inspired by the bureaucratic labyrinth of Asterix's “The Place That Sends You Mad” (Passierschein A38). No real accounts, identities, permits or legal instruments are created; nothing issued here has any legal, evidentiary or official value; no fee is ever charged and no payment details are ever requested; and this service is not affiliated with any government, agency or real organisation the brand names may evoke. The reference numbers are genuine cryptographic artefacts, produced for demonstration only.
We say all of this plainly because the joke, such as it is, works best when nobody is deceived. The humour lies not in tricking you into believing that a real permit is at stake, but in the recognition — rueful, we hope, rather than bitter — that real bureaucracies do at times behave exactly like this: demanding a reference to obtain the reference required to obtain the first reference, and treating the mildest inconsistency as grounds for beginning again. If you have ever stood in such a queue, you will find the departments of Identifly oddly familiar, and if you have not, consider this guide a gentle inoculation against the day you do.
And yet, beneath the parody, the mechanics are real and worth understanding. The reference numbers really are signed; the consistency checks really do compare your answers; the cross-service dependencies really are resolvable by anyone willing to read the labels and follow the links. In that sense this guide has taught you something transferable: how to move calmly through a system that assumes you will panic, how to read a rejection message for the single fact it is trying to convey, and how to prepare so thoroughly that thoroughness ceases to be an obstacle. Those habits outlast any single form. Carry them with you, and no labyrinth — ours or anyone else's — will hold you for long.
If, having read all of this, you are ready to begin, we wish you a calm passage through the departments and a swiftly issued number at the end of it.