Quick answer
Before a printed campaign sends concentrated traffic to your website, tell your host the campaign date, list the pages and forms it depends on, and ask who to contact, what they monitor and what they will do if the site slows. Label traffic expectations as assumptions and never invent a number.
- Write down the campaign date and traffic assumptions, labelled as assumptions, and use past campaign data if you have it.
- List the pages, forms and tools the campaign depends on; a slow form can matter more than a slow page.
- Decide who at your business acts if the site slows, and do not assume the host will notice unreported problems.
A printed campaign can send concentrated traffic to a website at a known time. This article lists questions to ask your host about expected demand, dependencies and monitoring, without inventing capacity figures. It is written for businesses evaluating hosting arrangements and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A printed campaign could send concentrated traffic to a website at a known time.
What happens. A business is sending a printed flyer to many homes on a set date. It writes down the timing and its assumptions about extra visits, lists the pages and forms that must work, confirms who to contact at the host, asks what monitoring and response the host provides and plans who acts if the site is slow.
Expected demand
Write the campaign date and any assumptions about extra traffic, labelled as assumptions. Use the campaign timing and expected traffic assumptions fields. Do not invent a number. If you have past campaign data, use it, and say how it was measured.
Dependencies
List the pages, forms and tools the campaign depends on, such as a booking form or a payment page. Use the page dependencies field. A host can only help with what it knows about, and a slow form can be a bigger problem than a slow page.
Monitoring and response
Ask the host who to contact during the campaign, what they monitor and what they will do if the site slows. Use the host contact, monitoring and response fields. Agree who at your business decides what to do. Do not assume the host will notice a problem you have not told them about.
Campaign readiness briefing sheet
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Campaign timing | Expected traffic assumptions | Page dependencies | Host contact | Monitoring | Response |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Campaign timing | Expected traffic assumptions | Page dependencies | Host contact | Monitoring | Response |
|---|---|---|---|---|---|
| Print drop on a set date | Unknown; assumption recorded | Form and phone page | Host support contact | Uptime monitoring | Who acts if slow |
Working through the completed row
The example briefing sheet gives a print drop on a set date, an expected-traffic assumption recorded as unknown, the form and phone page as dependencies, a host support contact, uptime monitoring and a named person who acts if the site is slow.
Common mistakes
- Inventing a traffic number.
- Telling the host nothing about the campaign.
- Not deciding who acts.
Questions to settle before you rely on it
- When is the campaign and where does it send people?
- Which pages and forms matter most?
- Who acts if the site slows?
How you know it is complete
The sheet is complete when timing, assumptions, dependencies, contact, monitoring and response are written. Record who reviewed it and the date.
Where you may not have the answer
The host cannot give a figure for capacity. Ask what they can do, and plan to monitor the site yourself. The handoff, not a guess, is the correct next step.
Your next action
Complete the sheet before the campaign.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Secure web hosting arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Domains and hosting can be held in the client’s name or managed by Web Design Davao, depending on the client’s requirements. Either way, record who holds each login and who can recover it.
- Preventative website maintenance includes keeping plugins up to date and reviewing website code for known vulnerabilities. This reduces exposure to attack; it does not guarantee a site cannot be compromised. See website updates and uptime monitoring.
Frequently asked questions
What should I tell my host before a print campaign?
Tell them the campaign date and your assumptions about extra traffic, labelled as assumptions. List the pages and forms the campaign depends on, such as a booking form or payment page, because a host can only help with what it knows about.
What if my host cannot give a capacity figure?
Ask what they can do instead, and plan to monitor the site yourself. Do not invent a capacity or traffic number to fill the gap. Agree who contacts the host, what is monitored and who at your business decides what to do if the site slows.
Who should act if the website slows during the campaign?
Name a person at your business who decides what to do, and get a support contact at the host. Ask what monitoring and response the host provides. Do not assume the host will notice a problem you have not told them about.