Enter project data once,

When a project is created, a certain amount of foundational information gets defined right away: the client, the start date, the due date, the location, identifiers specific to the engagement, or the contract. That information belongs to the project, but it’s also relevant to many of the individual tasks within it. Before Version 4, there was no direct connection between the two. The project had its data, and the tasks had theirs, and if a task needed to reflect something from the project level, someone had to enter it again manually. On a project with dozens of tasks, that’s a lot of repeated entry, and every repeated entry is an opportunity for the information to be slightly different from what’s in the project record.

Version 4 of Feng Office closes that gap with variable data in project templates.

When you build a project template in Feng Office, you can now define variables inside that template that reference project-level fields. These variables act as placeholders. When the template is launched, and a project is created, the system fills those placeholders automatically with the actual values from the project record.

Set the client name once at the project level, and every task in the template that references the client variable receives that value on creation. Set the project start date or due date, and tasks that depend on those dates are populated accordingly. Set a location code or a client-specific identifier, and it flows through to the tasks that need it, without anyone entering it a second time.

The most immediate effect is time. Information that previously had to be typed into the project and then typed again into individual tasks now only needs to be entered once. For project managers setting up a new project from a template, that’s a meaningful reduction in setup time, particularly on projects with a large number of tasks or complex task structures.

When the same information is entered in multiple places manually, inconsistencies creep in. A date formatted differently in one task, a client name abbreviated in another, a location code that doesn’t quite match the one in the project record. These small mismatches create confusion during execution and errors in reporting. When the data flows from one source into all the tasks that need it, the information is the same everywhere because it comes from the same place.

Dates are a particular area where manual entry causes problems. If a project start date changes and tasks have to be updated individually to reflect it, some will get updated, and some won’t. With variable data, the task receives the date from the project record when the template runs, which means the task structure is built on accurate timing from the start rather than on whatever someone typed at the time.

Variable data works alongside the other template improvements in Version 4. A template can carry conditional workflows that determine which tasks are created based on project properties, budgeted expenses already linked to the right tasks, and now variable data that populates those tasks with project-level information on creation. Together, these features mean that when a template is launched, the resulting project isn’t just a skeleton that needs to be filled in. It arrives with its structure, its financial picture, and its key data already in place.

For project-based firms that run similar project types repeatedly, that full definition at the point of creation is a significant change in how much setup work remains after the template runs.

A firm creates a new project record, enters the client, the location, the start and due dates, and any identifiers specific to that engagement. They launch the project template. The tasks are created, the expenses are linked, and the variable fields inside each task are already populated with the client name, the location, and the relevant dates pulled directly from the project record. The team can start working from a complete, accurate task list without a setup phase in between.

Variable data in project templates means information entered at the project level flows automatically into the tasks created from that template. Client, dates, location, identifiers, and anything defined as a variable in the template are populated on creation from the project record. You enter it once, and the system puts it where it needs to be, consistently, across every task in the project.

Book a private tour

See variable data flow from a project record into tasks in real time

The setup time saved by variable data is something you feel immediately when you see it working. You tell us what information your team currently re-enters across tasks when setting up a new project, and we’ll show you how templates handle that automatically in Version 4.

• Watch project-level data populate into tasks automatically the moment a template is launched
• Walk through how variables are defined in the template and which field types they can reference
• Ask anything about how variable data works alongside conditional workflows and linked expenses
• Get a clear picture of how much manual setup this removes from your project creation process before you commit to anything