Two hours a day can support consistent practice or a small service, but available time is not the same as production time. Messages, file setup, quality checks and revisions consume part of each session. Plan the week around one output, then reserve those supporting hours before accepting a deadline.
A 12-hour practice week
| Day | First hour | Second hour |
|---|---|---|
| Monday | Read the brief and mark unknowns | Complete the first part |
| Tuesday | Complete remaining work | Check against the brief |
| Wednesday | Revise | Prepare the editable output |
| Thursday | Build the sample page | Test links and phone layout |
| Friday | Research one suitable brief | Draft a tailored response |
| Saturday | Review time and costs | Buffer for unfinished work |
Sunday is unallocated. This is a planning example, not twelve billable hours or an earnings forecast. Download the weekly capacity sheet, enter your actual hours and compare the plan with what happened.
Work backward from the deadline
Suppose four evenings remain before delivery. Four sessions of two hours give eight hours. Reserve one hour for questions and messages and two hours for checking and revisions. Five hours remain for production. If a comparable task took seven, the promised scope does not fit.
You can reduce the scope, agree a later delivery, or decline. A higher price does not create the missing two hours. Nor should the same buffer be counted as free time for a second order.
| Capacity calculation | Example hours |
|---|---|
| Time available before delivery | 8 |
| Communication and setup | -1 |
| Checks and included revision | -2 |
| Production capacity | 5 |
| Production estimate | 7 |
| Gap to resolve | 2 |
Change the plan when paid work arrives
A beginner week emphasises learning and proof. A delivery week must make room for the agreed project. For ten available hours, an illustrative allocation is six for production, two for checking and communication, and two for maintaining a small lead list. If a revision needs another hour, move something else explicitly.
Do not keep a full learning schedule and layer a full delivery schedule on top of it. Record the trade-off so you can see what was postponed and why.
Make interruptions manageable
Keep an offline task ready, such as reviewing a brief or editing text, and save work at the end of each session. Write the next action before stopping. Where connectivity or power interruptions are common, leave a realistic delivery buffer and a permitted way to notify the client early.
Do not move confidential files to an unapproved public service during an outage. A backup route must preserve the project's permissions, not merely make a transfer possible.
Review the right measures
After several weeks, compare planned and actual minutes by task, completed samples, suitable applications, replies and delivered work. If setup repeatedly consumes half a session, prepare files in advance. If revisions exceed the allowance, improve the brief and scope.
More hours are not automatically the answer. First identify whether time is being lost to an unclear task, a skill gap, interruptions or an unrealistic promise. Use the scope guide before agreeing another fixed deadline.
Practice work and illustrative amounts are labelled in the article. See how we prepare and correct guides and how the resource checks work. Report a specific error or broken step.