Start with the pages you agreed to build
Give each planned page a stable name or URL. Break it into separate rows when the input, owner or reviewer changes. A hero, process explanation and case study may share a page but need different sources and decisions.
Ask for a usable contribution instead of writing ‘send copy’. For a service introduction, that might mean the service name, intended reader and next step. For an image, identify the file, subject and permission that needs confirmation.
- Copy the agreed sitemap and list the sections needing client input.
- Name the content owner and reviewer for each request.
- Link the brief, draft or asset in its existing project location.
Make the status describe the review
Material can arrive without being ready for a build. Use states such as Drafting, Needs revision, Ready for review, Approved for build and Blocked. A named reviewer must explicitly approve the specific version before it is treated as approved.
If reviewers disagree or the response does not identify a version, record the question and keep the row open. A quiet inbox is not a decision. Keep sensitive material in its existing access-controlled location and check that the people who need it can open it.
A fictional matrix for Northfield Studio
Northfield Studio and everyone in this example are fictional. Its services-page hero needs the intended audience and approved wording. The process section is ready for review, but image permission needs confirmation. A case-study outcome is blocked because neither publishable evidence nor photo permission has been supplied.
At the next check-in, ask about the blocked row rather than requesting the whole package again. The original worksheet retains the fictional rows, reviewers, dates and file references as a supplementary example.
Review changes before work moves on
Filter for blocked items, decisions awaiting review and work coming due. Give each an owner and one next action. Before design starts, look again at evidence, image permissions and calls to action; a complete row does not prove that a claim is true.
When a draft changes, update its reference and review date while retaining the earlier version. An approval for one version should not silently become approval for its replacement.
Preparing the requests with Areinum
Ask Areinum Assistant to help organize the page requests and prepare unresolved questions from material you provide. Check the proposed list against the actual sources and let the named reviewer decide. The matrix also works in your existing spreadsheet.
See the example
Page-by-Page Website Content Matrix
All names, pages, and entries in the matrix are fictional examples.
| Page URL | Section | Requested input | Copy or source link | Image or asset link | Client reviewer | Status | Open question or next action | Content owner | Version and review date |
|---|---|---|---|---|---|---|---|---|---|
| /services/ | Hero introduction | Paragraph naming the service, intended reader, and next step | Northfield Studio brief v2, fictional | Hero image folder, fictional | Morgan Lee, fictional | Needs revision | Confirm the intended audience and supply approved wording | Casey, fictional client writer | Brief v2; review due 2026-10-20 |
| /services/ | Process section | Three steps the client can verify | Process draft v1, fictional | Process illustration brief, fictional | Morgan Lee, fictional | Ready for review | Confirm step two wording and image permission | Casey, fictional client writer | Process draft v1; review due 2026-10-21 |
| /case-study/river | Outcome section | Client-approved result with a supporting source | No approved text supplied | Photo permission pending | Morgan Lee, fictional | Blocked | Confirm publishable evidence and permission before drafting | Dana, fictional case-study owner | No approved version; source review due 2026-10-22 |
- Create one row for each page section that needs a separate answer, asset, or approval.
- Replace the fictional Northfield Studio entries with the real page URL, content owner, reviewer, version and review date. Link the source in your existing project folder.
- Use Needs revision when material exists but cannot move forward, and Blocked when an answer, permission, or source is missing.
- Use Ready for review only when the named reviewer can inspect a specific version. Change it to Approved for build only after that reviewer gives an explicit decision.
- At each check-in, filter by status and next action, then update the source link and date. Keep the original message or file in its current location.
Limits of this method
- The selected evidence is adjacent to website content collection and does not show how often website clients miss page-level inputs.
- A shared-drive feature description does not prove that the client's account, permissions, or organization policy supports a proposed handoff.
- A complete matrix cannot verify the truth of a claim, image rights, or client approval by itself. The responsible reviewer must check each item.
Questions you may have
How detailed should the matrix be?
Use a separate row whenever a section has a different source, owner or reviewer. Combine items when one person can review them together.
Does receiving an image mean we can publish it?
No. Check permission for the proposed use. If the source or permission is missing, leave the row open.
What if a client approves one draft and then sends changes?
Record the approved version, link the revision separately and ask the reviewer to decide on that version.
Sources and further reading
- Getting info from clients
A self-described tax-practice owner reports missing items despite a checklist. The website matrix adapts the question of missing inputs to a different kind of project.
This is one person's account about a tax practice, not evidence of how often website content is missing.
A self-reported tax-practice owner describes clients saying a checklist is complete while requested items remain missing. This is adjacent process context only.
One anonymous Reddit account describes a tax-document workflow, not website production. Identity, representativeness, and the frequency of this problem are unverified.
2026-10-18 - What are shared drives?
Google describes shared-drive storage and sharing controls. The matrix points to materials in the location your team uses.
Availability and sharing depend on the organization's settings; the page does not establish a particular client's access or validate the matrix.
Google documents shared-drive storage, team ownership, search, access, and sharing with external people when the organization allows it.
Vendor documentation describes Drive mechanisms. It does not establish that a page-by-page content matrix is needed or that a particular client can access a shared drive.
2026-10-18
The demo is in English. Access may need to be arranged.
Explore the demo