Kostenlose Projektvorlagen

Ship your next product on a plan that already exists. This launch template lays out the full arc, customer discovery, MVP build, closed beta, and GA day, as 12 scheduled tasks with priorities, effort estimates, and two launch milestones. Open it in Onplana and you start from a working plan instead of a blank board.

Plan, produce, launch, and measure an integrated campaign without reinventing the checklist. This campaign template covers the whole cycle, goals and channel mix, creative production, paid and owned launch, and the post-campaign retrospective, as 10 scheduled tasks across four phases with a go-live milestone at day 28.

Run your event on a 90-day countdown instead of a sticky-note wall. This event planning template sequences everything from venue tours and speaker outreach to badge printing, volunteer briefings, and the day-of run sheet, 14 scheduled tasks across five phases, each timed backwards from event day.

Move your Microsoft Project schedules with a plan, not a prayer. This template sequences a 30-day move of your .mpp and Project XML files into Onplana: inventory and stakeholder sign-off, collecting and cleaning the files, staging import, reconciliation and pilot UAT, then the production import. It ships with a pre-logged risk about legacy custom-field mapping, so the most common surprise is already on your radar.

A migration project plan for SharePoint, Microsoft 365, file server and Azure moves, as an Excel file or a live project. Migrations do not fail at the copy, they fail at the edges: permissions that did not come across, a wave sized from a lab measurement, and the delta nobody ran. This plan sequences a 60-day move as waves rather than a weekend, with a pilot signed off before wave one, a delta sync behind every wave, and two pre-logged risks that account for most of the overruns.

Run a complete OKR cycle, not just a kickoff meeting. This quarterly OKR template schedules the whole 90 days: drafting company objectives, workshopping key results, cascading to teams, weekly check-ins, a mid-quarter review, and end-of-quarter scoring. Eight tasks across four phases keep the cadence honest from week 1 to week 13.

A consulting engagement that starts without agreed acceptance criteria ends in an argument about the final invoice. This template schedules the whole nine weeks: signed scope and rate card first, discovery that tests what the statement of work assumed, delivery with change requests priced as they arise, and a close that ends in written acceptance and a margin review.

Phase-gate development works when the gates are real decisions and fails when they are status meetings. This template schedules six months from concept to market with four explicit gate reviews, each one a go, no-go, or recycle with the reviewers and conditions recorded, plus the design freeze that turns every later change into formal change control.

Architecture practices lose fees between stages, not inside them: the concept change reworked into Stage 3 without a variation, the construction-stage hours that outrun the Stage 5 share. This template lays the RIBA Plan of Work 2020 out as eight phases, with a client sign-off closing each of Stages 1 to 4, so the fee schedule, the programme and the hours are one record from Stage 0 to handover.

The AIA phases already come with a fee split most owners recognise: 15 percent schematic design, 20 design development, 40 construction documents, 5 bidding, 20 construction administration. What practices lose is the link between that split and the hours, when a design-development change is drawn into the construction documents without an additional-services request. This template lays the five phases out, with an owner approval closing each of the three design phases, so the approval, the fee share and the hours are one record.

Closeout is where a building project drifts for months: the punch list that never quite closes, the manuals nobody delivered, the retainage released too early. This template plans it from the day the construction documents are issued, with a closeout list agreed at preconstruction, submittals and RFIs through construction administration, a punch list backed to zero, and every manual, warranty, record drawing and lien waiver in hand before final payment.

Next year's portfolio as one plan you can argue about before it is funded. Eight sample initiatives, each with a case for it, the delivery and a check on whether it paid off, sit as phases on one timeline, with the plan approval and four portfolio reviews as milestones. Opened in Onplana, it also brings a capacity sheet by role and quarter and a one-page scoring guide, so the debate about what fits runs on numbers.

A general project schedule for a 12-week project, laid out the way a schedule is built: charter and kickoff, a work breakdown with a duration on every task, a baseline, three work packages, the weekly control loop running alongside them, and a proper close. Rename the work packages and it fits most projects that are not yet sure what shape they are.

A six-month project on one page: a month to discover, two to design and build, one to test, one to launch and one to measure what it achieved. Fewer, longer tasks than a working schedule, and a milestone at the end of each stretch, so it reads at a glance in a steering meeting.

A building project from the general contractor's side, start to handover: estimate, permits and buyout in preconstruction, then site work and foundations, the frame, the envelope, MEP rough-in and interiors, and closeout to the certificate of occupancy. About 36 weeks for a small commercial building, with the inspections and the dry-in date where they really fall.

A nine-week agile project: a short sprint 0 to write the vision, build the first backlog and agree the definition of done, three two-week sprints with planning, delivery and a review and retrospective, then a release sprint to harden, ship and refine the backlog for what comes next.

A plain project tracker: set up, plan, do, review and close, 15 tasks in all, and three columns on every row for the questions a tracker answers each week: what state is it in, who has it, and how far along is it. Every row starts at Not started, no owner and 0 percent, ready for your names.

A plan built around its milestones: seven of them, from the approved brief to the closed project, and before each one a sign-off task that says what proves it was met. Fill in the work between them and the milestones stay the dates everyone outside the team watches.