Weekly Project Format Guide
ESTECH Hub. CI Africa Ltd
ESTECH Academy
The 4-Page Weekly Project Format
Every weekly project across all departments is submitted as a clean, standard 4-page report — simple to write, yet structured to the level any academic body would recognise as excellent. Follow the four pages below.
How Weekly Projects Work
Each week your instructor publishes a Weekly Project Task for your department. It contains:
Task Title
The project you must build this week.
Instructions
Exactly what the project must do.
Submission Type
PDF report, Video demo, or both.
Grading Rubric
What the reviewer looks for.
Max Score
Out of 100 points.
Your job is to build the project, then write it up using the same 4-page format below — no matter your department. The four pages are short by design: the goal is a crisp, professional "plan sheet", not a long essay.
Page 1
Cover Sheet
A single branded cover page. Use the layout below as your template.
ESTECH Hub. CI Africa Ltd
ESTECH Academy
Weekly Project Report
Project Title
[The Week's Project Title — from your task]
Student: [Full Name]
Student ID: ESTECH-STU-YYYY-XXXXX
Department: [Department]
Cohort: [e.g. Jan – Mar 2026]
Week: Week X
Date: DD MMMM YYYY
Page 2
Project Overview
One page explaining what you are building and why.
Restate the week's task in your own words — the problem it solves.
3–4 specific things your project must achieve (bullet list).
Languages, frameworks, and the plan you followed.
What is included and what you deliberately left out.
Page 3
Build & Results
One page showing how you built it and the result.
Numbered list of the key steps you took.
A labelled screenshot / diagram / figure (Figure 1) of the working result.
Only the most important code/logic snippet — well commented.
A small table: input → expected → actual → pass/fail, plus a one-line result.
Tip: keep figures and code small — this entire page should fit on one sheet.
Page 4
Reflection & References
One page closing the report honestly and credibly.
2–3 real obstacles you faced and how you solved each.
The key skill or concept this week taught you.
Did you meet the objectives? One short paragraph.
Only the sources you actually used, in APA or IEEE style.
Repository, live demo, or deployed URL (if any).
Video Submission (when required)
When the task asks for a video, it complements — not replaces — the 4-page report.
Length
3–8 minutes, tightly edited.
Quality
1080p, clear audio, good lighting.
Structure
Intro (name/dept/week) → problem → demo → walkthrough → conclusion.
Format
MP4 / WebM, screen-record or camera.
Formatting Standards
| Element | Standard |
|---|---|
| Length | Exactly 4 pages (no more) |
| Paper size | A4 |
| Margins | 2.54 cm (1 inch) all sides |
| Body font | Times New Roman or Calibri, 12pt |
| Headings | 14pt bold, numbered (2.1, 2.2…) |
| Line spacing | 1.5 lines, justified |
| Figures | Numbered + captioned (Figure 1, Table 1) |
| Citation style | APA or IEEE |
| File format | PDF only |
| File name | ESTECH_<Dept>_Wk<#>_<FullName>.pdf |
Pre-Submission Checklist
How this maps to your grade
Reviewers score you against the week's rubric out of 100. A clean, complete 4-page report — covering brief, objectives, build, results, and reflection — directly satisfies the structure, clarity, and presentation criteria that separate an A from a pass.