Sites with End Dates: Running a Project Estate from One Workspace
Most of the websites an office like this runs will not exist in four years, and that is the plan rather than an oversight. A workspace built for a project estate has to answer a question a brand portfolio never asks: not only how each property is doing, but what will still be provable about it once it closes.
The inventory is longer than the organisation chart suggests. An association runs its own site, plus one site for each of two EU-funded projects that end when the grant agreements end, plus a campaign site for a legislative file that will be settled within eighteen months, plus a members-only portal almost nobody outside the membership ever sees. And there is a conference site rebuilt every year on a domain carrying the year in it, so the estate grows by one property each autumn.
Six properties, one communications officer, a shared trainee, and one property with an indefinite life. That is not a portfolio but a set of deliverables with a calendar attached, and the questions that matter are administrative before they are editorial: what happens to a site when its funding period closes, who may still touch it afterwards, and whether the evidence of what it achieved survives to reach the final report to the funder.
An inventory in which most entries have an end date
Write the estate down before configuring anything. Four columns are enough, and the last two are the ones normally missing: how long the property is meant to live, and what has to remain demonstrable once it stops being updated.
| Property | Expected life | Who may change it | What must outlive it |
|---|---|---|---|
| The association's own site | Indefinite | In-house communications | Nothing special; it carries its own record |
| Project site, grant A | To the end of the grant | Communications, project officer | Reach figures for the final report |
| Project site, grant B | To the end of the grant | Communications, a partner's staff | The same, plus each partner's contribution |
| Campaign site, one file | Until the file is decided | Communications, policy lead | A dated record of the audience reached |
| Members-only portal | Indefinite, deliberately quiet | Membership team | Who held access, and when |
| Conference site, current year | One year, then frozen | Events, then nobody | The attendance case for next year |
The fourth column decides the configuration. Where it says "nothing special", light monitoring is enough. Where it names a document a funding body will read, the property needs a measurement routine from its first day online: a figure cannot be reconstructed from a frozen site.
Registering an estate without inheriting its confusion
Each property becomes its own project, with its own analytics, campaign state and feed. That sounds obvious until you notice how often the alternative is chosen: one project standing in for everything.
Two structural details matter more here than for a business with one website. Google properties attach in linked account groups, so a project site verified under a partner's account and a campaign site verified under yours sit in one workspace without anyone handing over a password. And background workers refresh the data, which turns a Monday glance across six properties into a two-minute task.
- One project per domain, year domains included. Separate histories; merging them destroys the year-on-year comparison the events team needs.
- Attach the Google property at registration. Data accumulates from connection onwards; a project connected in month nine has nothing for months one to eight.
- Name projects the way the grant names them. With the funder's reference in the name, whoever compiles the final report finds it without asking you.
Campaign work, unlike the workspace itself, is charged per domain. Reading a property across the analytics views is one thing; running an active campaign on it is a separate decision — in practice two or three properties, not six.
Where an active campaign earns its monthly line
For the properties whose visibility somebody will be asked about in writing.
- The permanent site usually earns it. It outlives every project and it is what a tender longlist lands on, so work there compounds instead of expiring.
- A campaign site earns it for a fixed window. Eighteen months at the automated tier is a defensible line. The property closes, and so does the line.
- Project sites often do not. Where the grant funds dissemination, the cost may belong in the project budget rather than the association's. Settle that before the audit.
- Reviewed output where text carries weight. The higher tier adds review before on-site changes go live — the only version usable where nothing may appear unread.
Granting takes a minute; withdrawing needs a date in a diary
Staff here rotate. Seconded national experts arrive for two years. Project officers hold contracts that end with the action. A member federation lends a communications officer for a campaign. Every arrival produces an access grant; almost no departure produces a withdrawal unless somebody wrote the date down.
The mechanism is deliberately narrow. A property is shared with one registered email address, and the recipient sees that property and nothing else — not the estate, not the tags, not the other projects' figures. Grants already made can be listed and withdrawn. The narrowness makes the estate safe to share; the listing makes it auditable.
The seconded expert
Arrives with an end date written into the secondment agreement — the easiest withdrawal trigger you will get.
- Grant on arrival, diarise the end
- Needs one project, not six
The partner's project officer
Sits in another organisation and needs the site their institution co-signed for, on their own account.
- One property, one address
- Withdrawal belongs to close-out
The external agency
Runs one microsite for a season and needs no line of sight to the campaign or the members' portal.
- Scoped to the single microsite
- Withdraw at final invoice
The policy lead
Wants the campaign site's numbers during the file, and stops needing them the week of the vote.
- Access follows the file
- Review at each milestone
Tags that answer the two questions you are actually asked
A tag is a label attached to a property, and once attached it narrows every view to the properties carrying it. That makes tags cheap to create and easy to overdo. Six properties need no taxonomy; they need two axes, chosen because two questions recur.
The first comes from finance and the funder: which properties sit on which budget line. The second comes from you and your successor: which are live, which are winding down, which are frozen.
- Axis one: what pays for it. The grant reference, the association's own budget, or the campaign fund — what filters the estate down to exactly what one funder may ask about.
- Axis two: where it is in its life. Live, closing, frozen. Three values, and a property moves through them in one direction only.
- Set the axes before the estate grows. Tagging six properties takes an afternoon. Tagging twenty retrospectively is a project nobody funds.
- Resist the third axis. Language and audience feel like tags but behave like report columns. As a third dimension they make every filtered view ambiguous.
A thousand URLs a day, shared by everything you own
The indexing budget belongs to the account, not to the property. One thousand URLs a day covers the whole estate, and that arithmetic becomes visible in the week when two properties need it at once — which, on a calendar of grant deadlines and an annual conference, is often.
The submission budget and what fits inside it
For the weeks when a relaunch and a publication push collide.
- A daily ceiling on submissions, not on crawling. A thousand URLs a day is what you may hand over; what search engines then do follows their own timetable.
- Batches are large, the day is not. Ten thousand URLs go in as one batch, which can hold several days of budget and drains at the daily rate.
- Sitemaps are parsed three levels deep. An index file pointing at index files is followed down three levels, up to a thousand sitemaps per job.
- Two jobs run at once, twenty may wait. A scheduling constraint worth knowing before you queue the whole estate on one morning.
- Submission goes out over IndexNow. The per-URL log records the bot visit with a timestamp, the status and any error, beside counters for submitted, found and failed.
The collision is worth planning on paper, because the resolution is only an order of service. A rebuilt conference site wants its structure discovered after launch; a project at its dissemination deadline wants new pages found before the cut-off. One has to go first.
| Day | Property | What goes in | Roughly |
|---|---|---|---|
| Monday | Project site, grant A | Deliverable pages, landing page | 40 URLs |
| Monday | Conference site, new year | Sitemap job, full structure | Job queued |
| Tuesday–Thursday | Conference site, new year | Programme, speakers, sessions | Up to 960 a day |
| Friday | The association's own site | Changed pages only | 20–60 URLs |
| Following week | Frozen properties | Nothing | 0 URLs |
The last row is the point. Frozen properties need no share of the budget, and an estate that stops submitting for them has more room in the weeks that matter. Sending the whole allocation to the two properties with a deadline is ordinary once the budget is understood as one pot; the indexing hub and its per-URL log then show whether submissions were acted on.
What has to survive the closing of a funding period
This is what separates a project estate from every other kind. Each grant ends in a final report carrying a claim about how many people the project's website reached, read by somebody whose job is to check claims. It needs a date range, a stated method and a figure traceable to a source — showing what a property achieved is not reporting hygiene here but a condition of the next grant.
Two constraints shape the routine, both unforgiving about timing. CSV and JSON exports run to ten thousand rows, a server-rendered PDF to two hundred and fifty. And access follows the workspace, so the moment to export is while the project is open, not in the week the report is assembled.
- Take the baseline on day one. Clicks, impressions and positions recorded before dissemination starts are what make the closing figure a comparison rather than an assertion.
- Export quarterly, not at the end. A quarterly CSV in the project's own document store means the final report can be written from files the coordinator already holds.
- Keep the method beside the number. Which property, which range, which view. A figure without those three is one a reviewer may disregard.
- Let the PDF summarise, never archive. Two hundred and fifty rows is an annex; the ten-thousand-row export is the evidence behind it.
| What you export | Format | When | Where it ends up |
|---|---|---|---|
| Baseline: clicks, impressions, positions | CSV | Before first publication | Project folder, month zero |
| Quarterly reach by country and device | CSV or JSON | Every quarter, same week | Project folder, dated |
| Branded summary for the steering group | PDF, up to 250 rows | Mid-term and final | Meeting papers |
| Full period series for the annex | CSV | Two weeks before the report | Report annex |
| Closing snapshot of the property | CSV and PDF | Before the site is frozen | Archive, with the method note |
The report builder takes a logo and colours, which matters more than it sounds: a project's visual identity is usually a funding condition, and a report in the project's livery is one fewer thing to reformat. Time series, metric cards, sparklines and country and device heatmaps are the components; the per-project reporting views let a configuration agreed once be repeated each quarter.
Freezing a site without losing the year it had
Closure is where estates lose their evidence, and it happens quietly. The grant ends, the project officer's contract ends with it, the domain renewal falls to whoever notices, and nobody can later say what the site did.
A shared project feed helps here more than any dashboard. Each project carries a chronological stream where reports, campaign activity, new placements and open tasks sit together rather than in four inboxes; tasks can be active, deferred or discarded, the feed filters to links, files or to-dos, and all of it is searchable. Where the person answering in November rarely did the work in March, that is not a convenience.
Kick-off
Register the property, attach the Google account, record the baseline, tag it to the grant and to "live" — one afternoon.
- The baseline exists or never will
- Access granted with end dates
Mid-term review
The steering group wants a figure. Produce it from the standing report configuration rather than building something new.
- Same shape as the final report
- Quarterly exports already on file
Final report
Export the full period before the closing date and write the method beside each figure.
- CSV as evidence, PDF as summary
- Traceable to a view and a range
Freeze
Move the tag to "frozen", withdraw every external grant of access, stop submitting URLs, name a domain owner.
- Withdrawals done, not intended
- One named owner for renewal
A frozen property is worth keeping. It costs nothing to leave registered, its history stays readable, and when a successor project applies for funding on the same subject, the previous action's reach figures are the strongest paragraph in the application. Deleting a project is the only irreversible step here.
Frequently asked questions
Can a partner organisation see the rest of our estate?
No. Sharing is done property by property to a single registered email address, and the recipient sees that property alone — not the other projects, not the tags, not estate-wide figures. Grants can be listed and withdrawn at any point, which is what makes the quarterly review worth doing.
What happens to a project site's data when the funding period ends?
The history stays as long as the project stays registered, and a frozen property costs nothing to keep. What you should not rely on is retrieving it years later through people who have left. Export the full period before the closing date and store it with the project's own documents.
Our conference domain changes every year. Is that a problem?
It costs you the accumulated standing of the old domain each time — a real price, and a decision for the events team rather than a search tool. In the workspace, treat each edition as its own project, tagged by year and state. The compensation is a multi-year attendance series that a rolling domain would have blurred.
Why does the project assistant sometimes answer without our figures?
Because a routing step decides per question which data blocks to load — between none and three — and a general question about method legitimately needs none. When you want an answer grounded in your data, name the property, the range and the metric. Twenty messages of context are kept, so the follow-up need not repeat them.
What a project estate actually needs from a workspace
Read back across the six properties and the pattern states itself. Register everything, the quiet and the expiring included. Attach the Google property at the start; a baseline cannot be created retrospectively. Use two tag axes and refuse the third. Treat the daily allowance as one pot and spend it where there is a deadline. Export quarterly at ten thousand rows and keep the method beside the number. Grant access narrowly, and diarise the withdrawal as you grant it.
None of that is technically demanding. What makes it hard is that every item is owed to somebody not yet in the room — an auditor, a reviewer of the next application, the colleague who inherits the estate. That is why it repays doing properly: an office that can produce a dated, sourced reach figure for an action closed two years ago is an office whose next application reads differently. Our work with institutional communications teams and the other articles in this series go further into measurement, including what Stream, the per-project feed keeps and what it does not.
If you would rather test the structure than read about it, start narrow: open the dashboard and register two properties — the permanent site, and whichever project closes soonest. A month of running that pair through one workspace will tell you more than any specification, and the one with a deadline will show you where the routine breaks.
Besoin d'Aide Avec Votre SEO ?
Notre équipe d'experts est prête à vous aider à améliorer votre classement dans les moteurs de recherche et à développer votre présence en ligne.
Consultation Gratuite