The task and original case
Plan reuse of six original assets across two formats without counting twelve scheduled items as twelve new pieces of reporting. The portfolio artifact is a calendar with source ownership, review and actual-publication states. A scheduled date is a plan, not evidence that anything went live.
| Case element | Value or requirement |
|---|---|
| Inputs | Six original assets are each scheduled for two formats, producing 12 scheduled publications. |
| Build | An editorial calendar with source owner, approval and publication fields. |
This is an original invented exercise. It is independent practice, with no employer assessment or open-vacancy claim. Download the inputs, attempt your own result, then open the separate answer key.
Data and worked inputs
Build a result another person can follow
Create an asset register for A1 through A6, each with an original owner and a source/version reference. Create a separate publication table containing an asset ID, format, planned date, approval status, actual date and public destination. Each asset has a guide and worksheet row, producing twelve planned entries.
Keep the register and calendar linked by asset ID. GitHub's README guidance describes useful repository documentation; use a README to explain the two tables and their states. Define what evidence changes a row from drafted to approved, scheduled and published. In this invented fixture, all twelve are scheduled and actual publications are zero.
Sources[1]
Check the worked result
The register contains six original assets. The calendar contains twelve scheduled format items. Neither count establishes twelve distinct new reporting projects, and the actual publication count remains zero until a real dated destination is verified.
A summary can therefore show originals 6, scheduled items 12 and verified publications 0. This separation helps a reviewer distinguish editorial production, reuse and distribution without devaluing the usefulness of a worksheet adapted from a guide.
Make the failure visible
Duplicate one calendar row and check a uniqueness key such as asset ID plus format plus planned version. Cancel a worksheet and keep the cancellation state rather than deleting its history. If an asset's facts change, mark dependent formats for review; a link to an old source version should not look like a fresh approval.
Revise it and ask someone to reproduce it
Ask a peer to update one fictional guide row to a simulated published state using an explicitly labelled example destination. Verify that the model count changes by one while originals remain six. For your own real project, require actual live evidence and record the observation date before using the word published.
- Six source assets remain distinct from twelve format entries.
- Approval, scheduling and publication are separate fields.
- Reuse preserves source/version ownership and prompts dependent review.
Describe the work accurately
After completing your own version, you could adapt this project bullet: “Created an independent editorial-reuse calendar separating original assets, format schedules, review dependencies and verified-publication states.”
Use Projects or Independent practice as the heading. Keep the input files, result and revision together. Describe only your own completed work; the invented numbers are model outputs, not employer results or measured business impact.