Nine Lines Every IT Request Note Should Include

Nine Lines Every IT Request Note Should Include

You know the feeling. Something in your tech stack needs outside hands, a freelancer, a small consultancy or a specialist for a week, and you fire off a quick message because you are busy. Two days later the replies are all over the place, and you are explaining the same background for the third time. Here is a friendlier way: nine lines, written once, that you can paste into any message. Think of it as a requirements note you carry around, ready for whenever the next job turns up.

The nine lines, one by one

1. The outcome, in plain words

Start with what will be different when the work is done. “Our backups restore in under an hour and someone other than me has done it.” Not “improve backups”. If it can be pictured, it can be delivered.

2. The date, with a reason

A date alone is a number. A date with a reason is information. “Before the audit on the 28th” tells the reader how firm it is and why. It also helps them tell you early if it is not realistic, which is a gift.

3. The budget range

Say it out loud, even if it feels awkward. A range you can truly spend, plus a line about what is in it: hours only, or tools and licences too. Readers cannot size the work without it, and they will not mind that you said it.

4. What you already have

List the stack in a few words: cloud provider, repository host, monitoring, who has access. This one line saves a surprising number of questions. Teams working on incident response, for instance, will find the groundwork for a plan in an overview of speeding up incident handling with smarter operations tooling, which helps you describe your current setup accurately.

5. What must not change

Production freezes, naming rules, a compliance duty, a tool the whole team loves. Put it here. Nothing frustrates a specialist more than discovering a hard limit in week three.

6. What you would like to avoid

Negative preferences are useful. “No new vendor accounts”, “no weekend work”, “please do not move our logs.” Short and friendly beats a long list of fears.

7. What done looks like

A test someone else can run. “A new engineer follows the steps in the document and succeeds on the first try.” This line prevents more arguments than any other, because it replaces opinions with a check.

8. Who decides and who answers

Name the person who approves work and the person who answers questions, even if they are the same person. Add roughly when each is reachable. If a manager must sign off, mention it now.

9. How you will reply

End by saying what happens next: “I will read replies on Friday and respond within two working days.” It sets a pace and stops mutual silence from turning into awkwardness.

Where to send your nine lines

First try your own circle: colleagues, past vendors, community groups. If you need to cast a wider net, one place to look is ProfessNow, an online marketplace where professionals list themselves under a trade and a town, so you can pick one and send a booking request with the nine lines pasted in. Technology and consulting are among the categories on the site, so there is a good chance of finding someone relevant in your area. The directory does the finding; your note does the explaining.

A tiny example in full

Here is a complete note, around a hundred and fifty words, for a small team that wants a monitoring clean-up.

“Hi! We run a handful of web services on one cloud account and want our alerts cleaned up so the right person is told at the right time. Please see the nine lines below. Outcome: each service has an alert owner and an on-call order written down. Date: two weeks from today, because a new hire starts then. Budget: a stated range including one handover call. Already have: a hosted code repository, a basic monitoring tool, three engineers. Must not change: the existing paging number. Avoid: new paid tools. Done means: a new engineer can follow the document to find who owns any alert. Decisions: I approve; my colleague answers questions. I will reply within two working days.”

Tips for keeping the list friendly

  • Use short sentences. If a line needs a semicolon, it is probably two lines.
  • Skip the history lesson. One sentence of background is enough; offer more on request.
  • Keep your tone human. A greeting and a thank-you cost nothing and set the mood.
  • Update the note. After each reply, fix whichever line caused a question.
  • Save it as a template. Next time, change three lines and you are ready.

Why nine, and why not more

The number is not magic. Nine is simply what remained after trimming a longer template down to the lines that, in practice, prompt the most useful replies. Earlier drafts had a separate line for communication tools, one for reporting format and one for risks. Those were folded into other lines or moved into the optional details section, because a note that grows past a screen stops getting read closely. If your own situation needs a tenth line, add it, but remove something else. The discipline of staying short forces you to decide what really matters in the first message.

Try the nine-line test on a past job too. Take a project that went sideways and fill in the lines as they should have been written at the start. You will usually find that one or two lines were blank, and that those blanks were exactly where the trouble began. It is a friendly, low-stakes way to see the value of the note.

When the job is bigger than nine lines

Some projects, such as a pipeline overhaul or a migration, need more than one page. That is fine. Keep the nine lines on top as a summary and attach details below. Readers can then skim the top, decide if the work suits them, and dig into the rest only if it does. If your project involves release automation, a long-form look at the moving parts of build and release pipelines offers extra vocabulary for the details section. And for broader planning of operations work, a practical roadmap for operations teams adopting smarter tooling may suggest what to put in the “already have” line.

One last nudge

Do not wait for the perfect version. Write the nine lines today, even badly, then read them as if you were the person receiving them. Cross out anything that would make you ask a question. Send it. By the second round of replies you will know which lines to improve, and your note will be sharper than most formal documents.

Finally, share the note with your own team before it goes out. A second pair of eyes catches the line that only makes sense to you, and it ensures everyone is asking for the same thing.